How to replicate EngageOne (4.X) Environment

Follow these steps:
1. Create a full backup of databases (both EngageOne i.e eo and activiti)  on source environment.
2. Create a full backup of active-drive folder on source environment.
3. Restore both databases (eo and activiti) on a destination database server.
4. Restore active-drive folder (from backup created in step #2) on a destination server. If possible, the path to it should be the same as it was on the source server (where the backup has been created).
5. Change the configuration of all EO bundles except core to make them aware of the fact that DB is now running on a new server.
6. Perform uninstall steps for core bundle (-service and -bundle).
7. Perform installation steps for core bundle (-install, -validate and -configure). If the path to active-drive folder in DR environment is different than in the original production environment, Steps 8 and 9 needs to be performed else these should be skipped.
8. In EngageOne database, find all the values which contain direct reference to active-drive folder. To do this, use attached DB_Search.sql.
9. Based on the results of the previous step, modify all the data accordingly. Be aware of the fact that if a particular column is listed in results, it doesn’t automatically mean that all values in that column have to be updated.
10. Start EO services (security, core, composition and conversion) and do a sanity check.

Further actions are optional and depend on sanity tests results. For example if key maps are used and path to key map’s resources is different in  destination environment than in the original environment , there would be a need to update references to key map’s resources in EngageOne database (table OCM_KEYMAP). The final step is a modification of all existing files which contain reference to old key map’s resources folder.
All the files are stored in active-drive folder. This action has to be performed manually for each file, there is no possibility to modify them automatically.
UPDATED:  April 19, 2017