|Bookshelf Home | Contents | Index | PDF|
For a cloning operation, the existing installed Siebel software instance from which you create a clone is called the source instance, and the computer where the software instance is installed is called the source computer. The new Siebel software instance that you deploy is called the target instance, and the computer where you deploy it is called the target computer.
When you deploy a Siebel Server clone, you can optionally create a new Siebel Gateway Name Server on the target computer. Alternatively, you can specify that the target instance of Siebel Server should use an existing installed instance of Siebel Gateway Name Server on another computer.
When you create the clone for the Siebel Server source instance, you can include certain configuration data sets, such as the Siebel Server configuration or the Siebel Enterprise configuration. Typically, you export the Siebel Server configuration as part of the clone. If you will create a new Siebel Gateway Name Server on the target instance, then you also export the Siebel Enterprise configuration. When you deploy the clone, you can import this configuration data into the new or existing Siebel Gateway Name Server for the new target instance of Siebel Server.
To specify these (and other) variations in how you create and deploy a clone, you use different settings in the cloning properties files, which are described in Properties File Settings for Cloning an Installation.
The files for the Siebel Database Configuration Utilities, Siebel EAI, and Siebel Management Agent are also included if you create and deploy a clone for a Siebel Server instance for which these modules were also installed. However, do not use the Database Configuration Wizard on the target instance, because you already have it on the source instance. You must configure the Siebel Management Agent instance separately on the target computer after deploying the clone.
The files that make up the Siebel cloning utility are provided in the file clone.zip. You can find clone.zip with the JAR files after you unpack the media zip files for the current release, Siebel CRM version 126.96.36.199 or version 188.8.131.52. For more information about obtaining the Siebel CRM media, see About Siebel CRM Releases and Obtaining Siebel Installation Media Files. See also the applicable Siebel Maintenance Release Guide on My Oracle Support.
You must save or copy the file clone.zip to any computer that will be used as a source or target computer for a cloning operation. On each source or target computer, you use a standard unpacking tool, such as WinZip or unzip, to extract files into a directory named
Cloning an existing source instance includes separate tasks to create the clone on a source computer and to deploy the clone on a target computer. Both of these tasks involve running the Siebel cloning utility. These tasks are outlined in Process of Cloning a Siebel Installation.
You can specify files or file types that you want to exclude from a cloning operation. You do this by specifying a value for the Exclude File List parameter in the properties file. It is strongly recommended that you do not exclude any files from the cloning operation unless you are certain that the target instance does not require those files. Log files are never cloned and do not have to be specified for exclusion.
|Siebel Installation Guide for UNIX||Copyright © 2014, Oracle and/or its affiliates. All rights reserved. Legal Notices.|