Deploying the Agent Application for Version 2.2 J2EE Agents

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:

PolicyAgent-base/etc/agentapp.extension

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 (optionally, you can add a hyper link to and from the relevant prompt). 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 the deployment container, deploy this application using Application Context Path as the URI specified during agent installation.

For IBM WebSphere Application Server and IBM WebSphere Portal Server 6.0 only, the agentapp.extension must be bound to both listening ports used by the WebSphere Administration Server instance and the WebSphere Portal Server instance.

For example, to bind the agentapp.extension to both listening ports:

1. From the Administration console, deploy agentapp.extension to the virtual host admin_host.

2. In the Administration console:

   1. Click Environment, Virtual Hosts, and then admin_host.

   2. Select Host Aliases and then click New.

   3. Specify * in the Host Name field and 10038 in the Port field.

   4. Click Apply, save link, and then Save.

      In this example, 10038 is the Portal Server instance's port.

3. Restart both the Administration server instance and the Portal Server instance.