Select Page

Self Signed Certificate for Siebel 17

It has been rather quiet of late, I’m afraid. The trials and responsibilities of everyday life continue to thwart my efforts to update the blog and keep you appraised of all things “after Siebel”! However, Siebel 17 is not forgotten and I’ve been working closely with Oracle to iron out a bug or two in the IP 2017 deployment process as well a running a project to deploy IP 2017 as part of a large Enterprise programme. More on all that shortly.

In the meantime, I wanted to put the question of self signed certificates to bed and show you how to produce keystore and truststore files for an IP 2017 installation.

You’ll have to install OpenSSL and a Java SDK somewhere on your machine. The machine itself must have a Fully Qualified Domain Name: “MySiebelHost” will not do, it must be “MySiebelHost.mydomain”. In Windows, you can easily get around this without having to actually create a domain and register your machine on it by setting the “Full computer name” in the System Properties:

Anyway, without further ado, I give you “MakeKeys.bat”:

Simply save to a .BAT file (this is Windows, but should work with small mods on a Linux environment) and set the parameters appropriately. Execute the file and use the resulting “siebelkeystore.jks” file for both the keystore and truststore in your Siebel installations, across all components on that machine.

Windows Clustering in Siebel – Part 2

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 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:

  1. Connect to your first cluster host
  2. Click Start > All Program > Administrative Tools > Cluster Administrator
  3. Select the File > New > Cluster… menu item
  4. Click next then enter the domain that you set up on the AD server you installed form last time. I’m using
  5. Give the cluster a name (SIEB-CLUST) and click next
  6. Enter the first node host name and click next
  7. Windows will validate your node and cluster config to make sure you have everything in place
  8. Enter an IP address for the cluster – something like
  9. Specific an Admin user within your domain (Administrator and the password you set up when configuring AD will do nicely)
  10. Click the Quorum button on the summary screen and make sure your shared SAN disk is selected
  11. Click next to finish the configuration.

You should see something like this:

Now add the second node:

  1. Select File > New > Node
  2. Add the name of your second host
  3. Windows will now do a bit of checking – enter your admin password, same as before
  4. 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

  1. Perform a standard Siebel Gateway installation as normal
  2. When prompted, check the ‘Clustered Gateway’ option and specify the cluster name – SIEBEL-CLUSTER in the example above
  3. 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
  4. 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
  5. Specify the Siebel Gateway service name – gtwyns

Start it up and you’ll have something like this:

Now, fail the group over to node 2 and setup the Gateway:

  1. Right click the Cluster Group and select ‘Move Group…’
  2. You’ll see your resources come up on node 2
  3. Now, connect to node 2 as the Gateway installation disk is now hosted on this server
  4. Open a command prompt and navigate to the Gateway installation location and CD to the ADMIN folder
  5. Run the cluster configuration batch file: cluster_gtwy.bat
  6. This will set up various bits and pieces, such as ODBC entries, that will allow the Gateway to run on the second node.
  7. 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.

Windows Clustering in Siebel

I’m going to move away from configuration for the time being and go back to the architecture and installation side of Siebel.

A recent project had me building an entire Siebel Production environment from scratch. I’ve been using Windows clustering, Siebel load balancing, Oracle reporting and a wide range of other technologies. This particular environment is built on Windows 2003 Server but the same principles apply to 2008. So, I thought I’d start off a new series of articles starting with Windows Clustering and its application in Siebel.

In particular, the following components of Siebel fit well into a clustered architecture:

  1. The Siebel Gateway
  2. One or more Siebel Application Servers
  3. The Siebel File System

We’ll look at setting up Windows Clustering, defining resource groups and resources to support it and we’ll look at installing and configuring Siebel in a clustered environment.

As ever, Siebel Bookshelf has a lot of information on the Siebel side of things. Windows Clustering is separate but you’ll find a load of information on a site such as Microsoft Technet. It’s well worth a Google in advance of the articles, to familiarise yourself with the technology.

In order to learn this stuff I installed some Windows 2003 VMs in my Virtual Box environment:


I also downloaded a free SAN server environment called OpenFiler that I installed on a Linux VM:


I’d encourage you to do the same and have a basic setup of the 3 machines before we start. The SAN disk needs to be mounted and visible on both of the cluster nodes.

See you next time for more clustering fun.