to register a business process management (BPM) tool as a workflow engine and to map the workflow engine to
Operational Reference Stores
.
The default, predefined workflow engine is the licensed version of the ActiveVOS
®
Server that is included with
Multidomain MDM
. The installation process integrates this version of the
ActiveVOS Server
with the
MDM Hub
and
Data Director
, and deploys predefined MDM workflows, task types, and roles.
The Informatica ActiveVOS workflow engine supports the following adapters:
An adapter for tasks that operate on business entities through business services. The adapter name is
BE ActiveVOS
.
An adapter for tasks that operate on subject areas through SIF APIs. The adapter name is
Informatica ActiveVOS
.
You can also choose to integrate standalone instances of BPM tools:
Informatica ActiveVOS
If you run a standalone instance of
Informatica ActiveVOS
in your environment, you can manually integrate your instance with the
MDM Hub
and
Data Director
. You can deploy the predefined MDM workflows or create custom workflows. For more information, see the
Multidomain MDM Data Director - ActiveVOS Integration Guide
.
Third-party BPM tool
If you run a third-party instance in your environment, you can manually integrate your instance with the
MDM Hub
and
Data Director
. You can deploy the predefined MDM workflows or create custom workflows. For more information, see the
Multidomain MDM Business Process Manager Adapter SDK Implementation Guide
.
Informatica recommends that you migrate to the business entity-based ActiveVOS workflow adapter. The Siperian workflow adapter is deprecated. Informatica will continue to support the deprecated adapter, but it will become obsolete and Informatica will drop support in a future release. The MDM Hub supports a primary workflow engine and a secondary workflow engine. You can migrate from the Siperian workflow adapter to the business entity-based ActiveVOS workflow adapter.