0% found this document useful (0 votes)

34 views

50ESS - Migrating From Development To Test

The document provides instructions for migrating data and configurations from a Siebel development environment to a test environment. It discusses: 1) Preparing the source (development) and target (test) environments, including compiling files and installing/configuring databases and servers. 2) Populating the target database using tools like the Database Server Configuration Utility, Enterprise Integration Manager (EIM), and Application Deployment Manager (ADM). ADM is used for small data volumes while EIM supports bulk import/export. 3) The ADM process of setting up deployment projects and filters, then deploying sessions to transfer user-supplied data between environments.

Uploaded by

AkhamiePatrickOshioke

Available Formats

Download as PPT, PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

34 views

50ESS - Migrating From Development To Test

Uploaded by

AkhamiePatrickOshioke

Available Formats

Download as PPT, PDF, TXT or read online on Scribd

You are on page 1/ 25

Essentials (Siebel 7.

Module 50: Migrating from

Development to Test
Module Objectives

After completing this module you will be able to:

 Describe the requirements and tasks for migrating from
development to test
 Use Application Deployment Manager to migrate run-time
configuration data from one environment to another

Why you need to know:

 One of the activities of a Siebel product implementation is
to migrate from a development to test environment

Module 50: Migrating from Development to Test 2 of 25

Migrating Requirements
 Different requirements exist for development, testing, and
production
 Development environment is unstable as software is changing
 Testing environment is stable so users can test and track defects
 Production environment includes only tested and stable software
 Development and testing are sometimes done concurrently
 Requires developed software to be migrated to a separate
environment for testing

Development Test/QA Production

Module 50: Migrating from Development to Test 3 of 25

Migrating Requirements Continued
 Tasks to perform:
1. Prepare the source environment
2. Prepare the target environment
3. Populate the target database

Source Target
Production
(Development) (Test/QA)

Focus of this module

Module 50: Migrating from Development to Test 4 of 25

Migrating from Development to Test/QA
 Initial implementation requires the following to be migrated from
Development to Test/QA
 Siebel repository file (.srf)
 Siebel File System
 Physical UI files
 Siebel configuration files (.cfg)
 Data

Module 50: Migrating from Development to Test 5 of 25

Migrating from Development to Test/QA Continued

 Different types of data need to be migrated

 Seed data
 Initial data delivered with the standard application that is populated
during the database configuration
 Repository data
 Object definitions that specify the application look, behavior, and data
 Populated during repository import (database configuration)
 Can be modified during configuration
 User-supplied data Siebel Database
 Administrative data
 Run-time configuration data defined
Seed Data
within the application UI outside Repository Data
the repository
User-Supplied Data
 Customer and master data

Module 50: Migrating from Development to Test 6 of 25

1. Prepare Source Environment
 Prepare source (development) environment
 Identify all files composing the build
 Capture/lock down/freeze all build files
 Check in all projects to server
 Compile all projects from source repository to build new .srf

Check in Compile

Tools New
Client DB Server .srf

.srf,
.cfg, and so on
Build X

Module 50: Migrating from Development to Test 7 of 25

2. Prepare Target Environment
 Prepare target (test/QA) environment
 Install database and server software on target server
 Install client software (if required)
 Copy .srf and other client files to server and necessary clients
 Verify parameters (.cfg, ODBC, and so on)

Gateway Server

Target Enterprise Server Target

Mobile
Server Siebel Server Client Web Client
Component

New
.srf
Database Siebel
Server File System

Module 50: Migrating from Development to Test 8 of 25

0/3

3. Populate the Target Database

Database Server Configuration Utility

Enterprise Integration Manager (EIM)

Application Deployment Manager (ADM)

Module 50: Migrating from Development to Test 9 of 25

1/3

Database Server Configuration Utility

 Use the Database Server Configuration utility to migrate custom
repository and schema changes from source to target database
 Upgrades data in the target database to the new schema
 Updates repository object definitions

Source Target

Repository Data Repository Data

Module 50: Migrating from Development to Test 10 of 25

2/3

Enterprise Integration Manager (EIM)

 Use Siebel EIM and database vendor tools to copy user-
supplied data
 Run EIM to export source
 Use database vendor tools to move data from source to target EIM
tables
 Run EIM to import into target base tables
 Supports large data volumes; intended for bulk import or export

SQL
Source Target
Selected
user-supplied
data Base EIM EIM Base

EIM EIM
export import

Module 50: Migrating from Development to Test 11 of 25

3/3

Application Deployment Manager (ADM)

 Use Application Deployment Manager (ADM) to migrate user-
supplied data
 Supports small data volumes; not intended for bulk import or
export

Source Target

User-Supplied Data User-Supplied Data

Module 50: Migrating from Development to Test 12 of 25

0/3

ADM Process Flow

1. Prerequisites

2. Setup: Create ADM Deployment Projects

3. Deployment

Module 50: Migrating from Development to Test 13 of 25

1/3

Prerequisites
 Before migrating data using ADM:
 Complete repository migration task
 Ensure that the following components are enabled and available:
 Workflow Management (Workflow)
 Enterprise Application Integration (EAI)
 Synchronize server components
 Activate necessary workflows that have a name starting with UDA

Module 50: Migrating from Development to Test 14 of 25

2/3

Setup: Create ADM Deployment Projects

 Projects are templates that can be reused to migrate the same
data types on a regular basis
 Projects can contain many data types
 Navigate to Application Deployment Manager > Deployment
Projects 1. Create a
master project
record

2. Add data types

as project items
and define filters

Module 50: Migrating from Development to Test 15 of 25

2/3

Setup: Create ADM Deployment Projects Continued

 Filters can also be set or modified when creating a deployment
project
 Task is optional but recommended
3. Enable

2. Click the
Validate Filter
button to
validate

1. Create or enter
a deployment filter

Module 50: Migrating from Development to Test 16 of 25

3/3

Deployment
 Three options for deploying sessions:
 Transfer data using ADM screen
 Transfer data using export files
 Transfer data using the command line interface (not covered)

Module 50: Migrating from Development to Test 17 of 25

Transfer Data Using ADM Screen
 Navigate to Application Deployment Manager > Deployment
Sessions
 Only enabled projects are visible
Refresh adds the
data types in the
lower applet and any
filters created

1. Create a 2. Click the

new record Deploy
and select button
project

Module 50: Migrating from Development to Test 18 of 25

Transfer Data Using Export Files
 Two steps:
1. Export a deployment session from the source system to a
deployment session XML file
2. Import the deployment session XML file to the target system

Module 50: Migrating from Development to Test 19 of 25

1. Export a Deployment Session File
 Access the source system from which you want to migrate
application customizations
 Navigate to Application Development Manager > Deployment
Sessions 2. Click
Deploy

1. Select the
deployment
session of interest 3. Enter the
network path
for the export
directory and
click Export

Module 50: Migrating from Development to Test 20 of 25

2. Import a Deployment Session File
 Specify the target system from which you want to migrate
application customizations
 Make sure the source file is accessible

2. Enter the
network path and
file name for the
import file and click
the Import button

1. Click the
Menu button
and select
Deploy from
File

Module 50: Migrating from Development to Test 21 of 25

Review ADM Data Migration
 Any executed session has a log file attached which can be
saved to a location or opened at that point
 Use to see if errors occurred

Drill down
on Log
ID…

… to view
Session
Header and
transaction
information

Module 50: Migrating from Development to Test 22 of 25

Test (Target) Environment Is Ready
 Your application is now ready to be tested in a stable and
controlled environment

Gateway Server

Target Enterprise Server Target

Mobile
Server Siebel Server Client Web Client
Component

New
.srf
Database Siebel
Server File System

Module 50: Migrating from Development to Test 23 of 25

Summary

This module showed you how to:

 Describe the requirements and tasks for migrating from
development to test
 Use Application Deployment Manager to migrate run-time
configuration data from one environment to another