7.3

2 Wait for DNS replication and zone distribution to occur.
3 Log in as root to the replica node vRealize Automation appliance management interface.
https://vrealize-automation-appliance-FQDN:5480
4 Click the Network tab.
5 Below the tabs, click Address.
6 In the Hostname text box, enter the new name in FQDN format.
7 At the upper right, click Save Settings.
8 Log in as root to a console session on the replica vRealize Automation appliance, and run the
following script.
/usr/lib/vcac/tools/change-hostname/change-hostname.sh old-replica-FQDN new-
replica-FQDN
9 Log in as root to a console session on all other vRealize Automation appliances in the cluster,
including the master node and other replicas, and run the following command.
sed -i "s/old-replica-FQDN/new-replica-FQDN/g" "/etc/haproxy/conf.d/10-psql.cfg"
"/etc/haproxy/conf.d/20-vcac.cfg"
10 Log in as root to the master vRealize Automation appliance management interface.
https://vrealize-automation-appliance-FQDN:5480
11 Click the vRA Settings tab.
12 Below the tabs, click Messaging.
13 To reconfigure the messaging services with the new name on all nodes, click Reset RabbitMQ
Cluster.
14 Restart the master vRealize Automation appliance.
15 Restart all replica vRealize Automation appliances, one at a time.
16 If the old replica vRealize Automation appliance host name was used in a certificate, update the
certificate with the new name.
For information about updating certificates, see Managing vRealize Automation.
17 If the old replica vRealize Automation appliance host name was used with a load balancer in an HA
environment, check and reconfigure the load balancer with the new name.
18 Verify that all authentication connectors are working correctly.
19 In DNS, remove the existing DNS record with the old replica host name.
Adjusting the SQL Database for a Changed Host Name
You must revise configuration settings if you move the vRealize Automation IaaS SQL database to a
different host name.
Installing vRealize Automation
VMware, Inc. 136