Common Post-Installation Tasks for All Version 2.2 J2EE Agents

The following task applies to all J2EE agents:

• Deploying the Agent Application for Version 2.2 J2EE Agents

• Updating the Agent Profile for Version 2.2 J2EE Agents

Deploying the Agent Application for Version 2.2 J2EE Agents

The agent application is a housekeeping application used by the agent for notifications and other internal functionality. This application is bundled with the agent 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.

Updating the Agent Profile for Version 2.2 J2EE Agents

Updating the agent profile is optional. You create the agent profile in the Access Manager Console before you install the agent, as described in Creating a J2EE Agent Profile. After you install the agent, you can update the agent profile at anytime, if you wish. If you do update the agent profile in the Access Manager Console, you must then re-configure the agent, as described in this section.

To Update the Agent Profile for Version 2.2 J2EE Agents

Before You Begin

Update 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 theAccess 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 Agent for WebSphere Application Server 6.1.

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 theAccess 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 deployment container.

   You must restart the container because the properties that you edited in this task are not hot-swap enabled.