You can export the configuration from your existing external Orchestrator instance and import it to the Orchestrator server that is built 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.

  • Stop the Orchestrator server service of the external Orchestrator.

  • 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 of the external Orchestrator server 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.
  2. Migrate the exported configuration into the embedded Orchestrator instance.
    1. Upload the exported Orchestrator configuration file to the /usr/lib/vco/tools/configuration-cli/bin directory of the vRealize Automation Appliance.
    2. Log in to the vRealize Automation Appliance over SSH as root.
    3. 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
    4. 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)
    5. 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)
    6. Navigate to the /usr/lib/vco/tools/configuration-cli/bin directory.
    7. Change the ownership of the exported Orchestrator configuration file.
      chown vco:vco orchestrator-config-export-orchestrator_appliance_ip-date_hour.zip
    8. 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
  3. 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
  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. Revert to the default configuration of the postgresql.conf and the pg_hba.conf file.
    1. Restart the PostgreSQL server service.
  7. Replace the catalina.properties, server.xml, and web.xml files from the imported configuration with the backup copy you created in Step 2d.

    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
  8. Replace the setenv.sh file from the imported configuration with the backup copy you created in Step 2e.

    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 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.