In this article, we'll tell you how to get started with Design Mover. You'll also get some examples of the benefits of working with automatic release management of your features and processes in Easit GO.
Preparatory analysis
Before you start using Mover 1:1 or Design Hub, you need to do a thorough analysis and cleanup of your production environment. This step is crucial for a smooth transfer of configuration between environments.
Start by checking if your production database contains multiple objects with identical system names. You can use the Mover 1:1 tool to identify and resolve any conflicts before continuing.
Next, it's time to create a snapshot of your production environment. The snapshot file will serve as an exact copy of your production environment, with the exception of some system-specific parameters.
An important prerequisite is that you have at least one test environment where all configuration and testing is performed, and a production environment where only minimal manual configuration is required. When you add Mover to GO, a development environment is included at no cost.
Workflow
When both the source and target systems have an identical configuration, you can start using the following workflow:
Configure changes and new processes in the test environment
All configuration of the system should be done in the test environment. If you make manual changes in production, they will be overwritten when you import configuration from test. This should only be done in exceptional cases.
Copy configuration from test to production:
Once new configurations are ready and verified in the test environment, they can be imported into the production environment.
Exporting Snapshots
To create a snapshot, go to Control Panel > Mover 1:1 > Export Design tab and click the “Generate Snapshot” button. This may take a few minutes depending on the amount of configuration in the system.
Importing Snapshots
Before you can perform a raw import, you need to prepare the environment. Enable maintenance mode to prevent users from logging in or starting background jobs during the import process.
To test the import, you can use the “Test run snapshot” button. The result of the test run is displayed in a tree structure. If the test run is successful, you can start the raw import by clicking the “Import snapshot” button.
Sharp Import
The final step is to do a hard import to the production environment. Before you do this, make sure you have a good idea of the time it will take to complete the import so you can choose a suitable time of day. This step is done automatically so you can easily do it outside of office hours or even at night.
Summary
Effective environment management with Mover 1:1 in Easit GO is an important component in ensuring that your system runs smoothly and that the configuration is transferred correctly between different environments.
By following careful procedures and using the right tools, you can reduce the risk of problems and improve your system administration.
In addition to higher quality, you will need less time for configuration and testing, thus freeing up time to do new fun things in GO.
Get in touch and we'll tell you more. We're here to help you!