test

Sun Java System Access Manager Policy Agent 2.2 Guide for BEA WebLogic Server 9.0/9.1

Configuring Node Manager With Agent for BEA WebLogic Server 9.0/9.1: Clustered Setup

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

ProcedureTo Configure Node Manager With Agent for BEA WebLogic Server 9.0/9.1: 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.

  1. In the BEA WebLogic Server 9.0/9.1 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 BEA WebLogic Server 9.0/9.1 Administration Console, select the Configuration tab.

    2. Select the Remote Start tab.

    3. Locate the agent classpath for the specific Managed Server as found in setAgentEnv_managed_server_name.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_managed_server_name.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.

  4. Configure the agent java options in Node Manager.

    1. In the BEA WebLogic Server 9.0/9.1 Administration Console, select the Configuration tab.

    2. Select the Remote Start tab.

    3. Locate the java options as found in setAgentEnv_managed_server_name.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_managed_server_name.sh file to avoid any misconfiguration due to typographical errors.

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

      You can now start the Managed Servers in the cluster using the Node Manager in addition to customized scripts.