Installing and configuring the WebLogic Server/Portal 10 agent in a clustered environment is similar to the process for a stand-alone environment. Exceptions are noted in this section.
In a cluster, you must install the WebLogic Server/Portal 10 agent in this order:
First, install the agent on the Administration Server. The agent on the Administration Server sets up the Agent Authenticator for the entire domain. See Installing the WebLogic Server/Portal 10 Agent on the Administration Server.
Then, install the agent on each of the Managed Servers that you want to protect. See Installing the WebLogic Server/Portal 10 Agent on a Managed Server.
Ensure that the Administration Server is not running.
Install the agent as you would in a stand-alone environment. See Installing the WebLogic Server/Portal 10 Agent.
Configure the agent classpath for the Administration Server. See Configuring a WebLogic Server 10 Instance With the Agent classpath and Java Options.
Start the Administration Server.
Configure the Agent Authentication Provider. See Configuring the Agent Authentication Provider for the WebLogic Server/Portal 10Agent.
Ensure that the Managed Server is not running.
Install the WebLogic Server/Portal 10 agent as you would in a stand-alone environment, with these exceptions:
When you are prompted to enter the startup script location, specify the same path that you provided when you installed the agent on the Administration Server.
When you are prompted to enter the WebLogic Server instance name, specify the Managed Server instance name. For example: server1
Start the Managed Server using the appropriate startup script:
Solaris and Linux systems: domain-name/bin/startManagedWeblogic.sh
Windows systems: domain-name\bin\startManagedWeblogic.cmd
where domain-name is where you located the domain.
For example, on a Solaris system:
cd /opt/bea/user_projects/domains/domain1/bin ./startManagedWeblogic.sh server1 http://adminhost.example.com:7001
Alternatively, you can start a Managed Server instance using Node Manager. See Configuring Node Manager 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 | |
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
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.
Login to the WebLogic Server/Portal 10 Administration Console
Expand the Deployments tab.
Click Lock & Edit.
In the right pane, click Install.
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.
You have the option of starting Managed Servers in a cluster using the WebLogic Server/Portal 10 Node Manager.
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:
In the Administration Console, select the Configuration tab.
Select the Server Start tab.
Locate the agent classpath for the specific Managed Server as found in setAgentEnv_sever-instance.sh.
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.
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.
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.
Click Save.
Click Activate Changes.
Configure the agent Java options in Server Start.
In the WebLogic Server/Portal 10 Administration Console, select the Configuration tab.
Select the Server Start tab.
Locate the Java options as found in setAgentEnv_sever-instance .sh for the specific Managed Server.
Add the Java options to the Arguments text field as follows:
-Djava.util.logging.config.file=PolicyAgent-base/config/ OpenSSOAgentLogConfig.properties -DLOG_COMPATMODE=Off
To avoid typing errors, copy and paste the agent Java option entries from the setAgentEnv_managed-sever-instance.sh file.
Click Save.
Click Activate Changes.