IBM Tivoli Composite Application Manager for Application Diagnostics, Version 7.1.0.1
Pre-configuration steps for supporting customized startup script for JBoss - J2EE Agent
If a customized script is used for starting the JBoss server, there are additional steps to be performed. The steps are necessary for the Configuration Tool to correctly locate the appropriate section of the script and insert the configurations of the data collector accordingly.
Two anchors are needed to be specified in the customized script before running the Configuration Tool. They are ITCAM_DC_SCRIPT and ITCAM_OPTIONS.
- Anchor ITCAM_DC_SCRIPT
To support a customized startup script, the anchor ITCAM_DC_SCRIPT is needed to be specified in the script. It must be defined in a new line and before the execution of java command. When the Configuration Tool runs, the configuration of the data collector is inserted before this anchor.
Syntax:
<comment_tab> ITCAM_DC_SCRIPT...where:
<comment_tab> is the character used for indicating a line of comment in a script. In UNIX, this is '###'. In Windows, this is 'REM'
Examples:
Add the following line in a customized script on UNIX:
#### ITCAM_DC_SCRIPTAdd the following line in a customized script on Windows:
REM ITCAM_DC_SCRIPT- Anchor ITCAM_OPTIONS
The second anchor is required to be added as the last JVM option in the customized script. User needs to find where the JVM options is and insert $ITCAM_OPTIONS (on UNIX) or %ITCAM_OPTIONS% (on Windows). The anchor ITCAM_OPTIONS should be specified as the last JVM option, before the main class %MAINCLASS% in the JBoss JVM startup options.
Any existing GC logging argument or Java security policy will be overwritten after the configuration process
Examples:
"%JAVA%" %JAVA_OPTS% %ITCAM_OPTIONS% "-Djava.endorsed.dirs=%JBOSS_ENDORSED_DIRS%" -classpath "%JBOSS_CLASSPATH%" org.jboss.Main %*
Parent topic:
Configure the ITCAM for J2EE data collector