2
Upgrade to Informatica Version 9.1.0: Tips, Tricks, and FAQs
Greg Mason
Duke Energy ICC Manager
Duke Energy
Shannon Heustess
IPS Upgrade Specialist
Informatica Professional Services
3
Speaker Roles and Background Info
Greg Mason – Duke Energy ICC Manager
• Coordinate ICC development resources with application teams and business partners
• Plan for implementation of new products or features
• Negotiate outage timing with operations and application development teams
Shannon Heustess - Informatica Principal Consultant
• Upgrade specialist with Informatica professional services
• Execution and oversight for enterprise level upgrades
• Enablement of the Informatica practice for execution of upgrades and best practices leveraged
4
Agenda
• Upgrade Strategies
• Styles of upgrades you can conduct
• When should you leverage them
• Deep Dive into the Duke 9.1.0 Upgrade
• Overview of the environment
• The required planning effort
• The execution model
• Frequently Asked Upgrade Questions
5
Upgrade Type Strategies
6
In Place Upgrade Process
• This is the process of
leveraging the installer or the
application service wizard
upgrading the original
metadata without providing a
parallel environment.
• Typically Seen During
• Very Short Upgrade Cycles
• After Certifying a Sandbox Build Out
• Environments with many installations and lifecycles
7
Steps to Perform In Place Upgrade
To Upgrade Domain
• Run pre installation check
tool i9pi to make sure all
pre requisite are met
• Backup Domain and
repository
• Run the installer to
upgrade Domain
8
Steps Perform In Place Upgrade
To Upgrade Services
• Navigate to Administrator
Tool
• Select upgrade from
manage drop down
• Select services to upgrade
• Specify the user name and
password required
• Execute the upgrade
process
9
In Place Upgrade Pro’s and Cons
• Pros • Simplifies the upgrade
process
• No additional schemas needed for parallelism
• Minimized risk due to setting differences
• No Need to migrate users and groups (8.5.1 and higher upgrades)
• Cons • Makes it harder for parallel
version development
• Can not change domain names
• Can not change node name
• Requires an outage for the domain restore and installation
10
Parallel Upgrade Process
• This is the process of installing a fresh copy of the server and taking a
snapshot of your ETL repository environment and upgrading the
snapshot.
• Typically Seen During
• Longer Upgrade Cycles
• A Sandbox Build Out
• Pre-Production Go Live
• Where outage windows are tight
11
Steps to Perform Parallel Upgrade
To perform Parallel Upgrade
• Install fresh Informatica 9 and
create new Domain
• Use comand exportusergroup and
importusergroup to import and
users and groups from previous
version (8.5 and higher)
• Navigate to the legacy domain and
create an empty repository
• Use copy content from option to
take snapshot of desired repository
into the empty repository
• Stop new repository service in
legacy domain
12
Steps to Perform Parallel Upgrade
Parallel Upgrade Continued
• Navigate to Informatica 9.x
instance
• Create an empty repository
service with the same DB
credentials as the one
repository you just copied the
contents into
• Enable the service
• Upgrade the repository using
actions drop down or upgrade
wizard
• Upgrade users and groups
(8.1.x only)
13
Parallel Upgrade Pro’s and Cons
• Pros • Allows for a parallel
environment to be built out
• Faster Go Live strategy
• Can change domain names
• Can change node name
• Does not requires an outage for the domain installation
• No additional caveats for https enabled domains
• Cons • Needs additional schemas
for level of parallelism
• Need to migrate users and groups (8.5.1 and higher upgrades)
• Small risk due to potential setting differences for services
14
Cloned Upgrade Process
• This is the process of taking a snapshot of your domain and
upgrading the domain snapshot using the Informatica 9.x
installer
• Typically Seen During
• Pre-Production Go Live
• A Sandbox Build Out
• Where outage windows are tight
15
Steps to Perform Cloned Upgrade
To Perform Cloned upgrade
• Take a backup of domain from
previous version.
• Stop domain and restore to new
schema
• Start existing domain
• Run the installer and choose
option to upgrade
• Enable Allow changes to the node
host name and port numbers
option
• Provide domain configuration
where it has been restored
16
Steps to Perform Cloned Upgrade
Cloned Upgrade Continued
• Adjust port numbers to prevent
port conflicts
• Navigate to 9.1.0 Administrator
after successful upgrade
• Run the upgrade wizard to
upgrade any services you want
to upgrade in place.
• If you need to create parallel
repository services then follow
the same approach outlined
early by copying contents
17
Cloned Upgrade Pro’s and Cons
• Pros • Allows for your identical
clone of your environment to ready for go live
• Faster Go Live strategy
• Minimized risk due to setting differences
• No Need to migrate users and groups (8.5.1 and higher upgrades)
• Cons • Needs additional schemas
for level of parallelism
• Can not change domain names
• Can not change node name
• Requires an outage for the domain restore and installation
• Additional caveats for https enabled domains
18
When to use upgrade types
Cases Types of upgrade
Very Short Upgrade Cycles In place
Environments with many installations and lifecycles In place
Longer Upgrade Cycles Parallel / Phased
A Sandbox Build Out Parallel, Clone
Pre-Production Go Live Parallel, Clone
Where outage windows are tight Parallel, Clone
Minimize risk due to no setting differences In place, Clone
If want to change Domain and node name Parallel
If want to avoid outages Parallel
19
Duke Energy – PowerCenter 8.6.1 to 9.1.0 Upgrade
Fall 2011
20
Information Center of Excellence
Application
Systems
Architect
Informatica
Competency
Center
Business
Intelligence
Center
Data
Architecture
& Govern.
7 FTE
1 FTE
8 FTE
1 FTE
Business
Unit
A
~200 Developers
~10 Testers
Business
Unit
B
~90 Developers
~15 Testers
Business
Unit
C
~195 Developers
~20 Testers
Information
Center
Of Excellence
21
Enterprise Data Hub background information
21
Data Hubs (ODS/DW)
Interfacing
systems Finance
HRMS
Supply Chain
Customer Billing
Outage Mgt
Mobile Work Mgt
Finance
Customer
Materials
Equipment
Workforce
Etc..
Analytics and
Reporting
23
Environment Overview v8.6.1
NAS File
share
server
Integration
servers
Integration
servers
DR Site
Primary Data
Center
Integration
servers
Integration
servers
Integration
servers
Integration
servers
Integration
servers
Integration
servers
Integration
servers
Primary Repository server
NAS File
share
server
NAS File
share
server
Primary Repository server Primary Repository server
DR/HA Repository Server DR/HA Repository ServerDR/HA Repository Server
24
Environment Overview (cont’d)
• Monthly volumes for non-prod:
• Sessions executed: 1.1 Million (unique: 6,100)
• Workflows executed: 270,000 (unique: 4,500)
• Total rows affected : 8.5 Billion
• Monthly volumes for prod:
• Sessions executed: 5.1 Million (unique: 15,000)
• Workflows executed: 1.3 Million (unique: 2,600)
• Rows affected: 21 Billion
• DW prod 5Tb – SQL server 2008 R2 (~50% compression)
• ODS prod 3Tb - SQL server 2008 R2 (~50% compression)
25
Duke Upgrade / Patch Process Overview
• Since much of our environment is windows-based, we allow a 3
hour window per month for patching.
• Twice a year (Spring and Fall) we reserve for more significant
items (product upgrades or major infrastructure changes)
• Typically a Saturday is selected which is distanced from major
business processes (Financial closing process, Nuclear
refueling outages).
• For the twice-yearly Bundle upgrade, Non-production is always
upgraded 1 month prior to production.
• During 1 month gap between non-prod and prod, an
intermediate PowerCenter environment is provided for
production support (running same version as production)
26
Upgrade Objectives:
• Increase PowerCenter capacity
• Merger was announced January 2011 – both companies have PowerCenter – the goal was to be able to process twice the current daily volume by merger-close (proposed December 2011)
• Keep product set current (Informatica PowerCenter Version, Oracle Version, Windows Version could reach end-of-life during 1st year after merger)
• Keep hardware current (P5 frames nearing end-of-life)
• Part of fall bundle process (window of opportunity – Fall 2011)
27
Deliverables:
• Upgrade P5 frames to P7
• Upgrade AIX from 5.3 to 6.1
• Upgrade Oracle (repositories) from 10.2.0.5 to 11gR2
• Upgrade existing Windows 2003 servers (integration servers) to Windows 2008
• Add new integration servers for increased processing capability
• Additional PowerCenter licenses
28
Deliverables Continued:
• Upgrade PowerCenter to v 9.1.0
• Servers
• Standard desktops – client tools pushed via Marimba (Designer, WF Manager, etc.)
• Citrix servers
• PC Client software on ESP scheduling servers & Migration tool server
• Clean-up tasks (e.g. obsolete folder deletions, setting changes for consistency: SonG, Backward log compatibility) for consistency
• Provide Parallel v8.6.1 environment for several LD-1/in-flight projects which were implementing within the 1 month window between Dev / Test & Production
• Provide full Production Support environment (Dev, Test, & QA) v8.6.1
29
Upgrade timeline
30
Constraints
• Strict limits on the ability to purchase new hardware
• It was critical to hit the planned window for all of the
upgrades due to negative impact on key business
processes (e.g. Financial close for LD1)
• Production support
• Special circumstance (merger)
• Parallel environment to support in-flight projects
• Staggered upgrades (typically all non-prods are done on one day and all production areas are done on another)
31
Methodology
• Upgrade options were (to remain within
hardware constraints):
• Straight upgrade-in-place
• Utilizing Ghost/image to build/repurpose some machines on the day-of-upgrade
• “Shell Game”:
1. Leverage machines from other areas temporarily
2. Dual-purpose some machines (which would end up being true production machines)
3. Allowed us to pre-stage the software on new servers as well as configure firewall exception rules
32
Upgrade – overall flow
• Spring – Build 3 Sandbox environments
• Validates install of 9.1
• ICC performs functional testing
• Key user areas perform functional testing
• Request hardware for Parallel 8.6.1 environment
• Late Spring – Testing summit
• Assign expectations for testers
• Late Spring to Mid Summer
• Parallel environment being used by LD1 projects (their code is required to be migrated to current 8.6.1 production prior to production upgrade)
• Since Parallel was built as a 2-node grid, some load-testing was performed
33
Flow – cont’d
• Late summer
• CORP Non-prod upgrade
• Left original environment intact to provide 8.6.1 Production support (removed security and only added groups who needed access)
• ICC performs functional testing
• Early Fall
• ECOM & CUST Non-prod upgrades on weekend #3
• CORP PROD upgrade on weekend #4
• Fall
• ECOM & CUST Prod upgrade
• Validation / Backout (allowed 1 day)
34
PowerCenter 9.1 environment post-upgrade (current)
Integration
server
NAS File share
server
Primary Repository server
DR/HA Repository server
DR Site
Primary Data Center
Integration
server
Integration
server
Integration
serverCORP PROD
Integration
server
NAS File share
server
DR/HA Repository server
Integration
server
CUST PROD
NAS File share
server
DR/HA Repository server
Integration
server
ECOM PROD
Integration
server
Integration
server
Integration
server
Integration
server
Integration
server
PCTR Client ToolsWeb-based migration
tool
ESP job scheduling
farm
Citrix FarmLaptops & Desktops
35
Summary
• Complete project (excluding the additional license
purchase process) was approximately 5 ½ months
• Total project hours: 4,400
• Key elements which contributed to on-time & on-budget
success of project:
• Early involvement of Informatica Professional Services
• Dedicated PM
• Early acquisition of new hardware
• Leveraging Testing summit to engage Developer community
• Testers (from application teams) required participation during upgrade process
• Operational staff required on-site with open conference line for duration of actual upgrade
36
Frequently Asked Upgrade Questions
37
Frequently Asked Upgrade Questions
“We are planning to upgrade our Informatica 8 Servers to
Informatica 9.1. Can someone share their upgrade experience,
known issues and challenges faced. Thanks in advance.”
My Support Forum Poster Answer:
The best places to find information like this are the following
locations:
• My Support Forums
• Informatica World
• Break Out Sessions
• Birds of a Feather Discussions
• Informatica User Group Meetings
• Your sales team concerning customer references
38
Frequently Asked Upgrade Questions
“Where can I find the new features, bug fixes, or issues when
upgrading to the newest release?”
Various
Answer:
The best places to find information like this are the following
locations:
• Support Flash
• Contains the latest hotfix information
• EBF’s that have been created
• Support Announcements
• Top support Articles
• Release Notes and Release Guides
• Released with each major release and hotfix
• Contains a running history of all fixes and known issues
• Contains a running history of all new features
39
Frequently Asked Upgrade Questions
“Can I export a mapping from a previous version of Informatica
into the new version of Informatica”
Various
Answer:
It depends!
If a repository service upgrade is required then no it is not
supported / endorsed to conduct an export import. This could lead
to corruption of the repository.
So when can you?
Exporting from 8.5 and importing into 8.6.x
Exporting from 9.0.1 and importing into 9.1.0
Support
Statement
40
Frequently Asked Upgrade Questions
“Do I have to conduct a set of full regression tests? If I do it will
take too long for me to complete my upgrade!”
Various
Answer:
It depends!
At a minimum you want to test those mappings that are mission
critical for the enterprise.
If everything is mission critical then you start looking at design
patterns and reduce the number of mappings based on these
patterns.
Look to leverage DVO where you maybe able to fully regression test
for the same amount of time for low % partial regression test with far
less resources.
41
Marketplace Overview A Trusted, Open Ecosystem
• Virtual Marketplace for Data Integration Apps
• Solutions across all technology areas – DI, DQ, MDM, Cloud, etc.
• Open Ecosystem – Apps from Partners, ISVs, Consultants, and Developers
• Seal of Approval ensures App quality
• More than 600 Apps, over 200 Free!
• 15k visits per month, 2k downloads
http://marketplace.informatica.com
R
M
42
Informatica Velocity Methodology
Velocity is the blueprint for delivering efficient and successful Informatica solutions that solve business problems.
New Website • New search capability • Filtering/viewing content by
• project type • project phase • or other tags
• New accelerator tools • Hot links between the articles
Access at: mysupport.informatica.com
Visit the Informatica Pavilion at the Technology and Solutions Fair for more details. Check out
more than 100
new articles!
43
Questions
44
Appendix
45
Phased Upgrade Approach
46
Phased Upgrade Process
• Typically the first style of
upgrade one considers
• Requires the most
resources and effort to
accomplish
• Client has many projects
that have individual go
live dates
• The upgrade process
usually takes the longest
to complete because of
the amount work involved. USE AS A LAST OPTION
47
Steps to Conduct a Phased Upgrade
To perform Phased upgrade
• Backup your desired PC
Repository
• Restore it into a repository that is
going to act as your final repository
• Delete out all of the folders from
the final repository
• Leaves a blank repository with
nothing but connections
48
Steps to Conduct a Phased Upgrade
• To perform Phased upgrade
• Install version 9
• Create an instance of the final repository
• Upgrade instance of final repository
• Restore backup into temp repository.
• Stop temp repository service
• Create instance of temp repository inside of 9
49
Steps to Conduct a Phased Upgrade
• To perform Phased upgrade
• Upgrade temp instance of the repository
• Open Repository 9 Manager
• Create a query to conduct find all objects in a folder
• Export all desired objects out of temporary repository
• Import all object to final repository.
50
Phased Upgrade Approach Timeline
Folder migrations from v8 to v9 on development and new development instance to
support new code projects
Infa V8 DEV
Infa V8 QA
Infa V9 New Dev Projects
Infa V8 SIT
Infa V8 PROD
Infa V9 DEV
Infa V9 SIT
Infa V9 QA
Infa V9 PROD
Temporary Infa Dev
March April May June
6
7
10
11
16
12 15
13 18
2
17
19
21
14 20
1 4
3
5
8
9
*
*
*
*
* - No modifications allowed for existing project code unless the developer will complete the same code changes in both Infa8 and Infa9 environments.
*
*
51
Parallel Build Out
Parallel Build Out with Full Repository Restore
Infa V8 QA
Infa V8 SIT
Infa V8 PROD
Infa V9 DEV
Infa V9 SIT
Infa V9 QA
Infa V9 PROD
March April May June
1
* - No modifications allowed for existing project code unless the developer will complete the same code changes in both Infa8 and Infa9 environments.
Infa V8 DEV
52
Advanced Upgrade Styles
53
Installer Upgrade Overview
• The installer has 3 paths in 9.1.0:
• Install 9.1.0 on a new machines and create a new 9.1.0 domain. This is for first time installs and will create a brand new domain.
• Install 9.1.0 on a new machine and join an existing 9.1.0 domain. This will install new binaries but requires an 9.1.0 domain with at least 1 gateway node to be running to join.
• Upgrade a previous installed version to 9.1.0. This requires a previous install of PowerCenter 8.x or Informatica 9.x
• By default the upgrade component of the installer requires
access to a the previous installation of Informatica to perform
an upgrade.
• A user can override the domain configuration information if
they choose “Allow changes to hostname and port” option
54
Advanced Upgrade Option : Node Configuration Changes
• Why is this feature required ?
• Many customers plan for hardware and database upgrades when upgrading Informatica products
• This may be mandated by PAM changes
• Customers need a capability to support following use cases :
• Upgrade a node that runs on an unsupported operating system
• Upgrade a clone of a production domain (without altering the production environment)
• Functionality introduced in 9.0.1 HF1 and been refined in 9.1.0
55
Server Migration Scenarios
Windows 2003
Server AIX 6.1
PowerCenter
Installation
File Transfer
Informatica
Platform Installer
File Transfer
56
Unsupported DB Scenarios
AIX 5.3 with
DB2 v8 AIX 5.3 with
DB2 v9
PowerCenter
Version 8 DB Version 9 DB
Domain Export Informatica
Platform Installer Linking
Linking
57
Cloned Upgrade Scenarios
AIX 6.1 with
Oracle 11 AIX 6.1 with
Oracle 11
PowerCenter
Oracle 11
Schema A Oracle 11
Schema B
Domain Export Informatica
Platform Installer Linking
Linking
Recommended
