AppDynamics Application Intelligence Platform
3.8.x Documentation
The AppDynamics Java App Server Agent bootstraps using the javaagent command line option.
To add the javaagent command in a WebSphere 7.x and InfoSphere 8.x environment
1. Log in to the Administrator console of the WebSphere node where you want to install the App Server Agent.
2. In the Administration Console click Servers.
3. Expand Server Type and click WebSphere application servers.
4. Click the name of your server.
5. Expand Java and Process Management and click Process Definition.
6. Under the Additional Properties section, click Java Virtual Machine.
7. Enter the javaagent option with the full path to the AppDynamics javaagent.jar file in the Generic JVM arguments field.
For Windows:
-javaagent:<Drive Letter>:<agent install location>\javaagent.jar
For Linux:
-javaagent:<agent install location>/javaagent.jar
If you are a Self-Service Trial user, add the App Agent for Java javaagent argument to your JVM start script where <my-app-jvm1> is the name you use for the application running on that JVM.
-javaagent:<drive>:\<agent_home>\javaagent.jar=uniqueID=<my-app-jvm1>
8. Click OK.
May require OSGI bootdelegation
Websphere uses Equinox as its OSGi container. In some cases you may also need to add the Java agent packages to the OSGi bootdelegation system property as follows:
-Dorg.osgi.framework.bootdelegation=META-INF.services,com.singularity.*,com.ibm.*
To add the javaagent command in a WebSphere 6.x environment
1. Log in to the Administrator console of the WebSphere node where you want to install the App Server Agent.
2. In the left navigation tree, click Servers -> Application servers.
3. Click the name of your server in the list of servers.
4. In the "Configuration" tab, click Java and Process Management.
5. Enter the javaagent option with the full path to the AppDynamics javaagent.jar file in the Generic JVM arguments field.
For Windows:
-javaagent:<Drive Letter>:<agent install location>\javaagent.jar
For Linux:
-javaagent:<agent install location>/javaagent.jar
If you are a Self-Service Trial user, add the App Agent for Java javaagent argument to your JVM start script where <my-app-jvm1> is the name you use for the application running on that JVM.
-javaagent:<drive>:\<agent_home>\javaagent.jar=uniqueID=<my-app-jvm1>
8. Click OK.
To add the javaagent command in a WebSphere 5.x environment
1. Log in to the Administrator console of the WebSphere node where you want to install the App Server Agent.
2. In the Administrative Console, click Servers.
3. Select Application Servers.
4. Click the name of your server.
5. Under Additional Properties, select Process Definition.
6. On the next page, under Additional Properties select Java Virtual Machine.
7. Enter the javaagent option with the full path to the AppDynamics javaagent.jar file in the Generic JVM arguments field.
For Windows:
-javaagent:<Drive Letter>:<agent install location>\javaagent.jar
For Linux:
-javaagent:<agent install location>/javaagent.jar
If you are a Self-Service Trial user, add the App Agent for Java javaagent argument to your JVM start script where <my-app-jvm1> is the name you use for the application running on that JVM.
-javaagent:<drive>:\<agent_home>\javaagent.jar=uniqueID=<my-app-jvm1>
8. Click OK.
To verify the Agent configuration
Verify the configuration settings by checking the server.xml file of the WebSphere node where you installed the App Server Agent. The server.xml file should have this entry:
<jvmEntries ... genericJvmArguments='-javaagent:E:\test1\AppServerAgent\javaagent.jar' disableJIT="false"/>
Security Requirements
Full permissions are required for the agent to function correctly with WebSphere. Grant all permissions on both the server level and the profile level.
Running WebSphere with Security Enabled
If you want to run WebSphere while J2EE security or Global security is enabled, you need to make changes to WebSphere's server.policy file to prevent problems within the interaction between WebSphere and the Java agent. Make the change listed below to the server.policy file, which is located in <websphere_home>/properties or in <websphere_profile_home>/properties.
Add the following block to the WebSphere server.policy file:
grant codeBase "file:\* AGENT_DEPLOYMENT_DIRECTORY \*/-"
{
permission java.security.AllPermission;
};
WebSphere in z-OS or Mainframe Environments
Overview
Content Tools