Configuring JVMs in IBM Operational Decision Manager

To monitor a JVM that runs in IBM Operational Decision Manager (IBM ODM), update the <ODM_hilev>.SHBRPARM(HBRMSTR) member to add the -javaagent enablement option to the existing JAVA_OPTIONS parameter.

About this task

There is a 255 character limitation for the JAVA_OPTIONS string. If the monitoring parameters cause the string to exceed the 255 character limit, the JAVA_OPTIONS parameter must be specified with a continuation character.

To enable the continuation, add a plus sign (+) at the end of your JAVA_OPTIONS line, and then indent the next line with at least one space. The following example shows how to enable the continuation:
JAVA_OPTIONS=-Xms256M -Xmx768M +                 
    -Djava.util.prefs.userRoot=/tmp/hbr1 +           
    -Xbootclasspath/p:+                              
    /usr/lpp/kan/hca_64/lib/ext/healthcenter.jar +   
    -agentpath:/usr/lpp/kan/hca_64/bin/libhealthcenter.so+ 
    =path=/usr/lpp/kan/hca_64,level=inprocess,disableCH +                      
    -javaagent:/usr/lpp/kan/bin/IBM/kjj.jar +        
    -Dcom.ibm.tivoli.kjj.collector.id=KJJX +         
    -DKJJ_DEBUG=KJJ:INFO
Notes:
  • -Xbootclasspath: and -agentpath: are required only when the external Health Center agent is used.
  • -javaagent: is required for monitoring. /usr/lpp/kan/bin/IBM/kjj.jar is the default path for the kjj.jar file. If the kjj.jar file is installed to another directory, update this statement accordingly.
  • -Dcom.ibm.tivoli.kjj.collector.id= is required only when the default KJJ1 collector ID is not used.

For information about adding the enablement options, see Configuring JVMs in subsystems.