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 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.
# clresourcetype register SUNW.sblgtwy
# clresourcegroup create [-n node] gateway-rg
Specifies the node name that can master this resource group.
Specifies your choice of the name of the failover resource group to add. This name must begin with an ASCII character.
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
Specifies an optional resource name of your choice.
# clresourcegroup online -M gateway-rg
The owner of this file launches the Siebel Gateway Server when the Siebel Gateway resource is brought online.
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
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 HA for Siebel Gateway Fault Monitor.
export GTWYUSR=gtwyuser export GTWYPWD=gtwyuserpassword
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
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
# clresource create -g gateway-rg \ -t SUNW.sblgtwy \ -p Confdir_list=gateway_root -p siebel_version=version number sblgtwy-rs
Specifies the name of the resource type for the resource.
Specifies the path name to the Siebel Server root directory.
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.
Specifies your choice of the name of the resource to add.
The resource is created in the enabled state.