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
Log In Fails After Upgrade
You must exit the browser and log in again after an upgrade for sessions that use unsynchronized user
accounts.
Problem
After an upgrade to vRealize Automation 7.0.1, unsynchronized user accounts are denied access at login.
Solution
Exit the browser and relaunch vRealize Automation.
Catalog Items Appear in the Service Catalog But Are Not
Available to Request
Catalog items that use certain property definitions from prior versions appear in the service catalog but
are not available to request after upgrading to vRealize Automation 7.0.1.
Problem
If you upgraded from a 6.2.x or earlier version and you had property definitions with the following control
types or attributes, the attributes are missing from the property definitions and any catalog items that use
the definitions do not function the way that they did before upgrading .
n n
Control types. Check box or link.
n
Attributes. Relationship, regular expressions, or property layouts.
Cause
Beginning in vRealize Automation 7.0, the property definitions no longer use the attributes. You must
recreate the property definition or configure the property definition to use avRealize Orchestrator script
action rather than the embedded control types or attributes.
In vRealize Automation 7.0 and later, the property definitions no longer use the attributes. You must
recreate the property definition or configure the property definition to use a vRealize Orchestrator script
action rather than the embedded control types or attributes.
Migrate the control type or attributes to vRealize Automation 7.0 using a script action.
Solution
1 In vRealize Orchestrator, create a script action that returns the property values. The action must
return a simple type. For example, return strings, integers, or other supported types. The action can
take the other properties on which it depends as an input parameter. For information about creating
script actions, see the vRealize Orchestrator documentation.
Upgrading from vRealize Automation 6.2 to 7.0.1
VMware, Inc. 54