Configuring Node Manager With Agent for BEA WebLogic Server/Portal 9.2: Clustered Setup (Sun Java System Access Manager Policy Agent 2.2 Guide for BEA WebLogic Server/Portal 9.2)

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

Previous: Deploy the Agent Application of Agent for BEA WebLogic Server/Portal 9.2: Cluster
Next: Chapter 6 Managing Policy Agent 2.2 for BEA WebLogic Server/Portal 9.2

Configuring Node Manager With Agent for BEA WebLogic Server/Portal 9.2: Clustered Setup

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

To Configure Node Manager With Agent for BEA WebLogic Server/Portal 9.2: Clustered Setup

Note –

Throughout this guide scripting files apply to both UNIX platforms and Windows platforms even when the script for Windows platforms is not expressly mentioned. The difference is that scripts for UNIX platforms have the .sh extension while scripts for Windows platforms have the .cmd extension.

For the following task description, server-instance is a place holder that represents the Managed Server instance name entered during installation. For example, ManagedServer1.

In the BEA WebLogic Server/Portal 9.2 Administration Console, expand the Servers node.

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

Configure the agent classpath in Node Manager
1. In the BEA WebLogic Server/Portal 9.2 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 class path to the following Classpath text field:
  
  Note –
  A safe practice is to cut and paste agent classpath entries from the setAgentEnv_sever-instance.sh file to avoid any misconfiguration due to typographical errors.
```
${CLASSPATH}:PolicyAgent-base/lib/agent.jar:PolicyAgent-base/
lib/amclientsdk.jar:PolicyAgent-base/locale:PolicyAgent-base/
AgentInstance-Dir/config
```
  where AgentInstance-Dir represents an agent instance directory, such as agent_001.
  
  For information about PolicyAgent-base, see J2EE Agent Directory Structure in Policy Agent 2.2.
5. To the same Classpath text field referred to in the preceding substep, prepend the following classpath entries:
```
DeployContainer-base/BEA-Java-Home/lib/tools.jar:
DeployContainer-base/weblogic92/server/lib/weblogic.jar
```
  DeployContainer-base
  
  represents the directory in which BEA WebLogic Server/Portal 9.2 was installed.
  
  BEA-Java-Home
  
  represents the directory that contains the JDK for the BEA WebLogic Server/Portal 9.2 instance.
6. Click Save.
7. Click Activate Changes.

Configure the agent Java options in Server Start.
1. In the BEA WebLogic Server/Portal 9.2 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 shown:
  
  Note –
  A safe practice is to cut and paste agent Java option entries from the setAgentEnv_sever-instance.sh file to avoid any misconfiguration due to typographical errors.
```
-Djava.util.logging.config.file=PolicyAgent-base/config/
AMAgentLogConfig.properties 
-DLOG_COMPATMODE=Off
```
5. Click Save.
6. Click Activate Changes.