At the end of the installation process, the installation program displays a summary of the agent installation. For example:
SUMMARY OF AGENT INSTALLATION ----------------------------- Agent instance name: agent_001 Agent Configuration file location: /opt/j2ee_agents/am_jboss_agent/agent_001/config/AMAgent.properties Agent Audit directory location: /opt/j2ee_agents/am_jboss_agent/agent_001/logs/audit Agent Debug directory location: /opt/j2ee_agents/am_jboss_agent/agent_001/logs/debug Install log file location: /opt/j2ee_agents/am_jboss_agent/logs/audit/install.log Thank you for using Access Manager Policy Agent
In the following descriptions, PolicyAgent-base represents the J2EE base installation directory for the agent, and agent_001 identifies this specific agent installation. For more information about the location of a J2EE agent base directory, see Location of the J2EE Agent Base Directory in Policy Agent 2.2.
Files in the SUMMARY OF AGENT INSTALLATION include:
Location of the J2EE agent AMAgent.properties 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 determine the cause of the failure.
Before performing the post-installation steps as described in Chapter 4, Post-Installation Tasks of Policy Agent 2.2 for JBoss Application Server 4.0, be sure to review the install.log file.