Migrate your 5.5.x and 6.x Orchestrator Windows standalone configuration to the Orchestrator Appliance.

Prerequisites

  • Stop the source and target Orchestrator servers.

  • Back up the database of the source Orchestrator server, including the database schema.

Procedure

  1. Download the migration tool from the target Orchestrator server.
    1. Log in to Control Center as root.
    2. Open the Export/Import Configuration page and click the Migrate Configuration tab.
    3. Download the migration tool as specified in the description on the page, or download it directly from https://orchestrator_server_IP_or_DNS_name:8283/vco-controlcenter/api/server/migration-tool.
  2. Export the Orchestrator configuration from the source Orchestrator server.
    1. Unzip the downloaded archive and place the folder in the Orchestrator install folder.

      The default path to the Orchestrator install folder in a Windows-based installation is C:\Program Files\VMware\Orchestrator.

    2. Set the PATH environment variable by pointing it to the bin folder of the Java JRE installed with Orchestrator.
    3. Use the Windows command prompt to navigate to the bin folder under the Orchestrator install folder.

      By default, the path to the bin folder is C:\Program Files\VMware\Orchestrator\migration-cli\bin.

    4. Run the export command from the command line.
      C:\Program Files\VMware\Orchestrator\migration-cli\bin\vro-migrate.bat export

      This command combines the VMware vRealize Orchestrator configuration files and plug-ins into an export archive.

      The archive is created in the same folder as the migration-cli folder.

  3. Import the configuration to the target Orchestrator server.
    1. Open Export/Import Configuration in Control Center and click the Migrate Configuration tab.
    2. Click Import.
    3. Select the type of files that you want to import.
      Note:

      If the source and target Orchestrator servers are configured to use the same external database, leave the Migrate database settings check box unselected to avoid upgrading the database schema to the newer version. Otherwise the source Orchestrator environment stops working.

    4. Click Finish Migration.
  4. If the source vRealize Orchestrator uses vRealize Automation as an authentication provider, import the SSL certificate of the vRealize Automation server to the Orchestrator trust store and change the license provider on the target Orchestrator server.
    1. On the Certificates page in Control Center, click Import from URL.
    2. Provide the URL of the vRealize Automation server.
    3. Go to the Licensing page in Control Center.
    4. From the Select License Provider drop-down menu, select vRA License.
  5. If the source vRealize Orchestrator uses vSphere or SSO (Legacy) authentication mode, change the license provider to Manual License and provide the manual license key.

Results

A message indicates that the migration finished successfully.

What to do next

  • Verify that vRealize Orchestrator is configured properly by opening the Validate Configuration page in Control Center.

  • Restart the Orchestrator server from the Startup Options page in Control Center for the changes to take effect.