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
Upgrade and Identity Appliance Specifications
You congure identity appliance upgrade information in response to prompts that are generated by the
vRealize Automation upgrade executable.
The target deployment uses the VMware Identity Manager.
Upgrade and Licensing
During the upgrade, your existing vRealize Automation 6.x licenses, and any vCloud Suite 6.x licenses that
you have, are removed. You must reenter your licenses in the vRealize Automation 7 vRealize Automation
appliance.
You now use vRealize Automation licensing for virtual appliances and IaaS by entering license key
information in the vRealize Automation appliance. Licensing information is no longer available in the IaaS
user interface and IaaS no longer performs licensing checks. Endpoints and quotas are enforced through the
end-user license agreements (EULAs).
N Write down your vCloud Suite 6.x license key if you used it for vRealize Automation 6.2.x before the
upgrade. Upon upgrade, existing license keys are removed from the database.
For more information about re-entering your license information during or after upgrade, see “Update the
License Key,” on page 24 .
Understanding How Roles Are Upgraded
When you upgrade vRealize Automation, your organization's existing role assignments are maintained. The
upgrade also creates some role assignments to support additional blueprint architect roles.
The following architect roles are used to support the blueprint denition in the design canvas:
n
Application architect. Assembles existing components and blueprints to create composite blueprints.
n
Infrastructure architect. Creates and manages machine blueprints.
n
XaaS architect. Creates and manages XaaS blueprints.
n
Software architect. Creates and manages Software components.
In vRealize Automation 7, tenant administrators and business group managers cannot design blueprints by
default. Upgraded tenant administrators and business group managers are given the infrastructure architect
role.
All users with the ability to recongure a machine in the vRealize Automation 6.2 source version are
authorized to change machine ownership after upgrading to this vRealize Automation version.
The following role assignments are made during the upgrade. Roles that are not listed in the table are
upgraded to the same role name in the target deployment.
Table 5. Roles Assigned During Upgrade
Role in Source Deployment Role in Target Deployment
Tenant administrator Tenant administrator and Infrastructure architect
Business group manager Business group manager and Infrastructure architect
Service architect XaaS architect
Application architect Software architect
For more information about tenant roles, see Foundations and Concepts.
Upgrading from vRealize Automation 6.2 to 7.1
10 VMware, Inc.