In the recent past I received a lot of questions about migrating BPM, its database as well as the deployed snapshots and the running instances.
This is a very complex topic with a lot of traps and pitfalls - and not everything is possible.
First of all, we have to differentiate between the migration of your environment and your application.
There are some good articles available with step-by-step instructions on how to migrate a BPM setup from one physical environment to another one. Please have a look at this DeveloperWorks article.
In this context I was asked, if one could not simply clone an existing database and use it for the new environment to save time. In theory this is possible, as long as you do not change specific things like storegroup, db name, schema name etc.
However, every BPM environment has its own GUID. After cloning you will have to absolutely identical environments. In most cases this is not desirable. Hence the suggested way to create new databases is using the scripts provided with the product - after all that does not take much more time compared to cloning.
The other question that came up was: What does migrating running instances actually mean?
Instance migration means that currently running instances are migrated to the new snapshot that you are deploying.
In that context, whatever the actual step of the running instances is, the new version is implemented for the next item or step. Some problems may occur if the new version removes steps or other components from the business process definition (BPD).
Please have a look at this Knowledgecenter article about instance migration.
The instance migration is supported as a in-place migration, which means a newer version of the application is deployed to the same BPM environment where the old version already existed.
But what about migrating instances to completely different environments?
Unfortunately, that is NOT supported. Please refer to the following dw-answers thread.
Last but not least, I was asked if it is possible to migrate the BPM DB from one supported DB type/vendor to another. Yes, this is possible, but this is fairly complex and requires a lot of planning. In these cases I can only recommend to engage our IBM Consulting Services. They have the experience to help you getting this mammoth job done.
So, my dear friends, I hope I was able to bring some light into the darkness of migration questions.
And if not, take two of these and call me in the morning.
Your Doc D