Sun Cluster Data Service for Siebel Guide for Solaris OS

Registering and Configuring Sun Cluster HA for Siebel

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

Setting Sun Cluster 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 Sun Cluster HA for Siebel requires you to set. For information about all Sun Cluster HA for Siebel extension properties, see Appendix A, Sun 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 scrgadm(1M) command that creates or modifies the resource:


-x property=value 
-x 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 Sun Cluster Data Services Planning and Administration Guide for Solaris OS to configure resources after the resources are created.

ProcedureHow to Register and Configure Sun Cluster HA for Siebel as a Failover Data Service

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

Steps
  1. Become superuser on one of the nodes in the cluster that hosts the application server.

  2. Add the resource type for the Siebel gateway.


    # scrgadm -a -t 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.



    # scrgadm -a -g gateway-rg [-h nodelist]
    
  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.


    # scrgadm -a -L -g gateway-rg -l logical_hostname
    
  5. Bring the resource group online.


    # scswitch -Z -g 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. Create the Siebel gateway resource.


    # scrgadm -a -j sblgtwy-rs -g gateway-rg \
    -t SUNW.sblgtwy  \
    -x Confdir_list=gateway_root
    
  8. Enable the Siebel gateway resource.


    # scswitch -e -j sblgtwy-rs
    
  9. Verify that the Siebel resource group and the Siebel gateway resource are online by using scstat —g and ps —ef.

ProcedureHow to Register and Configure the Siebel Server

Steps
  1. Add the resource type for the Siebel server.


    # scrgadm -a -t 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.



    # scrgadm -a -g siebel-rg [-h nodelist]
    
  3. Add the logical hostname resource.

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


    # scrgadm -a -L -g siebel-rg -l logical-hostname
    
  4. Bring the resource group online.

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


    # scswitch -Z -g 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 Sun Cluster 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. Create the Siebel server resource.


    # scrgadm -a -j sblsrvr-rs -g siebel-rg \
    -t SUNW.sblsrvr \
    -x Confdir_list=server_root \
    -x siebel_enterprise=siebel enterprise name \
    -x siebel_server=siebel server name
    

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


  11. Enable the Siebel server resource.


    # scswitch -e -j sblsrvr-rs
    
  12. Verify that the resource group and the Siebel server resource are online, by using scstat –g and ps –ef commands.