These instructions assume that you are at the WebLogic Server Configuration list of options for configuring HA for WebLogic Server in the clsetup utility.
Use this procedure to configure HA for WebLogic Server Managed Servers, using the clsetup utility. The utility starts a wizard to guide you through the creation of resource groups and resources for the Managed Server instances. The Managed Servers can be configured either in failover or multi-instance mode.
Before You Begin
You must perform the steps in How to Register and Configure the HA for WebLogic Server as an Administration Server (clsetup) before configuring Managed Servers.
Any project you created to run Oracle WebLogic Server exists in the projects name service database for the user that runs that application. If no custom project is created for the application, the default project is used. For more information, see the projects(1) man page.
Have available the logical hostnames that you plan to add to the resource group.
The Verify Prerequisites screen lists the tasks that you should have already performed before you continue.
The utility prompts you to enter the location of the domain.
Type the complete path to the domain directory.
The utility prompts you to enter the location of the WebLogic home directory.
The directory you specify must be accessible from each cluster node.
The clsetup utility supplies the default path to the script found in the WebLogic domain directory. You can accept this value or type a new path.
The clsetup utility prompts for the path to the WebLogic Server environment file.
You can accept the default or enter a new name. The environment file is typically $WEBLOGIC_HOME/server/bin/setWLSEnv.sh if WebLogic Server is configured through the installation wizard.
The clsetup utility prompts you for the project to use.
If you did not create a project where WebLogic Server will run, select the default project. The clsetup utility validates the environment file, then prompts you to specify a configuration mode.
In failover mode, the WebLogic Server Managed Server instance runs on only a single node. If the fault monitor detects an error, it restarts the instance on the same node or starts an instance on another cluster node that is configured to master the WebLogic data service.
In multi-instance mode, one WebLogic Managed Server instance runs on the cluster node that is the primary node of the Managed Server's logical host. With this type of configuration there could be any number of Managed Server instances.
See Standard Data Service Configurations for more information about configuration modes.
The clsetup utility displays a list of Managed Servers that you can configure.
The clsetup utility displays logical hostname resources that are available for the specified Managed Server.
The logical host name resource you choose is configured as the host for the Managed Server resource that is created. The Managed Server resource has a resource dependency on the logical hostname resource. The Managed Server selected will be configured on the same resource group where the selected logical host exists, in failover mode.
In multi-instance mode, for each selected instance one logical hostname resource should be selected. You can select the same logical hostname resource for multiple Managed Server instances. A new resource and resource group will be created for each Managed Server instance.
The clsetup utility prompts you to specify the optional monitoring URI. This URI can be used by the fault monitor to test the functionality of the WebLogic Server by doing an HTTP GET on the URI.
The URIs will be validated against the configured logical host resources when the resource is created.
The clsetup utility then displays the server URI value.
In failover mode, the clsetup utility supplies the default server URI value for the selected Managed Server. You can accept this value or type a new value.
In multi-instance mode, a default server URI value is provided for each of the selected instances. You can accept this value or type a new value.
The clsetup utility then displays highly available storage resources.
The storage resources must contain the WebLogic home and domain directory.
The storage resources displayed should be based on the WebLogic home directory value you specified earlier, but if clsetup cannot find any, all configured storage resources on the selected cluster are displayed instead.
You can select one from the list, or proceed without selecting anything by typing d.
The review panel shows the values for all the properties associated with the Managed Servers.
A new panel is displayed where you can then edit the Managed Server resource names one at a time, then type d when you are done.
The utility displays a summary of the information that will be used to create the configuration for the WebLogic Managed Server instance for your review. You cannot edit any of the values here.
The clsetup utility displays the list of commands that are invoked on the cluster and also shows a status message indicating a success or failure. In the event that the configuration fails, a rollback is attempted.
The clsetup utility returns to the WebLogic Server Configuration screen.
Continue to the next procedure for Reverse Proxy Server configuration.