P. 1
Developing and Deploying Siebel Business Applications

Developing and Deploying Siebel Business Applications

|Views: 616|Likes:
Published by suyashshrestha

More info:

Published by: suyashshrestha on Feb 22, 2011
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

06/10/2013

pdf

text

original

Migrating application run-time customization data from one Siebel application environment to
another is a common requirement when going live to a new development, test, or production
environment. The Application Deployment Manager (ADM) feature automates the migration of the
Siebel application run-time customization data.

Application Deployment Manager (ADM) is a feature that automates the process of migrating
enterprise customization data (views, responsibilities, assignment rules, and so on) from one Siebel
application environment to another. For example, ADM can move customization data from a
development environment to a testing environment. ADM eliminates the former process of
transferring this data manually.

NOTE:The term migrating is used in the ADM context as the moving of data from one environment
to another. No changes to the data take place during migration.

The bulk of the administrative tasks to migrate data using ADM are performed at the Application
Deployment Manager screen in the Siebel application GUI. These tasks are intended for those with
Siebel administrator responsibility. The ADM set-up process in the ADM GUI creates a template in
which one data type can be migrated on a regular basis, if required. The fundamental structure of
this template is the deployment project. The deployment project consists of one or more data types
that can be migrated.

The following data types are available for migration with ADM:

Access Groups

Assignment Rule

Expense Types

List of Value (LOV)

Product Feature

Product Line

Public Predefined Query (PDQs)

Responsibility

State Model

Files

File Location

Cascading Style Sheets

siebsrvr_root\webmaster\images\language_code

Images

siebsrvr_root\webmaster\images\language_code

Web Templates

siebsrvr_root\WEBTEMPL

Migrating to the Test Environment ■ Migrating Nonrepository Data from Development to
Test

Developing and Deploying Siebel Business Applications Version 8.0

179

User List

View

These data types are preconfigured in the standard Siebel Business application. Using Siebel Tools
you can add more data types for use with ADM.

For more information on migrating nonrepository data and using ADM, read Siebel Application
Deployment Manager Guide.

Developing and Deploying Siebel Business Applications Version 8.0

Migrating to the Test Environment ■ Migrating Nonrepository Data from Development to
Test

180

Developing and Deploying Siebel Business Applications Version 8.0

181

13Using EIM to Load Data Into the
Test Environment

You have already completed many of the tasks to prepare your test environment. For example, you
have moved the application (including your configuration changes) from development to test and
have performed the setup tasks described in Chapter14, “Required Application Administration Tasks.”

To do further development and testing work, however, you need to have actual corporate data in your
Siebel database. Up until now, you have been working only with the sample data available with your
Siebel installation.

This chapter tells you how to load data from your legacy applications into a Siebel database, using
the Siebel Enterprise Integration Manager (EIM).

Generally, EIM is used to exchange data between Siebel database tables and other data sources. This
exchange of data can include bulk imports, exports, merges, and deletes. Because the current goal
is to load data into a Siebel database, this chapter deals only with bulk imports. For detailed
information about EIM, read Siebel Enterprise Integration Manager Administration Guide.

This chapter focuses on one specific import example: loading account data for the NREC. The section
“Import Example” on page182, provides more detailed information about the specific import example
presented in this chapter.

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->