How to migrate artifacts from an old DE version to the New DE Server

book

Article ID: 142851

calendar_today

Updated On:

Products

CA Workload Automation DE DSERIES- SERVER CA Workload Automation DE - Scheduler (dSeries)

Issue/Introduction

We are currently running Workload Automation DE on Windows 2008 R2.

We plan to install the latest DE version on Windows 2016.

How can we proceed to get all the DE artifacts from the old DE version and recreate them properly on the new DE version.

We would like to keep the old DE Server in the current state while we will install and test the new version.

 

Environment

Release : 12.0

Component : CA WORKLOAD AUTOMATION DE (DSERIES)

Resolution

The recommended solution is to download and install the latest DE version on the new server first.

You can consult the DE compatibility matrix under the following link for detailed information:

https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/intelligent-automation/ca-workload-automation-de/12-0-02/release-notes/support-matrix.html

 

Once DE new version is installed successfully on the new Server, you can use the “Migration Method” to migrate “Artifacts”, “Global Variables” and “History Data” to the new server.

The “Migration Method” preserves the old Server while letting you use the new Server to run your previously defined workload.

 

The following scenario walks you through the process of upgrading the server using the migration method:

 

 

When you run the migration utility, you can choose to migrate artifacts, global variables, or history data, or any combination of them. For example, you can migrate artifacts and history data, but not global variables. You can also skip the migration of application versions during artifacts migration by configuring the migration.default.conf file.

 

The following illustration shows how artifacts, global variables, and history data are migrated:

When artifacts are migrated, the migration utility reads them from the source server, converts them to the new format, and stores them in files on the new server.

When you start the new server after migration, the stored artifacts are imported into the new server database.

 

You can consult the following DE documentation page for more information about the "Migration Method":

https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/intelligent-automation/ca-workload-automation-de/12-2/upgrade-the-server-using-migration-method0.html

 

 

Attachments