7.1
Table Of Contents
- Upgrading from vRealize Automation 6.2 to 7.1
- Contents
- Upgrading to vRealize Automation 7.1
- Updated Information
- Upgrading vRealize Automation
- Checklist for Upgrading vRealize Automation Components
- Considerations About Upgrading to This vRealize Automation Version
- Upgrade and Identity Appliance Specifications
- Upgrade and Licensing
- Understanding How Roles Are Upgraded
- Understanding How Blueprints Are Upgraded
- Upgrade and vApp Blueprints, vCloud Endpoints, and vCloud Reservations
- Understanding How Multi-Machine Blueprints Are Upgraded
- Upgrade and Physical Endpoints, Reservations, and Blueprints
- Upgrade and Network Profile Settings
- Upgrade and Entitled Actions
- Upgrade and Custom Properties
- Upgrade and Application Services
- Upgrade and Advanced Service Design
- Upgrade and Blueprint Cost Information
- Prerequisites for Upgrading vRealize Automation
- Preparing to Upgrade vRealize Automation
- Updating the vRealize Automation Appliance
- Upgrading the IaaS Server Components
- Upgrade Stand-Alone External vRealize Orchestrator for Use With vRealize Automation
- Upgrade External vRealize Orchestrator Appliance Clusters
- Add Users or Groups to an Active Directory Connection
- Enable Your Load Balancers
- Post-Upgrade Tasks for vRealize Automation
- Troubleshooting the Upgrade
- Migration of Identity Store Fails Because the Active Directory is...
- Migration of Identity Store Fails Because of Incorrect Credentials
- Migration of Identity Store Fails With a Timeout Error Message...
- Installation or Upgrade Fails with a Load Balancer Timeout Error...
- Upgrade Fails for Website Component During IaaS Upgrade
- Incorrect Tab Names Appear Intermittently
- Manager Service Fails to Run Due to SSL Validation Errors...
- Log In Fails After Upgrade
- Catalog Items Appear in the Service Catalog But Are Not...
- User Migration Batch Files Are Ineffective
- PostgreSQL External Database Merge is Unsuccessful
- Join Cluster Command Appears to Fail After Upgrading a High Availability Environment
- Increase Free Space on the Root Partition
- Manual PostgreSQL Database Merge
- Upgrade Fails to Upgrade the Management Agent or Certificate Not Installed on a IaaS Node
- Bad PostgreSQL Service State Stops Upgrade and Displays Error Message
- Backup Copies of .xml Files Cause the System to Time Out
- Index
Reconfigure External Workflow Timeouts
You must recongure the vRealize Automation external workow timeouts because the upgrade process
overwrites xmldb les.
Procedure
1 Open the external workow conguration (xmldb) les on your system from the following directory.
\VMware\vCAC\Server\ExternalWorkflows\xmldb\.
2 Recongure the external workow timeout seings.
3 Save your seings.
Verify That vRealize Orchestrator Service Is Available
After you upgrade to VMware vRealize ™ Automation 7.1, you must verify the connection between
vRealize Automation and VMware vRealize ™ Orchestrator ™. Sometimes after upgrade you must restore
the connection.
Prerequisites
Log in to the vRealize Orchestrator conguration interface.
Procedure
1 Click Validate .
2 If the Authentication section has a green check, go to step 4.
3 If the Authentication section does not have a green check, perform the following steps to restore the
connection to vRealize Orchestrator .
a Click Home.
b Click Authentication Provider.
c In the Admin group text box, select Change, and choose a new Admin group that can be properly
resolved.
The vcoadmins group is available only at the default vsphere.local tenant. If you are using another
tenant for the vRealize Orchestrator, then you must select another group.
d Click Save Changes, and if prompted, restart the vRealize Orchestrator server.
e Click Home.
4 Repeat step 1 to conrm that the Authentication section still has a green check.
5 Click Home, and close the vRealize Orchestrator Control Center.
Restore Embedded vRealize Orchestrator Endpoint
If you add an embedded vRealize Orchestrator endpoint to a vRealize Automation 6.x deployment and
upgrade to vRealize Automation 7.1, you must make changes to the vRealize Orchestrator endpoint URL to
restore the connection.
In vRealize Automation 6.x, the URL for the embedded vRealize Orchestrator is hps://hostname:8281/vco. In
vRealize Automation 7.0, the URL for an embedded vRealize Orchestrator changes to hps://hostname/vco.
Because the 6.x URL does not change when you upgrade to 7.0, the system cannot nd
vRealize Orchestrator. Perform the following steps to x this problem.
Upgrading from vRealize Automation 6.2.x to 7.1
VMware, Inc. 41