Module 52 Application Deployment Manager - Introduction

1 of 37Application Deployment Manager - Introduction

Siebel 8.0 Essentials

Module 50: Application Deployment Manager - Introduction


Module Objectives

• Business Needs

• Functional Overview

• Technical Architecture

• Troubleshooting

• Limitations

• Q&A


What’s the Problem?

Deploying customizations is complex and time-consuming

• Labour-intensive– Manual process

• Error-prone– Many different deployment techniques

• Intrusive– Can require lengthy outages


What’s 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


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


What’s Needed?

Automated deployment

Re-usable deployment

Decreased deployment time

Decreased down-time

Greater insight to what’s being deployed


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


ADM Feature Roadmap

Initially released in Siebel 7.7

Enhanced in Siebel 7.8• Additional data types (objects) supported

Major Enhancements in Siebel 8.0• Packaging• Automation• Many new data types• Backup/restore• Activation

Development will continue through later Siebel releases


New and Changed Features for ADM

New unified framework for deployment operations

Packaging of customizations into re-usable packages

* Please see Bookshelf for all objects.

Category 7.7 7.8 8.0

Objects* Functions Objects* Functions Objects* Functions

Runtime Objects

List of Values

State Models

Access Groups

Import

Export

Price Lists

Custom Products

Export

Import

Smart Scripts

WF Policies

Proposal Templates

Enhanced Export

Packaging

Automated Deployment Activation, Backup, Restore

Files SRF

Web templates

Repository Objects Workflow Processes

Applets

Views


Functional Overview

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

• Database (i.e. Workflow Policy)– Exported through Siebel client– Exported as XML file

• File (i.e. Web Template)– Exported through simple file copy

Package Deploy Activate Recover


Functional Overview…

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



Functional Overview …


Recovery• Backup/Restore support for items affected on target system

Framework-Generic• 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


Scenario: Minor/Major Release – Limited Repository

ADM PackageADM PackageTarget

EnterpriseRepository

Sh

ut D

ow

n

Deploy

Sta

rtu

p

ADM PackageADM PackageFiles

Deploy Activate

ADM PackageADM PackageDB Records

Deploy &Activate

ActivateCompile

SRF

Separate or

combined packages

“Release to Test” step only

SyncSchema


Scenario: Major Release – Full Repository

ADM PackageADM PackageRepository

ADM PackageADM PackageFiles

ADM PackageADM PackageDB Records

RepositoryDat file

Target Enterprise

Import SyncSchema

Sta

rtu

p

Deploy Activate

Deploy &Activate

Sh

ut D

ow

n

Activate WF & Task

Activation PackageActivation PackageWF / Tasks

Repository

Test Enterprise


ADM – Functional Overview : User Process Flows

PROCESS

Start

Source

environment

(Packaging)

Load deployment

package

Acknowledge, toterminate session

Deploy / Activate package

Perform target

env. validation

Create deployment

session for target

enterprise

Create and validate

deployment package

Deployment Server (Deploying)

Identify

customizations

and export to file

Verify deployment

(perform any

recovery actions)


Deployment Steps

valent

load

create

validate

backup

copy

activate

restore_session

restore_copy

restore_activate

optional

Verify*

Deployment Recovery

acknowledge

delete

* manual step


Deployment Package

Target environment

Deployment Diagram

Source environment

Siebel enterprise

Orchestration environment

Management Server

Siebel Server

Agent

Siebel Server

Agent

Siebel Server

Agent


High Level Architecture Diagram

Deployment Package

Deployment Package

Siebel Server

Management Functions(includes ADM modules)

JMX Remote – (OEM)

Server Siebel Server

Local database

Management Server

JMX Agent (MBeans)

ADM Admin Db Export (Db Items)

Siebel Tools(Repository

Items)

Source Environment

Target Environment

ADM Server Comp

Orchestration Environment

ADM Registry

(XML)

Target Profile (XML)

Other Dev Editors

(File Items)

ADM Package Utility

(Descriptor)

3rd Party Change Mgmt Tools

RMI

Client Environment

Command Line Interface

RMI

JMX Remote (OEM)

Shared File Staging

Area


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.


Repository/Database Deployment Flow

Management Server

Management Agent

Siebel Server

ADM OM

PackageLoad

Package

Deploy Package

Deploy to SiebSrvr

Create Async Req

S_SRM_REQUEST

ADM Processor

Invoke Activation

Activate

Report Status

Notify Status

Log Status

Note: Separate execution for Deployment and Activation


File Deployment Flow

Management Server

Management Agent

Siebel Server

PackageLoad

Package

Deploy Package

Copy to SiebSrvr

Notify Status

Log Status

File


Deployment Architecture


Ensure service startup successful

In Control Panel -> Admin Tools -> Services


Management Server successful start

Management Server Log

MgmtServer INFO2006-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 ]


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!


Management Agent Log

• No errors should be printed in the Agent.log file


How to know the session number?

Session Number


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}'.


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


Successful DeploymentManagement 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.


Successful Deployment Siebel Server


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 1xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx… xxxxxxxxxxxx', which is longer than allowed length of 50 characters.

ObjMgrLog Error 1 0000000845580158:0 2006-11-13 05:30:14 (adptutils.cpp (1222)) SBL-EAI-04397: No user key can be used for the Integration Component instance 'Responsibility'.

EAISiebAdpt EAISiebAdptErr 1 0000000845580158:0 2006-11-13 05:30:14 [0] No user key can be used for the Integration Component instance 'Responsibility'.(SBL-EAI-04397) (IDS_ERR_EAI_SA_NO_USERKEY)

ObjMgrLog Error 1 0000000845580158:0 2006-11-13 05:30:14 (stepexec.cpp (1540)) SBL-BPR-00162: Error invoking service 'UDA Service', method 'Sync Transaction Property Set' at step 'Import Data'.

ADM Event UDAGenericError 1 0000000845580158:0 2006-11-13 05:30:14 Failed to deploy eai data.

ADM Event UDAGenericError 1 0000000845580158:0 2006-11-13 05:30:14 Deployment failed.


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


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


ADM Limitations…

Extendibility• Can only extend for Database / File data types

– No extendibility needed for Repository objects– Can’t add new categories of data type

• No support for Activation– Theoretically possible if suitable Business Service exists, but not tested


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, can’t be changed— No Impact— Rolling Server restart— Manual Activation— User Reconnect

– Defined in ADM Registry for each data type

– Accessible through package definition

Documents

Module 52 Application Deployment Manager - Introduction