X

News, tips, partners, and perspectives for the Oracle Solaris operating system

Try Oracle Cloud Platform For Free

Configuring HA for Oracle WebLogic Server Managed Servers by Using the clsetup Wizard

Harish Mallya

This
post describes the steps to use the clsetup
wizard to configure an Oracle WebLogic Server Managed Servers
instance as a highly available failover data service with Oracle
Solaris Cluster software.

HA
Prerequisites

  • The

    logical host resource to be used by the data service is configured.

  • The

    administration server instance of Oracle WebLogic Server software is

    running. This is to avoid the delay during discovery of the managed

    servers, which might take 10 minutes or longer.

  • The

    common agent container (cacao) service is running on the nodes on

    which Oracle WebLogic Server software will be configured.

Application
Prerequisites

  • The

    boot.properties

    file is in the $DOMAIN_DIR/servers/<server-name>/security

    folder.

  • The

    Managed Server to be configured is created.

Points to
Note

While
using the clsetup
wizard:

  • Type

    a question mark (?) to access the help.

  • Type

    a left angle bracket (<) or a right angle bracket (>) to move

    backward or forward, respectively.

  • Each

    input provided is validated by the wizard.

Procedure

From
a command prompt, type clsetup
to start the utility. From the clsetup
menu, select "Data Services". In the next menu, select
“Oracle WebLogic Server”.

The
following table is an overview of the steps that the clsetup
wizard performs to configure the data service.

#

Step

Remarks

1

Select

Oracle WebLogic Server Location

Select

"Global Cluster" or "Zone Cluster". If

you select “Zone Cluster”, in the next menu select the zone

cluster in which to configure the data service.

2

WebLogic

Server Configuration

Lists

the available types of configuration. Select “Managed Servers”.

3

Verify

Prerequisites

Make

sure all listed prerequisites are met.

4

Specify

Domain Location

Be

sure to provide the proper domain location. If you provide the

proper domain location and no customized configuration is made in

the Oracle

WebLogic Server software, the clsetup

wizard will auto-discover the parameter values.

5

Specify

WebLogic Home Directory

Either

select a directory from the discovered values or specify your own

home directory by selecting the option “Specify explicitly”.

6

Specify

WebLogic Managed Server Start Script

Press

“RETURN” to accept the discovered value or type your own

value.

7

Specify

WebLogic Server Environment File

Press

“RETURN” to accept the discovered value or type your own

value.

8

Select

Configuration Mode for Managed Servers

Select

“Failover”.

9

Select

Managed Server

Select

from the displayed list the Managed Server that you want to

configure.

10

Select

Logical Hostname for Managed Server <Managed Server Name>

Select

the appropriate logicalhost from the list.

11

Specify

Monitoring URI

Specify

the URI or leave the field blank. To specify multiple monitoring

URIs, separate them by commas. If you specify a URI, it will be

validated.

12

Configure

Highly Available Storage Resources

Select

the appropriate storage from the list.

13

Review

Panel

Displays

the values entered. To edit the information, choose the

corresponding number.

14

Summary

Panel

Displays

the values you entered. [This panel is read only.]

Configuring
the HA for Oracle WebLogic Server service by using the clsetup
wizard is easy, effective, and ensures proper configuration of
properties for resources and resource groups.

For
additional information for the Oracle Solaris Cluster 3.3 3/13
release, see Oracle
Solaris Cluster Data Service for Oracle WebLogic Server Guide.
For other applicable Oracle Solaris Cluster releases, see the Oracle
Systems Software documentation
indexes.

- Sabareesh

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.

Recent Content