The following sections refer to specific deployment scenarios involving Policy Agent 2.2 for BEA WebLogic Server 9.0/9.1. These scenarios are likely to affect how you respond to prompts during the installation process. You might also need to perform additional configurations.
Once a J2EE agent is installed for a particular domain configuration directory, you can install the agent on more than one BEA WebLogic Server 9.0/9.1 instance associated with the same domain by running the agentadmin --install command. Once prompted to enter the appropriate server instance name, enter the domain configuration directory and unique instance name that will enable the agent to distinguish the first instance from consecutive instances.
Once a J2EE agent is installed for a specific domain, the J2EE agent binaries cannot be used on that same host for a different BEA WebLogic Server 9.0/9.1 domain. If you attempt to use previously installed J2EE agent binaries on the same host, but on a different domain, the installation fails.
J2EE agents associate a specific set of agent binaries with a particular domain for BEA WebLogic Server 9.0/9.1. If you want to install a J2EE agent on a different domain, unpack a new set of bits and copy them to a separate location before running the agentadmin --install command for the second domain.
If a J2EE agent and Access Manager are collocated on the same container, enter true for 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]: true
In this case, the agentadmin program will make the necessary changes to install and configure the agent on the same BEA WebLogic Server 9.0/9.1 instance that hosts Access Manager.
However, this deployment scenario changes the agent configuration in a manner that requires your attention. For details, see Combining J2EE Agents With Access Manager.