AnsweredAssumed Answered

CA Wily on HP ALM application

Question asked by CMCN1982 on Dec 22, 2017
Latest reply on Jan 4, 2018 by Hiko_Davis

Hi, 

 

I have Wily successfully configured in our HP ALM production environment. I can see both of my applications listed in the Investigator console and they are monitoring resource usage as expected.

 

However, when I try to set it up in the exact same way in my HP ALM Development environment it does not work. The application server cannot be seen in the Investigator console.

 

Details below:

 

We are using CA APM Introscope Agent 10.1.0.15 in both Production and Dev.

Install path is the same on both: D:\Wily

 

In the application's wrapper file we have it configured exactly the same.

 

wrapper.java.additional.20=-javaagent:D:\\wily\\Agent.jar
wrapper.java.additional.21=-Dcom.wily.introscope.agentProfile=D:\wily\core\config\IntroscopeAgent.profile

 

In the IntroscopeAgent.profile they are configured similarly, the only difference being that we point to different Wily DNS names to distinguish between our Wily production and Wily dev. For example:

 

Prod:

introscope.agent.enterprisemanager.transport.tcp.host.DEFAULT=XX.***.***.*** (Our Wily Prod IP)
introscope.agent.enterprisemanager.transport.tcp.port.DEFAULT=5101
introscope.agent.enterprisemanager.transport.tcp.socketfactory.DEFAULT=com.wily.isengard.postofficehub.link.net.DefaultSocketFactory

 

Dev: 

 

introscope.agent.enterprisemanager.transport.tcp.host.DEFAULT=***.XX.***.XX (Our Wily Dev IP)
introscope.agent.enterprisemanager.transport.tcp.port.DEFAULT=5101
introscope.agent.enterprisemanager.transport.tcp.socketfactory.DEFAULT=com.wily.isengard.postofficehub.link.net.DefaultSocketFactory

 

We restart the application's service as well as the server, but still cannot figure out why the Wily agent is not being triggered. This is what I see in the wrapper.log file of the application when it restarts:

 

Launching a JVM...
INFO | jvm 1 | 2017/12/20 11:03:20.072 | -XX:+ExplicitGCInvokesConcurrent -XX:+HeapDumpOnOutOfMemoryError -XX:InitialHeapSize=8594128896 -XX:MaxHeapSize=8594128896 -XX:MaxPermSize=536870912 -XX:MaxTenuringThreshold=6 -XX:NewRatio=2 -XX:OldPLABSize=16 -XX:+PrintCommandLineFlags -XX:+PrintFlagsFinal -XX:+UseCompressedOops -XX:+UseConcMarkSweepGC -XX:-UseLargePagesIndividualAllocation -XX:+UseParNewGC

 

So no mention of Wily there. But when I check the same wrapper log file in Production, Wily isn't mentioned there either. But yet it works in Production.

 

Does anyone have any tips or advice? Thanks.

Outcomes