Sun Java System Access Manager Policy Agent 2.2 Guide for Apache Tomcat 6.0

Summary of a J2EE Agent Installation in Policy Agent 2.2

At the end of the installation process, the installation program prints the status of the installation along with the installed J2EE agent information. The information that the program displays can be very useful. For example, the program displays the agent instance name, which is needed when configuring a remote instance. The program also displays the location of specific files, which can be of great importance. In fact, you might want to view the installation log file once the installation is complete, before performing the post-installation steps as described in Chapter 4, Post-Installation Tasks of Policy Agent 2.2 for Apache Tomcat 6.0.

The location of directories displayed by the installer are specific. However, throughout this guide and specifically in Summary of Agent Installation shown in this section, PolicyAgent-base is used to describe the directory where the distribution files are stored for a specific J2EE agent.

The following example serves as a quick description of the location of the J2EE agent base directory (PolicyAgent-base) of Policy Agent 2.2 for Apache Tomcat 6.0.

Example 3–1 Policy Agent Base Directory of Agent for Apache Tomcat 6.0

The following directory represents PolicyAgent-base of Agent for Apache Tomcat 6.0:


where Agent-HomeDirectory is the directory you choose in which to unpack the J2EE agent binaries.

Information regarding the location of the J2EE agent base directory is explained in detail in Location of the J2EE Agent Base Directory in Policy Agent 2.2.

The following type of information is printed by the installer:

Agent instance name: Agent_001
Agent Configuration file location:
Agent Audit directory location:
Agent Debug directory location:

Install log file location:

Thank you for using Access Manager Policy Agent

Once the agent is installed, the directories shown in the preceding example are created in the agent_00x directory, which for this example is specifically Agent_001. Those directories and files are briefly described in the following paragraphs.


Location of the J2EE agent configuration file for the agent instance. Every instance of a J2EE agent has a unique copy of this file. You can configure this file to meet your site's requirements. For more information, see the following sections:


Location of the J2EE agent local audit trail.


Location of all debug files required to debug an agent installation or configuration issue.


Location of the file that has the agent install file location. If the installation failed for any reason, you can look at this file to diagnose the issue.