ADM Application Deployment Manager€“ Low quality of deployment / Cost of rework ... Management Agent Siebel Server ADM OM Package Load ... Session-510 INFO 2006-11-13 04:55:55Successfully

Copyright © 2006, Oracle. All rights reserved.

ADMApplication Deployment

Manager

Copyright © 2006, Oracle. All rights reserved.2

Purpose:This document provides an overview of features and enhancements included in CRM 8.0. It is intended solely to help you assess the business benefits of upgrading to CRM 8.0.

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, which has been executed and 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 prior written consent of Oracle. 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 for informational purposes only and is intended solely to assist you in planning for the implementation and upgrade of the product features described. It 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 described in this document remains at the sole discretion of Oracle. 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.


ADMApplication Deployment Manager

Functional Deep Dive


Agenda

• Business Needs• Functional Overview• Technical Architecture• Demonstration• Troubleshooting• Limitations• Q&A


Agenda



Agenda



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


Agenda



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 comman d


ADM Feature Roadmap

Initially released in Siebel 7.7Enhanced 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 forADM

New unified framework for deployment operationsPackaging of customizations into re-usable packages

* Please see Bookshelf for all objects.

8.07.87.7Category

Workflow ProcessesAppletsViews

Repository Objects

SRFWeb templates

Files

Enhanced Export

Packaging

Automated Deployment Activation, Backup, Restore

Smart Scripts WF PoliciesProposal Templates

ExportImport

Price ListsCustom Products

ImportExport

List of ValuesState ModelsAccess Groups

Runtime Objects

FunctionsObjects*FunctionsObjects*FunctionsObjects*


Functional Overview

Bundle objects into single packageOne package can contain multiple different data typ esCan 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 (contd.)

Deployment/Activation• Automated deployment and activation • Activation-only support (e.g., for objects deployed via dev2prod)• Staged deployment by category / server / step• 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 (contd.)


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 PackageADM PackageADM PackageADM PackageADM PackageADM PackageADM PackageTargetTargetTargetTarget

EnterpriseEnterpriseEnterpriseEnterpriseRepositoryRepositoryRepositoryRepository

Shut Dow

nShut D

own

Shut Dow

nShut D

own

Deploy

Star

tup

Star

tup

Star

tup

Star

tup

ADM PackageADM PackageADM PackageADM PackageADM PackageADM PackageADM PackageADM PackageFilesFilesFilesFiles Deploy Activate

ADM PackageADM PackageADM PackageADM PackageADM PackageADM PackageADM PackageADM PackageDB RecordsDB RecordsDB RecordsDB Records

Deploy &Activate

ActivateCompile

SRF

Separate or Separate or Separate or Separate or combined combined combined combined packagespackagespackagespackages

““““Release to TestRelease to TestRelease to TestRelease to Test””””step onlystep onlystep onlystep only

SyncSchema


Scenario: Major Release – Full Repository

ADM PackageADM PackageADM PackageADM PackageADM PackageADM PackageADM PackageADM PackageRepositoryRepositoryRepositoryRepository

ADM PackageADM PackageADM PackageADM PackageADM PackageADM PackageADM PackageADM PackageFilesFilesFilesFiles

ADM PackageADM PackageADM PackageADM PackageADM PackageADM PackageADM PackageADM PackageDB RecordsDB RecordsDB RecordsDB Records

RepositoryRepositoryRepositoryRepositoryDatDatDatDat filefilefilefile

Target Enterprise

Import SyncSchema

Star

tup

Star

tup

Star

tup

Star

tup

Deploy Activate

Deploy &Activate

Shut Dow

nShut D

own

Shut Dow

nShut D

own

Activate WF & Task

ActivationActivationActivationActivation PackagePackagePackagePackageActivationActivationActivationActivation PackagePackagePackagePackageWF / TasksWF / TasksWF / TasksWF / Tasks

RepositoryRepositoryRepositoryRepository

Test EnterpriseTest EnterpriseTest EnterpriseTest Enterprise


Agenda



Automated process

ADM – Functional OverviewUser Process Flows

PROCESS

Start

Source environment(Packaging)

Load deployment package

Acknowledge, toterminate session

Deploy / Activate package

Perform targetenv. validation

Create deployment session for target

enterprise

Create and validatedeployment 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)

Siebel 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)


Technologies

Agent - JMXThe 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 - RMIThe Java Remote Method Invocation (RMI) system allows an object running in one Java Virtual Machine (VM) to invoke methods on anobject 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


Agenda



Agenda



Ensure service startup successful

In Control Panel -> Admin Tools -> Services


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://SDCHS2 2N002:1199/jmx/siebe

l/agent state= online ]


Management Server log info

• Ignore messages “Agent not online or name is invali d”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 DeploymentManagement 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 upda ted 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 noti fication is for performance purpose only, not for status reporting!, Session Number=510, Stat us=MIGRATION_COMPLETE, Server Host Name=sdchs22n002}'.


Successful DeploymentManagement 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 destinat ion file 'D:\20302\ses\siebsrvr\REPORTS\ENU\sample.rox'.

FileMBean INFO 2006-11-13 04:55:53 Deploying to destin ation 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 deployme nt 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/siebe l/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 DeploymentSiebel Server


Failed deploymentSiebel 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:1 4 (eaiobjinst.cpp (2208)) SBL-EAI-13011: Field 'Name' in the integration component 'Responsi bility' contains value 'ADM Sample Responsibility 1xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxx… xxxxxxxxxxxx', which is longer than allowed length of 50 characters.

ObjMgrLog Error 1 0000000845580158:0 2006-11-13 05:30:1 4 (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:1 4 (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.


Agenda



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 transactio n• 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


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 specif ic

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


System Impact


Agenda



Thank You

Thank You

Documents

ADM Application Deployment Manager€“ Low quality of deployment / Cost of rework ... Management Agent Siebel Server ADM OM Package Load ... Session-510 INFO 2006-11-13 04:55:55Successfully