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

The following sections refer to specific deployment scenarios involving Policy Agent 2.2 for BEA WebLogic Server/Portal 8.1 SP4. 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 8.1 SP4 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 8.1 SP4 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 8.1 SP4 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 8.1 SP4 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 8.1 SP4. 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 8.1 SP4 on a Portal Domain

If you are installing Agent forBEA WebLogic Server/Portal 8.1 SP4 on a portal domain, you must perform the steps outlined in this section. First you must answer questions appropriately during the agent installation process. Then you have to perform specific configuration steps as follows:

To Install Agent for BEA WebLogic Server/Portal 8.1 SP4 on a Portal Domain: Installer Prompts

Perform the steps in this task during the installation:

1. Enter true to following prompt:

   Enter true if the agent is being installed on a Portal domain [ ? : Help, < : Back, ! : Exit ] Is the agent being installed on a Portal domain ? [false]: true

   By answering true to this question, you cause the installer to generate another prompt, which is presented in the following step.

2. Provide the correct deployment URI as requested by the following prompt:

   Enter the Deployment URI for the portal application that is protected by the agent. [ ? : Help, < : Back, ! : Exit ] Enter the Deployment URI for the portal Application [/]: /myportal

To Install Agent for BEA WebLogic Server/Portal 8.1 SP4 on a Portal Domain: Configuration

After the installation program has finished, perform the following steps:

1. Configure the Agent Authenticator.

   For detailed information about configuring the Agent Authenticator, see Configuring the Agent Authentication Provider on Agent for BEA WebLogic Server/Portal 8.1 SP4

2. Create the portal users in the Portal Administrator.

   You must create the same users in the portal server that exist in Access Manager.

3. (Optional) Edit the J2EE agent AMAgent.properties configuration file to suit your site's requirement.

   The following properties influence the configuration of the portal domain:

   com.sun.identity.agents.config.logout.uri[] =

   This property is a map construct that is application specific. It identifies a request URI which indicates a logout event.

   com.sun.identity.agents.config.logout.request.param[] =

   This property is a map construct that is application specific. It identifies a parameter which when present in the HTTP request indicates a logout event.

   com.sun.identity.agents.config.logout.introspect.enabled = false

   This property is a flag that allows the agent to search an HTTP request body for a logout parameter.

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

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/Portal 8.1 SP4 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.