Configuring Deployment Manager for data migration pipelines
Use Deployment Manager 4.6.x or later in data migration pipelines so that you can automatically export simulation data from a production system and import it into a simulation system.
- Install or upgrade to Deployment Manager 4.6.x or
later.
For first-time installations or upgrades from Deployment Manager 3.2.1 on the candidate systems (production and simulation environments) and the orchestration server.
Upgrading is done automatically, and you do not need to do post-upgrade steps.
For more information, see Using Deployment Manager for model-driven DevOps
If you are upgrading from a Deployment Manager release earlier than 3.2.1, do post-upgrade steps.
You do not need to do post-upgrade steps if you are upgrading from version 3.2.1 or later.
For more information, see Using Deployment Manager for model-driven DevOps
- For first-time installations, configure communication between the orchestration
server and the candidate systems.
- Enable default operators on each system. For more information, see Using Deployment Manager for model-driven DevOps
- Configure the authentication profiles, which enable communication between systems, on each system. Configuring communication consists of enabling the default operators in each system and configuring the authentication profiles, which enables communication between systems, on each system. Deployment Manager provides default authentication profiles, or you can create your own.
- Optional: To move orchestration server to a different environment, migrate your pipelines
to the new orchestration server, and then configure, on the new orchestration
server, the URL of the new orchestration server. This URL is used to update the
task status on the orchestration server and for diagnostics checks.
For more information, see Using Deployment Manager for model-driven DevOps
Previous topic Data migration pipeline overview Next topic Configuring the system for running simulations of decision strategies