7.4
Table Of Contents
- Managing vRealize Automation
- Contents
- Managing vRealize Automation
- Maintaining and Customizing vRealize Automation Components and Options
- Broadcast a Message on the Message Board Portlet
- Starting Up and Shutting Down vRealize Automation
- Updating vRealize Automation Certificates
- Extracting Certificates and Private Keys
- Replace Certificates in the vRealize Automation Appliance
- Replace the Infrastructure as a Service Certificate
- Replace the IaaS Manager Service Certificate
- Update Embedded vRealize Orchestrator to Trust vRealize Automation Certificates
- Update External vRealize Orchestrator to Trust vRealize Automation Certificates
- Updating the vRealize Automation Appliance Management Site Certificate
- Replace a Management Agent Certificate
- Change the Polling Method for Certificates
- Managing the vRealize Automation Postgres Appliance Database
- Backup and Recovery for vRealize Automation Installations
- The Customer Experience Improvement Program
- Adjusting System Settings
- Monitoring vRealize Automation
- Monitoring vRealize Automation Health
- Monitoring and Managing Resources
- Monitoring Containers
- Bulk Import, Update, or Migrate Virtual Machines
7 Restart Manager Service nodes and wait for startup to finish.
If running automatic Manager Service failover, and you want to keep the active and passive nodes the
same, restart in the following order:
a Stop the passive Manager Service nodes without restarting them.
b Completely restart the active Manager Service node.
c Start the passive Manager Service nodes.
8 Restart the Distributed Execution Manager Orchestrator and Workers and all vRealize Automation
agents, and wait for startup to finish for all components.
You can restart these components in any order.
9 Verify that the service you restarted is registered.
a Open a Web browser to the vRealize Automation appliance management interface URL.
b Click the Services tab.
c Click the Refresh tab to monitor the progress of service startup.
When all services are listed as registered, the system is ready to use.
Shut Down vRealize Automation
To preserve data integrity, you must shut down vRealize Automation in a specified order.
If you are using vCenter Server to manage your virtual machines, use the guest shutdown command to
shut down vRealize Automation.
Procedure
1 Shut down the Distributed Execution Manager Orchestrator and Workers and all vRealize Automation
agents in any order and wait for all components to finish shutting down.
2 Shut down virtual machines that are running the Manager Service and wait for the shutdown to finish.
3 (Optional) For distributed deployments, shut down all secondary Web nodes and wait for the
shutdown to finish.
4 Shut down the primary Web node, and wait for the shutdown to finish.
5 (Optional) For distributed deployments, shut down all secondary vRealize Automation appliance
instances and wait for the shutdown to finish.
6 Shut down the primary vRealize Automation appliance and wait for the shutdown to finish.
If applicable, the primary vRealize Automation appliance is the one that contains the master, or
writeable, appliance database. Make a note of the name of the primary vRealize Automation
appliance. You use this information when you restart vRealize Automation.
7 Shut down the MSSQL virtual machines in any order and wait for the shutdown to finish.
8 If you are using a legacy standalone PostgreSQL database, also shut down that machine.
Managing vRealize Automation
VMware, Inc. 11