Installation Notes

This section describes some of the key points of the installation, configuration, and uninstallation for Sun Java System Access Manager Policy Agent 2.2. Information about installation is divided by agent type as follows:

• Installation Notes for Web Agents in Policy Agent 2.2

• Installation Notes for J2EE Agents in Policy Agent 2.2

See also Policy Agent 2.2 documentation should reference OpenSSO (6857941).

Installation Notes for Web Agents in Policy Agent 2.2

While the functionality of web agents has increased considerably for this release, the installation, post-installation configuration, and uninstallation processes have not changed significantly from the 2.1 release. The following section points out a change in the name of the uninstallation script. Changes in the installation and uninstallation process tend to be along this scale. See the individual web agent guides for detailed information. For a current list of the individual web agent guides, see Supported Servers and Documentation of Web Agents in Policy Agent 2.2 in Sun Java System Access Manager Policy Agent 2.2 User’s Guide.

Uninstallation Script for Web Agents in Policy Agent 2.2

The uninstallation script name for web agents in the 2.2 release has a different suffix for each web container. The suffix is a short name for the web container. For example, the following is the uninstallation script name for Agent for Sun Java System Web Server 6.1:

uninstall_agent_es6

Installation Notes for J2EE Agents in Policy Agent 2.2

The installation and uninstallation processes for this release have changed dramatically. However, the post-installation configuration has not changed as much. For this release, the installation and uninstallation processes rely heavily on the agentadmin program. The directory structure of J2EE agents has also changed significantly. This section briefly describes these aspects of J2EE agents. See the individual J2EE agent guides for detailed information. For a current list of individual J2EE agent guides, see Supported Servers and Documentation of J2EE Agents in Policy Agent 2.2 in Sun Java System Access Manager Policy Agent 2.2 User’s Guide.

Using the agentadmin Program with J2EE Agents

The agentadmin program is a required tool for the 2.2 release of J2EE agents. The most basic of tasks, such as installation and uninstallation can only be performed with this program.

This section lists the tasks you can perform with this program. Moreover, this section lists the specific options you need to issue with the agentadmin command to accomplish each task:

• All agent installation and uninstallation is achieved with the agentadmin command.

• All tasks performed by the agentadmin program, except those involving uninstallation, require the acceptance of a license agreement. This agreement is only presented the first time you use the program.

• The following table lists options that can be used with the agentadmin command and gives a brief description of the specific task initiated by the option.

Table 8 The agentadmin Command: Supported Options

Policy Agent Directories

Agent instance information is stored in its own directory at the following location:

PolicyAgent-base/AgentInstance-Dir

where PolicyAgent-base represents the directory where a J2EE agent is installed

and where AgentInstance-Dir refers to an agent instance directory and represents the directory for a specific instance of a J2EE agent.

Deploying the Agent Application

The following task is a required post-installation step.

Deploy the URI for the agent application using the deployment container, such as the application server.

The agent application is a housekeeping application used by the agent for notifications and other internal functionality. This application is bundled with the agent binaries.

Combining a J2EE Agent With Access Manager (Conditional)

This is a conditional post-installation step that must be performed when a J2EE agent is installed on an deployment container instance where Access Manager has already been installed. Note that Access Manager should be installed prior to the agent being installed.