The installation, registration, and configuration procedures in this chapter assume that you are
installing the configuration that is described in Standard Data Service Configurations. This section provides examples of other
possible Oracle Solaris Cluster HA for WebLogic Server configurations.

Creating a Simple WebLogic Server Resource

This configuration assumes that the START script, startWebLogic.sh, can start the WebLogic
Server without any arguments to the script. The user name and password that
are needed to start the WebLogic Server can be configured within this START
script or in the boot.properties file.

Note - Starting with WebLogic Server version 10.3, the boot.properties file must reside in
both the $DOMAIN_DIR and $DOMAIN_DIR/servers/server-name/security directories to bypass the need to prompt for
user credentials when starting instances of WebLogic Server.

Creating a Resource With a Server Name Argument

If the WebLogic Server START script startManagedWebLogic.sh uses a Managed Server name as
an argument, then the extension property Server_name can be set. The START
script startManagedWebLogic.sh can be used to start several Managed Servers. The ADMIN_URL must be
configured within the START script. To start the WebLogic Server manually, use the
following commands.

Creating a Resource That Shuts Down Smoothly

The default for the Oracle Solaris Cluster HA for WebLogic Server STOP
method kills the WebLogic Server process to shut down the instance. To enable
smooth shutdown of the WebLogic Server, set the Smooth_shutdown extension property to TRUE.
If this extension property is enabled, the $DOMAIN_DIR/boot.properties file must contain a valid user
name and password.

Note - Starting with WebLogic Server version 10.3, the boot.properties file must reside in
both the $DOMAIN_DIR and $DOMAIN_DIR/servers/server-name/security directories to bypass the need to prompt for
user credentials when stopping instances of WebLogic Server. If the $DOMAIN_DIR/servers/server-name/security directory does
not exist or does not include a boot.properties file, create the directory and
copy the boot.properties file from the $DOMAIN_DIR.

To configure a resource which will shut down smoothly in a failover configuration,
use the following commands.

Creating a Resource That Probes the Database

The Oracle Solaris Cluster HA for WebLogic Server does not probe the
database health. If the database is down when Oracle Solaris Cluster HA for
WebLogic Server starts, the data service fails to start. To have the
Oracle Solaris Cluster HA for WebLogic Server probe the database, supply your own
database probe script to Oracle Solaris Cluster HA for WebLogic Server as
an extension property. This database probe must return zero for success and nonzero
for failure.

To configure a resource with the DB_probe script extension property set, use the
following commands.

Creating a Resource That Monitors URIs

To enable the Oracle Solaris Cluster HA for WebLogic Server resource to
monitor URIs that are served by the WebLogic Server configured in the resource,
use the following commands to set the extension property Monitor_uri_list.

Using a Non-Clustered Managed Server Instance as a Proxy Server

You can configure a non-clustered managed server instance to run as a proxy
server that hosts a servlet that directs the requests to the clustered managed
server instances. In this configuration, you can define a failover configuration to make
the WebLogic proxy server highly-available. When you define this configuration, make sure that
you specify a resource dependency from the WebLogic Server proxy server to the
managed server resource. Setting this dependency ensures that the proxy server resource will
not try to come online unless the managed server resource is online.