1. Atlanta User Group PowerCenter 9.x Upgrade Strategy

2. Atlanta User Group Introductions Rick Lee Director Business Services and Project Delivery Richard. Lee@softpath.net Rizwan Mohammed Informatica Applications Architect Rizwan.Mohammed@softpath.net Srini Sunkara Informatica Applications Architect Srini.Sunkara@softpath.net

3. Atlanta User Group About Softpath …. Based in Atlanta, Softpath is a leading consulting services and IT staffing company. We are a 500 member team and growing. Informatica partner and value added reseller working coast to coast. Enterprise Information Management Services Master Data Management Data Governance Data Quality Data Integration (PowerCenter) One of the Largest US Practices 70+ Certified MDM Developers 50+ MDM Projects 100+ PowerCenter Upgrades One of the Largest US Practices 70+ Certified MDM Developers 50+ MDM Projects 100+ PowerCenter Upgrades Partial Client List

4. Atlanta User Group Upgrading PowerCenter is a Journey! Numerous paths available Not sure what to expect No time available for unexpected road blocks Risk averse approach needed

5. Atlanta User Group Today’s Mission – Arm you with Knowledge Benefits Planning / Approach Prep Work Install Work Testing Production

6. Atlanta User Group Benefits Why Upgrade?

7. Atlanta User Group  Administration Unified Informatica Administrator PowerCenter, powerexchange, data quality and dataservices  Development Cache Update in lookup Transformation Active configuration of the lookup Transformation Auto-commit Passive configuration of SQL transformation XML Parser to route error messages Proactive monitoring Enhanced Deployment methods Benefits Why Upgrade?

8. Atlanta User Group Planning Legacy systems XML Informatica PowerCenter 1 Domain 6 Environments 8 Integration Services 6 Repository Services 24X7 Environment’s active. 400+ ETL jobs Shell scripts..etc 50+ Users Extract ODS Oracle External Load files JMS Queue Flat Files Trans form Load EDW Staging Oracle Reporting Environment Overview – One Upgrade Customer

9. Atlanta User Group Approach Informatica Product From Version Intermediate Version To version PowerCenter8.1.x8.6.19.5 PowerCenter8.5.x8.6.19.5 PowerCenter8.68.6.19.5 Data Quality8.6.29.0.19.5 Data Quality9.09.0.19.5 Data Services9.09.0.19.5 Migration Paths Available

10. Atlanta User Group 1.Navigate to 8.6.1 admin console 2.Copy the 8.6.1 repository content to pc_95_repu1@orcl_mdb2 3.DO NOT upgrade, Fresh install the v95 on the new unix box. 4.Login to “unix_solaris101” and execute the installer for Powercenter 9.5. 5.Create new domain with new ports. 6.Migrate the user & group using the Export / import utility 7.Login to New v9.5 admin console & create repository using the details from step2. 8.Also create the soft links used for mapping the informatica file system. 9.Stop all the workflows from 861 environment and schedule them from the new environment. 1.Navigate to 8.6.1 admin console 2.Copy the 8.6.1 repository content to pc_95_repu1@orcl_mdb2 3.DO NOT upgrade, Fresh install the v95 on the new unix box. 4.Login to “unix_solaris101” and execute the installer for Powercenter 9.5. 5.Create new domain with new ports. 6.Migrate the user & group using the Export / import utility 7.Login to New v9.5 admin console & create repository using the details from step2. 8.Also create the soft links used for mapping the informatica file system. 9.Stop all the workflows from 861 environment and schedule them from the new environment. ZERO DOWN TIME

11. Atlanta User Group 1.Create 2 Schemas in the new compatible database for 1 domain and 1 repository. 2.Navigate to 8.6.1 admin console, Copy the 8.6.1 repository content to pc_95_repu1@orcl_mdb2 3.DO NOT UPGRADE, Fresh install the v95 on the existing Unix server but with a different Account. 4.Login to “unix_solaris101” and execute the installer for Powercenter 9.5. 5.Create new domain with new ports. 6.Migrate the user & group using the Export / import utility 7.Login to New v9.5 admin console & create repository using the details from step2. User Upgrade content of repository option. 8.Also create the soft links used for mapping the informatica file system. 9.Stop all the workflows from 861 environment and schedule them from the new environment. 1.Create 2 Schemas in the new compatible database for 1 domain and 1 repository. 2.Navigate to 8.6.1 admin console, Copy the 8.6.1 repository content to pc_95_repu1@orcl_mdb2 3.DO NOT UPGRADE, Fresh install the v95 on the existing Unix server but with a different Account. 4.Login to “unix_solaris101” and execute the installer for Powercenter 9.5. 5.Create new domain with new ports. 6.Migrate the user & group using the Export / import utility 7.Login to New v9.5 admin console & create repository using the details from step2. User Upgrade content of repository option. 8.Also create the soft links used for mapping the informatica file system. 9.Stop all the workflows from 861 environment and schedule them from the new environment. PARALLEL UPGRADE

12. Atlanta User Group 1.Create 2 Schemas in the new compatible database for 1 domain and 1 repository. 2.Clone the content of the schemas from mdb1 to mdb2. repository content can be cloned using the “copy content from” option in adminconsole 3.Shutdown the v8 domain and move the environment variables from.bash_profile. 4.Create.bash_profile for v9 installation. DO NOT UPGRADE, Fresh install the v95 on the existing Unix server but with the same Unix account. Only the mdb will change in this process. 5.Login to “unix_solaris101” and execute the installer for Powercenter 9.5 & Create new domain with new ports. 6.Migrate the user & group using the Export / import utility 7.Login to New v9.5 admin console & create repository using the details from step2. User Upgrade content of repository option. 8.Also create the soft links used for mapping the informatica file system (infa_shared). 9.Unscheduled all the workflows from 861 environment and schedule them from the new environment. 1.Create 2 Schemas in the new compatible database for 1 domain and 1 repository. 2.Clone the content of the schemas from mdb1 to mdb2. repository content can be cloned using the “copy content from” option in adminconsole 3.Shutdown the v8 domain and move the environment variables from.bash_profile. 4.Create.bash_profile for v9 installation. DO NOT UPGRADE, Fresh install the v95 on the existing Unix server but with the same Unix account. Only the mdb will change in this process. 5.Login to “unix_solaris101” and execute the installer for Powercenter 9.5 & Create new domain with new ports. 6.Migrate the user & group using the Export / import utility 7.Login to New v9.5 admin console & create repository using the details from step2. User Upgrade content of repository option. 8.Also create the soft links used for mapping the informatica file system (infa_shared). 9.Unscheduled all the workflows from 861 environment and schedule them from the new environment. CLONE UPGRADE

13. Atlanta User Group IN PLACE UPGRADE 1.Backup Domain using infasetup.sh and also backup the repository using pmrep or adminconsole. 2.Run pre installation check tool i9pi to validate the pre requisites. 3.Shutdown the Domain, backup / verify / update the.bash_profile for the existing unix application account. 4.Run the Installer and select the upgrade option. 5.During the upgrade process for domain creation / upgrade using the existing schema user and password. 6.Login to the admin console and on the top right corner under the Manage option, select individual services to upgrade. 7.Also create the soft links used for mapping the informatica file system (infa_shared). 8.Restart the integration service to put back the workflows on schedule. **Considering All the pre-requisites (technical / non technical) have been met.

14. Atlanta User Group Prep Work Work with Informatica for license procurement and Production documentation. Softpath can help. Download the Informatica binaries to the server which needs an upgrade. Review the OS configuration, version and patch requirements Review the current File System allocation. Better Storage allocations allows future upgrades seamless and other file processing growth demand. Determine the temp space requirement Review the Network Configuration, Dual NIC with Bonding and Jumbo frame enable System User Accounts Unix Profile & Environment Variables setup Clear the repository logs Backup the Domain Backup the Repository Backup the Users and Groups Review the LDAP security and OS Profile configurations. Review the current scripts and scheduler setup Determine Port Configuration, Availability and Firewall Configuration requirements Database account(s) for metadata

15. Atlanta User Group Install Work 1. Install or Upgrade?

16. Atlanta User Group Install Work 2. Verify Pre-requisites 3. Enter Directory Information

17. Atlanta User Group Install Work 4. Setting Verification

18. Atlanta User Group Install Work 5A. Configurations

19. Atlanta User Group Install Work 5B. Configurations 6. Domain and Node Configurations

20. Atlanta User Group Install Work 6A. Port Configurations Post Installation Summary

21. Atlanta User Group Testing Unit Regression Performance Select the few mappings which has combination of active and passive transformations(Joiners, Expressions, SQL Transformation, XML Parser, Java Transformation, Sorter, Aggregator, Web Service, Lookups (Cached, Un- cached), Web Service and Queue(JMS,MQ) Prepare the test data which are identical to production volume. Intentionally create the data backlog, delayed runs to simulate data volumes. Gather run time statics, number of rows in and out, session memory utilization, Connect to the Production Read only source to simulate data volumes Run the repository queries to find the run timings, records in/out and throughput and compare with production repository queries to identify potential workflows which may need further attention Select subset of workflows which are mission critical for the business operations Review the logs for workflows and Sessions, observer the SQL generation, run time properties and compare with production logs

22. Atlanta User Group Upgrade Options ApproachBenefitsTimeRisk Zero downtime upgrade Easy to Switch between Environments Partial Back out is possible Low Risk Isolated Approach HighLow Parallel upgrade Faster Upgrade Parallel Environments under application accounts Partial Back out is possible No additional Hardware is required Med Cloned upgrade Faster Upgrade Easy Back out Existing file system configurations can be reused No need to migrate users and groups Med+ In place upgrade Easy Upgrade Minimal Configuration changes No additional infrastructure No need to migrate users and groups LowHigh Production

23. Atlanta User Group Production Production Considerations Pre-Production Release Back Out Plan Upgrade Validation and Health Check Upgrade Status Broadcast DR Activation Steps Execute Upgrade Production Conduct Post Implementation Testing Assess the Migration (upgrade) Determine Go Forward / Fall Back Communicate

24. Atlanta User Group Questions Rick Lee Director Business Services and Project Delivery Richard.Lee@softpath.net Rizwan Mohammed Informatica Applications Architect Rizwan.Mohammed@softpath.net Srini Sunkara Informatica Applications Architect Srini.Sunkara@softpath.net