The document describes Oracle's Siebel Server Cloning utility which allows users to clone Siebel server installations, configurations, and patches from a source environment to target environments. The utility captures the source installation, server configuration, and changes during patching and allows users to deploy these to other target environments. This simplifies Siebel server provisioning and improves manageability. The utility is available in Siebel 8.1.1.9+ and 8.2.2.2+ innovation packs.

1. Oracle Online Training Materials – Usage Agreement
Use of the information, documents and online training courses (collectively, “Materials”) found on this area of the Site constitutes
agreement with the following terms and conditions (as well as those set forth in the Purpose and Disclaimer sections below):
1. Oracle is pleased to allow its business partner (“Partner”) to download and copy the Materials found on this area of the Site. The
Materials are proprietary information of Oracle. Partner or other third party at no time has any right to resell, redistribute or create
derivative works from the Materials. The use of the Materials is restricted to the non-commercial, internal training of the Partner’s
employees only. The Materials may not be used for training, promotion, or sales to customers or other partners or third parties.
2. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective
owners.
3. Oracle disclaims any warranties or representations as to the accuracy or completeness of any Materials. Materials are provided "as
is" without warranty of any kind, either express, implied or statutory, including without limitation the implied warranties of merchantability,
satisfactory quality, fitness for a particular purpose, accuracy, timeliness and non-infringement of third-party rights. The information
contained herein is subject to change without notice.
4. Under no circumstances shall Oracle be liable for any loss, damage, liability or expense incurred or suffered which is claimed to have
resulted from use of these Materials. As a condition of use of the Materials, Partner agrees to indemnify Oracle from and against any and
all actions, claims, losses, damages, liabilities and expenses (including reasonable attorneys' fees) arising out of Partner’s use of the
Materials.
1 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential

2. Purpose:
This document provides an overview of features and enhancements included in Siebel Release 8.1.1.8 and applicable updates. It is
intended solely to help you assess the business benefits of upgrading your existing Oracle Products to this release, or implementing
completely new Oracle developed products, and planning your I.T. Projects.
Disclaimer:
This document in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle. Your
access to and use of this confidential material is subject to the terms and conditions of your Oracle Software License and Service
Agreement or other applicable contract with Oracle, with which you agree to comply. This document and information contained herein
may not be disclosed, copied, reproduced or distributed to anyone outside Oracle without Oracle’s prior written consent. This document
is not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or
affiliates.
This document is intended to outline our general product direction. It is intended for informational purposes only and solely to assist you
in planning for the implementation and upgrade of the product features described. Release information contained in this document is not
a firm development plan. This is not a commitment to deliver any material, code, or functionality, and should not be relied upon in
making purchasing decisions. The development, release, and timing of any features or functionality, and inclusion or not thereof in the
commercially available version of the Software, if any, is subject to change at any time and is always at Oracle’s sole discretion. This
document is not considered part of the applicable program documentation.
Due to the nature of the product architecture, it may not be possible to safely include all features described in this document without
risking significant destabilization of the code.
2 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential

3. <Insert Picture Here>
Siebel Server Cloning
September 2012
Agnes Zhang, Oracle Siebel CRM Product Management

4. Siebel Server Deployment
•Ease of
Installation & Patching
Software/Patch Installation &
1 Deployment
Host A Patching
-Software Binaries
-Gateway -Patch Binaries
•Ease of
-Server Configuration
-Siebel Server
-SWSE 3 Host B
Server
-Software Binaries
Configuration
-Patch Binaries
-Server Configuration
2 Server Configuration
•Ease of
Host C Server
-Gateway -Software Binaries
Provisioning
-Patch Binaries
-Siebel Server
-Server Configuration
-SWSE
Server Configuration
Deployment
•Oracle EM
Target Environments Integration
4 Oracle Enterprise Manager

5. Siebel Server Cloning
• Installation Cloning
• Siebel server cloning
• Enterprise cloning
• Patch Deployment
• Capture installation changes
• Apply changes to target environments
• Server Configuration Deployment
• Extract server configuration settings
• Migrate server configurations to target
environments
Siebel Server Cloning is available in 8.1.1.9+/8.2.2.2+ Innovation
Packs.

6. Business Benefits
• Reduce total cost of operations of Siebel installation
and patching
• Improve Siebel server manageability through faster
and reliable server provisioning

7. Siebel Server Cloning
2 Test Environment
1
Source Environment
2
Step 1: create snapshot from source
Production Environment
Step 2: apply snapshot to target

8. Prerequisites & Scope
• Prerequisites
• JRE 6 is required on both Source and Target machines.
• Source and Target directory structure must be same.
• Configure database client on the target machine prior to cloning
• Snapshot location must be accessible from Target machine.
• Scope
• Includes Siebel Enterprise, Siebel Server and SWSE cloning
• Siebel Database Configuration Utilities, Siebel EAI and Siebel
Management Server are also included if your Siebel Server instance
already has these modules installed. Re-configuration of MS is
needed on the target instance.
• Database & web server cloning is not included.
• Manual Web Server cloning is needed on target machine before
application URL can be brought up.

9. Access Server Cloning Utility

10. Access Server Cloning Utility
Source
Property Files:
used for
generating
snapshot
Target
Property Files:
used for
deploying
snapshots to
target
environment
Usage: served
as templates
only. User should
create their own
property files.

11. Property File - Clone
Mode
(clone)
Type (full,
delta)
Snapshot
Location
Delta Zip

12. Property File - Clone
Enterprise
& Server
Name
Export
Enterprise
Export
Siebel Server

13. Your Source Environment

14. Create Snapshot
On Unix: execute ./clone.sh <properties file>

15. Create Snapshot

16. Create Snapshot

17. Create Snapshot

18. Your Target Environment

19. Your Target Environment

20. Property File - Deploy
Mode
(Deploy)
Type (full,
delta)
Snapshot
Location

21. Property File - Deploy
Import
Enterprise
Import
Server
Create
Gateway

22. Deploy Snapshot to Target
•Add –invPtrLoc to register Oracle home into product inventory on target instance
•On Unix: execute ./clone.sh <properties file>
•AIX only: add –jreLoc

23. Your Cloned Environment

24. Your Cloned Environment

25. Usage Scenarios
• Full Clone: Siebel Gateway, Enterprise, Siebel Server
and SWSE Logical Profile is installed on the same
host. Clone the full deck from source to target.
• Delta Clone: Gateway, Enterprise, Siebel Server and
SWSE Logical Profile is installed on the same host.
Clone incremental changes from source to target.
• Single Enterprise, multiple Siebel Servers

26. Usage Scenarios
• Clone a Siebel Server and point it to an existing Siebel Gateway
• Set up an instance where you have configured Siebel Gateway and
Enterprise (instance #3)
• Clone Siebel Server from your Source instance
• On Target/Staging machine, set create Gateway=N & Import
Enterprise=N
• On Target/Staging machine, set Target Gateway Server Host Name
in property file and point it to instance #3
• Import Siebel configuration. This will import Siebel configuration into
instance #3.
• Siebel Gateway is never get cloned. We either create a new one
on target or connect to an existing Siebel Gateway.

27. Known Limitations
• Cloning will only clone the software and server
configuration. After cloning, users need to manually
create application shortcuts on target instance.
• Database and Web Server clone is not included.
• Make sure the clone utility on Unix has full execute
permissions
• Server configuration cloning cannot be executed
separately

28. Siebel Server Cloning
Server Cloning
packaged separately
Templates provided
out-of-the-box
Source: 4
Target: 4
Supports end-to-end
cloning process
Installation clone
Server config clone
Server cloning supports
both full clone and delta
clone

29. Testing Coverage
Platforms: all supported Windows &
Unix platforms
Languages: ENU & primary non-
ENU languages
Cloning Scenarios
Enterprise Server only
Enterprise Server + Siebel Server
Siebel Server only
Multiple Siebel Servers
Siebel Web Server Extension only