IBM BPM, V8.0.1, All platforms > Get started with IBM BPM > Key concepts > Versioning > BPEL processes > Migrating running process instances to a new version of the BPEL process

BPEL process migration tracking

If events are defined for a BPEL process, you can track process migration using Common Base Events. An event can be generated when the migration is started and again when the migration is complete. In addition, a history of process migrations is kept for each process instance in the Business Process Choreographer database.


Common Base Events for migration

You can use Common Base Events to monitor process instance migrations. These events are exploited by IBM Business Monitor.

The following events can be generated:

PROCESS_MIGRATION_TRIGGERED

This event is emitted when the migration of process instances to use a new template is started.

PROCESS_MIGRATED

This event is emitted when a process is migrated to use a new template.


Process migration history

A history of each process instance migration is kept in the Business Process Choreographer database. This information is available for each process instance and it is deleted when the process instance is deleted.

When a process instance is migrated, the isMigrated property is set to TRUE in the PROCESS_INSTANCE database view. The MIGRATION_FRONT database view provides the migration history for each process instance migration. This view contains information about where the process instance was in its navigation when it was migrated to the new version of the process template.

Migrating running process instances to a new version of the BPEL process


Related concepts:
Migrating running process instances to a new version of the BPEL process
BPEL process events overview
BPEL process model changes and runtime migration


Related reference:
Database views for Business Process Choreographer