Informatica Powercenter is a data integration and quality service tool using the ETL (Extract, Transform and Load) architecture. It offers the capability to connect and fetch data from different heterogeneous sources and processing of data. Opsera provides users the ability to leverage Informatica’s services into their pipelines through configuration in the Tool Registry. The Opsera Informatica pipeline contains 2 pipelines steps in the workflow: An export and import step, both using the configured Informatica tool. Start by configuring the Informatica tool in Opsera’s Tool Registry.
Informatica Tool Registry Setup
Create a new tool in Tool Registry with identifier ‘informatica’.
Navigate to ‘Connections’ tab and provide proper credentials. Once credentials are entered, press ‘Test Connection’ to verify connection is successful.
Regions - Select proper region.
Username - Provide your username from Informatica
Password - Provide your password from Informatica.
Navigate to ‘Validation Rules’ tab to enter Rule Mapping. Select Informatica Type from the dropdown then specify a Rule. Selected Rules should match those provided within Informatica’s portal in the Data Integration area.
Informatica Type - Assets provided within Informatica will match Informatica Type.
Rule - If the rule provided does not match rule given in Opsera’s pipeline, this will receive a ‘fail’ status. If existing rules from Informatica are NOT added in this tab they will pass.
4. Click ‘Save’ button.
Informatica Pipeline Setup
Informatica Pipeline Prerequisite: In the pipeline’s Summary tab, verify that the ‘Type’ selected is Informatica. Click on the pencil icon to the right of the ‘Type’ field and select ‘Informatica’ from the dropdown. Once selected, click the disk icon to save.
The informatica pipeline contains 2 steps in the Workflow: Import & Export
In the pipeline Workflow, create a new pipeline step. In the Step Setup, provide a ‘Step Name’ and select ‘Informatica’ in the Tool dropdown. Once saved, provide configurations. In Step Configuration, make the following selections:
Type of Execution - Choose ‘Export Objects’.
Informatica Tool - Select the configured Informatica tool from the Tool Registry.
SCM Type - Choose from Bitbucket, GitHub or GitLab.
SCM Account - Select the configured SCM account.
Workspace/Project - Select the workspace or project containing the repository.
Repository -
Branch -
Create a new branch - Enable the toggle to enter information about your new branch
Source Branch - Select the branch that your new branch will be based off of.
Dynamic Branch Name - Enter a name for the new branch name. To make this a dynamic name, changing with every new run, you can append the following keywords to your branch name of choice: “timestamp” - adds the current timestamp to end of the branch name. “run_count” - adds the current run count number. You can add both if desired, for example: “dynamicbranchname_timestamp_run_count”. Branch name will display as follows:
Include Dependencies -
Save the step.
Create a new pipeline step. In Step Setup. Select ‘Informatica’. In Step Configuration, make the following selections:
Type of Execution: Choose ‘Import Objects’.
Informatica Tool - Select the same configured Informatica tool used in the first pipeline step.
Informatica Export Object Step - Select the name of the export Informatica step from the dropdown.
Deploy from Git - Enable the toggle to provide values from dropdowns to indicate import location.
Click ‘Save’ button.
Once the pipeline steps have been configured properly, click the ‘Start Workflow’ button to enter the Informatica Pipeline Run Assistant.
Informatica Pipeline Run Assistant
Default configuration objects display in ‘Migration Objects’:
Scroll down further to view the Informatica asset Types selected with Rule Validation status selected in ‘Rule Validations’ tab of Tool Registry:
Fail - Rule validation is not satisfied.
Pass - Rule validation is satisfied OR no rule validation selected.
Select Migration Objects and click ‘Proceed with # Migration Objects’ button to trigger the pipeline start.