7.0
Table Of Contents
- Upgrading from vRealize Automation 6.2 to 7.0.1
- Contents
- Upgrading to vRealize Automation 7.0
- 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
- Backing up and Saving Your Existing Environment
- Shut Down vCloud Automation Center Services on Your IaaS Windows...
- Prepare a Clustered PostgreSQL Environment for Upgrade
- Increase vCenter Server Hardware Resources for Upgrade
- (Optional) Reconfigure Disk 1 on All vRealize Automation Appliance Nodes
- Create a SaaS Schema and Citext Extension for External vRealize...
- Downloading vRealize Automation Appliance Updates
- Updating the vRealize Automation Appliance
- (Alternative Option) Upgrade the External PostgreSQL Virtual Appliance
- Install the Update on the vRealize Automation Appliance
- Update Your Single Sign-On Password for VMware Identity Manager
- Update the License Key
- Migrate Identity Stores to the VMware Identity Manager
- Install the Update on Additional vRealize Automation Appliances
- 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
- Port Configuration for High-Availability Deployments
- Enabling the Connect to Remote Console Action for Consumers
- Reconfigure External Workflow Timeouts
- Verify That vRealize Orchestrator Service is Available
- Restore Embedded vRealize Orchestrator Endpoint
- Configure an External PostgreSQL Database to Merge into an Embedded PostgreSQL Environment
- Restore Changes to Logging
- Ensure Deployed Virtual Machines Register With Software Service
- 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
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 reconfigure 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.
Understanding How Blueprints Are Upgraded
As a rule, published blueprints are upgraded as published blueprints.
However, there are exceptions to that rule. Multi-machine blueprints are upgraded as composite
blueprints that contain blueprint components. Multi-machine blueprints that contain unsupported settings
are upgraded as unpublished.
For related information see Upgrade and vApp Blueprints, vCloud Endpoints, and vCloud Reservations
and Understanding How Multi-Machine Blueprints Are Upgraded.
Upgrade and vApp Blueprints, vCloud Endpoints, and vCloud Reservations
You cannot upgrade a deployment that contains vApp (vCloud) endpoints. The presence of endpoints of
type vApp (vCloud) prevent upgrade to vRealize Automation 7.0.1.
When upgrade encounters a vApp (vCloud) endpoint in the source deployment, upgrade fails on the
master virtual appliance and reports a message in the user interface and log. You can determine if your
source deployment contains vApp (vCloud) endpoint by logging in to vRealize Automation with Iaas
Administrator privileges, selecting Infrastructure > Endponts and noting the platform type value in the
Endpoints list. If the list contains endpoints of platform type vApp (vCloud), upgrade to 7.0.1is not
supported.
Upgrading from vRealize Automation 6.2 to 7.0.1
VMware, Inc. 13