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

Issues in Deploying Environment using MWS

  • 1.  Issues in Deploying Environment using MWS

    Posted Sun July 03, 2011 10:49 AM

    Hi All,

    I am getting the below error while deploying Environment in MWS.

    Error deploying logical server type “Data Collection Services v7.1.2.0 (1)” version “7.1.2.0” to host “localhost”
    Deployment Error: could not bind to path: [url]http://tech.forums.softwareag.com:15001/services/IRemoteConfiguration.wsdl[/url]
    One or more of the following configurations could not be deployed

    System Identity
    System Endpoint Registry
    Configuration type “Journal Logging” version “7.0.0.0”
    Configuration type “JNDI Configuration” version “7.0.0.0”
    Configuration type “DataCollector Settings” version “7.0.0.0”

    Error deploying logical server type “Analytic Engine v7.1.2.0 (1)” version “7.1.2.0” to host “localhost”
    Deployment Error: could not bind to path: [url]http://tech.forums.softwareag.com:15000/services/IRemoteConfiguration.wsdl[/url]
    One or more of the following configurations could not be deployed

    System Identity
    System Endpoint Registry
    Membership management
    JDBC alias configuration type “Analytic Repository” version “7.0.0.0”
    JDBC alias configuration type “Process Work Repository” version “7.0.0.0”
    JDBC alias configuration type “Process History Repository” version “7.0.0.0”
    JDBC alias configuration type “Process Model Repository” version “7.0.0.0”
    JDBC alias configuration type “Common Directory Repository” version “7.1.0.0”
    JDBC pool configuration “CentralConfigPool”
    Configuration type “Cache Configuration” version “7.1.0.0”
    Configuration type “Coherence Cache Configuration” version “7.0.0.0”
    Configuration type “Tangosol Coherence Configuration” version “7.1.0.0”
    Configuration type “Lock Configuration” version “7.0.0.0”
    Configuration type “Journal Logging” version “7.0.0.0”
    Configuration type “JNDI Configuration” version “7.0.0.0”
    Configuration type “Amoeba Behavior Settings” version “7.0.0.0”
    Configuration type “Analysis Engine Settings” version “7.0.0.0”
    Configuration type “Database Settings” version “7.1.0.0”
    Configuration type “Data Maintenance Settings” version “7.1.0.0”
    Configuration type “Mail Settings” version “7.0.0.0”
    Configuration type “Monitor Behavior Settings” version “7.1.0.0”
    Configuration type “Process Tracker Test Settings” version “7.0.0.0”
    Configuration type “Process Tracker Settings” version “7.0.0.2”
    Configuration type “Station Settings” version “7.0.0.0”
    Configuration type “Service Discovery Settings” version “7.0.0.0”
    Configuration type “WSAction Settings” version “7.0.0.2”
    Configuration type “SNMPAlert Settings” version “7.0.0.2”

    Error deploying logical server type “Prediction Engine v7.1.2.0 (1)” version “7.1.2.0” to host “localhost”
    Deployment Error: could not bind to path: [url]http://tech.forums.softwareag.com:15003/services/IRemoteConfiguration.wsdl[/url]
    One or more of the following configurations could not be deployed

    System Identity
    System Endpoint Registry
    JDBC alias configuration type “Analytic Repository” version “7.0.0.0”
    JDBC pool configuration “CentralConfigPool”
    Configuration type “Journal Logging” version “7.0.0.0”
    Configuration type “JNDI Configuration” version “7.0.0.0”
    Configuration type “Prediction Settings” version “7.0.0.0”
    Configuration type “Database Settings” version “7.1.0.0”

    Deployment of environment “MyLab” FAILED due to errors

    The deployment is successful when i deploy to a file. But when i import the same file , I am getting the below error.

    [COLOR=Red]com.webMethods.ccs.common.ConfigurationException: Error importing configuration environment at com.webMethods.ccs.engine.ConfigurationManager.deserialize(ConfigurationManager.java:1997) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at electric.util.reflect.Invocation.execute(Invocation.java:85) at electric.util.reflect.Invocation.invoke(Invocation.java:30) at electric.service.object.ObjectService.invoke(ObjectService.java:637) at electric.service.instrumentation.InstrumentingReference.invoke(InstrumentingReference.java:60) at electric.proxy.chain.ReferenceChain.invoke(ReferenceChain.java:155) at electric.proxy.handler.Proxy.invoke(Proxy.java:126) at $Proxy1.deserialize(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.webMethods.caf.wsclient.proxy.impl.WSClientDynamicProxy.invokeMethod(WSClientDynamicProxy.java:89) at com.webMethods.caf.wsclient.proxy.impl.WSClientDynamicProxy.invoke(WSClientDynamicProxy.java:134) at $Proxy0.deserialize(Unknown Source) at com.webMethods.portal.portlet.wm_cen_config_home.Cen_config_home.uploadFile(Cen_config_home.java:405) at com.webMethods.portal.portlet.wm_cen_config_home.Cen_config_home.finishUploadFile(Cen_config_home.java:739) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.webMethods.portal.mech.portlet.impl.PortletMechanics.executePortletMethod(PortletMechanics.java:117) at com.webMethods.portal.bizPolicy.command.portlet.ExecutePortletMethod.executePortletMethod(ExecutePortletMethod.java:53) at com.webMethods.portal.framework.portlet.LegacyPortletContainer.process(LegacyPortletContainer.java:229) at com.webMethods.portal.framework.portlet.LegacyPortletContainer.processPortletAction(LegacyPortletContainer.java:110) at com.webMethods.portal.framework.portlet.beans.rest.RestfulPCAHandler.handle(RestfulPCAHandler.java:182) at com.webMethods.portal.framework.dispatch.DispatchManager.handle(DispatchManager.java:438) at com.webMethods.portal.framework.dispatch.DispatchManager.handleDispatch(DispatchManager.java:371) at com.webMethods.portal.framework.impl.PortalServlet.service(PortalServlet.java:242) at javax.servlet.http.HttpServlet.service(HttpServlet.java:689) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:428) at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:830) at com.webMethods.portal.framework.impl.NTLMFilter.doFilter(NTLMFilter.java:50) at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821) at com.webMethods.caf.faces.servlet.GZIPFilter.doFilter(GZIPFilter.java:34) at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821) at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:471) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:568) at org.mortbay.http.HttpContext.handle(HttpContext.java:1530) at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:633) at org.mortbay.http.HttpContext.handle(HttpContext.java:1482) at com.webMethods.portal.webApplication.WmWebAppContext.handle(WmWebAppContext.java:159) at org.mortbay.http.HttpServer.service(HttpServer.java:909) at org.mortbay.http.HttpConnection.service(HttpConnection.java:820) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:986) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:837) at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:245) at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357) at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)

    Analytical Engine, Prediction engine, Data Collector MWS all are running in the default port.
    I had also tried defining a new environment again getting the same error. Is there any fix available for this.

    Please help me to overcome the issue.
    Thanks in advance…

    Thanks & Regards
    Vidhya
    [/COLOR]


    #BPM
    #webMethods-BPMS
    #webMethods


  • 2.  RE: Issues in Deploying Environment using MWS

    Posted Tue July 05, 2011 04:18 PM

    If you look in the installation guide, it specifically says not to use localhost for Optimize components. The issue you’re probably running into is that the Optimize ports are bound to one IP and localhost is resolving to a different one.

    To see if this is the problem, ping localhost to see what IP it comes back with. Then, do a netstat -an and look for the Optimize ports (e.g. netstat -an | findstr 15001). If the IP returned from netstat is different than the one returned from pinging localhost, there’s your problem. Change your environment so that it uses the host name associated with that IP or uses that IP directly.

    Percio


    #BPM
    #webMethods-BPMS
    #webMethods


  • 3.  RE: Issues in Deploying Environment using MWS

    Posted Thu January 29, 2015 06:43 PM

    I tried the command netstat for the optimize port, but the IP always listening 0.0.0.0. any advice?


    #webMethods
    #webMethods-BPMS
    #BPM