It’s been a very, very busy couple of months! Our baby is due in March and we’re manically trying to get things in place! Exciting times, but I’m finding less and less time for my beloved blog.
I’m going to try to conclude my article on Siebel Clustering today – this article may be a bit shorter than usual, as I have to assemble the new baby changing unit that arrived this morning. 😉
You should have 4 servers now in your virtual environment:
- A SAN server, exposing a folder location to act as the Quorum disk
- A Windows 2003 DNS and AD server, so that we can maintain our clusters and they know where to find each other
- 2 Windows 2003 Server that will run clustering, both registered on your new domain (I’ve gone for oli.com) and added as hosts to your AD
Your AD setup will look something like this:
The first thing to do is to enable clustering on the two hosts:
- Connect to your first cluster host
- Click Start > All Program > Administrative Tools > Cluster Administrator
- Select the File > New > Cluster… menu item
- Click next then enter the domain that you set up on the AD server you installed form last time. I’m using oli.com
- Give the cluster a name (SIEB-CLUST) and click next
- Enter the first node host name and click next
- Windows will validate your node and cluster config to make sure you have everything in place
- Enter an IP address for the cluster – something like 192.168.1.101
- Specific an Admin user within your domain (Administrator and the password you set up when configuring AD will do nicely)
- Click the Quorum button on the summary screen and make sure your shared SAN disk is selected
- Click next to finish the configuration.
You should see something like this:
- Select File > New > Node
- Add the name of your second host
- Windows will now do a bit of checking – enter your admin password, same as before
- Windows will complete the creation of the second node
You’ll have something like this:
Now to install the Siebel Gateway as a cluster service
- Perform a standard Siebel Gateway installation as normal
- When prompted, check the ‘Clustered Gateway’ option and specify the cluster name – SIEBEL-CLUSTER in the example above
- Install the Gateway to your shared disk resource – this would typically be a different drive to the Quorum disk, but we’ll use this in the example for simplicity
- Once installation is complete, create a generic service resource on your first node – we’ll use the Cluster Group for now but you should create a specific group for each application
- Specify the Siebel Gateway service name – gtwyns
Start it up and you’ll have something like this:
- Right click the Cluster Group and select ‘Move Group…’
- You’ll see your resources come up on node 2
- Now, connect to node 2 as the Gateway installation disk is now hosted on this server
- Open a command prompt and navigate to the Gateway installation location and CD to the ADMIN folder
- Run the cluster configuration batch file: cluster_gtwy.bat
- This will set up various bits and pieces, such as ODBC entries, that will allow the Gateway to run on the second node.
- Fail the resource group back to node 1 and you’re done!
Hopefully this article will have given you a basic understanding of what’s involved in enabling Windows Clustering and installing Siebel components into the cluster.
As ever, please feel free to post your own experiences or ask any questions on this topic.