7.3

Table Of Contents
Procedure
u
To restore the original health check settings so replica nodes can accept incoming traffic, configure
the load balancers for these items.
n
vRealize Automation appliance.
n
IaaS Web Server that hosts the Model Manager.
n
Manager Service.
Migrating an External vRealize Orchestrator Server to
vRealize Automation 7.3
You can migrate your existing external vRealize Orchestrator server to a vRealize Orchestrator instance
embedded in vRealize Automation.
You can deploy vRealize Orchestrator as an external server instance and configure vRealize Automation
to work with that external instance, or you can configure and use the vRealize Orchestrator server that is
included in the vRealize Automation appliance.
VMware recommends that you migrate your external vRealize Orchestrator to the Orchestrator server that
is built into vRealize Automation. The migration from an external to embedded Orchestrator provides the
following benefits:
n
Reduces the total cost of ownership.
n
Simplifies the deployment model.
n
Improves the operational efficiency.
Note Consider using the external vRealize Orchestrator in the following cases:
n
Multiple tenants in the vRealize Automation environment
n
Geographically dispersed environment
n
Workload handling
n
Use of specific plug-ins, such as the Site Recovery Manager plug-in
Control Center Dierences Between External and Embedded
Orchestrator
Some of the menu items that are available in Control Center of an external vRealize Orchestrator are not
included in the default Control Center view of an embedded Orchestrator instance.
In Control Center of the embedded Orchestrator server, a few options are hidden by default.
Menu Item Details
Licensing The embedded Orchestrator is preconfigured to use vRealize Automation as a license provider.
Export/Import Configuration The embedded Orchestrator configuration is included in the exported vRealize Automation
components.
Migrating vRealize Automation to 7.3 or 7.3.1
VMware, Inc. 36