Oracle® Solaris Cluster Data Service for Siebel Guide

Exit Print View

Updated: January 2016
 
 

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

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, 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 to 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, 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 Oracle Solaris 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.

    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

    Caution  -  If you enter incorrect values for siebel_enterprise or siebel_server, you might 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.