PDFs

On this page:

Your Rating:
Results:
PatheticBadOKGoodOutstanding!
48 rates

The Java Agent bootstraps using the javaagent command line option.

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.

Required Configurations

The following configurations are required for WebSphere to work correctly with AppDynamics.

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;
};

Performance Monitoring Statistic

Under Application servers > <server_name> > Performance Monitoring Infrastructure (PMI), set a Currently monitored statistic set to an option other than None for the JMX functionality to work.

Instrument WebSphere 7.x, 8.x, and 9.x or InfoSphere 8.x

  1. Log in to the administrative console for the WebSphere node where you want to install the App Server Agent.
  2. In the administrative console click Servers > Server Types > WebSphere application servers.
  3. Click the name of your server.
  4. In the Server Infrastructure section, click Java and Process Management > Process Definition.
  5. Under the Additional Properties section, click Java Virtual Machine.
  6. 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
    
  7. Click OK.

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.*

Instrument WebSphere 6.x

  1. Log in to the administrative console for the WebSphere node where you want to install the Java 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 Java Agent 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
    


    For example:

  6. Click OK

Instrument WebSphere 5.x

  1. Log in to the administrative console of the WebSphere node where you want to install the App Server Agent.
  2. In the administrative console, click Servers.
  3. Click Application Servers.
  4. Click the name of your server.
  5. Under Additional Properties, click Process Definition.
  6. On the next page, under Additional Properties, click Java Virtual Machine.
  7. Enter the javaagent option with the full path to the Java Agent 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
    
  8. Click OK.

Verifying the Java Agent Configuration

Verify the configuration settings by checking the server.xml file of the WebSphere node where you installed the Java Agent. The server.xml file should have this entry:

<jvmEntries ... genericJvmArguments='-javaagent:E:\test1\AppServerAgent\javaagent.jar' disableJIT="false"/>