test

Sun Java System Access Manager Policy Agent 2.2 Guide for BEA WebLogic Server/Portal 10

Implications of Specific Deployment Scenarios for the WebLogic Server/Portal 10 Agent

The following sections refer to specific deployment scenarios involving the WebLogic Server/Portal 10 agent. These scenarios can affect how you respond to prompts during the installation process.

Installing the Agent on Multiple WebLogic Server/Portal 10 Instances on the Same Domain

Once the agent is installed for a particular domain configuration directory, you can install the agent on more than one WebLogic Server/Portal 10 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 the Agent on a Different WebLogic Server/Portal 10 Domain

Caution – Caution –

Once the agent is installed for a specific domain, the agent binaries cannot be used on that same installation for a different WebLogic Server/Portal 10 domain. If you attempt to use previously installed agent binaries on the same installation, but on a different domain, the installation fails.

J2EE agents associate a specific set of agent binaries with a particular domain for WebLogic Server/Portal 10. If you want to install a J2EE agent on a different domain, unzip a new set of bits and copy them to a separate location before running the agentadmin --install command for the second domain.

Installing the WebLogic Server/Portal 10 Agent on the Access Manager Web Container

Currently, BEA WebLogic Server/Portal 10 is not a supported web container for Access Manager. Therefore, do not install the WebLogic Server/Portal 10 agent and Access Manager on the same WebLogic Server/Portal 10 instance. When you install the agent, always choose false (the default) 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]: