Table of Contents

Search

  1. Preface
  2. New Features and Changes (10.3)
  3. Version 10.2
  4. Version 10.1
  5. Version 10.0.0

Siperian BPM Workflow Engine

Siperian BPM Workflow Engine

Effective in version 10.0.0, the Siperian BPM workflow engine is deprecated. Previously, the Siperian BPM workflow engine was the default workflow engine in the MDM Hub. Informatica recommends that you install the ActiveVOS Server as part of the Hub Server installation. The ActiveVOS Server is the new default workflow engine.
You can continue to use Siperian BPM with this release. Before you upgrade, make a note of the settings defined for the Siperian BPM workflow engine. After you upgrade, define a Siperian BPM workflow engine with the same name and settings that you used in the previous release. Verify that the Operational Reference Stores use the Siperian BPM workflow engine.
If you want to switch workflow engines, first you need to close open tasks. You cannot migrate open tasks from one workflow engine to another.
You have the following options for moving from Siperian BPM to ActiveVOS Server:
  • Before you upgrade to this release, close all open tasks. After you upgrade, all upgraded Operational Reference Stores use the ActiveVOS Server as the workflow engine. You need to update your IDD applications to use ActiveVOS Server task definitions.
  • If you want to move to ActiveVOS Server after upgrading to this release, you can switch workflow engines after the upgrade. When you are ready to switch, close all open tasks. For each Operational Reference Store, change the workflow engine from Siperian BPM to the ActiveVOS Server. Update your IDD applications to use ActiveVOS Server task definitions.
For instructions, see
Informatica MDM Multidomain Edition Version 10 HotFix 1 Informatica Data Director Implementation Guide
.

0 COMMENTS

We’d like to hear from you!