This documentation supports the 21.3 version of Action Request System.

To view an earlier version, select the version from the Product version menu.

Using Migrator to automate migration of data and objects between AR System servers

Migrator  can migrate  Action Request System  objects and data in many ways:

  • To and from the same server
  • From one server to another
  • To many servers
  • From a server to a file
  • From a file to a server
  • From a file to a file
  • From a form to another form
  • From a form to a file

If you have two or more servers in your AR System  environment, you might need to transfer or synchronize definitions or data between servers. 

By using Migrator , you can migrate objects and data to and from servers quickly while still having all clients connected and running. Migrator checks for the integrity of objects, such as groups, active links, forms, and so on. It migrates only those objects that have changed after the initial migration. 

Migrator  automates the process of transferring objects and data from one source (server or file) to another. For example, you can develop workflow applications on a development server (source) and use Migrator  to transfer the applications to a production server (destination), ensuring the integrity of all migrated changes. For more information about using Migrator , see Migrating applications and data between AR System servers.

Was this page helpful? Yes No Submitting... Thank you

Comments