CA Wily - Java agent for Jboss

[MWRD]

Hi

We have installed CA Wily agent for CA Siteminder using the Jboss configuration steps as mentioned in the installation guide as available on CA Support portal.

We have made the desired changes to the introscope.profile and run.bat files as required but the CA Wily agent is not showing up in the CA Wily Workstation.

Please share if we need to make any more configuration changes in order to complete the process!

Regards,
Payal

[Legacy User]

Hi,

please look into IntroscopeAgent.log file and also check telnet connectivity on 5001 port between your EM and Agent Server.


Regards,
Irshad Khan

[MWRD]

Hi Irshad,

Thanks for your reply.

We are using port 5020 between EM and Agent server. Also, no log has been generated.

Regards,
Payal

[Anon Anon]

Hi Payal,

What is the version of JBoss Application server & CA Wily Agent ?

Thanks,
Sunil

[MWRD]

The version of Wily is 9.1.1.1 and that of SiteMinder is 12.0

[Viruvaibhav_apm]

Hi Payal,

I'll suggest you to re-check your installation process for IntroscopeAgent.profile and run.bat configurations.
Because your installation has not been successful as no logs have been generated.

Also as you said, you are using port 5020 for connection to EM. So have you changed it on the EM side. ( just for validation i am asking)

or Did you telnet bw your EM and Server using that port?

Regards,
Vaibhav

[MWRD]

Hi Vaibhav,

we have changed the port in EM side as well and have tried telnet too. Telnet is working.

Regards,
Payal.

[Anon Anon]

Can you please upload the IntroscopeAgent.profile and run.bat file.

Regards,
Jitesh

[Anon Anon]

Hi Payal,
Can you please clarify which of the two you are looking to install, is it the core java agent for JBOSS or the Siteminder Agent extension for the agent?

Regards
Vijay
CA APM Support

[MWRD]

Hi Vijay,

I am trying to install core Java agent for JBOSS.

Thanks,
Payal

[Haruhiko Davis]

Sounds like your installation is on Windows. You be checking your startup parameters in your JBOSS Windows service configuration.

[MWRD]

Please attached see the run.bat file.

Attachment(s)

run.zip   824 B 1 version

[Anon Anon]

Hi Payal,

Is your JBoss Application Server on Version 7 ? There is a known Java Agent Issue ( Agent Does Not Start in JBoss 7 - 84396, 76212) where the agent is not started when you use ORACLE/JDK 1.6 Update 15 & later versions.

Check the below info & see if it is applicable to your environment :-


Symptom:
When you use ORACLE/SUN JDK 1.6 Update 15 and later versions, the Agent is not started. This issue is a logger problem in JBoss 7 and is common for any agent that performs logging.

Solution:

Use one of the following workarounds to resolve the issue:
1. Use ORACLE/SUN JDK 1.6 Update 14 or previous versions.
2. Turn off the logging of WILY agent in the agent profile and start the server. Enable the logging after the server boots up.
3. Open the JBoss startup script in a text editor, and update with:
set JAVA_OPTS= %JAVA_OPTS%
-Djboss.modules.system.pkgs=org.jboss.logmanager,com.wily,com.wily.* -Djava.util.logging.manager=org.jboss.logmanager.LogManager -javaagent:%JBOSS_HOME%\wily\Agent.jar -Dcom.wily.introscope.agentProfile=%JBOSS_HOME%\wily\core\config\IntroscopeAgent.profile -Xbootclasspath/p:%JBOSS_HOME%\modules\org\jboss\logmanager\main\jboss-logmanager-1.2.2.GA.jar;%JBOSS_HOME%\modules\org\jboss\logmanager\log4j\main\jboss-logmanager-log4j-1.0.0.GA.jar;%JBOSS_HOME%\modules\org\apache\log4j\main\log4j-1.2.16.jar

Thanks,
Sunil

[Haruhiko Davis]

If you do all of the steps in Sunil's step #3, you will not need to turn off agent logging, if you want/need to keep it.

I just did the same thing setting up a test JBoss AS 7.1.1 server on RHEL 6.4 using Oracle JDK 1.6.

[Anon Anon]

Thank you Sunil for your share, it was actually the only good solution I found.

Actually I just added the JAVA_OPTS to the standalone.bat without the other steps and it worked perfectly.

Been using APM 9.5 and Jboss AS7.1.1 Final.

Thanks again.

 

set JAVA_OPTS= %JAVA_OPTS%
-Djboss.modules.system.pkgs=org.jboss.logmanager,com.wily,com.wily.* -Djava.util.logging.manager=org.jboss.logmanager.LogManager -javaagent:%JBOSS_HOME%\wily\Agent.jar -Dcom.wily.introscope.agentProfile=%JBOSS_HOME%\wily\core\config\IntroscopeAgent.profile -Xbootclasspath/p:%JBOSS_HOME%\modules\org\jboss\logmanager\main\jboss-logmanager-1.2.2.GA.jar;%JBOSS_HOME%\modules\org\jboss\logmanager\log4j\main\jboss-logmanager-log4j-1.0.0.GA.jar;%JBOSS_HOME%\modules\org\apache\log4j\main\log4j-1.2.16.jar

 

[Anon Anon]

med-adhoc:

Thank you Sunil for your share, it was actually the only good solution I found.

Actually I just added the JAVA_OPTS to the standalone.bat without the other steps and it worked perfectly.

Been using APM 9.5 and Jboss AS7.1.1 Final.

Thanks again.

 

set JAVA_OPTS= %JAVA_OPTS%
-Djboss.modules.system.pkgs=org.jboss.logmanager,com.wily,com.wily.* -Djava.util.logging.manager=org.jboss.logmanager.LogManager -javaagent:%JBOSS_HOME%\wily\Agent.jar -Dcom.wily.introscope.agentProfile=%JBOSS_HOME%\wily\core\config\IntroscopeAgent.profile -Xbootclasspath/p:%JBOSS_HOME%\modules\org\jboss\logmanager\main\jboss-logmanager-1.2.2.GA.jar;%JBOSS_HOME%\modules\org\jboss\logmanager\log4j\main\jboss-logmanager-log4j-1.0.0.GA.jar;%JBOSS_HOME%\modules\org\apache\log4j\main\log4j-1.2.16.jar

 

Hi med-adhoc,

I'm glad it worked for you. Thanks for the update :-).

Thanks,

Sunil

[Haruhiko Davis]

Please mark the answer you feel resolved the issue to close the thread.