application deployment manager - home: doag e.v. · –workflows process export/import –eim loads...

Application Deployment ManagerSiebel Architecture Technology Overview

Topics Covered

Copyright ©2007, Oracle. All rights reserved.Oracle Confidential

ApplicationDeploymentManager

• Introduction

• Framework features and process flow

• Architecture

• Supported application components

• Customer scenarios

• Summary


Business Challenge

• Current Problem: The process of migration to production requiresvarious objects and different processes to be deployed:

– Repository migration (dev2prod or db server scripts)– Data and Rule export/import– Workflows Process export/import– EIM Loads– SQL Loads (i.e Database utilities)– Manual data entry

• Performing all those different steps can be time consuming and errorprone.


Description

• Framework to automate and unify the deployment of applicationcustomizations

• Designed to reduce the deployment effort and application downtime,and to increase the application deployment quality

• Provides the means for an efficient and predicable deploymentoutcome through re-usable deployment packages and processautomation

• ADM provides a unified architecture to migrate between 2environments

– Dev -> Test– Test -> Prod

• Operates in a consistent and integrated manner


Features for ADM

• Unified framework for deployment operations• Packaging of customizations into re-usable packages

WorkflowProcessesAppletsViews

SRFWebtemplatesReports

Smart ScriptsWF PoliciesProposalTemplates

Added*

8.0

ExportImport

Functionality

7.87.7

CustomizedRepositoryObjects

Custom Files

-Enhanced Export-Packaging-AutomatedDeployment,Activation, Backup,Restore

Price ListsCustomProducts

ExportImport

List of ValuesState ModelsAccess Groups

RuntimeCustomizations

FunctionalityAdded*FunctionalityExamplesCategory

* Examples of objects added, not a complete list.

Topics Covered



• Introduction


• Architecture



• Summary


Framework Features

• Packaging– ADM Admin GUI/CLI to export database objects– Tools GUI/CLI to export repository objects– Deployment package utility

• 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

Package Deploy Activate Recover


Framework Features

• 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

Package Deploy Activate Recover


Automated process

User Process FlowsPROCESS

Start

Source environment (Packaging)

Load deploymentpackage

Acknowledge, toterminate session

Deploy / Activatepackage

Perform targetenv. validation

Create deploymentsession for target

enterprise

Create and validatedeployment package

Deployment Server (Deploying)

Identifycustomizationsand export to file

Verify deployment(perform any

recovery actions)

Topics Covered



• Introduction


• Architecture



• Summary


Architecture Diagram

DeploymentPackage

DeploymentPackage

Siebel Server

Management Functions(includes ADM modules)

JMX RemoteJMX Remote –– (OEM)(OEM)

Siebel Server Siebel Server

Localdatabase

ManagementServer

JMX Agent(MBeans)

ADM AdminDb Export

(Db Items)

Siebel Tools(Repository

Items)

SourceEnvironment

TargetEnvironment

ADMServerComp

OrchestrationEnvironment

ADMRegistry(XML)

TargetProfile(XML)

Other DevEditors

(File Items)

ADMPackageUtility

(Descriptor)

3rd Party Change3rd Party ChangeMgmt ToolsMgmt Tools

RMI

ClientEnvironment

CommandLine Interface

RMI

JMX Remote (OEM)JMX Remote (OEM)

Topics Covered



• Introduction


• Architecture



• Summary


Supported Application Components - Sample

7.7Responsibilities7.7State Model7.7Assignment Mgr8iHelp8SmartScripts8Webmaster files8Web Templates with downtime8Symbolic URL

7.7Predefine Queries8Audit Trail Admin8Access Control Admin8SRF with downtime

7.7List of Values8Runtime Events8Personalization Rules8WebServices8Dispatch Rule8Data Transformation

Version IntroducedVersion IntroducedComponent AreaComponent Area


Supported Application Components – Sample Cont

8Workflow Policies8Workflow Process8Taskbased UI (Repository – Task Definition)8Taskbased UI (Db - Registered Task)

7.7Access Groups7.7/7.8COM Areas (17 separate areas)

8Search (FAST)8Rules Engine

8ABS Scheduling8eMR templates Catalog/Category8Correspondence templates8Proposal Templates

7.7Expense Type8Report Files

7.7User List7.7Views

Version IntroducedVersion IntroducedComponent AreaComponent Area

Topics Covered



• Introduction


• Architecture



• Summary


Customer scenarios

• Customer scenarios– Business Release– Minor Functional Release or Bug Fix– Major Functional Release – Limited Repository– Major Functional Release – Full Repository

• Scenarios provided as a guidance to customers to outline theframework capabilities

• Customers still need to invest in their own deployment planning andexecution


Customer Scenarios - Overview

BusinessObjects

Schemachanges

Non CompiledObjects only

P

P

P

N/A

P

P

N/A

N/A

P

P

P

P

RuntimeCustomizations

PPMajorRelease-FullRepository

PPMajorRelease –LimitedRepository

PPMinorRelease orBug Fix

ExcludingSRFP

CustomerBusinessRelease

CustomizedServer Files

Repository CustomizationsCustomerReleases


Customer scenario (1)

• Customer Business ReleaseCharacteristics: Daily/Weekly. Typically driven by the business users due to

minor changes in the business needs. Typically does not represent achange in the business process.

Example:

No compiled Respository objectsNo schema changesC/OM - 1 JWS including 50 itemsWF Processes

5010Assignment Rules only102Responsibility/Views35LOVs

UpdateInsertData Type



• Customer Minor Functional Release or Bug FixCharacteristics: Weekly/Monthly. Driven by the business users or the IT

community. May include fixes to defects rolled out in the previous customerrelease or as reported by users. Will require minor modifications to theexisting business process and possibly adding new processes

No schema changes3 Report files20 Browser Scripts3 SRF files10 Repository objectsWF ProcessesC/OM - 1 JWS including >500 items

2030SmartScripts41WF Policies

5010Assignment Rules only52State Model

102Responsibility/Views35LOVs

UpdateInsertData TypeExample:



• Customer Major Functional Release – Limited RepositoryCharacteristics: Monthly/Quarterly. Periodically scheduled internalrelease containing a major change. Separate Repository Migration isnot used. Release contains schema changes.

Schema changes30 Web templates30 Report files20 Browser ScriptsThree SRF files200 Repository objectsWF ProcessesC/OM - 8 JWS including >500

83WF Policies020Views

5020Smart Scripts5010Assignment Rules only102State Model

1502Responsibility/Views5010LOVs

UpdateInsertData TypeExample:



• Customer Major Functional Release – Full RepositoryCharacteristics: Quarterly or less frequent. Release including majorfunctionality changes. Separate Repository Migration is used due tothe number of Repository changes. Release contains schemachanges.

Schema changes30 Web templates30 Report files20 Browser ScriptsThree SRF files>400 Repository objectsWF ProcessesC/OM - 8 JWS including >500 items

30100Plus various other areas30WF Policies

1050Views40Smart Scripts20Assignment Rules only10State Model20Responsibility/Views

1025LOVsUpdateInsertData TypeExample:


Customer Deployment Scenarios using ADM

Release to TestRelease to Test(SRF compile(SRF compile envenv))

ADM setup 2’

ADM setup 2’

ADM setup 2’

ADM setup 1

ADM setup 3

ADM setup 2

ADM setup 2

ADM setup 1

NonNon--productionproductionDeploymentDeployment

ADM setup 3Major Release- FullRepository

ADM setup 2Major Release –Limited Repository

ADM setup 2Minor Release or BugFix

ADM setup 1Customer BusinessRelease

ProductionProductionDeploymentDeployment

CustomerCustomerReleasesReleases

•Increase in rollout complexity and approvals•Increasing need for automation, auditing and security•Increase in HA deployment requirement

•Increase in customization com

plexity•Increase in business im

pact (downtim

e)•H

igher testing effort


Development/Deployment Process

Release to Test

Release PackageCustomizations(files)

TargetEnterprisefor Testing

Refresh(!)Deploy

Test cycle

Non-productionEnterprise1

RefreshDeploy


RefreshDeploy


RefreshDeploy

ProductionEnterprise Deploy

Development


ADM Setup 1: Customer Business Release

ADM PackageADM Package Target Enterprise

Deploy & Activatewith no/minimum

downtime

Non Compiled Repository

Files (no new SRF)

DB Records

Release to Test

ADM setup 2’

ADM setup 2’

ADM setup 2’

ADM setup 1

ADM setup 3

ADM setup 2

ADM setup 2

ADM setup 1

Non-productionDeployment



ADM setup 2Minor Release orBug Fix


ProductionDeploymentCustomer Releases


ADM Setup 2: Minor/Major Release – Limited Repository

Target Enterprise

Deploy

Deploy Activate

Deploy &Activate

ActivateCompileSRF

Separate orSeparate orcombinedcombinedpackagespackages

““Release to TestRelease to Test””

step onlystep only

SyncSchema

ADM PackageADM PackageRepository

ADM PackageADM PackageFiles

ADM PackageADM PackageDB Records

Shut Dow

n Star

tup

Release to Test

ADM setup 2’

ADM setup 2’

ADM setup 2’

ADM setup 1

ADM setup 3

ADM setup 2

ADM setup 2

ADM setup 1








ADM Setup 3: Major Release – Full Repository

RepositoryRepositoryRepositoryRepository

DatDat filefile

Target Enterprise

Import SyncSchema

Deploy Activate

Deploy &Activate

ActivateWF & Task

Test Enterprise

ADM PackageADM PackageRepository

ADM PackageADM PackageFiles

ADM PackageADM PackageDB Records

ActivationActivationPackagePackageWF/Tasks

Star

tup

Shut Dow

n

Release to Test

ADM setup 2’

ADM setup 2’

ADM setup 2’

ADM setup 1

ADM setup 3

ADM setup 2

ADM setup 2

ADM setup 1







Topics Covered



• Introduction


• Architecture



• Summary


A friendly reminder…

• ADM is designed to:– Identify and package customer customizations from a Siebel development

environment– Automate the deployment of these customizations to a same-version

Siebel target environment

• …and is not :– A mass data migration tool– A change management tool– A systems management tool– Appropriate for Installation, Patching, Upgrade nor server management


Summary

• Reduce overall deployment effort– Export and packaging of changes into re-usable packages– Automation of deployment and activation steps– Comprehensive logging and status reporting

• Increase application deployment quality– Unified means of deployment – hiding underlying complexities– Predicable deployment outcome through re-usable package and

automation• Reduce application downtime

– Reduced deployment-time by automation– Limited high-availability deployment support (online deployment/activation,

staged server deployment)– Performance report for deployment execution

Application Deployment ManagerSiebel Architecture Technology Overview

application deployment manager - home: doag e.v. · –workflows process export/import –eim loads...

Documents