Skip to Content

 

Introduction:

The purpose of the document is to provide the solution for Configuration Management in Data Services.

Problem statement:

While doing the deployment of the existing jobs and migrated data to multiple targets without modifying developed ETL package.

 

Proposed solution:

By Using existing feature of multiple profiles for single Datastore and configure the System Configuration.

 

Detailed Steps for the Solution:

Step 1: Create a Datastore and right click on created Datastore select “Edit” option

 

 

Step2: Select Edit Option from the context menu and click on “Advanced” button

STEP 3: Click on “Edit” button to edit configurations

 

 

Step 4: Click on Copy configuration ( )/New Configuration (  ) button

 

 

Step 5: Rename the new configuration profile name by Right lick on the configuration and select rename configuration)

Step 6: Update the Username, Password, Service name, Hostname, Port etc..

 

 

Step 7: Click on “Alias(Click here to create)” and enter the Alias name(Owner name which is at the time of Datastore creation) and click on “OK” button

 

Step 8: Enter the various schema names (Owner name) with respect to profile and click on “Apply” and Click on “OK” button

 

Step 9: Click “Ok” on Datastore edit window

Step 10: Select “Tools” > “System Configurations”…

 

  

Step 11: Click on New Configuration button () to create new configuration profile

 

Step 12: Right click on configurations and select Rename Configuration from context menu and rename the configuration with desired and standard naming convention

AND Select the required profile from the drop down list for selected Datastore (which we want to point to different schema at runtime) and click “Ok”

 

 

Step 13: Select the Job and right click and select Execute from context menu /

Click on Execute button 

Step 14: Select the required configuration form the system configuration drop down list and click ok to execute.

 

 

Conclusion:

While deploying the same data to multiple environments we required to execute the same job by pointing different targets each time which reduces the development and deployment effort and makes as one time activity for ETL life cycle

 

References:

http://wiki.scn.sap.com/wiki/display/EIM/Using+configurations+for+porting?original_fqdn=wiki.sdn.sap.com

http://wiki.scn.sap.com/wiki/display/EIM/Datastore+Configurations?original_fqdn=wiki.sdn.sap.com

http://scn.sap.com/community/data-services/blog/2012/11/06/data-services-code-migration-maintenance-simplify-your-lifecycle-improve-your-code

http://www.dwbiconcepts.com/etl/14-etl-informatica/74-stop-hardcoding-follow-parameterization-technique.html

 

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply