Introducing the Tidal Automation Adapter for Informatica PowerCenter

The Tidal Automation Adapter for Informatica PowerCenter lets you add advanced scheduling features to your setup and combine multiple schedulers into one centralized console. Working with Tidal Automation, the adapter makes it easy to define, launch, and monitor workflows in Informatica PowerCenter, improving automation and integrating smoothly into an enterprise-wide scheduling system.

The adapter integrates with Informatica PowerCenter version 10.5 and above using SOAP requests ensuring efficient communication and management of workflows between the adapter and Informatica PowerCenter. This integration facilitates the transfer of data between the adapter and Informatica PowerCenter.

To use this adapter, start by setting up connections to your Informatica PowerCenter environments. Then, create Informatica PowerCenter jobs just like you would with other jobs. With the Informatica PowerCenter adapter, you can easily choose folders or workflows, as well as monitor the job’s execution in real-time from the Job Activity pane.

Once the job is completed, the adapter updates the Job Activity pane with the final status, which helps manage any dependent jobs, along with run details. Additionally, the adapter allows users to cancel, abort, or rerun workflows directly from Tidal Automation, offering much more control over the environment compared to other standalone scheduling tools.

Note: The recover function works only for workflows without concurrent execution.

Note: Concurrent execution of workflows is not supported. Please run one workflow at a time.

Prerequisites

Note: The adapter integrates with Informatica PowerCenter version 10.5 and above.

To use the adapter, create and enable these services:

• Web Service Hub

• PowerCenter Integration Service

• PowerCenter Repository Service

Known limitations

• If you start a job containing multiple steps of the "Run Task Only" type and issue a Stop or Hold action during its execution, the step where the stop was triggered will complete. However, the subsequent steps will not execute. The job will then terminate with a status of either "Completed Normally" or "Completed Abnormally" depending on the result of the step that was completed.

• If you start a job, stop it during execution, and then resume it, the system adds a new step with the status Hold on the Run Info Tab for each stop-and-resume action. The number of Hold entries corresponds to the number of times the job is stopped and resumed.

• When a job completes, the Run Info tab initially shows statuses for all steps. However, if you close the tab using OK and reopen it, the Status column for the first step will appear blank. Always use Cancel to close the tab to retain the first step's status.

• The up and down arrow buttons do not save values; you will need to manually enter the numbers.