Siebel Server Installation Guide for Microsoft Windows > Preparing for the Installation >

Deployment of Siebel 7 Gateway Versus Siebel 6 Gateway

The differences between deployment recommendations for the Siebel Gateway in Siebel 7 versus Siebel 6 can be described as follows.

Deployment of Siebel 6 Gateway

In Siebel 6, the installer assumed that the Name Server and Central Dispatch Scheduler were located on the same server. If you selected the "Use Resonate" box during installation, the Siebel Gateway installer looked for Central Dispatch software on the local server. This forced the Name Server to colocate with either the Central Dispatch Scheduler (the default assumption) or a load-balanced Siebel Server.

When high availability was required by the Name Server, the Name Server could be clustered using Microsoft Cluster Service in a server pair. However, Central Dispatch could not be part of the cluster. Because Central Dispatch was colocated on the same server as the Name server, this forced customers to resort to installer workarounds to separate Central Dispatch from the Name Server. This is not required in Siebel 7.

Deployment of Siebel 7 Gateway

In Siebel 7, the Name Server installer does not look for local installation of the Central Dispatch software. You can, as a result, pick the Siebel Gateway deployment that best suits your needs. Also, Siebel eBusiness Applications do not support any clustering technology on the server with Central Dispatch components, whether these are the Central Dispatch Scheduler or a load-balanced Siebel Server. This results from the complexity of clustering a Central Dispatch server, but also due to the fact that Central Dispatch provides the same type of failover capability as the clustering technology.

NOTE:  This restriction does not necessarily increase the hardware requirement for the Siebel Gateway when Name Server high availability is required.

 Siebel Server Installation Guide for Microsoft Windows 
 Published: 25 June 2003