WebLogic Server/Portal 10 Files and Subdirectories

After you install the WebLogic Server/Portal 10 agent using the agentadmin ---install command, the files and subdirectories shown in Table 2–2 are available under the PolicyAgent-base directory. These files and subdirectories are described in detail after the table.

The files and directories under the PolicyAgent-base directory include:

bin

This directory contains the agentadmin program. For information about the tasks performed with this program, see Role of the agentadmin Program in a J2EE Agent for Policy Agent 2.2.

config

This directory contains configuration files used by the installer.

data

This directory has all the installer specific data.

---

Caution –

Do not edit any of the files in the data or config directories. If these directories or any of their contents lose their data integrity, the agentadmin program cannot function normally.

---

etc

This directory contains the agentapp file (agentapp.war file), which must be deployed after the installation is complete. This application helps the agent perform certain housekeeping tasks.

lib

The lib directory has a list of all the agent libraries that are used by the installer as well as the agent run time.

locale

This directory has all the agent installer information as well as agent run time specific locale information pertaining to the specific agent.

logs

This directory contains various log files, including log files created when you issue the agentadmin command.

This directory also contains the installation log file. For the 2.2 release of Policy Agent, log information is stored in the installation log file after you install a J2EE agent instance. The following is the location of this log file:

PolicyAgent-base/logs/audit/install.log

sampleapp

This directory contains the sample application included with Policy Agent 2.2. This application is extremely useful. Not only does it demonstrate configuration options and features, but the application can be used to test if an agent is running.

Use the sample application that comes with the agent or build the application from scratch. Find instructions for building, deploying, and running this application at the following location:

PolicyAgent-base/sampleapp/readme.txt

The full path to the sample application is as follows:

PolicyAgent-base/sampleapp/dist/agentsample.ear

For more information about the sample application, see The Sample Application.

Agent_001

The full path for this directory is as follows:

PolicyAgent-base/AgentInstance

where AgentInstance refers to an agent instance directory, which is Agent_001.

---

Note –

This directory does not exist until you successfully install the first instance of a J2EE agent. Once you have successfully executed one run of the agentadmin --install command, an agent specific directory, Agent_00x is created in the Policy Agent base directory. This directory is uniquely tied to an instance of the deployment container, such as an application server instance. Depending on the number of times the agentadmin --install command is run, the number that replaces the x in the Agent_00x directory name will vary.

---

After you successfully install the first instance of a J2EE agent, an agent instance directory named Agent_001 appears in the Policy Agent base directory. The path to this directory is as follows:

PolicyAgent-base/Agent_001

The next installation of the agent creates an agent instance directory named Agent_002. The directories for uninstalled agents are not automatically removed. Therefore, if Agent_001 and Agent_002 are uninstalled, the next agent instance directory is Agent_003.

Agent instance directories contain directories named config and logs.

---

Note –

When a J2EE agent is uninstalled, the config directory is removed from the agent instance directory, but the logs directory still exists.

---

logs

Two subdirectories exist within this directory as follows:

audit

This directory contains the local audit trail for the agent instance.

debug

This directory has all the agent-specific debug information. When the agent runs in full debug mode, this directory stores all the debug files that are generated by the agent code.

config

This directory contains the J2EE agent AMAgent.properties configuration file that is specific to the agent instance. Each J2EE agent can be configured by a unique instance of the J2EE agent AMAgent.properties configuration file. This file holds the key to the agent behavior at runtime.