Implications of Specific Deployment Scenarios in Agent for BEA WebLogic Server/Portal 9.2

The following subsections apply to both BEA WebLogic Server 9.2 and BEA WebLogic Portal 9.2.

The subsections that follow refer to specific deployment scenarios involving Policy Agent 2.2 for BEA WebLogic Server/Portal 9.2. These scenarios are likely to affect how you respond to prompts during the installation process. You might also need to perform additional configurations.

Installing a J2EE Agent on Multiple BEA WebLogic Server/Portal 9.2 Instances on the Same Domain

Once a J2EE agent is installed for a particular domain configuration directory, you can install the agent on more than one BEA WebLogic Server/Portal 9.2 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.

Installing a J2EE Agent for a BEA WebLogic Server/Portal 9.2 Instance on a Different Server Domain

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/Portal 9.2 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/Portal 9.2. 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.

Installing Agent for BEA WebLogic Server/Portal 9.2 on the Access Manager Host

The prompt illustrated in this section is presented by the installer of Agent for BEA WebLogic Server/Portal 9.2. However, at the time of the release of this agent, installing Access Manager on BEA WebLogic Server/Portal 9.2 is not supported. Until that support is in place, ensure the following apply:

• Do not install this agent and Access Manager on the same container.

• Accept the default response of false for this prompt.

Once this collocation scenario is supported, if Agent for BEA WebLogic Server/Portal 9.2 and Access Manager are installed on the same container, enter true for the following prompt:

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