Object Migration
- Nitin Beri (Unlicensed)
- Akash Kumar Jaiswal (Unlicensed)
Owned by Nitin Beri (Unlicensed)
Last updated: Apr 08, 2019 by Akash Kumar Jaiswal (Unlicensed)Version comment
2 min read
Loading data...
Deployment and Migration Capabilities
User requires admin access to server where Adeptia Connect components are installed for performing the following functions.
Export: Allows you to export objects from a source environment to a zip file.
Promote: Allows you to select objects from the exported zip file, compare them with the target system, and generate another zip file for the changes you want to update to the target system.
Deploy: Allows you to apply the changes to the target system using an exported zip file.
Interactive Migration: Interactive Migration utility UI to perform export, promote, and deploy functions.
Non-Interactive Migration: Non-Interactive Migration utility to perform export and deploy functions.
Key Points for Migration
- Identify key stakeholders and their roles and responsibilities involved in migration/promotion tasks. Typical roles are Developers, QA, Production Support.
- Most organizations have their own release management process and are adopting DevOps style processes. Adeptia recommends to include object/migration and promotion utility (Migration Utility) within their release management process as applicable. For example, using interactive and non-interactive modes of Migration utility as appropriate.
- Migration utility can be effectively used in non-interactive mode with scripts to automate exporting and importing objects in different environments. However, on Linux Operating System, Adeptia supports onlyl non-interactive migration/promotion.
- Before upgrading it is recommended to take a backup of objects from production environments for roll-back or recovery. It is important to maintain a separate repository for backup and latest copy of export zip file, preferably in a version controlled repository like TFS or GIT.
- Ensure while promoting or migration objects the # users allowed as per the licenses are adequate. For example Development/QA environment may have different # of users allowed than Prod environment which can give rise to issues while executing transactions in production.
| Interactive Migration |  |
|---|---|
| Non-Interactive Migration |  |
Help Links