Siebel Server Installation Guide for UNIX > Preparing for the Installation > Planning Your Siebel Deployment >

Planning the Siebel Directory Structure

You must plan where to install the various Siebel components on your servers, as well as how to install multiple versions, if your organization requires this for testing purposes.

Installing Multiple Versions of Siebel eBusiness Applications

If you are installing multiple versions of Siebel eBusiness Applications, each must be installed in a unique directory. You should use a naming convention that reflects the components and the version number being installed. Also check the value for RESONATE_ROOT in your siebenv.sh. The RESONATE_ROOT should be set to the actual Resonate install directory and not symbolic link; for example, /Export/Home/Resonate/.

CAUTION:  You can only install Siebel Gateway, Siebel Server, Database Server, Report Server Access, and EAI connectors in the same root directory. When installing multiple products into the same root directory, be sure that all products match the same release and patch level. You can install additional languages, but you cannot install additional products into a root directory after applying a patch. You must reapply the patch after you install additional languages.

Installing One Version of Siebel eBusiness Applications

On UNIX platforms, the Enterprise Server entities—the Name Server, Siebel Server, and Siebel Database Server installations—are installed by default under a common directory, referred to as SIEBEL_ROOT. In fact, there is no choice when you install the Siebel Database Server. It is automatically installed in the same directory as the Siebel Server. The SIEBEL_ROOT directory is created during the installation of the first Enterprise Server entity (for example, the Siebel Gateway) on a machine.

The component installers use /siebel as the default for SIEBEL_ROOT. Except when installing the Siebel Gateway Server, Siebel Server, Database Server, Report Server Access, or EAI connectors simultaneously, which are installed as subdirectories under the same root directory, you should install all other products in their own root directory to prevent potential conflicts.

Consider installing the CORBA Object Manager on a dedicated machine. The CORBA Object Manager can be installed on a machine that also supports the Siebel Enterprise Server components, although for best performance and scalability you should install the CORBA Object Manager onto a dedicated machine.

Record the directory names you decide on in your copy of the Deployment Planning Worksheet in Deployment Planning Worksheets.

NOTE:  Both the CORBA Object Manager and the Siebel Object Manager (a component of the Siebel Server) use configuration files located in $SIEBEL_ROOT/bin. If you install the CORBA Object Manager in a $SIEBEL_ROOT directory also used by the Siebel Server, be sure that you create uniquely named configuration files for the two types of Object Manager if their configurations differ. For information about how to register a configuration file with the appropriate component, see Siebel Server Administration Guide.


 Siebel Server Installation Guide for UNIX 
 Published: 24 June 2003