Post-Installation Tasks for the WebLogic Server/Portal 10 Agent in a Cluster

Table 4 Post-Installation Tasks for the WebLogic Server/Portal 10 Agent in a Cluster

Post-Installation Task	Where to go for Information
Setting the Java Options on IBM AIX Systems	Setting the Java Options on IBM AIX Systems
Adding a WebLogic Administrator to the Bypass List	Adding a WebLogic Administrator to the Bypass List for the WebLogic Server/Portal 10 Agent
Enabling Agent Protection in Web Applications	Installing the Agent Filter for the WebLogic Server/Portal 10 Agent
Deploying the Agent Application in a Cluster	Deploying the Agent Application for the WebLogic Server/Portal 10 Agent in a Cluster
Configuring Node Manager for the WebLogic Server/Portal 10 Agent in a Cluster	Configuring Node Manager for the WebLogic Server/Portal 10 Agent in a Cluster.

For additional tasks, see Post-Installation Tasks for the WebLogic Server/Portal 10 Agent

Deploying the Agent Application for the WebLogic Server/Portal 10 Agent in a Cluster

Deploy the agent application (agentapp.war) on each instance in the cluster on which the agent is installed, including the Administration Server and each Managed Server. Instances in the cluster require the agent application to receive notifications.

A deployment can have multiple applications protected by the same agent running on the same Managed Server instance. All applications hosted on the same Managed Server instance use the agent application deployed for that instance.

Deploy the agent application using either the WebLogic Server command-line tools or Administration Console.

To Deploy the Agent Application Using the WebLogic Server/Portal 10 Administration Console

1. Login to the WebLogic Server/Portal 10 Administration Console

2. Expand the Deployments tab.

3. Click Lock & Edit.

4. In the right pane, click Install.

5. Click upload your file(s).

   Upload the agentapp.war file from the following directory:

   PolicyAgent-base/etc/agentapp.war

   When selecting the target for the Web Application module, select either the entire cluster or individual servers. Deploy the agentapp.war file for each server node on which you installed the agent.

Configuring Node Manager for the WebLogic Server/Portal 10 Agent in a Cluster

You have the option of starting Managed Servers in a cluster using the WebLogic Server/Portal 10 Node Manager.

To Configure Node Manager for the WebLogic Server/Portal 10 Agent in a Cluster

1. In the WebLogic Server/Portal 10 Administration Console, expand the Servers node.

2. Select the node for the server you want to manage with Node Manager.

3. Configure the agent classpath in Node Manager:

   1. In the Administration Console, select the Configuration tab.

   2. Select the Server Start tab.

   3. Locate the agent classpath for the specific Managed Server as found in setAgentEnv_sever-instance.sh.

   4. Add the agent classpath to the following classpath text field:

      ${CLASSPATH}:PolicyAgent-base/lib/agent.jar:PolicyAgent-base/
      lib/openssoclientsdk.jar:PolicyAgent-base/locale:PolicyAgent-base/
      AgentInstance/config

      where AgentInstance represents the agent instance directory, such as Agent_001.

      ---

      Tip –

      To avoid typing errors, copy and paste the agent classpath entries from the setAgentEnv_managed-sever-instance.sh file.

      ---

      managed-server-instance is the name of the Managed Server instance. For example, server1.

   5. To the same classpath text field referred to in the previous step, prepend the following classpath entries:

      DeployContainer-base/BEA-Java-Home/lib/tools.jar:
      DeployContainer-base/wlserver_10.0/server/lib/weblogic.jar

      DeployContainer-base is the directory in whichWebLogic Server/Portal 10 was installed.

      BEA-Java-Home is the directory that contains the JDK for theWebLogic Server/Portal 10 instance.

   6. Click Save.

   7. Click Activate Changes.

4. Configure the agent Java options in Server Start.

   1. In the WebLogic Server/Portal 10 Administration Console, select the Configuration tab.

   2. Select the Server Start tab.

   3. Locate the Java options as found in setAgentEnv_sever-instance .sh for the specific Managed Server.

   4. Add the Java options to the Arguments text field as follows:

      -Djava.util.logging.config.file=PolicyAgent-base/config/
      OpenSSOAgentLogConfig.properties 
      -DLOG_COMPATMODE=Off

      ---

      Tip –

      To avoid typing errors, copy and paste the agent Java option entries from the setAgentEnv_managed-sever-instance.sh file.

      ---

   5. Click Save.

   6. Click Activate Changes.