Skip to ContentSun and Oracle Channel Sun How to Buy Log In

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

Contained Within

Sun Java System Access Manager Policy Agent 2.2

Find More Documentation

Featured Support Resources

Scarica il manuale in formato PDF (1403 KB)

Chapter 5 Installing and Configuring the WebLogic Server/Portal 10 Agent in a Cluster

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

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. You do not need to configure the Agent Authenticator for any Managed Servers. Failure to follow these guidelines can render the WebLogic Server/Portal 10 deployment inaccessible.

Installing Agent for WebLogic Server/Portal 10 on the Administration Server

Install the first instance of Agent for WebLogic Server/Portal 10 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 WebLogic Server/Portal 10 on the Administration Server

Ensure that the WebLogic Server/Portal 10 Administration Server is not running.

Install Agent for WebLogic Server/Portal 10 as you would in a stand-alone environment.

Configure the agent classpath for WebLogic Server/Portal 10 Administration Server as described in this guide.

Start the WebLogic Server/Portal 10 Administration Server.

Configure the Agent Authentication Provider.

Installing Agent for WebLogic Server/Portal 10 on a Managed Server

You can start Managed Servers in a clustered environment using command-line scripts or using WebLogic Server/Portal 10 Administration Console, specifically using the Node Manager. Both options are supported by Agent for WebLogic Server/Portal 10. 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 WebLogic Server/Portal 10: Clustered Setup.

To Install Agent for WebLogic Server/Portal 10 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.

Ensure that the WebLogic Server/Portal 10 Managed Server is not running.

Install Agent for WebLogic Server/Portal 10 as you would in a stand-alone environment.

During the installation, enter the same start up script location you provided when installing the agent instance on the Administration Server. Therefore, for the Administration Server and the Managed server, your response should be the same for the following prompt:
```
Enter the Startup script location
```
However, enter the instance name of the Managed server, such as server0, when presented with the following prompt:
```
Enter the WebLogic Server/Portal instance name
```

Start the Managed Server using the appropriate start up script.

For this scenario, the appropriate start up script is the startManagedWeblogic.sh script in the following directory:
```
domain-directory/bin
```
For the example provided thus far in this task, the following would be the appropriate command:
```
./startManagedWeblogic.sh server0 http://adminHost.example.com/:7001
```
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 WebLogic Server/Portal 10: Clustered Setup.

Post-Installation Tasks of Agent for WebLogic Server/Portal 10 in a Clustered Environment

This section describes the post-installation tasks involved with Agent for WebLogic Server/Portal 10 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 for the WebLogic Server/Portal 10 Agent. 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 WebLogic Server/Portal 10: Cluster

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

Install the Agent Filter for the Deployed Application on Agent for WebLogic Server/Portal 10: Cluster

Install the Agent Filter for each application deployed in an Administration Server or Managed Server protected by Agent for WebLogic Server/Portal 10. For information on this task, see Installing the Agent Filter for the WebLogic Server/Portal 10 Agent.

Deploy the Agent Application of Agent for WebLogic Server/Portal 10: Cluster

Before preceding to this task description, documented in Deploying the Agent Application, 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 WebLogic Server/Portal 10 Administration Console as detailed in the following task description.

To Deploy the Agent Application in the WebLogic Server/Portal 10 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 WebLogic Server/Portal 10 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 WebLogic Server/Portal 10 instance is dependent on any other instance for agent housekeeping operations.

Expand the Deployments tab.

Click Lock & Edit.

In the right pane, click Install.

Click “upload your file(s).”

This action uploads 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 WebLogic Server/Portal 10: Clustered Setup

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

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

Note –

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 WebLogic Server/Portal 10 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 WebLogic Server/Portal 10 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/config
```
  where AgentInstance represents an agent instance directory, such as Agent_001.
  
  For information about PolicyAgent-base, see WebLogic Server/Portal 10 Agent Directory Structure.
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/wlserver_10.0/server/lib/weblogic.jar
```
  where:
  
  DeployContainer-base represents the directory in which WebLogic Server/Portal 10 was installed.
  
  BEA-Java-Home represents the directory that contains the JDK for the WebLogic Server/Portal 10 instance.
6. Click Save.
7. Click Activate Changes.

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 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.