|Bookshelf Home | Contents | Index | PDF|
This topic is part of General Considerations in Planning Your Siebel Deployment.
By default, the Siebel installers automatically install Siebel software in unique directory names that will not conflict with other Siebel software components that you install on the same machine. To install another instance of the same version of a product on a single machine (where applicable), specify a custom installation path.
NOTE: In this context, same version refers to all releases sharing the same first two digits—such as 8.0, 18.104.22.168, 22.214.171.124, 8.0.1 (if available), and so on. Each product instance of the same version would be installed to the same default installation path, unless you specify a custom path. A three-digit release can be installed as a maintenance release if the prior release of the same series is already installed. For example, if available, 8.0.1 could be installed as a maintenance release if 8.0 or 8.0.0.x is already installed.
Components of the same Siebel Enterprise Server that you install on the same machine must be installed into the same root directory. These components include Siebel Gateway Name Server, Siebel Server, Database Configuration Utilities, and EAI Connector. See also File and Directory Naming Conventions.
NOTE: You cannot install additional Siebel Enterprise Server components 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.
Multiple versions of some Siebel components can be installed on the same machine. Sometimes you may need to do this as part of some upgrade scenarios. For more information about upgrading, see Siebel Database Upgrade Guide.
|Siebel Installation Guide for Microsoft Windows||Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices.|