You can migrate your vRealize Orchestrator 7.6 SaaS instance to the cloud extensibility proxy so you can use the new Automation Orchestrator 8.x functionality.

Automation Assembler now supports the integration of Automation Orchestrator 8.x instances through the cloud extensibility proxy. While you can continue using your existing vRealize Orchestrator 7.6 SaaS integration as it is, you cannot update its configuration. To overcome this limitation, you can migrate the vRealize Orchestrator 7.6 SaaS configuration to the cloud extensibility proxy.

The migration transfers the vRealize Orchestrator 7.6 SaaS configuration to your current Automation Orchestrator 8.x instance, overwriting all existing elements such as workflows, actions, configuration and resource elements, including secure strings in workflows and configuration elements, packages, tasks, policies, certificates and trusted certificates, plug-ins, custom records in the the js-io-rights.conf file, and Control Center system properties.

Note: Following the migration, all currently running entities on the vRealize Orchestrator 7.6 SaaS instance, such as workflow runs, policy runs, scheduled tasks, and workflows waiting for user interaction, are in a failed state in the Automation Orchestrator 8.x instance.

Prerequisites

Download and deploy a cloud extensibility proxy. See Download and deploy a cloud extensibility proxy.

Procedure

  1. Log in to the command line of your cloud extensibility proxy over SSH as root.
  2. To start the migration, run the vro-migrate command.
  3. Follow the command prompts to provide the fully qualified domain name (FQDN) and credentials of the vRealize Orchestrator 7.6 SaaS instance.
  4. (Optional) To follow the migration progress, access the migration log:
    1. Log in to the command line of your cloud extensibility proxy over a separate SSH session as root.
    2. Run the tail -f /var/log/vmware/prelude/vro-migration.log command.

Results

The migration process begins. You receive a notification on the cloud extensibility proxy when the migration finishes.