IBM webMethods Hybrid Integration

IBM webMethods Hybrid Integration

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
Expand all | Collapse all

Error enabling process model on my webMethods wm6.5

webMethods Community Member

webMethods Community MemberThu March 29, 2007 02:57 PM

  • 1.  Error enabling process model on my webMethods wm6.5

    Posted Fri January 20, 2006 03:54 AM

    Im having a problem in enabling process model on my webMethods portal server.
    I had doubled checked the monitor.cnf in ==> IntegrationServer/packages/WmMonitor/config.
    It is pointing to the right port 8080(default port), which im using for mywebmethods, not changed to a new port.

    When i click the enable checkbox, it just refresh and doesn’t enables the model.
    I had even referred to [SR-1-63257409], im not getting model enabled.

    Do anyone have encountered and solved this issue.
    I need to enable my models. Please share your views on this.

    Thanks, Madan


    #BPM
    #webMethods
    #webMethods-BPMS


  • 2.  RE: Error enabling process model on my webMethods wm6.5

    Posted Fri January 20, 2006 03:59 AM

    If you are seeing the following error in the IS server log:

    …Must be a PBEKey in RAW format…

    then this is known issue and there is a fix due out next week for this:

    Monitor_6-5-1_SP1_Fix1

    If not, then please specify what messages are showing up in the IS server log and/or MY webMethods logs (in /Portal/servers/default/logs)

    Hope this helps,

    Jonathan Heywood
    webMethods Professional Services


    #webMethods-BPMS
    #webMethods
    #BPM


  • 3.  RE: Error enabling process model on my webMethods wm6.5

    Posted Fri January 20, 2006 04:46 AM

    Thanks for your reply.
    Im attaching the error displaying in server & mywebmethods log.

    IS Log

    [4977]2006-01-20 16:29:33 SGT [MOD.0120.0000D] ******** filter: [INCLUDEALL]
    [4976]2006-01-20 16:29:33 SGT [MOD.0120.0000D] ******** DLS perm list length: 1
    [4975]2006-01-20 16:29:33 SGT [MOD.0120.0000D] ******** DLS: ((()) OR (()) OR (()) OR (()))
    [4974]
    [4973] at java.lang.Thread.run(Thread.java:534)
    [4972] at com.wm.util.pool.PooledThread.run(PooledThread.java:105)
    [4971] at com.wm.app.b2b.server.Dispatch.run(Dispatch.java:298)
    [4970] at com.wm.app.b2b.server.HTTPSOAPHandler.process(HTTPSOAPHandler.java:111)
    [4969] at com.wm.app.b2b.server.HTTPSOAPHandler._process(HTTPSOAPHandler.java:457)
    [4968] at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:128)
    [4967] at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:246)
    [4966] at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:369)
    [4965] at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:521)
    [4964] at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:407)
    [4963] at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:39)
    [4962] at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:194)
    [4961] at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:49)
    [4960] at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:226)
    [4959] at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:44)
    [4958] at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:612)
    [4957] at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:322)
    [4956] at java.lang.reflect.Method.invoke(Method.java:324)
    [4955] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [4954] at sun.reflect.GeneratedMethodAccessor40.invoke(Unknown Source)
    [4953] at wm.server.soap.rpc(soap.java:411)
    [4952] at com.wm.app.b2b.server.Service.doInvoke(Service.java:584)
    [4951] at com.wm.app.b2b.server.Service.doInvoke(Service.java:635)
    [4950] at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:113)
    [4949] at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:246)
    [4948] at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:369)
    [4947] at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:521)
    [4946] at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:407)

    myWebmethods Log

    2006-01-20 16:29:32 SGT (Framework : INFO) [RID:81] - Processing request [2c60kud261a2k:Administrator] http://sinctdbdicd1.sg.db.com:8080/meta/default/wm_xt_fabricfolder/0000003869 (GET) {wmp4920.pca_m = setProcessModelExecutionEnable; wmp4920.wmp_pm = view; wmp4919.refiningSearch = false; wmp4920.processModelIndex = 2; wmp4920.wmp_ws = normal; wmp4920.pingDBFlag = false; wmp4920.configlist_errormsg = Ready to Search; wmp4919.pca_p = simpleSearch; wmp4920 = /meta/default/wm_bam_process_config/0000004920; wmp4920.pca_p = businessProcessConfiguration; wmp4919.lastSearchState = keywords=,maxResults=200; wmp4919.pca_l = simpleSearch}
    2006-01-20 16:29:33 SGT (Framework : INFO) [RID:82] - Processing request [2c60kud261a2k:Administrator] http://sinctdbdicd1.sg.db.com:8080/meta/default/wm_xt_fabricfolder/0000003869 (GET) {wmp4920.wmp_pm = view; wmp4919.refiningSearch = false; wmp4920.wmp_ws = normal; wmp4920.processModelIndex = 2; wmp4920.modelsList_searchCrit = keywords=,maxResults=200; wmp4920.pingDBFlag = false; wmp4920.configlist_errormsg = ; wmp4919.pca_p = simpleSearch; wmp4920.pca_l = businessProcessConfiguration; wmp4920.pca_p = businessProcessConfiguration; wmp4919.lastSearchState = keywords=,maxResults=200; wmp4919.pca_l = simpleSearch}
    2006-01-20 16:29:34 SGT (wsclient : FATAL) [RID:82] - com.webMethods.caf.wsclient.proxy.impl.WSClientDynamicProxy: Failed to bind to endPoint: http://:/services/monitor.wsdl and interface: interface com.webMethods.bpo.service.IBaseWebService: could not bind to path: http://:/services/monitor.wsdl
    com.webMethods.caf.wsclient.WSClientException: Failed to bind to endPoint: http://:/services/monitor.wsdl and interface: interface com.webMethods.bpo.service.IBaseWebService: could not bind to path: http://:/services/monitor.wsdl
    at com.webMethods.caf.wsclient.proxy.impl.WSClientDynamicProxy.getBinding(WSClientDynamicProxy.java:232)
    at com.webMethods.caf.wsclient.proxy.impl.WSClientDynamicProxy.invokeMethod(WSClientDynamicProxy.java:83)
    at com.webMethods.caf.wsclient.proxy.impl.WSClientDynamicProxy.invoke(WSClientDynamicProxy.java:126)
    at $Proxy0.pingService(Unknown Source)
    at com.webMethods.bpo.portlet.wm_bam_ws_config.Bam_ws_config.pingOptimize(Bam_ws_config.java:143)
    at ui.portlets.wm_bam_ws_config._default._jspService(_default.java:5099)
    at com.webMethods.portal.framework.presentation.handlers.Jsp.render(Jsp.java:288)
    at com.webMethods.portal.framework.presentation.handlers.Jsp.render(Jsp.java:228)
    at com.webMethods.portal.framework.portlet.beans.JspPortletBean.generateContent(JspPortletBean.java:120)
    at com.webMethods.portal.framework.portlet.beans.JspPortletBean.getContentInternal(JspPortletBean.java:70)
    at com.webMethods.portal.framework.portlet.beans.BasicPortletBean.getContent(BasicPortletBean.java:133)
    at com.webMethods.portal.mech.portlet.impl.PortletMechanics.getPortletContent(PortletMechanics.java:91)
    at com.webMethods.portal.mech.storage.page.PortletHelper.initializeRuntimeProperties(PortletHelper.java:243)
    at com.webMethods.portal.mech.storage.page.PortletHelper.initializeRuntimeProperties(PortletHelper.java:253)
    at com.webMethods.portal.mech.storage.page.PortletHelper.getFullyInitializedBean(PortletHelper.java:309)
    at com.webMethods.portal.mech.portlet.impl.PortletMechanics.resolveWiring(PortletMechanics.java:563)
    at com.webMethods.portal.mech.storage.page.PortletHelper.initializeWiredProperties(PortletHelper.java:221)
    at com.webMethods.portal.mech.storage.page.PortletHelper.getInitializedBean(PortletHelper.java:285)
    at com.webMethods.portal.mech.storage.page.PortletHelper.getInitializedBean(PortletHelper.java:270)
    at com.webMethods.portal.framework.presentation.renderers.FolderRenderer.getRows(FolderRenderer.java:108)
    at com.webMethods.portal.framework.presentation.renderers.FolderRenderer.renderContent(FolderRenderer.java:88)
    at com.webMethods.portal.framework.presentation.renderers.FolderRenderer.renderPageContent(FolderRenderer.java:68)
    at com.webMethods.portal.framework.presentation.renderers.DefaultRenderer.render(DefaultRenderer.java:188)
    at com.webMethods.portal.framework.presentation.PresentationManager.handlePres(PresentationManager.java:354)
    at com.webMethods.portal.framework.dispatch.DispatchManager.pres(DispatchManager.java:584)
    at com.webMethods.portal.framework.dispatch.DispatchManager.handle(DispatchManager.java:424)
    at com.webMethods.portal.framework.dispatch.DispatchManager.handleDispatch(DispatchManager.java:338)
    at com.webMethods.portal.framework.impl.PortalServlet.service(PortalServlet.java:176)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:356)
    at org.mortbay.jetty.servlet.WebApplicationHandler$Chain.doFilter(WebApplicationHandler.java:342)
    at com.webMethods.portal.framework.impl.NTLMFilter.doFilter(NTLMFilter.java:50)
    at org.mortbay.jetty.servlet.WebApplicationHandler$Chain.doFilter(WebApplicationHandler.java:334)
    at com.webMethods.portal.framework.impl.CompressionFilter.doFilter(CompressionFilter.java:44)
    at org.mortbay.jetty.servlet.WebApplicationHandler$Chain.doFilter(WebApplicationHandler.java:334)
    at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:286)
    at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:567)
    at org.mortbay.http.HttpContext.handle(HttpContext.java:1723)
    at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:514)
    at org.mortbay.http.HttpContext.handle(HttpContext.java:1673)
    at org.mortbay.http.HttpServer.service(HttpServer.java:879)
    at org.mortbay.http.HttpConnection.service(HttpConnection.java:783)
    at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:945)
    at org.mortbay.http.HttpConnection.handle(HttpConnection.java:800)
    at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:201)
    at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:289)
    at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:454)
    Caused by: electric.registry.RegistryException: could not bind to path: http://:/services/monitor.wsdl
    at electric.registry.local.LocalRegistry.bind(Unknown Source)
    at electric.registry.compound.CompoundRegistry.bind(Unknown Source)
    at electric.registry.Registry.getReference(Unknown Source)
    at electric.registry.Registry.getProxy(Unknown Source)
    at electric.registry.Registry.bind(Unknown Source)
    at electric.registry.Registry.bind(Unknown Source)
    at com.webMethods.caf.wsclient.proxy.impl.WSClientDynamicProxy.getBinding(WSClientDynamicProxy.java:230)
    … 46 more
    Caused by: java.net.MalformedURLException: Malformed URL http://:/services/monitor
    at electric.util.XURL.(Unknown Source)
    at electric.registry.local.LocalRegistry.bindUsingEndpoint(Unknown Source)
    … 53 more


    #webMethods-BPMS
    #BPM
    #webMethods


  • 4.  RE: Error enabling process model on my webMethods wm6.5

    Posted Fri January 20, 2006 05:35 AM

    Adding up to the list, i also have this message

    "BAM Server: : is not reachable. Some data may not be available. "

    in mywebmethods - webmethodsconfiguration-processconfiguration-businessprocessconfiguration.
    does it relate to not enabling the models.


    #webMethods-BPMS
    #BPM
    #webMethods


  • 5.  RE: Error enabling process model on my webMethods wm6.5

    Posted Fri January 20, 2006 05:45 AM

    The message "BAM Server: : is not reachable. Some data may not be available. " is normal if you are not using BAM and is not related to enabling process models.

    The message reported by Madan seems to indicate some missing configuration. The messages "Failed to bind to endPoint: http://:/services/monitor.wsdl " imply that a host and port are not configured somewhere.

    Have you specified the IS host and port in the My webMethods system config screen?


    #webMethods
    #BPM
    #webMethods-BPMS


  • 6.  RE: Error enabling process model on my webMethods wm6.5

    Posted Fri January 20, 2006 05:56 AM

    Yes Jonathan, i had provided my IS host & Port in System Configuration.
    Should i need to provide details under System Configuration → System Information - Controller, DataHandler, My webMethods Server.


    #webMethods-BPMS
    #webMethods
    #BPM


  • 7.  RE: Error enabling process model on my webMethods wm6.5

    Posted Fri January 20, 2006 06:27 AM

    Madan,

    No, no need to specify Controller and DataHandler. They are only relevant for BAM and Manager, not for regular BPM.

    You might need to specify My webMethods Server. Check the webMethods Configuration → My webMethods Configuration → URL Setup.

    Otherwise, I suggest you raise an SR with Support. They should be able to track this down pretty quickly.

    Jonathan


    #webMethods-BPMS
    #webMethods
    #BPM


  • 8.  RE: Error enabling process model on my webMethods wm6.5

    Posted Fri January 20, 2006 06:43 AM

    Thanks Jonathan for your suggestions. I had given the url in “URL setup” too.
    I will raise the SR for this issue.
    Thanks, madan


    #webMethods-BPMS
    #webMethods
    #BPM


  • 9.  RE: Error enabling process model on my webMethods wm6.5

    Posted Tue March 28, 2006 02:12 PM

    Madan,
    Any resolution on this issue…I am also getting the same error saying "Remote Exception caught: com.webMethods.caf.wsclient.WSClientException: Failed to bind to endPoint: http://P3038867:5555/services/rule.wsdl and interface: interface com.webMethods.bpo.service.rules.IRuleService: could not bind to path: http://P3038867:5555/services/rule.wsdl "

      I appreciate any help.
    

    Thanks,
    Ramesh


    #webMethods
    #webMethods-BPMS
    #BPM


  • 10.  RE: Error enabling process model on my webMethods wm6.5

    Posted Sat April 15, 2006 03:32 PM

    Hi Madan,

    Any update on My webMethods throwing exception java.net.MalformedURLException: Malformed URL http://:/services/monitor when trying to connect to webMethods monitor ?

    Any help appreciated.

    Thank you
    Ranjith


    #BPM
    #webMethods-BPMS
    #webMethods


  • 11.  RE: Error enabling process model on my webMethods wm6.5

    Posted Tue May 02, 2006 03:23 PM

    Same here, any news

    2006-05-02 14:06:10 CDT (wsclient : FATAL) [RID:11] - com.webMethods.caf.wsclient.proxy.impl.WSClientDynamicProxy: Failed to bind to endPoint: http://:/services/monitor.wsdl and interface: interface com.webMethods.bpo.service.IBaseWebService: could not bind to path: http://:/services/monitor.wsdl
    com.webMethods.caf.wsclient.WSClientException: Failed to bind to endPoint: http://:/services/monitor.wsdl and interface: interface com.webMethods.bpo.service.IBaseWebService: could not bind to path: http://:/services/monitor.wsdl


    #BPM
    #webMethods-BPMS
    #webMethods


  • 12.  RE: Error enabling process model on my webMethods wm6.5

    Posted Thu July 13, 2006 07:39 AM

    Hi,

    I am getting an error like this:

    98]2006-07-13 13:21:29 CEST [MON.0119.0000D] ******** filter: [INCLUDEALL]
    [97]2006-07-13 13:21:29 CEST [MON.0119.0000D] ******** DLS perm list length: 1
    [96]2006-07-13 13:21:29 CEST [MON.0119.0000D] getting model DLS list…
    [95]2006-07-13 13:21:29 CEST [MON.0119.0000D] ******** DLS: ((()) OR (()) OR (()) OR (()))
    [94]2006-07-13 13:21:26 CEST [MON.0119.1500E] Incomplete portal url strings, check portalTransport, portalHost, portalPort in monitor.cnf.

    I am not able to see

    Configuration → My webMethods Configuration → URL Setup

    Have someone came across the same problem ???

    With Regards,
    Navanee


    #BPM
    #webMethods-BPMS
    #webMethods


  • 13.  RE: Error enabling process model on my webMethods wm6.5

    Posted Thu March 29, 2007 02:57 PM

    Any clue as to how this can be fixed?


    #webMethods-BPMS
    #webMethods
    #BPM


  • 14.  RE: Error enabling process model on my webMethods wm6.5

    Posted Tue September 18, 2007 09:16 AM

    We’ve come across this problem a couple of times already and everytime we struggle to fix it using some magic. Here is one spell which seems to work some times:

    The problem:

    Trying to enable a process model in MWS fails. Basically if you click “refresh


    #BPM
    #webMethods-BPMS
    #webMethods