7.4
Table Of Contents
- Migrating vRealize Automation to 7.4
- Contents
- Migrating vRealize Automation
- vRealize Automation Environment User Interfaces
- Migration Prerequisites
- Pre-Migration Tasks
- Review Changes Introduced by Migration from vRealize Automation 6.2.x to 7.x
- Apply Software Agent Patch
- Change DoDeletes Setting on the vSphere Agent to False
- Check Templates in Your vRealize Automation 6.x Source Environment
- Prepare vRealize Automation Virtual Machines for Migration
- Gather Information Required for Migration
- Obtain the Encryption Key
- List Tenant and IaaS Administrators
- Add Each Tenant from the Source Environment
- Create an Administrator for Each Added Tenant
- Synchronize Users and Groups Before Migration to a Minimal Environment
- Synchronize Users and Groups Before Migration to a High-Availability Environment
- Run Data Collection in Source
- Manually Clone the Source Microsoft SQL Database
- Snapshot the Target Environment
- Migration Procedures
- Post-Migration Tasks
- Add Tenant and IaaS Administrators
- Run Test Connection and Verify Migrated Endpoints
- Run Data Collection on Target
- Reconfigure Load Balancers After Migration
- Migrate an External Orchestrator Server
- Reconfigure the vRealize Automation Endpoint
- Reconfigure the vRealize Automation Infrastructure Endpoint
- Install vRealize Orchestrator Customization
- Reconfigure Embedded vRealize Orchestrator Endpoint
- Reconfigure the Azure Endpoint
- Migrate Automation Application Services
- Delete Original Target vRealize Automation IaaS Microsoft SQL Database
- Update Data Center Location Menu Contents After Migration
- Upgrading Software Agents to TLS 1.2
- Validate the Target vRealize Automation 7.4 Environment
- Troubleshooting Migration
- PostgreSQL Version Causes Error
- Some Virtual Machines Do Not Have a Deployment Created during Migration
- Migration Log Locations
- Catalog Items Appear in the Service Catalog After Migration But Are Not Available to Request
- Data Collection Radio buttons Disabled in vRealize Automation
- Troubleshooting the Software Agent Upgrade
Install vRealize Orchestrator Customization
You can run a workflow to install the customized state change workflow stubs and vRealize Orchestrator
menu operation workflows.
For information, see Install vRealize Orchestrator Customization in Life Cycle Extensibility.
Prerequisites
Successful migration to the latest version of vRealize Automation.
Reconfigure Embedded vRealize Orchestrator
Infrastructure Endpoint in the Target vRealize Automation
When you migrate from a vRealize Automation 6.2.x environment, you must update the URL of the
infrastructure endpoint that points to the target embedded vRealize Orchestrator server.
Prerequisites
n
Successfully migrate to vRealize Automation 7.4.
n
Log in to the target vRealize Automation console.
a Open the vRealize Automation console using the fully qualified domain name of the target virtual
appliance: https://vra-va-hostname.domain.name/vcac.
For a high-availability environment, open the console using the fully qualified domain name of the
target virtual appliance load balancer: https://vra-va-lb-hostname.domain.name/vcac.
b Log in as a IaaS administrator user.
Procedure
1 Select Infrastructure > Endpoints > Endpoints.
2 On the Endpoints page, select the vRealize Orchestrator endpoint, and click Edit.
3 In the Address text box, edit the vRealize Orchestrator endpoint URL.
n
If you migrated to a minimal environment, replace the vRealize Orchestrator endpoint URL with
https://vra-va-hostname.domain.name:443/vco.
n
If you migrated to a high-availability environment, replace the vRealize Orchestrator endpoint
URL with https://vra-va-lb-hostname.domain.name:443/vco.
4 Click OK.
5 Manually run a data collection on the vRealize Orchestrator endpoint.
a On the Endpoints page, select the vRealize Orchestrator endpoint.
b SelectActions > Data Collection.
Verify that the data collection is successful.
Migrating vRealize Automation to 7.4
VMware, Inc. 42