Siebel Server Cloning available in 8.1.1.9 / 8.2.2.2

2,665 views
2,456 views

Published on

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

Published in: Technology
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,665
On SlideShare
0
From Embeds
0
Number of Embeds
157
Actions
Shares
0
Downloads
0
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Siebel Server Cloning available in 8.1.1.9 / 8.2.2.2

  1. 1. <Insert Picture Here>Siebel Server Cloning
  2. 2. 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 Configuration2 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
  3. 3. 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+ InnovationPacks.
  4. 4. Business Benefits• Reduce total cost of operations of Siebel installation and patching• Improve Siebel server manageability through faster and reliable server provisioning
  5. 5. Siebel Server Cloning 2 Test Environment 1 Source Environment 2Step 1: create snapshot from source Production EnvironmentStep 2: apply snapshot to target
  6. 6. 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.
  7. 7. Access Server Cloning Utility
  8. 8. 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.
  9. 9. Property File - CloneMode(clone)Type (full,delta)SnapshotLocationDelta Zip
  10. 10. Property File - CloneEnterprise& ServerNameExportEnterpriseExportSiebel Server
  11. 11. Your Source Environment
  12. 12. Create SnapshotOn Unix: execute ./clone.sh <properties file>
  13. 13. Create Snapshot
  14. 14. Create Snapshot
  15. 15. Create Snapshot
  16. 16. Your Target Environment
  17. 17. Your Target Environment
  18. 18. Property File - DeployMode(Deploy)Type (full,delta)SnapshotLocation
  19. 19. Property File - DeployImportEnterpriseImportServerCreateGateway
  20. 20. 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
  21. 21. Your Cloned Environment
  22. 22. Your Cloned Environment
  23. 23. 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
  24. 24. 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.
  25. 25. 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
  26. 26. Siebel Server CloningServer Cloningpackaged separatelyTemplates providedout-of-the-box Source: 4 Target: 4Supports end-to-endcloning process Installation clone Server config cloneServer cloning supportsboth full clone and deltaclone
  27. 27. 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

×