Sun OpenSSO Enterprise Policy Agent 3.0 User's Guide for Web Agents

Web Agent Directory Structure in Policy Agent 3.0

The Policy Agent installation directory is referred to as the Policy Agent base directory (or PolicyAgent-base in code examples). The location of this directory and its internal structure are important facts that are described in this section.

Location of the Web Agent Base Directory in Policy Agent 3.0

Unpacking the web agent binaries creates a directory named web_agents, within which an agent-specific directory is created. Therefore, this directory name is different for each agent. For example, sjsws_agent is the directory name applicable to Agent for Sun Java System Web Server.

This agent-specific directory is the Policy Agent base directory, referred to throughout this guide as the PolicyAgent-base directory. For the full path to the PolicyAgent-base directory, see Example 3–1, which follows.

Example 3–1 Policy Agent Base Directory

The directory you choose in which to unpack the web agent binaries is referred to here as Agent-HomeDirectory. For illustration purposes, the following example uses Policy Agent 3.0 for Sun Java System Web Server 7.0 to demonstrate the path to the PolicyAgent-base. Be aware, that the directory sjsws_agent is only an example. This directory will vary from agent to agent:


References in this book to the PolicyAgent-base directory are references to the preceding path.

Inside the Web Agent Base Directory in Policy Agent 3.0

After you finish installing an agent by issuing the agentadmin ---install command and interacting with the installer, you will need to access web agent files in order to configure and otherwise work with the product. Within the Policy Agent base directory are various subdirectories that contain all agent configuration and log files. The structure of the Policy Agent base directory for a web agent is illustrated in Table 3–1.

The list that follows the table provides information about many of the items in the example Policy Agent base directory. The Policy Agent base directory is represented in this guide in code examples as PolicyAgent-base. The full path to any item in this directory is as follows:


where item-name represents the name of a file or subdirectory. For example, the full path to the bin directory is as follows:

Table 3–1 Example of Policy Agent Base Directory for a Web Agent

Directory Contents: Files and Subdirectories 











The preceding example of PolicyAgent-base lists files and directories you are likely to find in this directory. The notable items in this directory are summarized in the list that follows:


This directory contains the agentadmin script for the agent bits. You will use this script a great deal. For details about the tasks performed with this script, see Role of the agentadmin Program in Policy Agent 3.0.


This directory contains installation-related log files, for example log files created after you issue the agentadmin command.

Log information is stored in the installation log file after you install a web agent instance. The following is the location of this log file:



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


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


This directory has all the installer specific data.

Caution – Caution –

Do not edit any of the files in the data directory under any circumstance. If this directory or any of its content loses data integrity, the agentadmin program cannot function normally.


The full path for this directory is as follows:


where AgentInstance-Dir refers to an agent instance directory, which in this case is Agent_001.

Note –

This directory does not exist until you successfully install the first instance of a web 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 a web 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.

Furthermore, the string “Agent” in Agent_00x is configurable. You can change this string by editing the following file: PolicyAgent-base/config/ Search for the following setting:

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


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 web agent is uninstalled, the config directory is removed from the agent instance directory but the logs directory still exists.

The following table is an example of the contents of an agent instance, such as Agent_001, directory.

Example of an Agent Instance (Agent_001) Directory





Two subdirectories exist within this directory as follows:


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


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.


This directory contains the file and the file, which are specific to the agent instance. The file applies regardless of the agent configuration: centralized in the OpenSSO Enterprise server or local to the agent. However, the file is only meaningful when an agent instance is configured locally. In that scenario, the file holds the key to the agent behavior at runtime.