3.5. Migrating Running Processes

To migrate these processes follow the below steps:
  1. Shutdown any active BPM Suite servers using the older version.

    Important

    When the server is shutdown all processes will be terminated, and only the processes that have been persisted to the database will migrate smoothly. Before shutting down the BPM Suite server ensure that all rules are either waiting on a human task, so that they will be persisted, or not actively executing.
  2. Ensure the instructions in Section 3.4, “Database Migration for 6.x Instances” have been followed to upgrade the database to the new version.
  3. Start the new BPM Suite server, pointing to the same database that was previously in use.
  4. Before executing any processes on the new server follow the instructions for copying the maven and git repositories that pertain to the migration. These are discussed in Section 3.1.2, “Migrating Business Central Project, Repository, and Artifacts from 6.1.x to 6.2” and Section 3.2.2, “Migrating Business Central Project, Repository and Artifacts from 6.0.x to 6.1”.
  5. At this point the processes will be retrieved from the backing database and may be used as normal.

Note

Due to the database changes the server must be offline temporarily while the database is updated, and as such a true migration with no downtime does not exist. To minimize downtime it is recommended to use a load balancer in front of the BPM Suite servers and delegate requests to older instances until the full migration has completed. Once the database upgrade has completed, and the new JBoss BPM Suite servers started successfully, requests may be sent to these servers which will retrieve the persisted process.