Multi-environment setup
We're trying to setup our development and production environments to ease the process of migrating process flows. We currently have changes occurring in both environments, which makes promoting flows difficult, please advise on the best way to set up these instances.
If there is no way to promote these dynamic flows, we cannot make all changes in DEV environment.
They have also said there is no way to promote a single object, which I do not believe can be the case. They think it must be in a process flow.
-
We recommend that you should set up your development environment exactly how you would like you production environment to appear: no duplicate items (database connections, file sources, users, etc..). Then clear your production instance (i.e. a fresh install) and migrate your entire development environment to the fresh production environment.
With regards to your dynamic process flows, they can be migrated as well as long as all the objects from your development environment are migrated to your production environment. They're may be some configuration necessary, but this should already exist in your development environment.
With regards to promoting a single object, this feature is now included in the latest migration utility. The details can be found here: http://support.adeptia.com/entries/21338682-migrating-select-objects-using-the-migration-utility.
Moving forward, we recommend that all changes and testing be done within the development environment. When testing has been completed and the changes are approved, then you can migrate the object or process to the production environment. By following this method, you'll be able to avoid inconsistencies between environments as well as migration issues.
0
Please sign in to leave a comment.
Comments
1 comment