Chapter 3 Installing Policy Agent 2.2 for Sun Java System Application Server 8.1

Sun Java^TM System Access Manager Policy Agent 2.2 for Sun Java System Application Server 8.1, as with all J2EE agents in the 2.2 release of Policy Agent, is installed from the command line using the agentadmin program. For more information about the tasks you can perform with the agentadmin program, see Role of the agentadmin Program in a J2EE Agent for Policy Agent 2.2.

Before reading this chapter or performing any of the tasks described within, thoroughly review Chapter 2, Vital Installation Information for a J2EE Agent in Policy Agent 2.2 since various key concepts are introduced in that chapter.

This chapter is organized into the following sections:

• Installation Related Information About Agent for Sun Java System Application Server 8.1

• Preparing to Install Agent for Sun Java System Application Server 8.1

• Launching the Installation Program of Agent for Sun Java System Application Server 8.1

• Using the Installation Program of Agent for Sun Java System Application Server 8.1

Before describing any task, this chapter provides you with installation-related information specific to Sun Java System Application Server 8.1. The subsequent sections lead you through the pre-installation and installation steps and describe how to view the installation log files. First, perform the pre-installation (preparation) steps. Then, perform the installation, itself. The installation process has two phases. The first phase of the installation includes launching the installation program, which requires a directory to already have been selected for the agent files. The second phase of the installation involves interacting with the installation program. During this phase, the program prompts you step by step to enter information. Accompanying the prompts, are explanations of the type of information you need to enter. After you complete the installation, you can look at the installation log files.

Once you have completed the steps described in this chapter, complete the applicable post-installation tasks described in Chapter 4, Post-Installation Tasks of Policy Agent 2.2 for Sun Java System Application Server 8.1.

Installation Related Information About Agent for Sun Java System Application Server 8.1

The following sections provide important information about Policy Agent 2.2 for Sun Java System Application Server 8.1 needed before you install the agent.

Supported Platforms and Compatibility of Agent for Sun Java System Application Server 8.1

The following sections provide information about the supported platforms of Policy Agent 2.2 for Sun Java System Application Server 8.1 as well as the compatibility of this agent with Access Manager.

Platform and Version Support of Agent for Sun Java System Application Server 8.1

The following table presents the platforms supported by Policy Agent 2.2 for Sun Java System Application Server 8.1.

Compatibility of Agent for Sun Java System Application Server 8.1 With Access Manager

Compatibility of Policy Agent 2.2 With Access Manager 7 and Access Manager 7.1.

All agents in the Policy Agent 2.2 release are compatible with Access Manager 7 and Access Manager 7.1. Compatibility applies to both of the available modes of Access Manager: Realm Mode and Legacy Mode.

Install the latest Access Manager patches to ensure that all enhancements and fixes are applied. For an example of Access Manager patches that can be installed, see the compatibility information discussed in Sun Java System Access Manager Policy Agent 2.2 Release Notes.

Compatibility of Policy Agent 2.2 With Access Manager 6.3

All agents in Policy Agent 2.2 are also compatible with Access Manager 6.3 Patch 1 or greater. However, certain limitations apply. For more information, see J2EE Agent Backward Compatibility With Access Manager 6.3.

Domain Administration Server

Domain Administration Server (DAS) is an integral concept of Sun Java System Application Server 8.1. Installing the J2EE agent on Sun Java System Application Server 8.1 while not understanding the DAS concept can lead to complications. The following cautionary note describes one potential complication that can arise.

Once a J2EE agent is installed for a specific domain, the J2EE agent binaries cannot be used on that same host for a different Sun Java System Application Server 8.1 domain. If you attempt to use previously installed J2EE agent binaries on the same host, but on a different domain, the installation fails. For more information, see Installing a J2EE Agent for a Sun Java System Application Server 8.1 Instance on a Different Server Domain.

To protect content on Sun Java System Application Server 8.1 using an agent, you need to understand DAS. The following is a brief description of administrative domains and how they pertain to DAS.

Administrative domains provide a basic security structure whereby different administrators can administer specific groups (domains) of Sun Java System Application Server 8.1 instances. By grouping the server instances into separate domains, different organizations and administrators can share a single Sun Java System Application Server 8.1 installation.

Each domain has its own configuration, log files, and application deployment areas that are independent of other domains. If the configuration is changed for one domain, the configurations of other domains are not affected. Each domain has its own DAS, with a unique port number.

For more information on DAS and administrative domains, see the Sun Java System Application Server 8.1 Administration Guide.

Preparing to Install Agent for Sun Java System Application Server 8.1

Detailed information about unpacking the distribution files for J2EE agents in Policy Agent 2.2 is covered in Chapter 2, Vital Installation Information for a J2EE Agent in Policy Agent 2.2. The best practice is to follow the detailed steps outlined in that chapter before you implement any steps outlined in this chapter.

The following examples provide quick details about the unpacking process. Furthermore, this section provides the opportunity to present again the cautionary note that follows about the GNU_tar program.

For .tar.gz archives, do not use a program other than GNU_tar to untar the contents of the J2EE agent deliverables. Using a different program, such as another tar program, can result in some files not being extracted properly. To learn more about the GNU_tar program, visit the following web site:

http://www.gnu.org/software/tar/tar.html

Example 3–1 Format of the Distribution Files of Agent for Sun Java System Application Server 8.1

SJS_Appserver_81_agent_2.2.tar.gz
SJS_Appserver_81_agent_2.2.zip
SJS_Appserver_81_agent_2.2_SUNWamas.tar.gz

For detailed information on the format of the distribution files, see Format of the Distribution Files for a J2EE Agent Installation in Policy Agent 2.2.

Example 3–2 Unpacking Non-Package Formatted Deliverables of Agent for Sun Java System Application Server 8.1

# gzip -dc SJS_Appserver_81_agent_2.2.tar.gz | tar xvf -

For detailed information about this command, see To Unpack Non-Package Formatted Deliverables of a J2EE Agent in Policy Agent 2.2.

Example 3–3 Unpacking Package Formatted Deliverables of Agent for Sun Java System Application Server 8.1

# gzip -dc SJS_Appserver_81_agent_2.2_SUNWamas.tar.gz | tar xvf -

For detailed information about this command, see To Unpack Package Formatted Deliverables of a J2EE Agent in Policy Agent 2.2.

Example 3–4 Unpacking a .zip Compressed file of Agent for Sun Java System Application Server 8.1

unzip SJS_Appserver_81_agent_2.2.zip

For detailed information about this command, see To Unpack a .zip Compressed file of a J2EE Agent in Policy Agent 2.2.

Follow the specific steps outlined in the following section before you install the agent to reduce the chance of complications occurring during and after the installation.

To Prepare to Install Agent for Sun Java System Application Server 8.1

Perform the following pre-installation tasks:

1. Ensure that the Policy Agent 2.2 for Sun Java System Application Server 8.1 is supported on the desired platform as listed in Supported Platforms and Compatibility of Agent for Sun Java System Application Server 8.1.

2. Install Sun Java System Application Server 8.1 if not already installed.

   Refer to Sun Java Enterprise System installation-related documentation for information about installing Sun Java System Application Server 8.1. For example, see Sun Java Enterprise System 2005Q4 Installation Planning Guide and Sun Java Enterprise System 2005Q4 Installation Guide for UNIX. Also see Sun Java System Application Server 8.1 documentation, such as the Sun Java System Application Server 8.1 Administration Guide.

3. Ensure that the following servers are shut down:

   • Domain Administration Server (DAS)

   • Sun Java System Application Server 8.1 instance that will be protected by the agent

4. Create a valid agent profile in Access Manager Console if one has not already been created.

   For information on how to create an agent profile, see Creating a J2EE Agent Profile.

   To avoid a misconfiguration of the agent, ensure that you know the exact ID and password used to create the agent profile. You must enter the agent profile password correctly in the next step and you must enter the agent profile ID correctly when installing the agent.

5. Create a text file and add the agent profile password to that file.

   Ensure that this file is located in a secure directory of your choice. You will refer to this file during the agent installation process.

   With the agent profile password in this file, stored in a secure location, you do not need to enter sensitive information in the console. A valid password file can have only one line that contains the agent profile password.

Launching the Installation Program of Agent for Sun Java System Application Server 8.1

Once you have performed all the pre-installation steps, you can launch the installation program as described in the following subsection.

To Launch the Installation Program of Agent for Sun Java System Application Server 8.1

To launch the installation program, perform the following steps:

1. Change to the following directory:

   PolicyAgent-base/bin

   This directory contains the agentadmin program, which is used for installing a J2EE agent and for performing other tasks. For more information on the agentadmin program, see Role of the agentadmin Program in a J2EE Agent for Policy Agent 2.2.

2. Issue the following command:

   ./agentadmin --install

3. (Conditional) If you receive license agreement information, accept or reject the agreement prompts. If you reject any portion of the agreement, the program will end.

   The license agreement is displayed only during the first run of the agentadmin program.

Using the Installation Program of Agent for Sun Java System Application Server 8.1

After you issue the agentadmin command and accept the license agreement (if necessary) the installation program appears, prompting you for information.

The steps in the installation program are displayed in this section in an example interaction. Your answers to prompts can differ slightly or greatly from this example depending upon your specific deployment. In the example, most of the defaults have been accepted. This example is provided for your reference and does not necessarily indicate the precise information you should enter.

The following bulleted list provides key points about the installation program.

• Each step in the installation program includes an explanation that is followed by a more succinct prompt.

• For most of the steps you can type any of the following characters to get the results described:

  ?

  Type the question mark to display Help information for that specific step.

  <

  Type the left arrow symbol to go back to the previous interaction.

  !

  Type the exclamation point to exit the program.

• Most of the steps provide a default value that can be accepted or replaced. If a default value is correct for your site, accept it. If it is not correct, enter the correct value.

About Installation Prompts in Agent for Sun Java System Application Server 8.1

The following list provides information about specific prompts in the installation. Often the prompt is self explanatory. However, at other times you might find the extra information presented here to be very helpful. This extra information is often not obvious. Study this section carefully before issuing the agentadmin --install command.

The Deployment URI for the Agent Application

The deployment URI for the agent application is required for the agent to perform necessary housekeeping tasks such as registering policy and session notifications, legacy browser support, and CDSSO support. Accept /agentapp as the default value for this interaction. Once the installation is completed, browse the directory PolicyAgent-base/etc. Use the agentapp.war file to deploy the agent application in the application container. Please note that the deployment URI for agent application during install time should match the deployment URI for the same application when deployed in the J2EE container.

The Encryption Key

This key is used to encrypt sensitive information such the passwords. The key should be at least 12 characters long. A key is generated randomly and provided as the default. You can accept the random key generated by the installer or create your own using the .agentadmin --getEncryptKey command.

For information about creating a new encryption key, see agentadmin --getEncryptKey.

The Agent Profile Name

An agent profile should have been created as a pre-installation step. The creation of the agent profile is mentioned in that section. For the pre-installation steps, see Preparing to Install Agent for Sun Java System Application Server 8.1. For the actual information on creating an agent profile, see Creating a J2EE Agent Profile.

In summary, the J2EE agent communicates with Access Manager with a specific ID and password created through an agent profile using Access Manager Console. For J2EE agents, the creation of an agent profile is mandatory. Access Manager uses the agent profile to authenticate an agent. This is part of the security infrastructure.

The J2EE Password File

The J2EE password file should have been created as a pre-installation step. For the pre-installation steps, see Preparing to Install Agent for Sun Java System Application Server 8.1.

When the installation program prompts you for the password for the agent, enter the fully qualified path to this password file.

After you have completed all the steps, a summary of your responses appears followed by options that allow you to navigate through those responses to accept or reject them.

When the summary appears, note the agent instance name, such as agent_001. You might be prompted for this name during the configuration process.

About the options, the default option is 1, Continue with Installation.

• If you are satisfied with the summary, choose 1 (the default).

• If you want to edit input from the last interaction, choose 2.

• If you want to edit input starting at the beginning of the installation program, choose 3.

• If you want to exit the installation program without installing, choose 4.

You can edit your responses as necessary, return to the options list, and choose option 1 to finally process your responses.

Example of Installation Program Interaction in Agent for Sun Java System Application Server 8.1

The following example is a sample installation snapshot of Policy Agent 2.2 for Sun Java System Application Server 8.1. By no means does this sample represent a real deployment scenario.

This sample represents an installation that is not on a remote server instance host. Installations on remote server instance hosts receive two additional prompts that are not present in this example. The section following this example, Implications of Specific Deployment Scenarios in Agent for Sun Java System Application Server 8.1, explains specific deployment scenarios, such as for remote servers. If any of these deployment scenarios apply to your deployment, you might need to respond to prompts in a specified manner during the installation as explained in that section. Review the explanations in that section before proceeding with the installation. Those explanations are divided into subsections as follows:

• Installing a J2EE Agent on Multiple Sun Java System Application Server 8.1 Instances on the Same Domain

• Installing a J2EE Agent for a Sun Java System Application Server 8.1 Instance on a Different Server Domain

• Installing a J2EE Agent on a Remote Sun Java System Application Server 8.1 Instance

• Installing Agent for Sun Java System Application Server 8.1 on the Access Manager Host

************************************************************************
Welcome to the Access Manager Policy Agent for Sun Java(TM) Application Server 8.1
************************************************************************
Enter the complete path to the directory which is used by Application Server to store 
its configuration Files. This directory uniquely identifies the Application Server 
instance that will be secured by this Agent.
[ ? : Help, ! : Exit ]
Enter the Application Server Config Directory Path
[/var/opt/SUNWappserver/domains/domain1/config]:

Enter the name of the Application Server instance that will be secured by this Agent .
[ ? : Help, < : Back, ! : Exit ]
Enter the Application Server Instance name [server]:

Enter the fully qualified host name of the server where Access Manager Services are 
installed.
[ ? : Help, < : Back, ! : Exit ]
Access Manager Services Host: subcompany22.company22.example.com

Enter the port number of the Server that runs Access Manager Services.
[ ? : Help, < : Back, ! : Exit ]
Access Manager Services port [80]: 58080

Enter http/https to specify the protocol used by the Server that runs Access Manager 
services.
[ ? : Help, < : Back, ! : Exit ]
Access Manager Services Protocol [http]: http

Enter the Deployment URI for Access Manager Services.
[ ? : Help, < : Back, ! : Exit ]
Access Manager Services Deployment URI [/amserver]:

Enter the fully qualified host name on which the Application Server protected by the agent 
is installed.
 [ ? : Help, < : Back, ! : Exit ]
Enter the Agent Host name: employee.company22.example.com

Enable this field only when the agent is being installed on a remote server
instance host.
[ ? : Help, < : Back, ! : Exit ]
Is Domain administration server host remote ? [false]:

Enter the preferred port number on which the application server provides its services.
 [ ? : Help, < : Back, ! : Exit ]
Enter the port number for Application Server instance [80]: 8080

Select http or https to specify the protocol used by the Application server instance that 
will be protected by Access Manager Policy Agent.
[ ? : Help, < : Back, ! : Exit ]
Enter the Preferred Protocol for Application Server instance [http]: http

Enter the deployment URI for the Agent Application. This Application is used by the agent 
for internal housekeeping.
[ ? : Help, < : Back, ! : Exit ]
Enter the Deployment URI for the Agent Application [/agentapp]: :

Enter a valid Encryption Key.
[ ? : Help, < : Back, ! : Exit ]
Enter the Encryption Key [sLK2JGqkJdFYArPYH6v2Md+HTKKmkif7JD]:

Enter a valid Agent profile name. Before proceeding with the agent 
installation, please ensure that a  valid Agent profile exists in Access 
Manager.
[ ? : Help, < : Back, ! : Exit ]
Enter the Agent Profile name: exampleagent

Enter the path to a file that contains the password to be used for identifying the Agent.
[ ? : Help, < : Back, ! : Exit ]
Enter the path to the password file: /export/temp/passwordfile

Enter true only if agent is being installed on a remote instance from the
Domain Administration server host.
[ ? : Help, < : Back, ! : Exit ]
Is the agent being installed on the DAS host for a remote instance ? [false]:

Enter true if the Agent is being installed on the same instance of Application
Server on which Access Manager is deployed. Enter false if that is not the
case.
[ ? : Help, < : Back, ! : Exit ]
Are the Agent and Access Manager installed on the same instance of
Application Server ? [false]:


*********************************************************
SUMMARY OR YOUR RESPONSES
*********************************************************

Application Server Config Directory :
/var/opt/SUNWappserver/domains/domain1/config
Application Server Instance name : server
Access Manager Services Host : subcompany22.company22.example.com
Access Manager Services Port : 58080
Access Manager Services Protocol : http
Access Manager Services Deployment URI : /amserver
Agent Host name : employee.company22.example.com
Application Server Instance Port number : 8080
Protocol for Application Server instance : http
Deployment URI for the Agent Application. : /agentapp
Encryption Key : sLK2JGqkJdFYArPYH6v2Md+HTKKmkif7JD
Agent Profile name : exampleagent
Agent Profile Password file name : /export/temp/passwordfile

Verify your settings above and decide from the choices below.
1. Continue with Installation
2. Back to the last interaction
3. Start Over
4. Exit
Please make your selection [1]:

         

Implications of Specific Deployment Scenarios in Agent for Sun Java System Application Server 8.1

The following sections refer to specific deployment scenarios involving Policy Agent 2.2 for Sun Java System Application Server 8.1. These scenarios are likely to affect how you respond to prompts during the installation process. You might also need to perform additional configurations.

Installing a J2EE Agent on Multiple Sun Java System Application Server 8.1 Instances on the Same Domain

Once a J2EE agent is installed for a particular domain configuration directory, you can install the agent on more than one Sun Java System Application Server 8.1 instance associated with the same domain by running the agentadmin --install command. Once prompted to enter the appropriate server instance name, enter the domain configuration directory and unique instance name that will enable the agent to distinguish the first instance from consecutive instances.

Installing a J2EE Agent for a Sun Java System Application Server 8.1 Instance on a Different Server Domain

Once a J2EE agent is installed for a specific domain, the J2EE agent binaries cannot be used on that same host for a different Sun Java System Application Server 8.1 domain. If you attempt to use previously installed J2EE agent binaries on the same host, but on a different domain, the installation fails.

J2EE agents associate a specific set of agent binaries with a particular domain for Sun Java System Application Server 8.1. If you want to install a J2EE agent on a different domain, unpack a new set of bits and copy them to a separate location before running the agentadmin --install command for the second domain.

Installing a J2EE Agent on a Remote Sun Java System Application Server 8.1 Instance

The agent installation for each remote Sun Java System Application Server 8.1 instance requires one installation run on the remote host and one configuration run for the remote agent on the DAS host. The following task is based on the assumption that the remote instance has been set up correctly.

To install Sun Java System Application Server 8.1 on a Remote Application Server 8.1 Instance

Before You Begin

Shutdown both the DAS domain and remote server instance before installing Agent for Sun Java System Application Server 8.1.

1. Install Agent for Sun Java System Application Server 8.1 on a remote server instance.

   For general information on installing the agent, see Using the Installation Program of Agent for Sun Java System Application Server 8.1.

   During the installation of this instance of the agent, answer the following questions as indicated.

   Enable this field only when the agent is being installed on a remote server instance host. [ ? : Help, < : Back, ! : Exit ] Is Domain administration server host remote ? [false]: True Enter true only if agent is being installed on a remote instance from the Domain Administration server host. [ ? : Help, < : Back, ! : Exit ] Is the agent being installed on the DAS host for a remote instance ? [false]: false

2. Install Agent for Sun Java System Application Server 8.1 on DAS host for the same remote server instance.

   During the installation of this instance of the agent, answer the following questions as indicated.

   Enable this field only when the agent is being installed on a remote server instance host. [ ? : Help, < : Back, ! : Exit ] Is Domain administration server host remote ? [false]: false Enter true only if agent is being installed on a remote instance from the Domain Administration server host. [ ? : Help, < : Back, ! : Exit ] Is the agent being installed on the DAS host for a remote instance ? [false]: true

   The following two questions are asked only when the answer to the previous question is true:

   Enter the value of the agent instance name provided by the agent installation on the remote instance. [ ? : Help, < : Back, ! : Exit ] Agent instance name []: agent_001

   ---

   Note –

   agent_001, as indicated as the response to the to the preceding prompt, is the agent instance name generated in Step 1 for the remote server instance. The agent installation generates an agent instance name, which is displayed at the end of the installation and is available in the install log. The instance name must be valid.

   ---

   Enter the value of the agent install directory on the remote instance host. [ ? : Help, < : Back, ! : Exit ] Agent install directory on remote instance host [/opt/j2ee_agents/am_as81_agent]:

   For the preceding prompt, enter the directory where the agent has been installed on the remote server instance host. This is the agent binary directory on the remote server instance host, not the agent binary directory on the DAS host.

3. Edit the appropriate files to allow the agent to work on the remote server instance as indicated in the following substeps:

   1. On the DAS host, open the DAS domain's domain.xml file.

      The following is an example of a full path to the domain.xml file:

      /var/opt/SUNWappserver/domains/domain1/config/domain.xml

   2. Delete the following code snippet:

      <jvm-options>
      -Djava.util.logging.config.file=PolicyAgent-base-on-DAS-host
      /j2ee_agents/am_as81_agent/config/AMAgentLogConfig.properties
      </jvm-options>

   3. Add the following code snippet:

      <jvm-options>
      -Djava.util.logging.config.file=
      PolicyAgent-base-on-remote-server-instance-host
      /j2ee_agents/am_as81_agent/config/AMAgentLogConfig.properties
      </jvm-options> 

   4. On the DAS host, open the DAS domain's server.policy file.

   5. Delete the following code snippet:

      grant codeBase "file:PolicyAgent-base-on-DAS-host/
      j2ee_agents/am_as81_agent/lib/*" {
             permission java.security.AllPermission;
      };

   6. Add the following code snippet:

      grant codeBase "file:PolicyAgent-base-on-remote-server-instance-host/
      j2ee_agents/am_as81_agent/lib/*" {
             permission java.security.AllPermission;
      };

Installing Agent for Sun Java System Application Server 8.1 on the Access Manager Host

If a J2EE agent and Access Manager are collocated on the same container, enter true for the following question:

Enter true if the Agent is being installed on the same instance of Application
Server on which Access Manager is deployed. Enter false if that is not the
case.
[ ? : Help, < : Back, ! : Exit ]
Are the Agent and Access Manager installed on the same instance of
Application Server ? [false]: true

In this case, the agentadmin program will make the necessary changes to install and configure the agent on the same Sun Java System Application Server 8.1 instance that hosts Access Manager.

However, this deployment scenario changes the agent configuration in a manner that requires your attention. For details, see Combining J2EE Agents With Access Manager.

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 Sun Java System Application Server 8.1.

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 Sun Java System Application Server 8.1.

Example 3–5 Policy Agent Base Directory of Agent for Sun Java System Application Server 8.1

The following directory represents PolicyAgent-base of Agent for Sun Java System Application Server 8.1:

Agent-HomeDirectory/j2ee_agents/am_as81_agent

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:

SUMMARY OF AGENT INSTALLATION
-----------------------------
Agent instance name: agent_001
Agent Configuration file location:
PolicyAgent-base/agent_001/config/AMAgent.properties
Agent Audit directory location:
PolicyAgent-base/agent_001/logs/audit
Agent Debug directory location:
PolicyAgent-base/agent_001/logs/debug

Install log file location:
PolicyAgent-base/logs/audit/install.log

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.

PolicyAgent-base/agent_001/config/AMAgent.properties

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:

• Appendix B, J2EE Agent AMAgent.properties Configuration File in Policy Agent 2.2

• Key Features and Tasks Performed With the J2EE AMAgent.properties Configuration File

PolicyAgent-base/agent_001/logs/audit

Location of the J2EE agent local audit trail.

PolicyAgent-base/agent_001/logs/debug

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

PolicyAgent-base/logs/audit/install.log

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.