03-28-2017 10:03 PM
Hi OnBase Community, I have some questions regarding Configuration Migration:
Q1) A customer is going to have the following OnBase environments: PROD, DEV, UAT and TRAIN. Is it possible to configure a linked system between all 4 environments?
Q2) If answer to Q1 is Yes, is this unrealistic or can are there any issues in a multi-project environment where some projects in UAT will be ready to test and others will be ready to migrate to PROD? Same goes for DEV-UAT?
Regards,
George
03-31-2017 12:33 PM
Hi George,
To answer your first question, it would be possible to have multiple linked environments such that:
PROD creates a linked database for UAT
UAT creates a linked database for TRAIN
TRAIN creates a linked database for DEV
Each system can only directly be linked to one other system. When set up this way, you would first need to migrate from DEV to TRAIN, then TRAIN to UAT, then UAT to PROD.
To answer your second question, although this is possible it could be extremely limiting, because while the systems are linked, no changes can be made except in DEV (or whichever is the last system to be created). When you migrate any one system up the chain, all changes in that system are migrated. In a multi-project environment this is probably not what you want.
An alternative is to use the import/export tools contained within OnBase Studio and Configuration (Utils | Change Management) to move changes between systems. You could still use Configuration Migration to create other systems from PROD (using the Unlinked option).
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.