...
APIs and libraries can have requiremets requirements and these are listed in the bottom container. Even before the migration, we check whether the requisitions are available on the target!
...
If the requirement needs to be updated or is not displayed at all, you will also receive a large warning message.
The resources of the libraries are taken from the local repositories of the Gateway Manager instance. So keep the git repositories of the libraries up to date.
Pipeline
In "Pipeline" you can perform various actions before and after the migration, such as "Disable via Admintools" or "Call an URL via GET". Default values can be set in Environments.
...
After testing the migration, they get an overview of the results, the entire XML and the logs. You can also download the folders, mappings, the bundle and more.
In this case, you should evaluate why the resource could not be migrated according to the action and possibly select a different action. Also consult the logs. With "go Back to the Migration" you can return to the overview and make your adjustments. Contact our team if you have any questions! Don't forget to set your adjustment for this resource as the new default. This will save you time for the next migration!
...
Perform
There is no such thing as an only partially successful migration! If something fails in the migration, the entire migration is not carried out. Your gateway will not be in an undefined state.
...
With "Revert Migration" you can completely undo a migration that has been carried out.
| Info |
|---|
...
This Feature is intended as an immediate recovery. If the gateway's resources have changed in the meantime, unpredictable things can happen. |