Child pages
  • Granting Java 2 permissions to the App Visibility agent
Skip to end of metadata
Go to start of metadata

The App Visibility agent requires permissions to the Java 2 system, such as write access to the application server computer (for log entries), and API access to various application interfaces to collect diagnostic information. On application servers that use Java 2 security, you must provide permissions to the App Visibility agent.

Granting the relevant permissions depends on the Java 2 security provider and application server type. This topic describes how to grant the relevant Java 2 permissions on different application server types.

To grant Java 2 permissions on IBM WebSphere

On secured WebSphere servers you grant Java 2 permissions by configuring the server.policy file, as described in the following steps:

  1. Locate and open the server.policy file, which is found in the properties library.
  2. Modify the server.policy file with the relevant permissions. For details, refer to the Configuring server.policy file resource section on the IBM website .
  3. Restart WebSphere.

    Example of the lines added to the IBM WebSphere server.policy file to grant Java 2 permission for the App Visibility agent:

    Example

    // Allow the App Visibility agent all permissions
    grant codeBase "file:C:/aps_agent/ADOPsInstall/-" {
      permission java.security.AllPermission;
    };
    

To grant Java 2 permissions on Oracle WebLogic

WebLogic does not have a default policy file and can be configured to use one, as described in the following steps:

  1. Locate the weblogic.policy file, which is usually found in the security library, and open it for editing.
  2. Modify the policy file with the relevant permissions. For details, refer to the Using Java Security to Protect WebLogic Resources and Java Security Overview sections on the Oracle website .
  3. Restart WebLogic.

To grant Java 2 permissions on Apache Tomcat

On secured Tomcat servers this is achieved by configuring the catalina.policy file, as described in the following steps:

  1. Locate the catalina.policy file, which is usually found in the conf library, and open it for editing.
  2. Modify the catalina.policy file with the relevant permissions. For details, refer to the Security Manager HOW-TO section on the Tomcat website .
  3. Restart Tomcat.

To grant Java 2 permissions on JBoss

JBoss does not have a default policy file. It uses the JVM’s default policy file, or you can configure it to use a different one, as described in the following steps:

  1. Locate the server.policy file, which is usually found in the conf library, and open it for editing.
  2. Modify the policy file with the relevant permissions. For details, refer to the Java Security Manager section on the JBoss website .
  3. Restart JBoss.

Where to go from here

Verifying the installation of App Visibility agent for Java

Related topics

Installing an App Visibility agent for Java

Updating Java options according to the application server type