Common Post-Installation Steps for All J2EE Version 2.2 Agents

The following tasks described in this section apply to all J2EE agent installations:

• Updating the Agent Profile for Version 2.2 J2EE Agents

• Deploying the Agent Application for Version 2.2 J2EE Agents

Updating the Agent Profile for Version 2.2 J2EE Agents

This procedure is not required. The agent profile is created and updated in Access Manager Console. The agent profile should originally be created prior to installing an agent. However, after you install a J2EE agent, you can update the agent profile at anytime. If you do update the agent profile in Access Manager Console, you must then configure the J2EE agent accordingly as described in this section.

To Update the Agent Profile for Version 2.2 J2EE Agents

Before You Begin

Change the agent profile in Access Manager using the Access Manager Console. For more information about the agent profile, see Creating a J2EE Agent Profile.

1. Change the password in the password file to match the new password you just created in the Access Manager Console as a part of the agent profile.

   The password file should originally have been created as a J2EE agent pre-installation task. For more information about pre-installation, see Preparing to Install the IBM WebSphere Portal Server 6.0 Agent.

2. In the command line, issue the agentadmin --encrypt command to encrypt the new password.

   For more information on this command, see agentadmin --encrypt.

3. Access the J2EE agent AMAgent.properties configuration file at the following location:

   PolicyAgent-base/AgentInstance-Dir/config

4. In this configuration file, edit the property for the agent ID to match the new ID in the agent profile as follows:

   com.sun.identity.agents.app.username = agentID
   

   where agentID represents the new agent ID that you created for the agent profile in the Access Manager Console.

5. Edit the property for the agent password as follows:

   com.iplanet.am.service.secret = encryptedPassword
   

   where encryptedPassword represents the new encrypted password you created when you issued the agentadmin --encrypt command.

6. Restart the J2EE agent container.

   The container must be restarted because neither property that you edited in this task is hot-swap enabled.

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.