...
...
...
...
Here you will find an overview of all migrations. The overview is divided into assigned, prepared or already completed migrations. With "Comment/Description" you can freely leave your notes on this migration or leave instructions for the assigned person. Click on "Details" to access the migration and continue with it.
...
Start a Migration
In the migrations overview you can see all prepared, assigned and already performed migrations.
You can also start migrations from here.
...
| Info |
|---|
Migrations are stored in the database for a retention period of 30 days. After this the migration and all the data stored associated to it are permanently deleted. |
| Html macro |
|---|
<iframe width="744" height="418" src="https://www.youtube-nocookie.com/embed/vL_GwCsWZIQ?si=NLZ-8CuMcoFyxe7j" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen></iframe> |
Start a Migration
In the migrations overview you can see all prepared, assigned and already performed migrations.
You can also start migrations from here.
...
| Info |
|---|
| Migrations are stored in the database for a retention period of 30 days. After this the migration and all the data stored associated to it are permanently deleted. |
Migration Sources
Each migration is associated with a migration source, which can be a Layer7 gateway, an XML bundle uploaded to the Gateway Manager, or bundles stored in a git repository. It's important to note that bundle upload and repository-based migrations are currently only available for managed services.
...
Mappings include the resources you intend to migrate (selected either from a managed service or any resource in the resource explorer) along with all of their first-level dependencies. The action chosen by the Gateway Manager during migration preparation is determined by suggestions from the Layer7 gateway and the default settings you've configured for each resource type (e.g., NewOrExisting for all JDBC connections) in the configuration. You also have the option to set a preferred action as the default on a per-resource basis.
A green highlight on any mapping indicates a difference in the hash of the source object compared to the hash of the target object. This serves as an indication of whether an object has changed.
Conversely, objects NOT highlighted in green are considered identical between the source and target, and therefore do not require migration.
...