You can export the configuration from your existing external Orchestrator instance and import it to the Orchestrator server that is embedded into vRealize Automation.

About this task

Note:

If you have 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 you have a cluster of external Orchestrator server nodes, select one of them to be used during migration. Stop all other Orchestrator server nodes and keep them stopped until the migration is completed.

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

Procedure

  1. Export the configuration from the external Orchestrator server.
    1. Log in to Control Center as root or as an administrator, depending on the source version.
    2. Stop the Orchestrator server service from the Startup Options page to prevent unwanted changes to the database.
    3. Go to the Export/Import Configuration page.
    4. On the Export Configuration page, select Export server configuration, Bundle plug-ins and Export plug-in configurations.
    5. (Optional) Enter a password to protect the configuration file.

      Use the same password when you import the configuration later.

    6. Click Export.
  2. Migrate the exported configuration into the embedded Orchestrator instance.
    1. Log in to each vRealize Automation Appliance over SSH as root.
    2. Stop the Orchestrator server service and the Control Center service of the embedded vRealize Orchestrator server.
      service vco-server stop && service vco-configurator stop
    3. On your primary vRealize Automation node, run the following commands to back up important configuration files, which need to be restored later.
      cp -p /etc/vco/app-server/catalina.properties /etc/vco/app-server/catalina.properties-backup
      cp -p /etc/vco/app-server/web.xml /etc/vco/app-server/web.xml-backup
      cp -p /etc/vco/app-server/server.xml /etc/vco/app-server/server.xml-backup
      cp -p /etc/vco/configuration/catalina.properties /etc/vco/configuration/catalina.properties-backup
      cp -p /etc/vco/configuration/web.xml /etc/vco/configuration/web.xml-backup
      cp -p /etc/vco/configuration/server.xml /etc/vco/configuration/server.xml-backup
      cp -p /usr/lib/vco/app-server/bin/setenv.sh /usr/lib/vco/app-server/bin/setenv.sh-backup
      cp -p /usr/lib/vco/configuration/bin/setenv.sh /usr/lib/vco/configuration/bin/setenv.sh-backup
  3. Import the configuration to the embedded Orchestrator instance of your primary vRealize Automation node.
    1. Log in to the vRealize Automation Appliance over SSH as root.
    2. Upload the exported Orchestrator configuration file to the /usr/lib/vco/tools/configuration-cli/bin directory of the vRealize Automation Appliance.
    3. Navigate to the /usr/lib/vco/tools/configuration-cli/bin directory.
    4. Change the ownership of the exported Orchestrator configuration file.
      chown vco:vco orchestrator-config-export-orchestrator_appliance_ip-date_hour.zip
    5. 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_hostname-date_hour.zip --password
      Note:

      Press Enter if the Orchestrator configuration export file is not password protected.

  4. Restore the original Orchestrator configuration files.
    1. Log in to your primary vRealize Automation Appliance node over SSH as root.
    2. Run the following commands to restore the Orchestrator configuration files.
      mv /etc/vco/app-server/catalina.properties-backup /etc/vco/app-server/catalina.properties
      mv /etc/vco/app-server/web.xml-backup /etc/vco/app-server/web.xml
      mv /etc/vco/app-server/server.xml-backup /etc/vco/app-server/server.xml
      mv /etc/vco/configuration/catalina.properties-backup /etc/vco/configuration/catalina.properties
      mv /etc/vco/configuration/web.xml-backup /etc/vco/configuration/web.xml
      mv /etc/vco/configuration/server.xml-backup /etc/vco/configuration/server.xml
      mv /usr/lib/vco/app-server/bin/setenv.sh-backup /usr/lib/vco/app-server/bin/setenv.sh
      mv /usr/lib/vco/configuration/bin/setenv.sh-backup /usr/lib/vco/configuration/bin/setenv.sh
  5. If the external Orchestrator server from which you want to migrate uses the built-in PostgreSQL database, edit its database configuration files.
    1. In the /var/vmware/vpostgres/current/pgdata/postgresql.conf file, uncomment the listen_addresses line.
    2. Set the values of listen_addresses to a wildcard (*).
      listen_addresses ='*'
    3. Append a line to the /var/vmware/vpostgres/current/pgdata/pg_hba.conf file.
      host all all vra-va-ip-address/32 md5	
      Note:

      The pg_hba.conf file requires using a CIDR prefix format instead on an IP address and a subnet mask.

    4. Restart the PostgreSQL server service.
      service vpostgres restart
  6. Migrate the external Orchestrator database to the embedded one in vRealize Automation.
    1. Log in to the vRealize Automation Appliance over SSH as root.
    2. Navigate to the /usr/lib/vco/tools/configuration-cli/bin directory.
    3. Run the following command to migrate the database:
      ./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

  7. 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';"
  8. Delete the external Orchestrator cluster nodes from the imported Orchestrator database.
    sudo -u postgres -i -- /opt/vmware/vpostgres/current/bin/psql vcac -c "DELETE FROM vmo_clustermember;"
  9. Start the embedded Orchestrator server services.
    1. Log in to each vRealize Automation Appliance over SSH as root.
    2. Start the Orchestrator server service.
      service vco-server start
  10. Verify that Orchestrator is configured properly at the Validate Configuration page in Control Center.

Results

You successfully migrated an external Orchestrator server instance to a vRealize Orchestrator instance embedded in vRealize Automation.

What to do next

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