Table of Contents

Table of Contents...............................................................................................................................1 1 Migration Procedures.......................................................................................................................2 1.1 Migration Guiding Principles......................................................................................................2 1.2 Description of Migration Component(s)......................................................................................2 1.2.1 Workflows to be migrated for APAC....................................................................................2 1.2.2 Workflows to be migrated for EMEA....................................................................................3 1.3 Template for Migration Notification.............................................................................................3 1.4 Pre Migration Tasks...................................................................................................................3 1.5 Detailed Migration Steps for PoweCenter (including common errors and fixes)..........................4 1.5.1 Steps for Importing are as given below:...............................................................................4 1.5.2 Resolving checkbox issue in ETL2B .................................................................................10 ........................................................................................................................................................11 1.5.1 Parameter path changes in workflow instances.................................................................13 1.5.2 Modification to Integration Service.....................................................................................15 1.5.3 Creation of connection strings...........................................................................................16 1.5.4 Setting User Permissions..................................................................................................17 1.6 Detailed Migration Steps for Database.....................................................................................19 1.7 Post Migration Tasks...............................................................................................................20 1.8 Rollback/Restoration procedures.............................................................................................20 1.9 Emergency Contact List...........................................................................................................20 1.9.1 Technical Architect............................................................................................................20 1.9.2 Migration Specialist...........................................................................................................20 1.9.3 DBA Group Lead...............................................................................................................20 1.9.4 Application Lead................................................................................................................20

02/04/12

Page 1 of 20

1 Migration Procedures
This document provides the pre-requisites, environment details and steps involved in migration of ETL components for AMZ - Customer Master Data Management project from source environment to target environment.

1.1 1.2

Migration Guiding Principles Description of Migration Component(s)

All master Workflows are same for APAC and EMEA. So there is no need to provide environment specific workflow; only one super master workflow is different for APAC and EMEA. 1.2.1 Workflows to be migrated for APAC

Phase Name Super Master Workflow For APAC ETL1 ETL2A ETL2B ETL3A ETL3B Match, Merge & Tokenizer Outbound Outbound XREF

Workflow Name super_mstr_wf_execute_mdm_process_apac mstr_wf_qsa_pre_ldg_load mstr_wf_pre_ldg_std_int_load mstr_wf_std_int_mdm_ldg_load mstr_wf_mdm_stg_prcs mstr_wf_mdm_ld_prcs mstr_wf_mdm_tknzr_mtch_mrg_prcs mstr_wf_mdm_base_object_outbound_load mstr_wf_mdm_base_object_outbound_load_xref

02/04/12

Page 2 of 20

1.2.2

Workflows to be migrated for EMEA

Phase Name Super Master Workflow For EMEA ETL1 ETL2A ETL2B ETL3A ETL3B Match, Merge & Tokenizer Outbound Outbound XREF

Workflow Name super_mstr_wf_execute_mdm_process_emea mstr_wf_qsa_pre_ldg_load mstr_wf_pre_ldg_std_int_load mstr_wf_std_int_mdm_ldg_load mstr_wf_mdm_stg_prcs mstr_wf_mdm_ld_prcs mstr_wf_mdm_tknzr_mtch_mrg_prcs mstr_wf_mdm_base_object_outbound_load mstr_wf_mdm_base_object_outbound_load_xref

1.3 1.4

Template for Migration Notification Pre Migration Tasks

1. Folder for migration should present in respective PowerCenter Repository. 2. The folder present in target repository for migration should be empty if migration is happening first time. 3. Generic user should be created in PowerCenter and he should have rights to access repository and folder. 4. Physical Directory structure should be present on servers shared path and it should be in a required manner. 5. User should have read write access on the shared directory. 6. Export of workflows in XML files should be present on shared path for importing it to target repository.

02/04/12

Page 3 of 20

1.5

Detailed Migration Steps for PoweCenter (including common errors and fixes)
1.5.1 Steps for Importing are as given below: 1) Open Informatica Power Center Repository Manager 2) Click on Repository, and select the option Configure Domains 3) Add the repository details depending on the environment in which this activity needs to be carried out. 4) Once the domain is created, right click on it and select Connect.

5) Once the domain is connected, all the objects appear in the Repository Navigator

6) Take the export of all present objects from the source environment for both APAC and EMEA environments. The names of the workflows to be exported are given in sections 4.2 & 4.3.

02/04/12

Page 4 of 20

7)

Save the XMLs in a shared path

02/04/12

Page 5 of 20

8) Once export process is completed, import the objects to target environment for APAC and EMEA respectively.

9) In the Import Wizard, browse and choose the path of the XML file that has to be imported.

02/04/12

Page 6 of 20

10)

Select the XML file that has to be imported.

11)

Click on Add All to import all the objects.

12)

Click on Next

02/04/12

Page 7 of 20

13) In the Folder Selection Dialog, choose the folder in the destination repository.

14) Click on Next in the Import Wizard dialog. 15) Click on Check In box. This will ensure that once imported all the objects will be in checked-in state.

16)

Click on Next in the Import Wizard dialog.

02/04/12

Page 8 of 20

17) Resolve conflicts, if any. Remember to select the REPLACE checkbox, to resolve conflicts and apply to all conflicts.

18)

Click on Import.

02/04/12

Page 9 of 20

19)

The status of the imports is shown in the dialog box.

In case of unsuccessful import, please take a new Export of the XML and repeat the entire process.

1.5.2

Resolving checkbox issue in ETL2B

1) Open Power Center Workflow Manager. Open the ETL2B workflow, i.e. mstr_wf_std_int_mdm_ldg_load and open the master worklet.

02/04/12

Page 10 of 20

2) Open each child worklet.

3) In the child worklet, choose the session for load and Edit it. For e.g.: The loading session for the address mapping is s_std_int_mdm_ldg_for_c_l_addr_load . Well have similar sessions for the other entities.

02/04/12

Page 11 of 20

4) In the Mapping tab, choose the Source and click on Set File Properties.

5) A pop-up opens listing Flat Files as sources. Click on the Advanced button. In the delimited file properties, in the Others section, tick the checkbox for the option Treat multiple delimiters as AND.

NOTE: This has to be done for all the child worklets for an entity. This has to be done for all the 13 entities for the ETL2B workflow. This has to be done in both APAC & EMEA repositories.

02/04/12

Page 12 of 20

1.5.1

Parameter path changes in workflow instances. We need to update the workflows with the correct parameter paths to ensure that they point to the appropriate parameter files. Steps for this parameter file path changes are given below: 1) Open Power Center Workflow Manager. Open one of the workflows in EDIT mode.

2) In the dialog box that opens, click on the button Configure Concurrent Execution.

3) Clear all the existing entries that you can see in the Instance Name and Parameter file. 4) Now, add all the new instance names and their corresponding parameter file paths. Please refer to the attached Excel Parameter_Path for the instance names and the parameter file paths.

02/04/12

Page 13 of 20

Please note that the excel needs to be updated with the appropriate shared paths for APAC & EMEA environment.

Parameter_Path.xlsx

This needs to be done for ALL the nine workflows and for both the APAC & EMEA repositories. Ensure that there are 48 entries in each workflow for EMEA and 10 entries for each workflow in APAC.

02/04/12

Page 14 of 20

1.5.2

Modification to Integration Service

1) Open Power Center Workflow Manager. Open one of the workflows in EDIT mode. 2) In the dialog box that opens, in the General tab, Click on the link for Browse Integration Services. The respective Integration Service Names will be provided prior to deployment.

3) Select the appropriate integration service name and Click on OK

NOTE : This needs to be done for all the nine workflows in both the repositorys for EMEA and APAC

02/04/12

Page 15 of 20

1.5.3

Creation of connection strings

1) In Power Center Workflow Manager, Click on the Connections option and choose Relational option

2) In the dialog box that opens, click on New Connection and select subtype as Oracle. Click on OK.

02/04/12

Page 16 of 20

3) Provide the connection details in the pop-up. Click on OK. Refer to the attached Excel Relational_Connection_String_Details for the connection string details.

Relational_Connectio n_String_Details.xlsx

NOTE : This needs to be done in both the repositorys for EMEA and APAC

1.5.4

Setting User Permissions 1) In PowerCenter Workflow Manager, Click on the Connections option and choose Relational option

02/04/12

Page 17 of 20

2) In the dialog box that opens, click on Permissions button.

3) In the resultant pop-up, select the appropriate username and give Read and Execute permissions to that user.

NOTE: This activity has to be done for both APAC & EMEA repositories.

02/04/12

Page 18 of 20

1.6

Detailed Migration Steps for Database

Following are the associated steps related to database activities during the ETL migration. Follow them in sequence. In each step schema is mentioned in which scripts need to be executed. Scripts are used to 1) Create required tables in different schema. 2) Inserts the required data in audit tables in audit schema. 3) To create the required sequence, packages and procedure in different schema. All below said script will be available on some shared path for executing. For EMEA Environment: Run the following scripts one by one: 1. Run Schema_Create.sql Scripts to be run in AMZN_MDM_ETL_AUDIT schema: 1. Run Create_Audit_tables.sql 2. Run Create_Sequence.sql 3. Run Insert_Seed_data_for_EMEA.sql 4. Run EMAIL_PKG.pck 5. Run PROC_DATALOAD_IND.sql Scripts to be run in AMZN_MDM_PRE_LNDNG schema: 1. Run Pre-Landing_Table_Creation_EMEA.sql 2. Run Proc_Truncate_Partition.prc Scripts to be run in AMZN_MDM_PPROD (MDM ORS): 1. Run CMXBJ_PKG.pck Scripts to be run in AMZN_MDM_PBLSH (MDM ORS): 1. Run Publish_Table_Creation_Script.sql For APAC Environment: Run the following scripts one by one: 1) Run Schema_Create.sql Scripts to be run in AMZN_MDM_ETL_AUDIT schema: 1. Run Create_Audit_tables.sql 2. Run Create_Sequence.sql 3. Run Insert_Seed_data_for_APAC.sql 4. Run EMAIL_PKG.pck 5. Run PROC_DATALOAD_IND.sql Scripts to be run in AMZN_MDM_PRE_LNDNG schema: 1. Run Pre-Landing_Table_Creation_APAC.sql 2. Run Proc_Truncate_Partition.prc Scripts to be run in AMZN_MDM_PPROD (MDM ORS): 1. Run CMXBJ_PKG.pck

02/04/12

Page 19 of 20

Scripts to be run in AMZN_MDM_PBLSH (MDM ORS): 1. Run Publish_Table_Creation_Script.sql

1.7

Post Migration Tasks

Steps to be followed post migration of all the workflows in target repository are 1. All 9 workflows are present in both EMEA and APAC target repository. 2. In ETL2B phase mstr_wf_std_int_mdm_ldg_load check source file properties that Treat multiple delimiters as AND check box is ticked. 3. Open some sessions and check the mapping associate with them are available with them. 4. All the PowerCenter connection strings are created with correct values. 5. Generic user should have read and execute access on all PowerCenter connection strings. 6. Correct integration services is associated with all the workflows. 7. All instances should be present in Workflow Manager for all the workflows. 8. Correct parameter file path should be present in instances created. 9. Check all the required objects are present in all the schemas. 10. Required partitions and seed data is present in required tables.

1.8

Rollback/Restoration procedures

There are few steps that need to be performed before importing into target repository. Please check with Pulak/Abhishek and ask them to populate this section.

1.9

Emergency Contact List

1.9.1 Technical Architect Name: Phone: e-mail: 1.9.2 Migration Specialist Name: Phone: e-mail: 1.9.3 DBA Group Lead Name: Phone: e-mail: 1.9.4 Application Lead Name: Phone: e-mail:

02/04/12

Page 20 of 20