Siebel 8.

0 Essentials

Application Deployment Manager - Introduction

1 of 37

Module 50: Application Deployment Manager Introduction

Module Objectives
Business Needs Functional Overview Technical Architecture Troubleshooting

Limitations
Q&A

Application Deployment Manager - Introduction

3 of 37

Whats the Problem?

Deploying customizations is complex and time-consuming
Labour-intensive Manual process Error-prone Many different deployment techniques

Intrusive Can require lengthy outages

Application Deployment Manager - Introduction

4 of 37

Whats the Problem?

Deploying customizations is complex and time-consuming
Labour-intensive High man-power costs Error-prone Low quality of deployment / Cost of rework Intrusive High cost of downtime

Application Deployment Manager - Introduction

5 of 37

Scale of Problem
Deployments not only to Production
Most deployments are to non-production environments Development, Test, Training, etc Often daily drops between development systems

Typically multiple Production drops each year

Each drop can take hours to deploy

Often hundreds or even thousands of drops per year in total

Application Deployment Manager - Introduction

6 of 37

Whats Needed?
Automated deployment Re-usable deployment Decreased deployment time Decreased down-time Greater insight to whats being deployed

Application Deployment Manager - Introduction

7 of 37

What Does ADM Do?

Provides consistent framework to migrate just about all types of Siebel customizations

Changes can be bundled into re-useable packages

Can deploy to multiple servers with a single command

Application Deployment Manager - Introduction

8 of 37

ADM Feature Roadmap

Initially released in Siebel 7.7 Enhanced in Siebel 7.8
Additional data types (objects) supported Packaging Automation Many new data types Backup/restore Activation

Major Enhancements in Siebel 8.0

Development will continue through later Siebel releases

Application Deployment Manager - Introduction

9 of 37

New and Changed Features for ADM

New unified framework for deployment operations Packaging of customizations into re-usable packages
Category
Objects* List of Values State Models Access Groups

7.7
Functions Import Export Objects* Price Lists Custom Products

7.8
Functions Export Import Objects* Smart Scripts WF Policies Proposal Templates

8.0
Functions Enhanced Export Packaging Automated Deployment Activation, Backup, Restore

Runtime Objects

Files

SRF Web templates

Repository Objects

Workflow Processes Applets Views

* Please see Bookshelf for all objects.

Application Deployment Manager - Introduction

10 of 37

Functional Overview
Package Deploy
Activate

Recover

Bundle objects into single package One package can contain multiple different data types Can include objects based on
Repository (i.e. BC)
Exported through Siebel Tools Exported as SIF file Exported through Siebel client Exported as XML file Exported through simple file copy

Database (i.e. Workflow Policy)

File (i.e. Web Template)

Application Deployment Manager - Introduction

11 of 37

Functional Overview
Package Deploy
Activate

Recover

Deployment/Activation Automated deployment and activation Activation-only support (e.g., for objects deployed via dev2prod) Staged deployment by category / server Deployment orchestration stop/restart Deployment status and history Command line interface for deployment Limited high-availability deployment support (online deployment/activation, staged server deployment)* Validation for deployment registry, profile, package and target enterprise
*Limitations apply, some downtime expected

Application Deployment Manager - Introduction

12 of 37

Functional Overview
Package Recovery
Backup/Restore support for items affected on target system Detailed logging for deployment operations Extensible and meta-data driven deployment framework Integration CLI interface for third-party change management tools Support for non-Siebel App Servers as deployment targets (e.g., Report Server) Support for multiple Siebel Enterprises from one ADM installation

Deploy

Activate

Recover

Framework-Generic

Application Deployment Manager - Introduction

13 of 37

Scenario: Minor/Major Release Limited Repository

Target Enterprise

ADM Package
Repository

Deploy

Compile SRF

Sync Schema

Activate

Shut Down

ADM Package
Files

Startup

Release to Test step only

Deploy

Activate

ADM Package
DB Records

Deploy & Activate

Separate or combined packages

Application Deployment Manager - Introduction

14 of 37

Scenario: Major Release Full Repository

Target Enterprise
Repository

Repository Dat file Activation Package

WF / Tasks

Import

Sync Schema
Activate WF & Task

ADM Package
Repository

Shut Down

Test Enterprise

ADM Package
Files

Startup

Deploy

Activate

ADM Package

DB Records

Deploy & Activate

Application Deployment Manager - Introduction

15 of 37

ADM Functional Overview : User Process Flows

PROCESS Start Identify customizations and export to file Create and validate deployment package Load deployment package Create deployment session for target enterprise Perform target env. validation

Source environment (Packaging)

Deploy / Activate package Verify deployment (perform any recovery actions) Acknowledge, to terminate session

Deployment Server (Deploying)

Application Deployment Manager - Introduction

16 of 37

Deployment Steps
Deployment
valent delete

Recovery

load
create validate backup copy activate

acknowledge
Verify*

restore_activate

restore_copy

restore_session

* manual step optional

Application Deployment Manager - Introduction

17 of 37

Deployment Diagram
Source environment
Orchestration environment

Deployment Package

Management Server

Target environment

Siebel enterprise

Agent Siebel Server

Agent Siebel Server

Agent Siebel Server

Application Deployment Manager - Introduction

18 of 37

High Level Architecture Diagram

3rd Party Change Mgmt Tools
Command Line Interface

Client Environment

ADM Package Utility (Descriptor) ADM Admin Db Export (Db Items)

RMI JMX Remote (OEM)

Management Server
Deployment Package Management Functions (includes ADM modules)

Target Profile (XML) ADM Registry (XML) Local database

Siebel Tools (Repository Items) JMX Remote (OEM) Other Dev Editors (File Items) RMI

Orchestration Environment
JMX Agent (MBeans)

Shared File Staging Area

Server

Siebel Server

ADM Server Comp

Siebel Server

Source Environment

Target Environment

Application Deployment Manager - Introduction

19 of 37

Technologies

Agent - JMX The Java Management Extensions (JMX) technology is an open technology for management and monitoring that can be deployed wherever management and monitoring are needed. By design, this standard is suitable for adapting legacy systems, implementing new management and monitoring solutions and plugging into those of the future. Command Line - RMI The Java Remote Method Invocation (RMI) system allows an object running in one Java Virtual Machine (VM) to invoke methods on an object running in another Java VM. RMI provides for remote communication between programs written in the Java programming language.

Application Deployment Manager - Introduction

20 of 37

Repository/Database Deployment Flow

Package Load Package Management Server Deploy Package Log Status

Deploy to SiebSrvr

Notify Status

Management Agent

Create Async Req S_SRM_REQUEST Invoke Activation Report Status

ADM OM

ADM Processor

Activate Siebel Server Note: Separate execution for Deployment and Activation

Application Deployment Manager - Introduction

21 of 37

File Deployment Flow

Package

Load Package Management Server Deploy Package Log Status

Copy to SiebSrvr

Notify Status

Management Agent

File Siebel Server

Application Deployment Manager - Introduction

22 of 37

Deployment Architecture

Application Deployment Manager - Introduction

23 of 37

Ensure service startup successful

In Control Panel -> Admin Tools -> Services

Application Deployment Manager - Introduction

24 of 37

Management Server successful start

Management Server Log

MgmtServer INFO 2006-11-13 04:27:38 new connection to [ name=SDCHS22N002_1199 url=service:jmx:rmi://SDCHS22N002/jndi/rmi://SDCHS22N002:1199/jmx/siebel /agent state=online ]

Application Deployment Manager - Introduction

25 of 37

Management Server log info

Ignore messages Agent not online or name is invalid as long as there is a final online message Ignore message AlertManager already started with a long stack trace!

Application Deployment Manager - Introduction

26 of 37

Management Agent Log

No errors should be printed in the Agent.log file

Application Deployment Manager - Introduction

27 of 37

How to know the session number?

Session Number

Application Deployment Manager - Introduction

28 of 37

Successful Deployment Management Server

<PackageName>_<Session_Number>.log

Application Server, StatusDetail=This notification is for performance purpose only, not for status reporting!, Session Number=510, Status=MIGRATION_RUNNING, Server Host Name=sdchs22n002}'. Session-510 INFO 2006-11-13 04:55:55Successfully updated unit status in deployment group 'File Group - Reports - Application Server'. Session-510 INFO 2006-11-13 04:55:56Submitting unit 'database/42-5FNZY_Responsibility.xml' to agent 'SDCHS22N002_1199' succeeded. Session-510 INFO 2006-11-13 04:55:56Start processing status message: '{Group Name=File Group Reports - Application Server, StatusDetail=This notification is for performance purpose only, not for status reporting!, Session Number=510, Status=MIGRATION_COMPLETE, Server Host Name=sdchs22n002}'.

Application Deployment Manager - Introduction

29 of 37

Successful Deployment Management Agent - File

2006-11-13 04:55:52 -0700 FileMBean INFO 2006-11-13 04:55:53 Copying from source file 'D:\20302MS\Packages\sample\file\AppServer\reports\ENU\sample.rox'. FileMBean INFO 2006-11-13 04:55:53 Backing up destination file 'D:\20302\ses\siebsrvr\REPORTS\ENU\sample.rox'. FileMBean INFO 2006-11-13 04:55:53 Deploying to destination file 'D:\20302\ses\siebsrvr\REPORTS\ENU\sample.rox'. FileMBean INFO 2006-11-13 04:55:54 Results from action 'DEPLOY_COPY':file/AppServer/reports/ENU/sample.rox DEPLOYMENT_COMPLETE

Application Deployment Manager - Introduction

30 of 37

Successful Deployment Management Agent Database/Repository

2006-11-13 04:55:53 -0700 DataMBean INFO 2006-11-13 04:55:53 Submitting deployment request starts, parameters are: Category=Database Package Name=sample Group Name=Database Group Unit Name=database/42-5FNZY_Responsibility.xml Session Number=510 Execution Id=1 Enterprise Profile Parameters: DestinationRoot=d:\20302\ses\siebsrvr PerformDeployment=Yes PerformBackup=Yes PackageLocation=D:\20302MS\Packages ServerConnectString=siebel://SDCHS22N002:3320/siebel/ADMObjMgr_enu PerformValidation=Yes Password=****** DegParallelism=1 User Name=SADMIN WFPolicyActSrvr=SDCHS22N002_1199 PerformActivation=No StopOnError=Yes ADMBackupDir=\\SDCHS22N002\upload DataMBean INFO 2006-11-13 04:55:56 Output from Siebel server are: Status=NOT_STARTED reqId=88-25C14 DataMBean INFO 2006-11-13 04:55:56 Deployment request successfully submitted.

Application Deployment Manager - Introduction

31 of 37

Successful Deployment Siebel Server

Application Deployment Manager - Introduction

32 of 37

Failed deployment Siebel Server

2021 2006-11-13 05:30:14 2006-11-13 05:30:14 -0700 000001a7 001 003f 0001 09 ADMProc 9437198 304 5512 d:\20302\ses\siebsrvr\log\ADMProc_0009_9437198.log 8.0 SIA [20302] ENU ObjMgrLog Error 1 0000000845580158:0 2006-11-13 05:30:14 (eaiobjinst.cpp (2208)) SBL-EAI-13011: Field 'Name' in the integration component 'Responsibility' contains value 'ADM Sample Responsibility 1xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxx xxxxxxxxxxxx', which is longer than allowed length of 50 characters. ObjMgrLog Error 1 0000000845580158:0 2006-11-13 05:30:14 Integration Component instance 'Responsibility'. (adptutils.cpp (1222)) SBL-EAI-04397: No user key can be used for the [0] No user key can be used for the Integration Component instance

EAISiebAdpt EAISiebAdptErr 1 0000000845580158:0 2006-11-13 05:30:14 'Responsibility'.(SBL-EAI-04397) (IDS_ERR_EAI_SA_NO_USERKEY) ObjMgrLog Error 1 0000000845580158:0 2006-11-13 05:30:14 method 'Sync Transaction Property Set' at step 'Import Data'. ADM Event ADM Event UDAGenericError UDAGenericError 1 1 0000000845580158:0 0000000845580158:0

(stepexec.cpp (1540)) SBL-BPR-00162: Error invoking service 'UDA Service', Failed to deploy eai data. Deployment failed.

2006-11-13 05:30:14 2006-11-13 05:30:14

Application Deployment Manager - Introduction

33 of 37

ADM Limitations
Data Volumes (database)
ADM is not designed as a volume data transfer tool ADM is based on the EAI architecture Each data type is loaded as a single EAI transaction Subject to the normal performance limits

Data Volumes (repository)

Same limitations as database data types DEV2PROD should be used where extensive repository changes have been made DEV2PROD runs outside ADM control

Application Deployment Manager - Introduction

34 of 37

ADM Limitations

Restore

Will replace current image with image at time of backup Will lose any changes made since backup Should only be used prior to going live with new deployment This process is not a DB restore it restores the changes which have been done by ADM tool only. Changes made through UI or other tools are not revoked

Application Deployment Manager - Introduction

35 of 37

ADM Limitations

Extendibility
Can only extend for Database / File data types
No extendibility needed for Repository objects Cant add new categories of data type

No support for Activation

Theoretically possible if suitable Business Service exists, but not tested

Application Deployment Manager - Introduction

36 of 37

ADM Limitations
Downtime
Not a zero-downtime solution Any repository changes require server restart (for SRF) Some other changes require user logout System Impact shows the impact of deploying specific data types
Information only field, cant be changed

No Impact Rolling Server restart Manual Activation User Reconnect

Defined in ADM Registry for each data type Accessible through package definition

Application Deployment Manager - Introduction

37 of 37