7.1
Table Of Contents
- Upgrading from vRealize Automation 7.0 to 7.1
- Contents
- Updated Information
- Upgrading vRealize Automation
- Preparing to Upgrade vRealize Automation
- Updating the vRealize Automation Appliance
- Upgrading the IaaS Server Components
- Add Users or Groups to an Active Directory Connection
- Enable Your Load Balancers
- Post-Upgrade Tasks for vRealize Automation
- Troubleshooting the Upgrade
- Installation or Upgrade Fails with a Load Balancer Timeout Error
- Upgrade Fails for Website Component During IaaS Upgrade
- Manager Service Fails to Run Due to SSL Validation Errors During Runtime
- Log In Fails After Upgrade
- Catalog Items Appear in the Service Catalog But Are Not Available to Request
- Unable to Upgrade Management Agent
- IaaS Windows Services Fail to Stop
- PostgreSQL External Database Merge Is Unsuccessful
- Delete Orphaned Nodes on vRealize Automation 7.0
- Delete Orphaned Nodes on vRealize Automation 7.0.1
- Join Cluster Command Appears to Fail After Upgrading a High-Availability Environment
- Upgrade Is Unsuccessful if Root Partition Does Not Provide Sufficient Free Space
- Manual PostgreSQL Database Merge
- Management Agent Upgrade is Unsuccessful
- 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
n
Your primary IaaS Website, Microsoft SQL database, and Model Manager node must have Java 8,
update 91, 64 bit, jdk-8u91-windows-x64.exe, installed. After you install Java, you must set the
environment variable, JAVA_HOME , to the new version on each server node.
n
If you have a Common Components Catalog component installed, you must uninstall the component
before you upgrade. After you nish the upgrade, you can reinstall the component with the appropriate
version. For more information, see the Common Components Catalog Installation Guide.
Procedure
1 If you are using a load balancer, prepare your environment.
a Verify that the Website on which Model Manager data is installed is enabled for load balancer
trac.
You can identify this node by the presence of the <vCAC Folder>\Server\ConfigTool folder.
b Disable all other Web sites and non-primary Manager Services for load balancer trac.
2 Right-click the setup__vra-va-hostname.domain.name@5480.exe setup le and select Run as
administrator.
3 Click Next.
4 Accept the license agreement and click Next.
5 Type the administrator credentials for your current deployment on the Log In page.
The user name is root and the password is the password that you specied when you deployed the
appliance.
6 Select Accept .
7 On the Installation Type page, verify that Upgrade is selected.
If Upgrade is not selected, the components on this system are already upgraded to this version.
8 Click Next.
9 Congure the upgrade seings.
Option Action
If you are upgrading the Model
Manager Data
Select the Model Manager Data check box in the vCAC Server section.
The check box is selected by default. Upgrade the Model Manager data
only once. If you are running the setup le on multiple machines to
upgrade a distributed installation, the Web servers stop functioning while
there is a version mismatch between the Web servers and the Model
Manager data. When you have upgraded the Model Manager data and all
of the Web servers, all of the Web servers should function.
If you are not upgrading the Model
Manager Data
Unselect the Model Manager Data check box in the vCAC Server section.
To preserve customized workflows
as the latest version in your Model
Manager Data
If you are upgrading the Model Manager Data, select the Preserve my
latest versions check box in the Extensibility Workows section.
The check box is selected by default. Customized workows are always
preserved. The checkbox determines version order only. If you used
vRealize Automation Designer to customize workows in the Model
Manager, select this option to maintain the most recent version of each
customized workow before upgrade as the most recent version after
upgrade.
If you do not select this option, the version of each workow provided
with vRealize Automation Designer becomes the most recent after
upgrade, and the most recent version before upgrade becomes the second
most recent.
For information about vRealize Automation Designer, see Life Cycle
Extensibility.
Chapter 4 Upgrading the IaaS Server Components
VMware, Inc. 25