Updating the Java options according to the application server type

The process of updating Java options is different for each application server type. This topic provides instructions for four of the leading types of application servers.

Note

When BMC Application Diagnostics is running in the same memory space as the monitored applications (same JVM), BMC recommends adding 256MB to the Max heapsize Java options flag -Xmx.

Example

set JAVA_OPTS=%JAVA_OPTS% -Xmx1024m

Refer to the section about adding parameters to the application server’s JVM options.
For full details about both the -javaagent and Xmx options, refer to the Java options for each application server type.

IBM WebSphere

You should configure WebSphere JVM options from the admin console; configuration should not be done from the start script.

Log in to the WebSphere admin console.
Expand Server Type and select WebSphere application servers.
Click the name of the server to which you would like to attach the BMC Application Diagnostics Agent.
Expand Java and Process Management and select Process Definition.
Under the Additional Properties section, click Java Virtual Machine.
Scroll down and locate the text box for Generic JVM arguments.
Add the following lines:
For Windows
-javaagent:<AgentInstallationDirectory>\ADOPsInstall\adops-agent.jar
-Dcom.bmc.adops.agent.server.id="AppServer5"
For Linux
-javaagent:<AgentInstallationDirectory>/ADOPsInstall/adops-agent.jar -Dcom.bmc.adops.agent.server.id="AppServer5"
where <AgentInstallationDirectory> is the location where the Agent is installed.

Note that the -Dcom.bmc.adops.agent.server.id parameter is automatically determined by the application server name. Add this line only if you want to customize the name.
Save the configuration.
Restart the WebSphere Application Server process.
For further information about setting JVM arguments in WebSphere, see the IBM website.

Oracle WebLogic

Edit the startWebLogic script. (File extensions are: cmd for Windows, and sh for Linux.) This script is used when starting both admin and managed servers. The startManagedWebLogic script calls the startWebLogic script.
Locate the JAVA_OPTIONS environment variable and add the following lines:
For Windows
set JAVA_OPTIONS=%JAVA_OPTIONS% -javaagent:<AgentInstallationDirectory>\ADOPsInstall\adops-agent.jar -Dcom.bmc.adops.agent.server.id="AppServer5"
For Linux

${JAVA_HOME}/bin/java ${JAVA_VM} ${MEM_ARGS} -Dweblogic.Name=${SERVER_NAME}${JAVA_OPTIONS} -javaagent:<AgentInstallationDirectory>/adops-agent.jar -Dcom.bmc.adops.agent.server.id="WebLogicServer3" -Djava.security.policy=${WL_HOME}/server/lib/weblogic.policy ${JAVA_OPTIONS} ${PROXY_SETTINGS} ${SERVER_CLASS}
where <AgentInstallationDirectory> is the location where the Agent is installed.

Note that the -Dcom.bmc.adops.agent.server.id parameter is automatically determined by the application server name. Add this line only if you want to customize the name.
Restart the WebLogic Application Server process.
For further information about specifying Java options for a WebLogic server instance, see the Oracle website.

Apache Tomcat

Edit Tomcat’s catalina script. (File extensions are: cmd for Windows, or sh for Linux.)
Locate the JAVA_OPTS environment variable .
Add the following lines:
For Windows
set CATALINA_OPTS=%CATALINA_OPTS% -javaagent:<AgentInstallationDirectory>\ADOPsInstall\adops-agent.jar -Dcom.bmc.adops.agent.server.id="AppServer5"
For Linux
CATALINA_OPTS=" -javaagent:<AgentInstallationDirectory>/adops-agent.jar -Dcom.bmc.adops.agent.server.id="Tomcat6_2""
where <AgentInstallationDirectory> is the location where the Agent is installed.
Restart the Apache Tomcat Application Server process.
For further information about changing Java options when Tomcat runs as a Windows Service, see the Apache website.

JBoss

Edit the JBoss run script. (File extensions are: cmd for Windows, or sh for Linux.)
Locate the JAVA_OPTS environment variable.
Add the following lines:
For Windows
set JAVA_OPTS=%JAVA_OPTS% -javaagent:<AgentInstallationDirectory>\ADOPsInstall\adops-agent.jar -Dcom.bmc.adops.agent.server.id="AppServer5"
For Linux

JAVA_OPTS="$JAVA_OPTS -Djava.net.preferIPv4Stack=true -javaagent:<AgentInstallationDirectory>/ADOPsInstall/adops-agent.jar -Dcom.bmc.adops.agent.server.id=Jboss3"
where <AgentInstallationDirectory> is the location where the Agent is installed.
Restart the JBoss Application Server process.
For further information about updating both the JBoss run.conf file and run script, see the JBoss website.