Sun and OracleChannel SunHow to BuyLog InРусский

Sun Java System Access Manager Policy Agent 2.2 Guide for BEA WebLogic Server 9.0/9.1
  Искать только в названиях книг
Помощь для поиска
Содержащиеся в
Найти другие документы
Ресурсы поддержки
 Загрузить это руководство в формате PDF (1360 КБ)

Chapter 5 Installing and Configuring Policy Agent 2.2 for BEA WebLogic Server 9.0/9.1: Cluster

Installing the Agent for BEA WebLogic Server 9.0/9.1 in a clustered environment is very similar to the installation process for a stand-alone environment. However, take great care configuring the BEA WebLogic Server 9.0/9.1 Administration Server and its Managed Servers. You must install the agent on the Administration Server in addition to each Managed Server that you want the agent to protect.

Caution – Caution –

The installation and configuration of the agent bits on the Administration Server are required to set up the Agent Authenticator for the entire domain. First, install the agent on the Administration Server. Next configure the Agent Authenticator. These two tasks must be complete before you install a Managed Server that is associated with the same domain. Do not install the Agent Authenticator on one of these Managed Servers. Failure to follow these guidelines can render the BEA WebLogic Server 9.0/9.1 deployment inaccessible.

Installing Agent for BEA WebLogic Server 9.0/9.1 on the Administration Server

Install the first instance of Agent for BEA WebLogic Server 9.0/9.1 on the Administration Server. The following is a relatively involved task description that directs you to other sections of this guide. When finished, install any subsequent agent instances on Managed Servers.

ПроцедураTo Install Agent for BEA WebLogic Server 9.0/9.1 on the Administration Server

  1. Ensure that the BEA WebLogic Server 9.0/9.1 Administration Server is not running.

  2. Install Agent for BEA WebLogic Server 9.0/9.1 as you would in a stand-alone environment.

    See Chapter 3, Installing Policy Agent 2.2 for BEA WebLogic Server 9.0/9.1 for detailed steps.

  3. Configure the agent classpath for BEA WebLogic Server 9.0/9.1 Administration Server by following the steps outlined in Configuring BEA WebLogic Server 9.0/9.1 Instance With Agent Classpath and Agent Java Options.

  4. Start the BEA WebLogic Server 9.0/9.1 Administration Server.

  5. Configure the Agent Authentication Provider.

    See Configuring the Agent Authentication Provider on Agent for BEA WebLogic Server 9.0/9.1 for details.

Installing Agent for BEA WebLogic Server 9.0/9.1 on a Managed Server

You can start Managed Servers in a clustered environment using command-line scripts or using BEA WebLogic Server 9.0/9.1 Administration Console, specifically using the Node Manager. Both options are supported by Agent for BEA WebLogic Server 9.0/9.1. This section describes installing and configuring the agent on a Managed Server to enable you to start a Managed Server with scripts. For information on installing and configuring Node Manager in order to start a Managed Server using Node Manager, see Configuring Node Manager With Agent for BEA WebLogic Server 9.0/9.1: Clustered Setup.

ПроцедураTo Install Agent for BEA WebLogic Server 9.0/9.1 on a Managed Server

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. Ensure that the BEA WebLogic Server 9.0/9.1 Managed Server is not running.

  2. Copy the startManagedWebLogic.sh script to an instance specific script on which the agent will be installed as illustrated by the following example:

    startManagedWebLogic.sh

    to

    start_new_Server_1.sh

  3. Edit the newly copied script by hard coding the following variables:

    • SERVER_NAME

    • ADMIN_URL

    The following is an example of these two variables hard coded:

    ADMIN_URL="http://example.company.com:7001"
SERVER_NAME="new_Server_1"

  4. Install Agent for BEA WebLogic Server 9.0/9.1 as you would in a stand-alone environment, pointing the startup script location to the Managed Server script name. For example, start_new_Server_1.sh, start_new_Server_2.sh, and such.

    See Chapter 3, Installing Policy Agent 2.2 for BEA WebLogic Server 9.0/9.1 for detailed steps.

  5. Configure the agent classpath for the BEA WebLogic Server 9.0/9.1 Managed Server by following the steps outlined in Configuring BEA WebLogic Server 9.0/9.1 Instance With Agent Classpath and Agent Java Options.

  6. You can now start your Managed Server using the customized script.

    Alternatively, you can start the Managed Servers via the Node Manager. To configure the Node Manager for this purpose, follow the instructions in Configuring Node Manager With Agent for BEA WebLogic Server 9.0/9.1: Clustered Setup.

Post-Installation Tasks of Agent for BEA WebLogic Server 9.0/9.1 in a Clustered Environment

This section describes the post-installation tasks involved with Agent for BEA WebLogic Server 9.0/9.1 in a clustered environment. This deployment involves the configuration of the Administration Server and of one or more Managed Servers. These tasks have, generally, already been documented in Chapter 4, Post-Installation Tasks of Policy Agent 2.2 for BEA WebLogic Server 9.0/9.1. This section directs you to sections in that chapter while discussing details specific to a clustered environment in this chapter.

Add a WebLogic Administrator to the Bypass List of Agent for BEA WebLogic Server 9.0/9.1: Cluster

For information on this task, see Adding a WebLogic Administrator to the Bypass List of Agent for BEA WebLogic Server 9.0/9.1.

Install the Agent Filter for the Deployed Application on Agent for BEA WebLogic Server 9.0/9.1: Cluster

Install the Agent Filter for each application deployed in an Administration Server or Managed Server protected by Agent for BEA WebLogic Server 9.0/9.1. For information on this task, see Installing the Agent Filter for the Deployed Application on Agent for BEA WebLogic Server 9.0/9.1.

Deploy the Agent Application of Agent for BEA WebLogic Server 9.0/9.1: Cluster

Before preceding to this task description, documented in Deploying the Agent Application for J2EE Agents in Policy Agent 2.2, take note of the information provided in this section.

You must deploy the agent application on every instance on which the agent has been installed. Failing to do so might disable the agent notification system on the Managed Servers, which in turn would prevent the agent from receiving important notifications. All agent applications hosted on the same instance use the agent application deployed in that instance. Each Managed Server needs to have the agent application deployed so that no Managed Server instance is dependent upon another Managed Server instance for notifications.

You also have the option of deploying the agent application using the BEA WebLogic Server 9.0/9.1 Administration Console as detailed in the following task description.

ПроцедураTo Deploy the Agent Application in the BEA WebLogic Server 9.0/9.1 Administration Console

If the agent was installed and configured on more than one managed instance, the agent housekeeping application agentapp.war has to be deployed on each and every Managed Server instance. This can be done through the Administration Console. The deployment can have multiple applications protected by the same agent running on the same Managed Server instance. All the applications in the same BEA WebLogic Server 9.0/9.1 server instance use the agent application deployed with this instance.

If more than one instance is being configured and protected by the agent, each Managed Server instance requires that the agent application be deployed. Thereby, no BEA WebLogic Server 9.0/9.1 instance is dependent on any other instance for agent housekeeping operations.

  1. Expand the Deployments tab.

  2. Click the Web Application node.

    A new page appears in the right pane.

  3. In the right pane, click Deploy a new Web Application Module.

  4. Click Upload to upload the agentapp.war file from the following directory:

    PolicyAgent-base/etc/agentapp.war

    When selecting the target for the Web Application module, you have the option of selecting the entire cluster or individual servers. Deploy the agentapp.war file for every server node on which you will install the agent.

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.

ПроцедураTo 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.