Sun Java System Access Manager Policy Agent 2.2 Guide for BEA WebLogic Server 9.0/9.1

Deploying the Agent Application for J2EE Agents in Policy Agent 2.2

Note –

Do not perform this task in the order it appears in this document. This task is described in this section with other tasks that are common to all agents, even though this particular task should be performed in the order indicated by the location of following section, Deploying the Agent Application.

The task described in this section is required. Deploy the URI for the agent application using the deployment container. 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 and can be found at the following location:


where extension refers to the .war extension or the .ear extension. The extension varies depending on the deployment container.

For more information about the Policy Agent base directory (PolicyAgent-base), see J2EE Agent Directory Structure in Policy Agent 2.2.

The agentapp application has to be deployed as a post installation step. In order for the agent to function correctly, this application must be deployed on the agent-protected deployment container instance using the same URI that was supplied during the agent installation process . For example during the installation process, if you entered /agentapp as the deployment URI for the agent application, then use that same context path to deploy the .war or .ear file in the deployment container. Using the administration console or command-line utilities of your deployment container, deploy this application using Application Context Path as the URI specified during agent installation.