Installing the WebLogic Server/Portal 10 Agent in a Cluster

In a cluster, you must install the WebLogic Server/Portal 10 agent in this order:

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

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

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

To Install the WebLogic Server/Portal 10 Agent on the Administration Server

1. Ensure that the Administration Server is not running.

2. Install the agent as you would in a stand-alone environment. See Installing the WebLogic Server/Portal 10 Agent.

3. Configure the agent classpath for the Administration Server. See Configuring a WebLogic Server 10 Instance With the Agent classpath and Java Options.

4. Start the Administration Server.

5. Configure the Agent Authentication Provider. See Configuring the Agent Authentication Provider for the WebLogic Server/Portal 10Agent.

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

To Install the WebLogic Server/Portal 10 Agent on a Managed Server

1. Ensure that the Managed Server is not running.

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

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