Agent Version and Property Configuration: Agent for Oracle Application Server 10g

The instructions presented in this section related to editing the J2EE agent AMAgent.properties configuration file are required for the initial version of Agent for Oracle Application Server 10g. Updated versions of the agent do not require the performance of these configuration instructions. Starting with Policy Agent 2.2 hot patch 4, the configuration instructions presented in this section should not be performed. If you are not certain of the version of this agent, perform the following task about checking the agent version.

To Check the Specific Version of Agent for Oracle Application Server 10g

1. Issue the following command:

   ./agentadmin --version

Next Steps

The preceding command results in the agent issuing version information. If the version indicated is a version prior to hot patch 4, then perform the task that follows. If the version is hot patch 4 or greater, skip the task that follows.

(Conditional) To Configure the J2EE agent AMAgent.properties Configuration File

1. Using the text editor of your choice, access the J2EE agent AMAgent.properties configuration file.

2. Edit the following property as such:

   java.util.logging.config.file = PolicyAgent-base/config/AMAgentLogConfig.properties

   The property was originally set as follows:

   java.util.logging.config.file = PolicyAgent-base/agent_001/config/AMAgentLogConfig.properties

   where agent_001 serves as an example that might be different in your situation depending upon the number of agents that have been installed on the machine.

   Editing the value for this property involves the removal of the following string “agent_001/”

3. Add the following property and value to the bottom of the configuration file:

   com.sun.identity.agents.config.composite.advice.file = PolicyAgent-base/locale/CompositeAdviceForm.txt

4. Save and close the updated J2EE agent AMAgent.properties configuration file.