Implications of Specific Deployment Scenarios in Agent for WebSphere Application Server 6.1

The following sections refer to specific deployment scenarios involving Policy Agent 2.2 for WebSphere Application Server 6.1. These scenarios are likely to affect how you respond to prompts during the installation process. You might also be required to perform additional configurations.

Installing a J2EE Agent on Multiple WebSphere Application Server 6.1 Instances

Once a J2EE agent is installed for a particular WebSphere Application Server 6.1 instance, you can install the agent on another instance on the same machine by running the agentadmin --install command. Once prompted to enter the appropriate server instance name, enter the server configuration directory and unique instance name that will enable the agent to distinguish the first instance from consecutive instances.

Installing Agent for WebSphere Application Server 6.1 on the Access Manager Host

IBM WebSphere Application Server 6.1 is not supported as a deployment container for Access Manager. Therefore, you must reply false to the following question:

Enter true if the Agent is being installed on the same instance of Application
Server on which Access Manager is deployed. Enter false if that is not the
case.
[ ? : Help, < : Back, ! : Exit ]
Are the Agent and Access Manager installed on the same instance of
Application Server ? [false]: false

For a list of the supported containers, see the Sun Java System Access Manager 7.1 Release Notes or the Sun Java System Access Manager 7 2005Q4 Release Notes.