After you upgrade your vRealize Automation from version 6.x to version 7.3, you can migrate your existing external Orchestrator 6.x installed on Windows to the Orchestrator server that is built into vRealize Automation 7.3.

About this task

Note:

If you have a distributed vRealize Automation environment with multiple vRealize Automation Appliance nodes, perform the migration procedure only on the primary vRealize Automation node.

Prerequisites

  • Upgrade or migrate your vRealize Automation to version 7.3. For more information, see Upgrading vRealize Automation in Installing or Upgrading vRealize Automation.

  • If the source Orchestrator uses a SHA1 package-signing certificate, make sure to regenerate the certificate using a stronger signing algorithm.

  • Stop the Orchestrator server service of the external Orchestrator.

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

Procedure

  1. Download the migration tool from the target Orchestrator server.
    1. Log in to the vRealize Automation Appliance over SSH as root.
    2. Download the migration-tool.zip archive that is located in the /var/lib/vco/downloads directory.
  2. Export the Orchestrator configuration from the source Orchestrator server.
    1. Set the PATH environment variable by pointing it to the bin folder of the Java JRE installed with Orchestrator.
    2. Upload the migration tool to the Windows server, on which the external Orchestrator is installed.
    3. Extract the downloaded archive in the Orchestrator install folder.

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

    4. Run the Windows command prompt as administrator and navigate to the bin folder in the Orchestrator install folder.

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

    5. 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. Migrate the exported configuration to the Orchestrator server that is built into vRealize Automation 7.3.
    1. On the vRealize Automation Appliance, stop the Orchestrator server service and the Control Center service of the built-in vRealize Orchestrator server.
      service vco-server stop && service vco-configurator stop
    2. Back up the catalina.properties, server.xml, and web.xml files in the /etc/vco/app-server and /etc/vco/configuration directories.

      For example:

      cp catalina.properties catalina.properties-$(date +%Y-%m-%d_%H-%M-%S)
    3. Back up the setenv.sh file in the /usr/lib/vco/app-server/bin and /usr/lib/vco/configuration/bin directories.
      cp setenv.sh setenv.sh-$(date +%Y-%m-%d_%H-%M-%S)
    4. Upload the exported configuration file to the /usr/lib/vco/tools/configuration-cli/bin directory on the vRealize Automation Appliance.
    5. Change the ownership of the exported Orchestrator configuration file.
      chown vco:vco orchestrator-config-export-orchestrator_ip_address-date_hour.zip
    6. Import the Orchestrator configuration file to the built-in vRealize Orchestrator server, by running the vro-configure script with the import command.
      ./vro-configure.sh import --skipDatabaseSettings --skipLicense --skipSettings --skipSslCertificate --notForceImportPlugins --notRemoveMissingPlugins --skipTrustStore --path orchestrator-config-export-orchestrator_appliance_ip-date_hour.zip
  4. Migrate the database to the internal PostgreSQL database, by running the vro-configure script with the db-migrate command.
    ./vro-configure.sh db-migrate --sourceJdbcUrl JDBC_connection_URL --sourceDbUsername database_user --sourceDbPassword database_user_password
    Note:

    Enclose passwords that contain special characters in single quotation marks.

    The JDBC_connection_URL depends on the type of database that you use.

    PostgreSQL: jdbc:postgresql://host:port/database_name
    MSSQL: jdbc:jtds:sqlserver://host:port/database_name\; if using SQL authentication and MSSQL: jdbc:jtds:sqlserver://host:port/database_name\;domain=domain\;useNTLMv2=TRUE if using Windows authentication.
    Oracle: jdbc:oracle:thin:@host:port:database_name 

    The default database login information is:

    database_name

    vmware

    database_user

    vmware

    database_user_password

    vmware

  5. If you migrated vRealize Automation instead of upgrading it, delete the trusted Single Sign-On certificates from the database of the embedded Orchestrator instance.
    sudo -u postgres -i -- /opt/vmware/vpostgres/current/bin/psql vcac -c "DELETE FROM vmo_keystore WHERE id='cakeystore-id';"
  6. Replace the catalina.properties, server.xml, and web.xml files from the imported configuration with the backup copy you created in Step 3b.

    For example:

    mv catalina.properties-date_hour catalina.properties
    1. Change the ownership of the files to the vco user.

      For example:

      chown vco:vco catalina.properties
  7. Replace the setenv.sh file from the imported configuration with the backup copy you created in Step 3c.

    For example:

    mv setenv.sh-date_hour setenv.sh
    1. Change the ownership of the files to the vco user.

      For example:

      chown vco:vco setenv.sh

Results

You successfully migrated an external vRealize Orchestrator 6.x installed on Windows to a vRealize Orchestrator instance embedded in vRealize Automation 7.3.

What to do next

Set up the built-in vRealize Orchestrator server. See Configure the Built-In vRealize Orchestrator Server.