7.3

Table Of Contents
5 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
6 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';"
7 Revert to the default configuration of the postgresql.conf and the pg_hba.conf file.
a Restart the PostgreSQL server service.
You successfully migrated an external vRealize Orchestrator 6.x Virtual Appliance 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.
Migrating vRealize Automation to 7.3 or 7.3.1
VMware, Inc. 42