module 53 application deployment manager - usage

7/30/2019 Module 53 Application Deployment Manager - Usage

1/21

1 of 20Application Deployment Manager - Introduction

Siebel 8.0 Essentials


2/21

Module 51: Application Deployment Manager :Usage


3/21


Module Objectives

Identify all customizations to deploy

Export database customizations

Export repository customizations

Move file customizations

Create an ADM package

Deploy the ADM package

Steps in using ADM


4/21


Identify Customizations

Database Customizations

Identify database changes using DB client or otherdatabase management tools

Repository Customizations

Use Siebel tools -> compare objects option

File Customizations

Determine file changes using file stamps at Operatingsystem level

Analyze Dependencies Understand parent child dependencies

Deploy Parent types before child types

Specify order of deployments Specify deployment order before DB export


5/21


Export Database customizations

Use Siebel Application URL > Application deployment manager >Deployment projects


6/21


Export Database Customizations

Save a query that selects & filters records

Use the saved query in deployment filter column


7/217 of 20

Application Deployment Manager - Introduction

Export Database customizations

Determine order of data type deployment using ApplicationDeployment Manager > Data type explorer view

Select parent data types first and then add child types.


8/218 of 20


Export Database Customizations

Use Application Deployment Manager >

Deployment Sessions Create new session ,specify project name &

deploy the session


9/219 of 20Application Deployment Manager - Introduction

Export Repository Customizations

Use Siebel Tools for exporting repository customizations

Files created by this process include A .sif file having changes

A descriptor file (xml file)

A log file

There are two provisions for exporting customizations Hot Fix : Ad hoc small set of customizations

Mid Level Release : Changes after specific date




How to create Hot-Fix?

1. Select the object definition2. Right click and select Add to hot fix

3. Specify name

4. Return to tools and repeat till all objects are selected

5. When done click export

Hot fix is saved in ..\tools\ADM\




How to create a mid-level release

1. Open Siebel tools > Navigate to View > Options > General; set changed

date to specify the cutoff release date2. Select Tools > Generate Mid-level Release

3. Provide a name and click generate list

4. Verify contents of list and delete extra entries if necessary

5. Click Export Package file is created in ..\Tools\ADM\



Move File customizations

Changed files needs to be identified and moved in correct

directory tree structure (i.e use copy paste ) between

source and target environment.

Do note that a .srf file is a file type and not a repositorytype.



Create ADM Package

ADM Package is a collection of customizations

It contains a directory structure identifying different types ofcustomizations.

And an ADM descriptor file describing its contents

ADM packager tool can be invoked by command line using the

command

% admpkgr

Steps to create package

Create an empty package

Populate the package directory structure

Generate the package descriptor file Validate the package



Create ADM Package > Create an empty package

Invoke admpkgr with the init command , use command line

% admpkgr init

Example :



Create ADM Package > Populate the package directorystructure

Move database,repository and file modifications to new

package directory

For database type move the .xml file containing data &

package descriptor

For repository type move the .sif file & the descriptor file

For file type

Move the .srf type \file\AppServer\objects\

Web templates \file\AppServer\webtempl\

Images,CSS files,browser script files

\file\AppServer\webmaster\

Report files \file\ReportServer\

Also Ensure unused package sub-directories are deleted



Create ADM Package > Generate the packagedescriptor file

Invoke admpkgr and use the following command line at theprompt

% admpkgr generate

Example :



Create ADM Package > Validate the package

Validation process is an optional process that verifies

existence and format of package descriptor file It Checks for unused , redundant units

It Performs consistency check

It Checks for valid unit files and descriptor files for database

and repositor types

Use % admpkgr validate fromcommand line to invoke package validation

Example :



Deploying the ADM packages

ADM command line interface to deploy package is executed

on the management server host

Typically batch file is named deploy_.bat

Following arguments can be supplied to the ADM interface

Command name User name

Password

Package name

Optional switches



Deploying the ADM package

The order of running ADM commands is highlighted in RED


20/2120 of 20


Deploying the ADM package

Following are the steps used in deploying an ADM package

Load deploy_ load

Create

deploy_ create

Copy

deploy_ copy

Activate

deploy_ activate

Status & Acknowledge

Deploy_ status


21/21


Example of ADM Deployment

module 53 application deployment manager - usage

Documents