Importing Workflows from PowerCenter
When you import a workflow from PowerCenter, the Start and Session task, which includes both reusable and non-reusable task, imports into the Model repository. In the Model repository, each workflow contains an End event after you import from PowerCenter.
Branches in the PowerCenter workflows gets routed through Inclusive gateways in the imported workflows in the Model repository. An Inclusive gateway requires at least one of its outgoing sequence flows to be set as default. The first outgoing sequence flow from the gateway becomes the default and the imported workflow remains valid.
Rules and Guidelines for Importing Workflows from PowerCenter
If you import a workflow, consider the following rules and guidelines:
- The import process links PowerCenter session or task instances without outgoing links to the End event in the Model repository.
- If a PowerCenter workflow contains a session or task instance that does not have outgoing links, the imported workflow adds a link to the gateway to connect the session or task instance to the End event in the Model repository.
- The imported workflow removes an unsupported PowerCenter task. If the unsupported tasks are part of a branch or merge, the import process removes unsupported tasks and replaces the branches or merges with gateway tasks.
- If a PowerCenter mapping contains an task in the workflow that is not supported for import into the Model repository, then the unsupported tasks are removed from the imported workflow in the Model repository. However, if the unsupported tasks were part of a branch or merge, the gateways for these tasks are created and are present as an unconnected task in the final imported workflow.
- The import process splits session tasks with additional session tasks for each mapping corresponding to each pipeline based on target load order.
- If a workflow contains a session task in PowerCenter, the task gets split when the session points to a mapping with multiple pipelines for each target load order after import in the Model repository. The imported workflow contains additional session tasks for each mapping corresponding to each pipeline based on the target load order.
- For example, you have a PowerCenter workflow containing a Start task linked to a session. The session points a mapping having two pipelines. The first pipeline has a source, Source1 pointing to the transformation, Tx1 that leads to a target, Target1. The second pipeline has source, Source2 that points to transformation, Tx2 that leads to the target, Target2.
- After you import the workflow in the Model repository, two sessions are created and linked according to the target load order as follows: Start -> Session_Mapping_pipeline_1 -> Session_Mapping_pipeline_2 -> End, where Session_Mapping_pipeline_1 points to the mapping created from the first pipeline and Session_Mapping_pipeline_2 points to the mapping created from the second pipeline.
Importing a Command Task from PowerCenter
You can import a Command task from PowerCenter into the Model repository.
If you import a Command task, consider the following information:
- You can add multiple commands within a PowerCenter Command task. The Developer tool has a single field for adding all the commands for the Command task.
- In PowerCenter, you can specify multiple commands within a Command task. In the Developer tool, a single field contains all the commands.
- Check if you have selected or deselected the Fail Task if Any Command Fails session property before importing the Command task.
- Before you import a Command task from PowerCenter into the Model repository, check whether you have selected the Fail Task if Any Command Fails session property in PowerCenter or not. The import process might append either a double ampersand (&&) or a single semicolon (;) at the end of each command except the last command based on the session property.
- If you have disabled the Fail Task if Any Command Fails session property for the Command task, the import process appends each command except the last one with a semicolon in the Developer tool. For example, <first_command>; <second_command>.
- If you have enabled the Fail Task if Any Command Fails session property for the Command task, the import process appends each command with a double ampersand (&&) in the Developer tool. For example, <first_command>&& <second_command>.
Conversion Behavior with the Command Task Import
Consider conversion behavior for importing the Command task when you use a semicolon or a backslash within a command.
The following scenarios show the conversion behavior with the Command task:
- •There are two commands in PowerCenter. The first command contains a semicolon at the end, such as <c1;c2;> and the second command is <c3>.
The import process converts the command with the following syntax:
“<C1;C2>”; “<C3>”
OR
“<C1;C2>”&& “<C3>”
- •There are two commands in PowerCenter. The first command contains a backslash and a semicolon at the end, such as <C1;C2\;> and the second command is <C3>.
The import process converts the command with the following syntax:
“<C1;C2\;>”; “<C3>”
OR
“<C1;C2\;>”&& “<C3>”
- •You have two commands in PowerCenter. The first command contains a backslash and two semicolons at the end as “<C1;C2\;;>” and the second command is “<C3>”.
The import process converts the command with the following syntax:
“<C1;C2\;>”; “<C3>” OR “<C1;C2\;>”&& “<C3>”
OR
“<C1;C2\;>”&& “<C3>”