Skip Navigation Links
Exit Print View
| Oracle Solaris Cluster Data Service for Siebel Guide ### Oracle Solaris Cluster 4.1SPARC Platform Edition

Search Scope:

- This Document
- Entire Library

## Registering and Configuring HA for Siebel

This section contains the procedures you need to configure HA for Siebel.

### Setting HA for Siebel Extension Properties

The sections that follow contain instructions for registering and configuring resources. These instructions explain how to set only extension properties that HA for Siebel requires you to set. For information about all HA for Siebel extension properties, see Appendix A, Oracle Solaris Cluster HA for Siebel Extension Properties. You can update some extension properties dynamically. You can update other properties, however, only when you create or disable a resource. The Tunable entry indicates when you can update a property.

To set an extension property of a resource, include the following option in the `clresource`(1CL) 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.

## How to Register and Configure HA for Siebel as a Failover Data Service

Use this procedure to configure HA for Siebel as a failover data service. This procedure assumes that the data service packages are already installed. If the HA for Siebel packages are not already installed, see Installing and Configuring the Siebel Application to install the packages. Otherwise, use this procedure to configure the HA for Siebel.

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 one of the nodes in the cluster that hosts the application server assume a role that provides `solaris.cluster.modify` and `solaris.cluster.admin` RBAC authorizations.
2. Register the resource type for the Siebel gateway.

       # clresourcetype register SUNW.sblgtwy

3. Create a failover resource group to hold the logical hostname and the Siebel gateway resources.

   Note - If you have already created a resource group, added the logical hostname resource, and brought the resource group online when you completed the How to Prepare the Nodes procedure, you may skip to Step 6.

       # clresourcegroup create [-n node] gateway-rg

   `-n` node

     Specifies the node name that can master this resource group.

   gateway-rg

     Specifies your choice of the name of the failover resource group to add. This name must begin with an ASCII character.

4. Add the logical hostname resource.

   Ensure that logical hostname matches the value of the `SIEBEL_GATEWAY` environment variable that is set in the `siebenv.sh` file of the Siebel gateway, and also the Siebel server installations.

       # clreslogicalhostname create -g gateway-rg logical_host

   logical_host

     Specifies an optional resource name of your choice.

5. Bring the resource group online.

       # clresourcegroup online -M gateway-rg

6. Verify that `siebenv.sh` file exists under gateway_root.

   The owner of this file launches the Siebel gateway server when the Siebel gateway resource is brought online.

7. If you are using Siebel 8.1 or later version, create a file called `scgtwyconfig` under gateway_root, owned by the owner of `siebenv.sh`.

   If the Siebel gateway is installed locally, create the file `scgtwyconfig` under gateway_root on all nodes. For security reasons, make this file readable only by the owner.

       # cd gateway_root
       # touch scgtwyconfig
       # chown siebel:siebel scgtwyconfig
       # chmod 400 scgtwyconfig

8. If you are using Siebel 8.1 or later version, in the `scgtwyconfig` file, enter the gateway user name and password that was given while configuring the gateway server enterprise.

   For example: `gtwyuser gtwypassword`

   This user name and password combination must have permission to connect to the database and also to the gateway server for use by the Oracle Solaris Cluster HA for Siebel Gateway Fault Monitor.

       export GTWYUSR=gtwyuser
       export GTWYPWD=gtwyuserpassword

9. Optional: If you want to encrypt the `scgtwyconfig` file, perform the following steps.
   1. As root user, encrypt the password file `scgtwyconfig` for the gateway server and place the password file and the key file in the `/var/cluster` directory.

      In the example below, the password file `scgtwyconfig` is being encrypted and `gtwy-rs` reflects the gateway server resource name. The key file name must be in the format `/var/cluster/.gateway_resource_name_key`. The password file name must be in the format `/var/cluster/.gateway_resource_name_gtwy_pdata`. The `PATH_TO_CONFIGFILE` is the location of the `scgtwyconfig` file.

          node1# dd if=/dev/urandom of=/var/cluster/.gtwy-rs_key bs=16 count=1
          node1#  chmod 400 /var/cluster/.gtwy-rs_key
          node1#  usr/sfw/bin/openssl enc -aes128 -e -in \
          $PATH_TO_CONFIGFILE/scgtwyconfig -k \
          /var/cluster/.gtwy-rs_key -out /var/cluster/.gtwy-rs_gtwy_pdata
          node1#  chmod 400 /var/cluster/.gtwy-rs_gtwy_pdata

   2. Verify that the encrypted password can be decrypted.

          node1# /usr/sfw/bin/openssl enc -aes128 -d -in /var/cluster/.gtwy-rs_gtwy_pdata \
          -k /var/cluster/.gtwy-rs_key -out /var/cluster/tmpfile

   3. Repeat steps a and b on all other Oracle Solaris Cluster nodes that will host the gateway server resource.
10. Create the Siebel gateway resource.

        # clresource create -g gateway-rg \
        -t SUNW.sblgtwy  \
        -p Confdir_list=gateway_root -p siebel_version=version number sblgtwy-rs \

    `-t` `SUNW.sblgtwy`

      Specifies the name of the resource type for the resource.

    `-p` Confdir_list

      Specifies the path name to the Siebel server root directory.

    `-p` `siebel_version`

      Specifies the Siebel server version.

      | Caution - If you enter an incorrect value for `siebel_version`, you might not see errors during validation but the resource startup will fail. If `siebel_version` is incorrect, the probe method is not able to verify database connectivity.

    sblgtwy-rs

      Specifies your choice of the name of the resource to add.

    The resource is created in the enabled state.

11. Verify that the Siebel resource group and the Siebel gateway resource are online by using `cluster status -t resourcegroup,resource` and `ps -ef`.

## How to Register and Configure the Siebel Server

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. Add the resource type for the Siebel server.

       # clresourcetype register SUNW.sblsrvr

2. Create the failover resource group to hold the logical hostname and the Siebel server resources.

   Note - If you have already created a resource group, added the logical hostname resource, and brought the resource group online when you completed the How to Prepare the Nodes procedure, you may skip to Step 5.

       # clresourcegroup create [-n node] siebel-rg

   `-n` node

     Specifies the node name that can master this resource group.

   siebel-rg

     Specifies your choice of the name of the failover resource group to add. This name must begin with an ASCII character.

3. Add the logical hostname resource.

   This logical hostname should match the value of the `HOST_NAME` parameter for the Siebel server.

       # clreslogicalhostname create -g siebel-rg logical_host

   logical_host

     Specifies an optional resource name of your choice.

4. Bring the resource group online.

   The following command brings the resource group online on the preferred node.

       # clresourcegroup online -M siebel-rg

5. Verify that the `siebenv.sh` file is located under server_root.
6. Create a file called `scsblconfig` under server_root , owned by the owner of `siebenv.sh`.

   If the Siebel server is installed locally, create the file `scsblconfig` under server_root on all nodes.

   For security reasons, make this file readable only by the owner.

       # cd server_root
       # touch scsblconfig
       # chown siebel:siebel scsblconfig
       # chmod 400 scsblconfig

7. Select a database user (for example, `dbuser/dbuserpassword`) with permission to connect to the database for use by the HA for Siebel Fault Monitor.
8. Select another Siebel user (for example, `sadmin/sadminpassword`) with permission to run the `compgrps` command in `srvrmgr`.
9. Add the following entries into the `sbsblconfig` file.

       export DBUSR=dbuser
       export DBPWD=dbuserpassword
       export SADMUSR=sadmin
       export SADMPWD=sadminpassword

10. Optional: If you want to encrypt the `scsblconfig` file, perform the following steps.
    1. As root user, encrypt the password file `scsblconfig` for the Siebel server and place the password file and the key file in the `/var/cluster` directory.

       In the example below, the password file `scsblconfig` is being encrypted and `sieb-rs` reflects the Siebel server resource name. The key file name must be in the format `/var/cluster/.siebelserver_resource_name_key`. The password file name must be in the format `/var/cluster/.siebelserver_resource_name_sbl_pdata`. The `PATH_TO_CONFIGFILE` is the location of the `scsblconfig` file.

           node1# dd if=/dev/urandom of=/var/cluster/.sieb-rs_key bs=16 count=1
           node1#  chmod 400 /var/cluster/.sieb-rs_key
           node1#  usr/sfw/bin/openssl enc -aes128 -e -in \
           $PATH_TO_CONFIGFILE/scsblconfig -k /var/cluster/.sieb-rs_key -out \
           /var/cluster/.sieb-rs_sbl_pdata
           node1#  chmod 400 /var/cluster/.sieb-rs_sbl_pdata

    2. Verify that the encrypted password can be decrypted.

           node1# /usr/sfw/bin/openssl enc -aes128 -d -in /var/cluster/.sieb-rs_sbl_pdata \
           -k /var/cluster/.sieb-rs_key -out /var/cluster/tmpfile

    3. Repeat steps a and b on all other Oracle Solaris Cluster nodes that will host the Siebel server resource.
11. If you are using Siebel 8.1 or later version, create a file called `scgtwyconfig` under server_root, owned by the owner of `siebenv.sh`.

    If the Siebel server is installed locally, create the file `scgtwyconfig` under server_root on all nodes. For security reasons, make this file readable only by the owner.

        # cd server_root
        # touch scgtwyconfig
        # chown siebel:siebel scgtwyconfig
        # chmod 400 scgtwyconfig

12. If you are using Siebel 8.1 or later version, in the `scgtwyconfig` file, enter the gateway user name and password that was given while configuring the gateway server enterprise.

    For example: `gtwyuser gtwypassword`

    This user name and password combination must have permission to connect to the database and also to the gateway server for use by the Sun Cluster HA for Siebel Gateway Fault Monitor.

        export GTWYUSR=gtwyuser
        export GTWYPWD=gtwyuserpassword

13. Optional: If you want to encrypt the `scgtwyconfig` file, perform the following steps.
    1. As root user, encrypt the password file `scgtwyconfig` for the Siebel server using the key file `/var/cluster/.siebelserver_resource_name_key`. Place the password file in the `/var/cluster` directory.

       In the example below, the password file `scgtwyconfig` is being encrypted and `sieb-rs` reflects the Siebel server resource name. The password file name must be in the format `/var/cluster/.siebelserver_resource_name_gtwy_pdata`. The `PATH_TO_CONFIGFILE` is the location of the `scgtwyconfig` file.

           node1#  usr/sfw/bin/openssl enc -aes128 -e -in \
           $PATH_TO_CONFIGFILE/scgtwyconfig -k /var/cluster/.sieb-rs_key -out \
           /var/cluster/.sieb-rs_gtwy_pdata
           node1#  chmod 400 /var/cluster/.sieb-rs_gtwy_pdata

    2. Verify that the encrypted password can be decrypted.

           node1# /usr/sfw/bin/openssl enc -aes128 -d -in /var/cluster/.sieb-rs_gtwy_pdata \
           -k /var/cluster/.sieb-rs_key -out /var/cluster/tmpfile

    3. Repeat steps a and b on all other Oracle Solaris Cluster nodes that will host the Siebel server resource.
14. Create the Siebel server resource.

        # clresource create -g siebel-rg \
        -t SUNW.sblsrvr \
        -p Confdir_list=server_root \
        -p siebel_enterprise=siebel enterprise name \
        -p siebel_server=siebel_server_name -p siebel_version=version_number sblsrvr-rs

    `-t` `SUNW.sblsrvr`

      Specifies the name of the resource type for the resource.

    `-p` Confdir_list

      Specifies the path name to the Siebel server root directory.

    `-p` `siebel_version`

      Specifies the Siebel server version.

      | Caution - If you enter an incorrect value for `siebel_version`, you might not see errors during validation but the resource startup will fail. If `siebel_version` is incorrect, the probe method is not able to verify database connectivity.

    `-p` siebel_enterprise

      Specifies the name of the Siebel enterprise.

    `-p` siebel_server

      Specifies the name of the Siebel server.

    sblsrvr-rs

      Specifies your choice of the name of the resource to add.

    The resource is created in the enabled state.

    | Caution - If you enter incorrect values for `siebel_enterprise` or `siebel_server`, you may not see any errors during validation. However, resource startup will fail. If `siebel_enterprise` is incorrect, `validate` method will not be able to verify database connectivity, which will result in a warning only.

15. Verify that the resource group and the Siebel server resource are online, by using `cluster status -t resourcegroup,resource` and `ps –ef` commands.

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