Siebel Installation Guide for Microsoft Windows: Servers, Mobile Web Clients, Tools > Installing the Siebel Gateway Name Server >

Siebel Gateway Name Server Installation Requirements


Review the following guidelines before installing the Siebel Gateway Name Server.

CAUTION:  Do not install Siebel Business Applications without first reviewing System Requirements and Supported Platforms on Siebel SupportWeb.

  • If the machine on which you are installing the Siebel Gateway Name Server will also support a Siebel Server, you must have all the required third-party products installed for that component, as listed in System Requirements and Supported Platforms on Siebel SupportWeb.
  • If you will be clustering the Gateway Name Server, plan your use of clustering or redundant disk arrays (RAID) to configure against a single point of failure. For more information on this topic, see the Deployment Planning Guide.
  • Each machine that supports a Siebel Server must have TCP/IP network connectivity to the machine on which the Siebel Gateway Name Server will be installed. Verify network connectivity between all such machines, using the ping utility.
  • Verify that the network names of the servers that will support the Siebel Gateway Name Server and all Siebel Servers are recorded in Deployment Planning Worksheet. You will need this information later when installing the Siebel Servers and Siebel clients.

    NOTE:  Gigabit Ethernet cards must be set to Auto Configure.

  • Install the Siebel Gateway Name Server only once for each Siebel Enterprise Server. If needed, multiple Siebel Enterprises can be supported by a single Siebel Gateway Name Server. It is recommended that you only install one Siebel Gateway Name Server on a machine.
  • Siebel Gateway Name Server uses port 2320 by default. If necessary, you can select any port number (lower than 32767) that is free on the machine where the Siebel Gateway Name Server is running. Do not use port number 2321, which is the default port number for the SCBroker (Siebel Connection Broker) component.
  • Review the issues described in Managing Temporary Disk Space Required by Installers. For example, make sure you have adequate disk space.
  • Verify that you have created a Siebel installation image that includes all products you require, and that you have appropriate permissions to the network directories where the Siebel image is located. For information about creating the Siebel installation image, see Creating the Siebel Installation Image on the Network.
  • You cannot install additional products into a root directory after applying a patch. You can install additional languages into a root directory after applying a patch, but you must reapply the patch afterwards.
Siebel Installation Guide for Microsoft Windows: Servers, Mobile Web Clients, Tools