Multi-Environment Migration

   Journey Manager (JM) The transaction engine for the platform.  |    System Manager / DevOps  |  All versions This feature is related to all versions.

Journey Manager allows you to migrate or promote its assets from one environment to another. You must migrate them in the following order:

1. Services
2. Form spaces
3. Security managersSecurity managers are the Journey Manager's components that are responsible for User Authentication, User Authorization, User Self-Registration, and Session Management. Security mangers are designed to handle various sets of users requiring access to different form spaces and can be associated with one or more form spaces. Users can be external or internal, and they can require access to form spaces or a combination of form spaces and modules in different environments. You can find security managers under Security > Security Managers.
4. Users
5. Roles
6. Organizations
7. Forms
8. Groups

For example, to migrate a space and an organization with all its forms from one environment to another, you must import them in this order:

1. A form space
2. An organization
3. Forms

You should review the server and environment specific configurations of the component before the migration, because it might need to be updated in the target environment. This is especially true for the following components:

• Services that contain endpoint URLs.
• Spaces that contain the context path.