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 BEA WebLogic Server 9.0/9.1 Managed Server is not running.
Copy the startManagedWebLogic.sh script to an instance specific script on which the agent will be installed as illustrated by the following example:
Edit the newly copied script by hard coding the following variables:
The following is an example of these two variables hard coded:
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.
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.
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.