Create and run data migration pipelines in Deployment Manager 4.8.x to automatically export simulation data from a production environment into a simulation environment in which you can test simulation data. You can also use Deployment Manager to monitor and obtain information about your simulations, for example, by running diagnostics to ensure that your environment configurations are correct and by and viewing reports that display key performance indicators (KPIs).

• Creating a pipeline

  Create a pipeline by defining the production and simulation environments and the application details for the pipeline. By using a data migration pipeline, you can export and import simulation data automatically.

• Modifying a pipeline

  You can change the URLs of your production and simulation environments. You can also change the application information for which you are creating the pipeline.

• Diagnosing a pipeline

  You can diagnose your pipeline to verify its configuration. For example, you can verify that the orchestration system can connect to the production and simulation environments.

• Scheduling a pipeline by creating a job scheduler rule

  You can schedule a data migration pipeline to run during a specified period of time by creating and running a job scheduler. The job scheduler runs a Deployment Manager activity (pzScheduleDataSyncPipeline) on the specified pipeline, based on your configuration, such as weekly or monthly.

• Starting a pipeline manually

  If you do not run a data migration pipeline based on a job scheduler, you can run it manually in Deployment Manager.

• Pausing a pipeline

  Pause a pipeline to stop processing the data migration. When you pause a data migration, the pipeline completes the current task and stops the data migration.

• Stopping a pipeline

  Stop a pipeline to stop data migrations from being exported and imported.

• Stopping and resuming a pipeline that has errors

  If a data migration has errors, the pipeline stops processing on it, and you can either resume or stop running the pipeline.

• Deleting a pipeline

  When you delete a pipeline, its associated application packages are not deleted from the pipeline repositories.

• Viewing data migration logs

  View the logs for a data migration to see the completion status of operations, for example, when a data migration moves to a new stage. You can change the logging level to control the events are displayed in the log. For example, you can change logging levels of your deployment from INFO to DEBUG for troubleshooting purposes. For more information, see Logging Level Settings tool.

• Viewing a report for a specific data migration

  You can view a report for a specific data migration to gain more visibility into data migrations on a pipeline.

• Viewing reports for all data migrations in a pipeline

  Reports provide a variety of information about all the data migrations in your pipeline so that you can gain more visibility into data migration processing. For example, you can view the average time taken to complete data migrations.