Installing and Configuring Oracle Web Tier Software

To install the Oracle Web Tier software, perform the following procedure.

See Oracle Web Tier documentation for standard installation instructions. Contact your Oracle sales representative for a complete list of Oracle Web Tier versions that are supported with the Oracle Solaris Cluster software.

How to Install and Configure the Oracle Web Tier Software and Resources

To install the Oracle Web Tier software, you must first create your chosen shared storage and logical host resources. Once complete, you must install an Oracle Fusion Middleware (FMW) environment before you install and configure the Oracle Web Tier software.

When you configure the Oracle Web Tier components as a failover service, you place the Oracle Process Management and Notification Server (OPMN) resource, the Oracle HTTP Server resource, and the network resource in a single resource group.

When a highly available local file system is used to store either the htdocs, or the htdocs and Oracle Web Tier software, then an HAStoragePlus storage resource is also placed in the failover resource group. Alternatively, when a cluster file system is used in a zone cluster, or when a NAS device is used, then a storage resource is placed in a separate scalable resource group.

Before You Begin

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

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

  ---

  Note - To avoid failures because of name-service lookup, verify that all the network addresses are present in the /etc/inet/hosts file on all of the cluster nodes. Configure the name service mapping by using the svccfg -s svc:/system/name-service/switch command. Ensure that the config/host entry is configured to first check the local files before accessing NIS, NIS+, or DNS.

  ---

1. Create an Oracle Solaris user account to own the Oracle Fusion Middleware and Oracle Web Tier software.

   Perform this step on all nodes that host the service. The user and group IDs for the account must be consistent on all nodes.

2. Create a failover resource group to hold the network and application resources.

   This resource group contains both network and failover application resources. If a highly available local file system is used to store the htdocs and application binaries directories, then the resource group also contains an HAStoragePlus storage resource.

   Optionally, you can specify with the -n option the set of nodes on which the data service can run.

   # clresourcegroup create [-n node-zone-list] resource-group

   resource-group

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

   [-n node-list]

   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.

3. Bring the failover resource group online.

   # clresourcegroup online -emM resource-group

   resource-group

   Specifies the name of the failover resource group.

4. Add a logical hostname network resource to the failover resource group that you created in Step 2.

   This is the hostname that clients will use to connect to the Oracle HTTP Server component.

   # clreslogicalhostname create -g resource-group \
   -h hostname[,…] [-N netiflist] resource

   -h hostname,…

   Specifies a comma-separated list of network resources to add.

   resource-group

   Specifies the name of the failover resource group that you created in Step 2.

   resource

   Specifies a resource name. If you do not supply your choice for a resource name, the name of the network resource defaults to the first name that is specified after the -h option.

   -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.

   ---

   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.

   ---

5. Configure the storage resources.
   • If you are storing the Oracle HTTP Server htdocs directory on a highly available local file system or on a cluster file system in the global zone, create a storage resource in the application failover resource group.

     # clresource create -g resource-group \
     -t SUNW.HAStoragePlus \
     {-p FileSystemMountPoints=mount-point,… | -p Zpools=zpool,...} \
     resource

     resource-group

     Specifies the name of the failover resource group that you created in Step 2.

     -p FileSystemMountPoints mount-point-list

     Specifies a comma-separated list of file system mount points to add.

     -p Zpools zpool-list

     Specifies a comma-separated list of zpools to add.

     resource

     Specifies a resource name.

   • If you are storing the Oracle HTTP Server htdocs and application binaries directories on a NAS mounted file system or on a cluster file system in a zone cluster, create a scalable resource group to contain the storage resource.
     1. Create a scalable resource group to contain the storage resource.

        # clresourcegroup create [-n node-zone-list] \
        -p Maximum_primaries=m \
        -p Desired_primaries=n \
        resource-group

        resource-group

        Specifies the name of the scalable service resource group to add.

        -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.

        -n node-list

        Specifies a comma-separated, ordered list of nodes that can master this resource group. The format of each entry in the list is node.

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

     2. Add a storage resource to the scalable resource group that you created in Step a.

        For example, an HAStoragePlus resource to manage a cluster file system that is to be mounted in a zone cluster is added as follows:

        # clresource create -g resource-group \
        -t SUNW.HAStoragePlus \
        -p FileSystemMountPoints=mount-point \
        resource

        resource-group

        Specifies the name of the scalable resource group that you created in Step a.

        -p FileSystemMountPoints mount-point

        Specifies a comma-separated list of file system mount points to add.

        resource

        Specifies a resource name.

     3. Bring the scalable resource group online.

        # clresourcegroup online -emM resource-group

        resource-group

        Specifies the name of the scalable resource group.

6. As the software owner created in Step 1, use the Oracle Fusion Middleware 11g installation media to install the Oracle WebLogic Server software.

   ---

   Note - Do not yet run quickstart or configure the software.

   ---

7. As the software owner, use the Oracle Web Tier installation media to install the software only.
   1. When prompted, run the createCentralInventory.sh script to create the central inventory.
   2. If the software has been installed centrally, do the following:
      1. When the installation is complete, switch the resource group containing the software to the other nodes that can host the service.
      2. Rerun the createCentralInventory.sh script to create the required directories in the /var hierarchy on the other nodes.
8. If necessary, update the Oracle Web Tier software with the latest Service Repository Updates (SRUs) and security fixes.
9. As the software owner, create an Oracle WebLogic Administration Server component for the domain.
   1. To ensure that the Enterprise Manager GUI uses the logical hostname, set the following environment variables.

      $ export LD_PRELOAD_32=$LD_PRELOAD_32:/usr/cluster/lib/libschost.so.1
      $ export LD_PRELOAD_64=$LD_PRELOAD_64:/usr/cluster/lib/64/libschost.so.1
      $ export SC_LHOSTNAME=logical-hostname

   2. Create the component.

      $ cd /FMW-Home/Web-Tier-Home/common/bin
      $ ./config.sh

10. If you want to make the Oracle WebLogic Administration Server component highly available, create the necessary resource groups and resources to control it.
11. As the software owner, create the Oracle HTTP Server component instance.
    1. To ensure that the Enterprise Manager GUI uses the logical hostname, set the following environment variables.

       $ export LD_PRELOAD_32=$LD_PRELOAD_32:/usr/cluster/lib/libschost.so.1
       $ export LD_PRELOAD_64=$LD_PRELOAD_64:/usr/cluster/lib/64/libschost.so.1
       $ export SC_LHOSTNAME=logical-hostname

    2. Create the component instance.

       $ cd /FMW-Home/Web-Tier-Home/bin
       $ ./config.sh

       ---

       Note - You can create both HTTP and Web Cache instances, but the HA for Oracle Web Tier only currently supports the HTTP instances. Observe the following requirements for HTTP instances:

       • When you are prompted to provide the instance name and the instance subdirectory, the instance name and the final component of the instance subdirectory must be the same. For example, if the Oracle Web Tier instance is named myinst1, then the corresponding directory for that instance must be of the form /FMW-Home/Web-Tier-Home/instances/myinst1.

       • The Oracle HTTP Server instance name must be the same on all nodes.

       Failure to meet these requirements will result in validation failures when attempting to create an Oracle HTTP Server resource.

       ---

12. Manually stop the Oracle HTTP Server and Oracle Process Management and Notification Server instances.

    $ cd /FMW-Home/Web-Tier-Home/instances/Instance-Name/bin
    $ ./opmnctl stopall

13. Edit the http.conf file.

    $ cd /FMW-Home/Web-Tier-Home/instances/Instance-Name/config/OHS/Component-Instance-Name
    $ vi http.conf

    Ensure that the file contains a line of the following form, where Logical-Hostname is the logical hostname resource that you created in Step 4:

    Listen Logical-Hostname:Port

See Also

The following sections provide examples of this procedure, as used in conjunction with the procedure to register and configure HA for Oracle Web Tier component resources:

• Example 1-1

• Example 1-2