Rollback Configuration

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

If the results of the triage indicate that some configuration is incorrect, for example, someone has put wrong details or updated it with a typo, you can try to rollback to a previous working configuration. There is no easy way to revert to previous configurations in Journey Manager, so each configuration change may have its own rollback procedure. You must relay on your change logs to find the previous working configuration and then do it manually via Manager.

It is recommended to version any new configuration changes, for example, a new security manager v2, and keep the previous ones. Then you can make use of the new configuration by assigning it to your form space. It will allow you to roll back to the previous configuration quickly and reliably.

To give a practical example, let's assume you need to change your current Local Security Manager. Instead of changing its configuration directly, you create a new Local Security Manager version 2 and populate it with the configuration of the current one. Then you update some specific configuration according to your requirements and assign the new security manager with your space. If you discover later than the new configuration stopped working by some unknown reasons, you can easily roll back to the previous Local Security Manager version 1 by re-assigning it to your form space.

Even if you have managed to fix a problem by rolling back a configuration change, you should always ensure that you determine why it changed, and how to prevent it being changed again. In particular, application-level configuration changes may be overwritten when a new version of the application is deployed. This type of change needs to be updated in the application at the source-code level.

Note

In some cases, you may need to contact our Customer Care team to get help in restoring your Manager configuration.

You can also use the configuration rollback as a way to promote or migrate it from one to another Manager server, for example, in different environments.

Next, learn how to promote the Journey Manager to another environment.