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

Language:

Use this procedure to configure HA for Siebel Gateway 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.

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.

Register the resource type for the Siebel Gateway.
```
# clresourcetype register SUNW.sblgtwy
```

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

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.

Bring the resource group online.
```
# clresourcegroup online -M gateway-rg
```

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.
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
```
In the scgtwyconfig file, enter the gateway user name and password that was given while configuring the Gateway Server enterprise.
For example: gtwyuser gtwy-user-password

This user name and password combination must have permission to connect to the database and also to the Gateway Server for use by the HA for Siebel Gateway Fault Monitor.
```
export GTWYUSR=gtwyuser
export GTWYPWD=gtwy-user-password
```
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 these steps on all other Oracle Solaris Cluster nodes that will host the Gateway Server resource.

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.

If you enter an incorrect value for Siebel_version, you might not see errors during validation, but the resource startup will fail. If the Siebel_version property 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.

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