This section describes the changes to Informatica workflow behavior in
version 10.0
.
Command Tasks
Effective in version
10.0
, a Command task does not fail when the working directory that the task specifies is not valid.
Previously, a Command task failed when the working directory was not valid.
For more information, see the
Informatica 10.0 Developer Workflow Guide
.
Data Integration Service Options
Effective in
version 10.0
, you configure a single Data Integration Service to run workflows.
Previously, you might configure different Data Integration Services to run Human tasks and to run the other stages in a workflow.
Effective in
version 10.0
, the Workflow Orchestration Service module on the Data Integration Service runs all stages in a workflow.
Previously, the Workflow Service module ran all stages in a workflow with the exception of a Human task. The Human Task Service module on the Data Integration Service ran a Human task in a workflow. The Workflow Orchestration Service module replaces the Workflow Service module and the Human Task Service module in
version 10.0
.
Complete all Human tasks that you run in an earlier version of Informatica before you upgrade to
version 10.0
.
For more information, see the
Informatica 10.0 Application Service Guide
.
Human Tasks
Effective in
version 10.0
, a Human task does not stop a workflow when the exceptionLoadCount input value on the task is less than 1. When the exceptionLoadCount input value is less than 1, the Human task completes but generates no data for Analyst tool users.
Previously, a Human task stopped a workflow when the exceptionLoadCount input value was less than 1.
Effective in version 10.0, a Human task sends email notifications using the email server configuration in the Email Service properties.
Previously, a Human task sent email notifications using the email server configuration in the Data Integration Service properties.
Effective in version
10.0
, you cannot move from one step to another in a Human task if you cancel the workflow in the following scenario:
The Human task is running.
The Data Integration Service distributed all of the task instances that the Human task specifies.
Previously, when you canceled the workflow, you could complete all of the steps in the Human task.
For more information, see the
Informatica 10.0 Developer Workflow Guide
.
Mapping Tasks
Effective in version 10.0, the Data Integration Service creates a log file for each instance of a Mapping task that runs in a workflow instance. If the Mapping task restarts following an interruption in an earlier workflow run, the Data Integration Service creates a log file for the restarted task.
Previously, the Data Integration Service stored log data for all instances of a Mapping task that ran in a workflow instance in a single file.
For more information, see the
Informatica 10.0 Administrator Guide
.
Notification Tasks
Effective in version 10.0, a Notification task sends email notifications using the email server configuration in the Email Service properties.
Previously, a Notification task sent email notifications using the email server configuration in the Data Integration Service properties.
For more information, see the
Informatica 10.0 Developer Workflow Guide
.
Run-Time Metadata
Effective in
version 10.0
, the Data Integration Service stores all run-time metadata for a workflow in a set of tables in a single database. You select the database connection as a Workflow Orchestration Service property on the Data Integration Service.
Previously, the Data Integration Service stored run-time metadata for a workflow in the Model repository and stored any Human task metadata in the Human task database. The Human task database is obsolete in
version 10.0
.
You must create the workflow database contents before you run a workflow. To create the contents, use the Actions menu options for the Data Integration Service in the Administrator tool.
For more information, see the
Informatica 10.0 Application Service Guide
.
Workflow Monitoring
Effective in
version 10.0
, a workflow can enter a completed state if a Command task or a Mapping task in the workflow sequence fails to complete.
For example, a workflow can continue to run to completion if a Mapping task fails in one of the following scenarios:
You enabled the workflow for recovery, and you configured the Mapping task with a skip recovery strategy.
You did not enable the workflow for recovery.
Previously, a workflow entered a failed state if a Command task or a Mapping task failed during the workflow run.
For more information, see the
Informatica 10.0 Administrator Guide
and the
Informatica 10.0 Developer Workflow Guide
.
Workflow Object Names
Effective in version 10.0, the following object names must use characters and symbols that conform to the XML
1.0
specification:
Workflow names
Task names
Gateway names
Workflow application names
Workflow variable names
Workflow parameter names
The XML
1.0
specification excludes a small number of characters and symbols from the names. If any name contains a character or symbol that the specification excludes, the workflow fails to run.
Previously, the XML 1.0 specification did not determine the range of valid characters and symbols in workflow names and associated object names.
If you upgrade to version 10.0 or later, edit any workflow or associated object name that contains a character or a symbol that the XML
1.0
specification does not support.
For more information, see the
Informatica 10.1 Upgrading from Version 9.5.1 Guide
and the
Informatica 10.1 Upgrading from Version 9.6.1 Guide
.
Workflow Recovery
Effective in
version 10.0
, the Data Integration Service does not impose a limit on the number of attempts to recover a workflow. The Administrator tool does not display the number of times that you try to recover the workflow.
Previously, you configured a maximum number of recovery attempts in the Developer tool. The monitoring features of the Administrator tool displayed the number of times that you tried to recover the workflow.
Effective in
version 10.0
, an aborted workflow is not recoverable.
Previously, an aborted workflow was recoverable.
Effective in
version 10.0
, when you cancel a workflow, the currently running task might remain in a Running state while the workflow enters a Canceled state. Because the task runs to completion, the workflow status can change to Canceled while the task is still running.
Previously, when you canceled a workflow, the workflow entered a Canceled state when the currently running task ended.
