andy.erskine

Monitoring Experian Powercurve with APM

Discussion created by andy.erskine on May 11, 2015
Latest reply on May 12, 2015 by Hiko_Davis

We have a requirement to monitor an application called Experian Powercurve which runs in a windows Env and a service is created with a batch code where we have entered our agent config, we have been told that --javaagent is unsupported so we are using the xbootclasspath method. however the agent is not starting .. to configure the agent we create a agentconnector.jar using the steps described here : Process SAML Authentication and then edit the following bat file :

 

SET APM_HOME_DIR=E:\apm

 

%SERVICE_NAME%.exe //IS//%SERVICE_NAME% --Startup=auto --JvmOptions=-Xrs;-XX:PermSize=128M;-XX:MaxPermSize=256M;-Xbootclasspath/p:%APM_HOME_DIR%\connectors\AutoProbeConnector.jar';'%APM_HOME_DIR%\Agent.jar';'-

Dcom.wily.introscope.agentProfile=%APM_HOME_DIR%\core\config\IntroscopeAgent.profile;-Xms3072M;-Xmx3072M;-Dlogback.configurationFile="%CLIENT_SOLUTION%\conf\system\logback.xml";-

Dclient.solution.home="%CLIENT_SOLUTION%";-Dib.home="%IB_HOME%";-Duser.dir="%CLIENT_SOLUTION%";-Dgroovy.source.encoding=UTF-8;-Dderby.stream.error.file="%DERBY_LOG%";%BOOTSTRAP_DEBUG_OPT%;%SECURITY_POLICY_OPT%;

--Jvm=auto --Classpath="%IB_HOME%\lib\core\enterprise-bootstrap.jar";"%IB_HOME%\bin";"%CLIENT_SOLUTION%\conf\system" --StartPath="%IB_HOME%\lib\core" --StartClass=com.experian.eda.enterprise.startup.Bootstrap --

StartParams=-fa;"%CLIENT_SOLUTION%\conf\system\camel-context.xml"; --StartMode=jvm --StopPath="%IB_HOME%\lib\core" --StopClass=com.experian.eda.enterprise.startup.Bootstrap --StopMethod=stopApplication --

StopMode=jvm --StopTimeout=0 --LogPrefix=service --StdOutput=auto --StdError=auto --LogPath="%CLIENT_SOLUTION%\logs\service" --LogLevel=Info --JavaHome="C:\Program Files\Java\jre7"

@echo Successfully installed Connectivity service.

 

When we run the bat file this writes to the registry the java startup config like such :

 

-Xrs

-XX:PermSize=128M

-XX:MaxPermSize=256M

-Xbootclasspath/p:E:\apm\connectors\AutoProbeConnector.jar;E:\apm\Agent.jar;-Dcom.wily.introscope.agentProfile=E:\apm\core\config\IntroscopeAgent.profile

-Xms3072M

-Xmx3072M

-Dlogback.configurationFile=E:\Experian\PCE_CON_Solution\conf\system\logback.xml

-Dclient.solution.home=E:\Experian\PCE_CON_Solution

-Dib.home=E:\Experian\PowerCurve\Connectivity\Connectivity v1.2SP6

-Duser.dir=E:\Experian\PCE_CON_Solution

-Dgroovy.source.encoding=UTF-8

-Dderby.stream.error.file=E:\Experian\PCE_CON_Solution\logs\derby.log

 

When we then start the Application from services the Application starts successfully however the Agent does not.

Looking in the Application logs we see the following :

 

2015-05-11 17:04:59 Commons Daemon procrun stderr initialized

5/11/15 05:05:01 PM EST [INFO] [IntroscopeAgent.Agent] Agent Release 9.6.1.0 (Build 961036)

5/11/15 05:05:01 PM EST [INFO] [IntroscopeAgent.Agent] Using Java VM version "Java HotSpot(TM) 64-Bit Server VM 1.7.0_45" from Oracle Corporation

5/11/15 05:05:01 PM EST [INFO] [IntroscopeAgent.Agent] Trying to load agent profile based on system property "com.wily.introscope.agentProfile"

5/11/15 05:05:01 PM EST [INFO] [IntroscopeAgent.Agent] Unable to load agent profile because the system property could not be found

5/11/15 05:05:01 PM EST [INFO] [IntroscopeAgent.Agent] Trying to load agent profile from resource from the class path based on system property "com.wily.introscope.agentResource"

5/11/15 05:05:01 PM EST [INFO] [IntroscopeAgent.Agent] Unable to load agent profile because the system property could not be found

5/11/15 05:05:01 PM EST [INFO] [IntroscopeAgent.Agent] Trying to load agent profile based on the working directory at: E:\Experian\PCE_CON_Solution\wily\IntroscopeAgent.profile

5/11/15 05:05:01 PM EST [INFO] [IntroscopeAgent.Agent] Unable to load agent profile because of: java.io.FileNotFoundException E:\Experian\PCE_CON_Solution\wily\IntroscopeAgent.profile (The system cannot find the path specified)

 

Any idea why the agent is looking in this location where we havent installed any APM files as they are in E:\APM ?

Something to do with using the AutoProbeConnector.jar file ?

 

 

Thanks.

Outcomes