Export the configuration from your existing external Orchestrator cluster and import it to the Orchestrator server that is built in to the vRealize Automation primary appliance. Migrate the Orchestrator database from the external Microsoft SQL server to the PostgreSQL server on the appliance.

Procedure

  1. Export the configuration from the external Orchestrator cluster.
    1. Open an SSH connection to the primary vRealize Orchestrator virtual appliance vra01vro01a.rainpole.local.
    2. Log in using the following credentials.

      Setting

      Value

      User name

      root

      Password

      vro_appA_root_password

    3. Run the following command to export the vRealize Orchestrator configuration as a /tmp/vro-config.zip file.
      /usr/lib/vco/tools/configuration-cli/bin/vro-configure.sh export --skipLicense --path /tmp/vro-config.zip
  2. Migrate the exported configuration to the embedded Orchestrator instance on the primary vRealize Automation appliance.
    1. Open an SSH connection to the primary vRealize Orchestrator virtual appliance vra01svr01a.rainpole.local.
    2. Log in using the following credentials.

      Setting

      Value

      User name

      root

      Password

      vra_appA_root_password

    3. Stop the Orchestrator server and the Control Center services of the built-in vRealize Orchestrator server.
      service vco-server stop && service vco-configurator stop
    4. By using scp copy the exported vRealize Orchestrator configuration ZIP file to vRealize Automation.
      scp root@vra01vro01a.rainpole.local:/tmp/vro-config.zip /tmp/vro-config.zip
    5. When prompted, accept the SSL certificate from the vRealize Orchestrator appliance by typing yes.
    6. Change the ownership of the exported Orchestrator configuration file.
      chown vco:vco /tmp/vro-config.zip
    7. Import the Orchestrator configuration file to the built-in vRealize Orchestrator server using vro-configure .
      /usr/lib/vco/tools/configuration-cli/bin/vro-configure.sh import --skipDatabaseSettings --skipLicense --skipSettings --skipSslCertificate --skipTrustStore --notForceImportPlugins --notRemoveMissingPlugins --path /tmp/vro-config.zip
    8. Set the Control Center service of the built-in vRealize Orchestrator server on vRealize Automation appliance vra01svr01a.rainpole.local to automatically start on restart of the appliance.
      chkconfig vco-configurator on
  3. Migrate the external vRealize Orchestrator database to the PostgreSQL server running on the vRealize Automation appliance.
    1. Run the following command to migrate the external vRealize Orchestrator database vROCluster from the vra01mssql01.rainpole.local Microsoft SQL node using the svc-vro service account for the PostgreSQL database.
      /usr/lib/vco/tools/configuration-cli/bin/vro-configure.sh db-migrate --sourceJdbcUrl jdbc:jtds:sqlserver://vra01mssql01:1433/VROCluster\;domain=rainpole.local --sourceDbUsername svc-vro --sourceDbPassword svc-vro_password
    2. Clean up irrelevant data from the imported vRealize Orchestrator database.
      sudo -u postgres -i -- /opt/vmware/vpostgres/current/bin/psql vcac -c "DELETE FROM vmo_clustermember;"
  4. Start the Orchestrator server and the Control Center services of the built-in vRealize Orchestrator server on the vRealize Automation appliance, and verify their status.
    service vco-configurator start && service vco-server start
    service vco-configurator status && service vco-server status