Skip Navigation Links
Exit Print View
| Oracle Solaris Cluster Data Service for Oracle iPlanet Web Server Guide Oracle Solaris Cluster 4.1

Search Scope:

- This Document
- Entire Library

## Registering and Configuring HA for Oracle iPlanet Web Server

You can configure HA for Oracle iPlanet Web Server as a failover data service or as a scalable data service. You must include some additional steps to configure Oracle iPlanet Web Server as a scalable data service. In the first procedure in this section, these additional steps begin with a notation that they are required for scalable services only. Individual examples of a failover service and a scalable service follow the procedure.

### Setting HA for Oracle iPlanet Web Server Extension Properties

The sections that follow contain instructions for registering and configuring HA for Oracle iPlanet Web Server resources. For information about the extension properties, see Appendix A, HA for Oracle iPlanet Web Server Extension Properties. The Tunable entry indicates when you can update a property.

See the `r_properties`(5), `rg_properties`(5), and `rt_properties`(5) man pages for details on all the Oracle Solaris Cluster properties.

To set an extension property of a resource, include the following option in the `clresource` command that creates or modifies the resource:

    -p property=value

`-p` property

  Identifies the extension property that you are setting.

value

  Specifies the value to which you are setting the extension property.

You can also use the procedures in Chapter 2, Administering Data Service Resources, in Oracle Solaris Cluster Data Services Planning and Administration Guide to configure resources after the resources are created.

### Monitoring Arbitrary URIs

Set the `Monitor_Uri_List` extension property if you want the web server fault monitor to probe an arbitrary list of applications (URIs) served by the web server. This extension property provides extended probing functionality and is useful if you are layering services in addition to your web server. The `Monitor_Uri_List` extension property is not supported with an SSL-based Oracle iPlanet Web Server instance. If you do not set the `Monitor_Uri_List` extension property , the fault monitor will perform basic probing. See Tuning the HA for Oracle iPlanet Web Server Fault Monitor for details. The following examples show how to set the `Monitor_Uri_List` extension property when you add the Oracle iPlanet Web Server instance to your configuration.

Example 1-1 Setting `Monitor_Uri_List` for Scalable Oracle iPlanet Web Server Instance

    (Add a non-SSL based Oracle iPlanet Web Server instance with default load balancing.)
    # clresource create -g resource-group-1 -t SUNW.iws \
    -p Confdir_List=/opt/SUNwbsrv/https-Sun-app-insecure-1 \
    -p Scalable=True -p Resource_dependencies=schost-1 \
    -p Port_list=8000/tcp \
    -p Monitor_Uri_list=http://schost-1:8000/servlet/monitor web-not-secure-1

Example 1-2 Setting `Monitor_Uri_List` for Failover Oracle iPlanet Web Server Instance

    (Add a non-SSL based Oracle iPlanet Web Server application resource instance.)
    # clresource create -g resource-group-1 -t SUNW.iws \
    -p Confdir_list=/opt/SUNwbsrv/conf -p Scalable=False \
    -p Resource_dependencies=schost-1 -p Port_list=80/tcp \
    -p Monitor_Uri_list=http://schost-1:80/servlet/monitor web-not-secure-1

Example 1-3 Setting `Monitor_Uri_List` for Failover Oracle iPlanet Web Proxy Server Instance

    (Add a non-SSL based Oracle iPlanet Web Proxy Server application resource instance.)
    # clresource create -g resource-group-1 -t SUNW.iws \
    -p Confdir_list=/opt/SUNwbproxy/conf -p Scalable=False \
    -p Resource_dependencies=schost-1 -p Port_list=80/tcp \
    -p Monitor_Uri_list=http://schost-1:80/servlet/monitor Sun-app-insecure-1

### Setting IP Addresses and Port Numbers for the Oracle iPlanet Web Server Application

The `Resource_dependencies` setting on the Oracle iPlanet Web Server application resource determines the set of IP addresses that Oracle iPlanet Web Server uses. The `Port_list` setting on the resource determines the list of port numbers that Oracle iPlanet Web Server uses. The fault monitor assumes that the Oracle iPlanet Web Server daemon is listening on all combinations of IP and port. You can configure the `server.xml` file for the Oracle iPlanet Web Server to listen on different port numbers (in addition to port `80`). The fault monitor attempts to probe all such combinations and starts to fail if the Oracle iPlanet Web Server is not listening on a particular IP address-port combination. If the Oracle iPlanet Web Server does not serve all IP address-port combinations, you must break the Oracle iPlanet Web Server into separate instances that do.

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

This procedure describes how to use the Oracle Solaris Cluster maintenance commands to register and configure HA for Oracle iPlanet Web Server in a failover configuration.

Note - Other options also enable you to register and configure the data service. See Tools for Data Service Resource Administration in Oracle Solaris Cluster Data Services Planning and Administration Guide for details about these options.

To perform this procedure, you must have the following information.

- The name of the resource type for HA for Oracle iPlanet Web Server. This name is `SUNW.iws`.

- The names of the cluster nodes that master the data service. For a failover service, only one node can master a data service at a time.

- The logical hostname (for failover services) or shared address (for scalable services) that clients use to access the data service.

- The path to the Oracle iPlanet binaries. You can install the binaries on the local disks or the cluster file system. See Configuration Guidelines for Oracle Solaris Cluster Data Services in Oracle Solaris Cluster Data Services Planning and Administration Guide for a discussion of the advantages and disadvantages of each location.

  Note - The `Resource_dependencies` setting on the Oracle iPlanet application resource determines the set of IP addresses that Oracle iPlanet Web Server uses. The `Port_list` setting on the resource determines the list of port numbers that Oracle iPlanet Web Server uses. The fault monitor assumes that the Oracle iPlanet Web Server daemon is listening on all combinations of IP and port. You can configure the `server.xml` file for the Oracle iPlanet Web Server to listen on different port numbers (in addition to port `80`). The fault monitor attempts to probe all such combinations and starts to fail if the Oracle iPlanet Web Server is not listening on a particular IP address-port combination. If the Oracle iPlanet Web Server does not serve all IP address-port combinations, you must break the Oracle iPlanet Web Server into separate instances that do.

Note - Perform this procedure on any cluster member.

1. On a cluster member, assume a role that provides `solaris.cluster.modify` and `solaris.cluster.admin` RBAC 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.

   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 logical hostname to the failover resource group.

       # clreslogicalhostname create -g resource-group \
       -h logical-hostname[,…] \
       [-p auxnodelist=node] [-N netiflist] resource-name

   `-g` resource-group

     Specifies the name of the failover resource group.

   `-h` logical-hostname[,…]

     Specifies a comma-separated list of logical hostnames 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.

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

     Note - If you require a fully qualified hostname, you must specify the fully qualified name with the `-h` option and you cannot use the fully qualified form in the resource name.

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

   resource

     Specifies the name of the resource.

6. Create an application resource in the failover 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.

       # clresource create -g resource-group \
       -t resource-type \
       -p Confdir_list=config-directory \
       -p Resource_dependencies=logical-hostname-list,.. \
       -p Port_list=port-number/protocol resource

   `-g` resource-group

     Specifies the name of the failover 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 the location of the Oracle iPlanet configuration files. The `Confdir_list` file for failover services must have exactly one entry only. The config-directory must contain a directory called `config`. HA for Oracle iPlanet Web Server requires this extension property.

   `-p` `Resource_dependencies``=`logical-hostname-list,…

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

   `-p` `Port_list``=`port-number/protocol

     Specifies the port number and protocol to use, for example, `80/tcp`. `Port_list` for failover services must have exactly one entry only because of the one-to-one mapping rule between `Port_list` and `Confdir_list`.

   resource

     Specifies the name of the resource to add.

   The resource is created in the enabled state.

   Note - Optionally, you can set additional extension properties that belong to the HA for Oracle iPlanet Web Server to override the default values of the properties. See Appendix A, HA for Oracle iPlanet Web Server Extension Properties for a list of these properties.

7. Bring the failover resource group online.

       # clresourcegroup online -M resource-group

   resource-group

     Specifies the name of the failover resource group.

Example 1-4 Registering a Failover HA for Oracle iPlanet Web Server on a Two-Node Cluster

    Cluster Information
    Node names: phys-schost-1, phys-schost-2
    Logical hostname: schost-1
    Resource group: resource-group-1 (for all resources)
    Resources: schost-1 (logical hostname), app-insecure-1 (non-SSL based
    application resource), app-secure-1 (SSL-based application resource)

    (Add the resource group to contain all resources.)
    # clresourcegroup create resource-group-1

    (Add the logical hostname resource to the resource group.)
    # clreslogicalhostname create -g resource-group-1 -h schost-1 resource-name schost-1

    (Register the resource type for the HA for Oracle iPlanet Web Server.)
    # clresourcetype register SUNW.iws

    (Add a non-SSL based application resource instance.)
    # clresource create -g resource-group-1 -t SUNW.iws \
    -p Confdir_list=/opt/SUNwbsrv/conf -p Scalable=False \
    -p Resource_dependencies=schost-1 -p Port_list=80/tcp app-insecure-1

    (Add an SSL-based application resource instance.)
    # clresource create -g resource-group-1 -t SUNW.iws \
    -p Confdir_List=/opt/SUNwbsrv/https-app-secure-1 -p Scalable=False \
    -p Resource_dependencies=schost-1 -p Port_list=443/tcp app-secure-1

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

Example 1-5 Registering a Failover HA for Oracle iPlanet Web Proxy Server on a Two-Node Cluster

    Cluster Information
    Node names: phys-schost-1, phys-schost-2
    Logical hostname: schost-1
    Resource group: resource-group-1 (for all resources)
    Resources: schost-1 (logical hostname), app-insecure-1 (non-SSL based
    application resource), app-secure-1 (SSL-based application resource)

    (Add the resource group to contain all resources.)
    # clresourcegroup create resource-group-1

    (Add the logical hostname resource to the resource group.)
    # clreslogicalhostname create -g resource-group-1 -h schost-1

    (Register the resource type for the HA for Oracle iPlanet Web Proxy Server.)
    # clresourcetype register SUNW.iws

    (Add a non-SSL based application resource instance.)
    # clresource create -g resource-group-1 -t SUNW.iws \
    -p Confdir_list=/opt/SUNwbproxy/proxy-insecure-1 -p Scalable=False \
    -p Resource_dependencies=schost-1 -p Port_list=80/tcp app-insecure-1

    (Add an SSL-based application resource instance.)
    # clresource create -g resource-group-1 -t SUNW.iws \
    -p Confdir_List=/opt/SUNwbproxy/proxy-secure-1 -p Scalable=False \
    -p Resource_dependencies=schost-1 -p Port_list=443/tcp app-secure-1

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

In this example, it is assumed that the global file system is being used. If a failover file system is used, you must set the dependency on the `HAStoragePlus` resource using the `Resource_dependencies` extension property during resource creation.

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

1. On a cluster member, assume a role that provides `solaris.cluster.modify` and `solaris.cluster.admin` RBAC 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-6 Registering a Scalable HA for Oracle iPlanet Web Server

    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

### How to Configure the `SUNW.HAStoragePlus` Resource Type

The `SUNW.HAStoragePlus` resource type synchronizes actions between HA storage and the data service. `SUNW.HAStoragePlus` also has an additional feature to make a local file system highly available.

See the `SUNW.HAStoragePlus`(5) man page and Relationship Between Resource Groups and Device Groups in Oracle Solaris Cluster Data Services Planning and Administration Guide for background information. See Synchronizing the Startups Between Resource Groups and Device Groups in Oracle Solaris Cluster Data Services Planning and Administration Guide for the procedure.

Copyright © 2009, 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices |