Analytical engine not connecting

Hi, Im trying to use analytical and business process using my webmethods. When I try to configure the Analytical Engine in My Webmethods Port, It couldnt connect to Analytical engine though it was running successfully. Below is the screen shot which shows the red dot indication. Could any tell me that what could be the reason and how to configure analytical engine.
Server Settings

DEFAULT
NAMEINTEGRATION SERVER
(MONITOR) HOST
PORT
USE SSL ANALYTIC ENGINE
HOST
PORT
USE SSL

Below is the stack trace from my webmethods server

2009-01-03 16:31:01 IST (webservice : WARN) [RID:7] - could not bind to path: http://localhost:15000/services/monitor.wsdl
java.lang.NumberFormatException: null
at java.lang.Integer.parseInt(Integer.java:415)
at java.lang.Integer.parseInt(Integer.java:497)
at electric.http.InboundHTTPResponse.readHeaders(Unknown Source)
at electric.http.HTTPMessage.readResponseHeaders(Unknown Source)
at electric.http.HTTPMessage.send(Unknown Source)
at electric.http.OutboundHTTPRequest.send(Unknown Source)
at electric.http.OutboundHTTPRequest.get(Unknown Source)
at electric.http.loader.HTTPResourceLoader.loadResource(Unknown Source)
at electric.util.resourceloader.ResourceLoaders.loadResource(Unknown Source)
at electric.wsdl.parser.WSDLParser.newWSDL(Unknown Source)
at electric.wsdl.loader.WSDLLoader.obtainWSDLBypassingCache(Unknown Source)
at electric.wsdl.loader.WSDLLoader.getWSDL(Unknown Source)
at electric.soap.registry.SOAPRegistry.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:276)
at com.webmethods.caf.wsclient.proxy.impl.WSClientDynamicProxy.invokeMethod(WSClientDynamicProxy.java:83)
at com.webmethods.caf.wsclient.proxy.impl.WSClientDynamicProxy.invoke(WSClientDynamicProxy.java:128)
at $Proxy4.pingService(Unknown Source)
at com.webmethods.bpo.portlet.wm_bam_ws_config.Bam_ws_config.pingOptimize(Bam_ws_config.java:536)
at com.webmethods.bpo.portlet.wm_bam_ws_config.Bam_ws_config.updateServerStatus(Bam_ws_config.java:706)
at com.webmethods.bpo.portlet.wm_bam_ws_config.Bam_ws_config.getServerListForDisplay(Bam_ws_config.java:315)
at ui.portlets.wm_bam_ws_config._default._jspService(_default.java:128)
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:123)
at com.webmethods.portal.framework.portlet.beans.JspPortletBean.getContentInternal(JspPortletBean.java:70)
at com.webmethods.portal.framework.portlet.beans.BasicPortletBean.getContent(BasicPortletBean.java:143)
at com.webmethods.portal.mech.portlet.impl.PortletMechanics.getPortletContent(PortletMechanics.java:95)
at com.webmethods.portal.mech.storage.page.PortletHelper.initializeRuntimeProperties(PortletHelper.java:246)
at com.webmethods.portal.mech.storage.page.PortletHelper.initializeRuntimeProperties(PortletHelper.java:302)
at com.webmethods.portal.mech.storage.page.PortletHelper.getFullyInitializedBean(PortletHelper.java:358)
at com.webmethods.portal.mech.portlet.impl.PortletMechanics.resolveWiringProperty(PortletMechanics.java:614)
at com.webmethods.portal.mech.portlet.impl.PortletMechanics.resolveWiring(PortletMechanics.java:593)
at com.webmethods.portal.mech.storage.page.PortletHelper.initializeWiredProperties(PortletHelper.java:224)
at com.webmethods.portal.mech.storage.page.PortletHelper.getInitializedBean(PortletHelper.java:334)
at com.webmethods.portal.mech.storage.page.PortletHelper.getInitializedBean(PortletHelper.java:319)
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:359)
at com.webmethods.portal.framework.dispatch.DispatchManager.pres(DispatchManager.java:618)
at com.webmethods.portal.framework.dispatch.DispatchManager.handle(DispatchManager.java:458)
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)

Thanks,

  • Ganesan

Ganesan,
Not sure that’s the right port, try 15503 instead. 15000 is the web service port but that’s not what you use at that configuration point.

Griffima, Thanks for the reply,

I tried as well with port 15503 but couldnt connect. But the analytic engine server is started with the port 15000. See the below message from Analytic engine server console.
[STARTUP] soap/http server started on http://tech.forums.softwareag.com:15000/services

Is there any configuration setting needs to be done.

  • Ganesan

Ganesan,
The analytic engine has several ports it uses, 15000, 15503(which is the one you connect to via MWS). Did you go through the environment config exercise with the central configurator to configure the analytic engine?

Griffima,

Yes, I have gone thro and created the logical server. But some how I could not deply the logical server instance because of below error.

Error deploying logical server type “Prediction Engine v7.1.0.0” version “7.1.0.0” to host “localhost”
Deployment Error: could not bind to path: http://tech.forums.softwareag.com:15003/services/IRemoteConfiguration.wsdl
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 “ORCL”
Configuration type “Journal Logging” version “7.0.0.0”
Configuration type “Prediction Settings” version “7.0.0.0”
Configuration type “Database Settings” version “7.1.0.0”
Configuration type “JNDI Configuration” version “7.0.0.0”
Error deploying logical server type “Data Collection Services v7.0.0.2” version “7.0.0.0” to host “localhost”
Deployment Error: could not bind to path: http://tech.forums.softwareag.com:15001/services/IRemoteConfiguration.wsdl
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 “DataCollector Settings” version “7.0.0.0”
Configuration type “JNDI Configuration” version “7.0.0.0”
Error deploying logical server type “Analytic Engine v7.1.0.0” version “7.1.0.0” to host “localhost”
Deployment Error: could not bind to path: http://tech.forums.softwareag.com:15000/services/IRemoteConfiguration.wsdl
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 “Common Directory Repository” version “7.1.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 “Process Work Repository” version “7.0.0.0”
JDBC pool configuration “ORCL”
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 “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”
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”
Deployment of environment “Dev” FAILED due to errors

Below is the config on logical server of analytical engine. Is the port (12503) you are trying to say?

ENDPOINT CONFIGURATION
Type
INCOMING CONNECTIONS
OUTGOING CONNECTIONS

ACTIONS


Analytic Engine v7.1.0.0
Configuration Agent
Web Service

JMS Provider
JMS
broker - Ganeshan:6849
MWS
MWS v7.1
http - Ganeshan:8585
WS Registry
Optimize Service Registry


Thanks,

Yes 12503 is correct, i changed all my default endpoints. So you have gone through the database setup, defined your environment but it would not deploy correct?

Have you check your analytic engine log to see if they attempts to communicate are happening? If not try, using a hostname instead of localhost.

DB also configured…
But still im facing the same problem…
My understanding about the config of logical server is when there are more than one env like prod, stag, dev and sandbox. In this case i belive we need to config env set using central configurator.

Is there any checklist before we configure…

But anyhow, pls find below log infor when i try to connect to analytical engine.

2009-01-07 21:54:24 IST (wsclient : FATAL) [RID:11] - com.webmethods.caf.wsclient.proxy.impl.WSClientDynamicProxy: Failed to bind to endPoint: http://ganeshan:12503/services/monitor.wsdl and interface: interface com.webmethods.bpo.service.IBaseWebService: could not bind to path: http://ganeshan:12503/services/monitor.wsdl
com.webmethods.caf.wsclient.WSClientException: Failed to bind to endPoint: http://ganeshan:12503/services/monitor.wsdl and interface: interface com.webmethods.bpo.service.IBaseWebService: could not bind to path: http://ganeshan:12503/services/monitor.wsdl
at com.webmethods.caf.wsclient.proxy.impl.WSClientDynamicProxy.getBinding(WSClientDynamicProxy.java:278)
at com.webmethods.caf.wsclient.proxy.impl.WSClientDynamicProxy.invokeMethod(WSClientDynamicProxy.java:83)
at com.webmethods.caf.wsclient.proxy.impl.WSClientDynamicProxy.invoke(WSClientDynamicProxy.java:128)
at $Proxy4.pingService(Unknown Source)
at com.webmethods.bpo.portlet.wm_bam_ws_config.Bam_ws_config.pingOptimize(Bam_ws_config.java:536)
at com.webmethods.bpo.portlet.wm_bam_ws_config.Bam_ws_config.updateServerStatus(Bam_ws_config.java:706)
at com.webmethods.bpo.portlet.wm_bam_ws_config.Bam_ws_config.getServerListForDisplay(Bam_ws_config.java:315)
at ui.portlets.wm_bam_ws_config._default._jspService(_default.java:128)
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:123)
at com.webmethods.portal.framework.portlet.beans.JspPortletBean.getContentInternal(JspPortletBean.java:70)
at com.webmethods.portal.framework.portlet.beans.BasicPortletBean.getContent(BasicPortletBean.java:143)
at com.webmethods.portal.mech.portlet.impl.PortletMechanics.getPortletContent(PortletMechanics.java:95)
at com.webmethods.portal.mech.storage.page.PortletHelper.initializeRuntimeProperties(PortletHelper.java:246)
at com.webmethods.portal.mech.storage.page.PortletHelper.initializeRuntimeProperties(PortletHelper.java:302)
at com.webmethods.portal.mech.storage.page.PortletHelper.getFullyInitializedBean(PortletHelper.java:358)
at com.webmethods.portal.mech.portlet.impl.PortletMechanics.resolveWiringProperty(PortletMechanics.java:614)
at com.webmethods.portal.mech.portlet.impl.PortletMechanics.resolveWiring(PortletMechanics.java:593)
at com.webmethods.portal.mech.storage.page.PortletHelper.initializeWiredProperties(PortletHelper.java:224)
at com.webmethods.portal.mech.storage.page.PortletHelper.getInitializedBean(PortletHelper.java:334)
at com.webmethods.portal.mech.storage.page.PortletHelper.getInitializedBean(PortletHelper.java:319)
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:359)
at com.webmethods.portal.framework.dispatch.DispatchManager.pres(DispatchManager.java:618)
at com.webmethods.portal.framework.dispatch.DispatchManager.handle(DispatchManager.java:458)
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)
Caused by: electric.registry.RegistryException: could not bind to path: http://ganeshan:12503/services/monitor.wsdl
at electric.soap.registry.SOAPRegistry.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:276)
… 50 more
Caused by: java.rmi.ConnectException: Connection refused: connect: unable to load file http://ganeshan:12503/services/monitor.wsdl
at electric.http.loader.HTTPResourceLoader.loadResource(Unknown Source)
at electric.util.resourceloader.ResourceLoaders.loadResource(Unknown Source)
at electric.wsdl.parser.WSDLParser.newWSDL(Unknown Source)
at electric.wsdl.loader.WSDLLoader.obtainWSDLBypassingCache(Unknown Source)
at electric.wsdl.loader.WSDLLoader.getWSDL(Unknown Source)
… 57 more
2009-01-07 21:54:24 IST (portlet : WARN) [RID:11] - Setting returnUrl inside render method is not permitted
2009-01-07 21:54:25 IST (portlet : WARN) [RID:11] - Setting returnUrl inside render method is not permitted

Ganesan,
I not sure from your last post whether you have deployed the configuration to the environment yet, you have to do that before you are going to be able to connect.

I was able to connect…As you said the problem was with deployment. Now the deployment successful and could connect to analytic engine.

thanks for your help.

Assuming after the configuration settings done(Add Environments,Add Logical Servers,Configure servers-define hosts,map servers,end points,db pools…) and you did “Deploy All” .After that trying to restart all Logical Servers?? and you are getting the above errors??

HTH,
RMG

Yes, After the logical server configuration of all the (Add Environments,Add Logical Servers,Configure servers-define hosts,map servers,end points,db pools…etc) I could deploy all the configuration. Once the deployment was successfull then we could successfully connect to analytical engine.

Thanks
Ganesan M

So you mean its working now after all the configurations done above finally??

HTH,
RMG

hi all,

i have a similar problem with the analytical server. I followed all of the above steps and the enviroment deployment went just fine but when i check the server status in My Webmethods->System Settings->Server Settings the analytic engine host is still not available.
Although when i check if the analytical server is online at System-Wide->System Information the server appears to be on-line.

Has anyone experienced this problem or has an idea why this is happening?

Thanks,
Bogdan

Hi
if the analytical server is online at System-Wide->System Information the server appears to be on-line, It doesnt mean it is connected. Check in the logs if you see analytic engine is started or not. If you can post the logs that would be more helpfull to look.

Also want to make sure that under the Define Environments -Map DB pools that the Common directory is pointed toward the MWS DB connection. Helped us!