Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Download
Standard view
Full view
of .
Save to My Library
Look up keyword or section
Like this
59Activity
P. 1
a Best Practices

a Best Practices

Ratings:

4.0

(1)
|Views: 2,998 |Likes:
Published by api-26810035

More info:

Published by: api-26810035 on Oct 15, 2008
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

03/18/2014

pdf

text

original

INFORMATI CA CONFI DENTI AL
BEST PRACTI CES
PAGE BP-i
Best Practices: Table of Contents
Best Practices
BP- 1
Configuration Management
BP- 1
Migration Procedures
BP- 1
Development Techniques
BP-16
Development FAQs
BP-16
Data Cleansing
BP-24
Data Connectivity Using PowerConnect for BW Integration Server
BP-29
Data Connectivity using PowerConnect for Mainframe
BP-33
Data Connectivity using PowerConnect for MQSeries
BP-36
Data Connectivity using PowerConnect for PeopleSoft
BP-40
Data Connectivity using PowerConnect for SAP
BP-46
Incremental Loads
BP-52
Mapping Design
BP-57
Metadata Reporting and Sharing
BP-62
Naming Conventions
BP-67
Session and Data Partitioning
BP-72
Using Parameters, Variables and Parameter Files
BP-75
Error Handling
BP-87
A Mapping Approach to Trapping Data Errors
BP-87
Design Error Handling Infrastructure
BP-91
Documenting Mappings Using Repository Reports
BP-94
Error Handling Strategies
BP-96
Using Shortcut Keys in PowerCenter Designer
BP-107
Object Management
BP-109
Creating Inventories of Reusable Objects & Mappings
BP-109
Operations
BP-113
PAGE BP-ii
BEST PRACTI CES
INFORMATI CA CONFI DENTI AL
Updating Repository Statistics
BP-113
Daily Operations
BP-117
Load Validation
BP-119
Third Party Scheduler
BP-122
Event Based Scheduling
BP-125
Repository Administration
BP-126
High Availability
BP-129
Performance Tuning
BP-131
Recommended Performance Tuning Procedures
BP-131
Performance Tuning Databases
BP-133
Performance Tuning UNIX Systems
BP-151
Performance Tuning Windows NT/ 2000 Systems
BP-157
Tuning Mappings for Better Performance
BP-161
Tuning Sessions for Better Performance
BP-170
Determining Bottlenecks
BP-177
Platform Configuration
BP-182
Advanced Client Configuration Options
BP-182
Advanced Server Configuration Options
BP-184
Platform Sizing
BP-189
Recovery
BP-193
Running Sessions in Recovery Mode
BP-193
Project Management
BP-199
Developing the Business Case
BP-199
Assessing the Business Case
BP-201
Defining and Prioritizing Requirements
BP-203
Developing a WBS
BP-205
Developing and Maintaining the Project Plan
BP-206
Managing the Project Lifecycle
BP-208
Security
BP-210
Configuring Security
BP-210
INFORMATI CA CONFI DENTI AL
BEST PRACTI CES
PAGE BP-1
Migration Procedures
Challenge
To develop a migration strategy that ensures clean migration between development,
test, QA, and production, thereby protecting the integrity of each of these
environments as the system evolves.
Description
In every application deployment, a migration strategy must be formulated to ensure

a clean migration between development, test, quality assurance, and production. The
migration strategy is largely influenced by the technologies that are deployed to
support the development and production environments. These technologies include
the databases, the operating systems, and the available hardware.

Informatica offers flexible migration techniques that can be adapted to fit the
existing technology and architecture of various sites, rather than proposing a single
fixed migration strategy. The means to migrate work from development to
production depends largely on the repository environment, which is either:
\u2022
Standalone PowerCenter, or
\u2022
Distributed PowerCenter
This Best Practice describes several migration strategies, outlining the advantages
and disadvantages of each. It also discusses an XML method provided in
PowerCenter 5.1 to support migration in either a Standalone or a Distributed
environment.
Standalone Pow erMart/ Pow erCenter

In a standalone environment, all work is performed in a single Informatica repository
that serves as the shared metadata store. In this standalone environment,
segregating the workspaces ensures that the migration from development to

production is seamless.
Workspace segregation can be achieved by creating separate folders for each work
area. For instance, we might build a single data mart for the finance division within a

Activity (59)

You've already reviewed this. Edit your review.
1 hundred reads
1 thousand reads
Pranab Pal liked this
Vinay Kumar liked this
Thang Le liked this
Flavio Uyemura liked this
rohit01234567890 liked this
rohit01234567890 liked this
rohit01234567890 liked this
rohit01234567890 liked this

You're Reading a Free Preview

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