Oracle® Solaris Cluster Data Service for Oracle iPlanet Web Server Guide

Exit Print View

Updated: July 2015
 
 

How to Register and Configure HA for Oracle iPlanet Web Server in a Scalable Configuration

Before You Begin

Ensure that the /etc/netmasks file has IP-address subnet and netmask entries for all logical hostnames. If necessary, edit the /etc/netmasks file to add any missing entries.

  1. On a cluster member, become an administrator that provides solaris.cluster.modify and solaris.cluster.admin authorization.
  2. Register the SUNW.iws resource type for HA for Oracle iPlanet Web Server.
    # clresourcetype register SUNW.iws
  3. Create a failover resource group for the shared address resource.

    You can optionally select the set of nodes on which the data service can run with the –n option.

    # clresourcegroup create [-n node[,…]] resource-group
    resource-group

    Specifies the name of the failover resource group. This name can be your choice but must be unique for resource groups within the cluster.

    –n node[,…]

    Specifies a comma-separated, ordered list of nodes that can master this resource group.

    This list is optional. If you omit this list, the global zone of each cluster node can master the resource group.

  4. Verify that all of the network addresses that you use have been added to your name service database.

    You should have performed this verification during the Oracle Solaris Cluster installation. See the planning chapter in the Oracle Solaris Cluster Software Installation Guide for details.


    Note -  To avoid any failures because of name service lookup, ensure that all logical hostnames and shared addresses are present in the server's and client's /etc/inet/hosts file. Configure name service mapping in /etc/nsswitch.conf on the servers to first check the local files before trying to access NIS or NIS+.
  5. Add a shared address resource to the failover resource group.
    # clressharedaddress create -g resource-group \
    -h shared-address[,…] \
    [-p auxnodelist=node[,…]] \
    [-N netiflist] \
    resource
    –g resource-group

    Specifies the name of the failover resource group.

    –h shared-address[,…]

    Specifies a comma-separated list of shared addresses that this resource is to make available.

    –p auxnodelist=node[,…]

    Specifies an optional comma-separated list of physical node IDs that identify cluster nodes that can host the shared address but never serve as a primary if failover occurs. These nodes are mutually exclusive with the nodes identified in nodelist for the resource group, if specified.

    resource-group

    Specifies the name of the resource group. This name can be your choice but must be unique for resource groups within the cluster.

    –N netiflist

    Specifies an optional, comma-separated list that identifies the IPMP groups that are on each node . The format of each entry in the list is netif@node. The replaceable items in this format are as follows:

    netif

    Specifies an IPMP group name, such as sc_ipmp0, or a public network interface card (NIC). If you specify a public NIC, Oracle Solaris Cluster attempts to create the required IPMP groups.

    node

    Specifies the name or ID of a node. To specify the global zone, or to specify a node without non-global zones, specify only node[,…]

    This list is optional. If you omit this list, Oracle Solaris Cluster attempts to create the required IPMP groups.


    Note -  Oracle Solaris Cluster does not currently support using the adapter name for netif.
    resource

    Specifies the name of the resource.

  6. Create a scalable resource group to run on all the desired cluster nodes.

    Create a resource group to hold a data service application resource. You must specify the maximum and desired number of primary nodes as well as a dependency between this resource group and the failover resource group that you created in Step 3. This dependency ensures that in the event of failover, the resource manager starts the network resource before starting any data services that depend on the network resource.

    # clresourcegroup create -p Maximum_primaries=m \
    -p Desired_primaries=n \
    -p RG_dependencies=resource-group \
    scalable-resource-group
    –p Maximum_primaries=m

    Specifies the maximum number of active primary nodes allowed for this resource group. If you do not assign a value to this property, the default is 1.

    –p Desired_primaries=n

    Specifies the desired number of active primary nodes allowed for this resource group. If you do not assign a value to this property, the default is 1.

    –p RG_dependencies= resource-group

    Identifies the resource group that contains the shared address resource on which the resource group being created depends.

    scalable-resource-group

    Specifies the scalable resource group.

  7. Create an application resource in the scalable resource group.

    You can repeat this step to add multiple application resources, such as SSL and non-SSL based versions, to the same resource group.

    To set load balancing for the data service, use the two standard resource properties Load_balancing_policy and Load_balancing_weights. See the r_properties (5) man page for a description of these properties. Additionally, see the examples that follow this section.

    # clresource create -g scalable-resource-group \
    -t resource-type \
    -p Confdir_list=config-directory[,…] \
    -p Resource_dependencies=shared-address[,…] \
    -p Port_list=port-number/protocol[,…] \
    -p Scalable=True \
    resource
    –g scalable-resource-group

    Specifies the name of the scalable resource group into which the resources are to be placed.

    –t resource-type

    Specifies the type of the resource to add.

    –p Confdir_list=config-directory[,…]

    Specifies a comma-separated list of the locations of the Oracle iPlanet configuration files. HA for Oracle iPlanet Web Server requires this extension property.

    –p Resource_dependencies=shared-address[,…]

    Specifies a comma-separated list of network resources that identify the shared addresses that the data service uses.

    –p Port_list=port-number/protocol[,…]

    Specifies a comma-separated list of port numbers and protocol to be used, for example, 80/tcp,81/tcp.

    –p Scalable=True

    Specifies a Boolean that is required for scalable services.

    resource

    Specifies the name of the resource to add.

    The resource is created in the enabled state.


    Note -  A one-to-one mapping applies for Confdir_List and Port_List. Each value in one list must correspond to the value in the other list in the specified order.
  8. Bring the failover resource group online.
    # clresourcegroup online -M resource-group
    resource-group

    Specifies the name of the failover resource group.

  9. Bring the scalable resource group online.
    # clresourcegroup online -M resource-group
    resource-group

    Specifies the name of the scalable resource group.

Example 1-4  Registering a Scalable HA for Oracle iPlanet Web Server

Ensure that the /etc/netmasks file has IP-address subnet and netmask entries for all logical hostnames. If necessary, edit the /etc/netmasks file to add any missing entries.

Cluster Information
Node names: phys-schost-1, phys-schost-2
Shared address: schost-1
Resource groups: sa-resource-group-1 (for shared addresses),
iws-resource-group-1 (for scalable application resources)
Resources: schost-1 (shared address), app-insecure-1 (non-SSL based  
application resource), app-secure-1 (SSL-based application resource)
 
(Add a failover resource group to contain shared addresses.)
# clresourcegroup create sa-resource-group-1
 
(Add the shared address resource to the failover resource group.)
# clressharedaddress create -g sa-resource-group-1 -h schost-1 sa-resource
 
(Add a scalable resource group.)
# clresourcegroup create -p Maximum_primaries=2 \
-p Desired_primaries=2 \
-p RG_dependencies=sa-resource-group-1 iws-resource-group-1
 
(Register the resource type for the HA for Oracle iPlanet Web Server.)
# clresourcetype register SUNW.iws
 
(Add a non-SSL based application instance with default load balancing.)
# clresource create -g iws-resource-group-1 -t SUNW.iws \
-p Confdir_List=/opt/SUNwbsrv/https-app-insecure-1 \
-p Scalable=True -p Resource_dependencies=schost-1 \
-p Port_list=80/tcp app-insecure-1 

(Add an SSL-based application instance with sticky IP load balancing.)
# clresource create -g iws-resource-group-1 -t SUNW.iws \
-p Confdir_List=/opt/SUNwbsrv/https-app-secure-1 \
-p Scalable=True -p Resource_dependencies=schost-1 \
-p Port_list=443/tcp -p Load_balancing_policy=LB_STICKY \
-p Load_balancing_weights=40@1,60@2 app-secure-1
 

(Bring the failover resource group online.)
# clresourcegroup online -M sa-resource-group-1
 
(Bring the scalable resource group online.)
# clresourcegroup online -M iws-resource-group-1