Security Requirements and Configuration
Full permissions are required for the agent to function correctly with WebSphere. Grant all permissions on both the server level and the profile level.
Run WebSphere with Security Enabled
To run WebSphere while J2EE security or Global security is enabled, you must make changes to WebSphere's server.policy file to prevent problems with the interaction between WebSphere and the Java Agent.
A codeBase value indicates the location of the source code. You must grant permissions to the code from that location. The codeBase is a URL value, and depends on the characters at the end. A codeBase with a trailing "/-" matches all files, both class and JAR files, in the directory and recursively all files in subdirectories contained in the directory.
- Navigate to the
server.policyfile, located in<websphere_home>/propertiesor in<websphere_profile_home>/properties. Add this code block to the WebSphere server.policy file:
Syntax
grant codeBase "file:</full/path/to/agent_install_directory>/-" { permission java.security.AllPermission; };Example
grant codeBase "file:/opt/appdynamics/javagent/agent4.5.1.23676/-" { permission java.security.AllPermission; };- Save the file.
Performance Monitoring Statistic
Under , set a Currently monitored statistic set to an option other than None for the JMX functionality to work.
Run WebSphere with Security EnabledLink to Run WebSphere with Security Enabled
server.policy file to prevent problems with the
interaction between WebSphere and the Java Agent. A codeBase value
indicates the location of the source code. You must grant permissions to the code
from that location. The codeBase is a URL value, and depends on the
characters at the end. A codeBase with a trailing
"/-" matches all files, both class and JAR files, in the directory and
recursively all files in subdirectories contained in the directory.