7.2

Case-sensitivity in Custom Property Names
Prior to vRealize Automation 7.0, custom property names were case-insensitive. In vRealize Automation 7.0
and later, custom property names are case-sensitive. During upgrade, custom property names must be an
exact match, including their case, to ensure that property values do not override one another and that they
correctly match property dictionary denitions. For example, a custom property expressed as hostname and
another custom property expressed as HOSTNAME are considered dierent custom properties by
vRealize Automation 7.0 and later and do not override one another during upgrade.
Reserved Property Names
Several keywords are now reserved and some upgraded properties might be impacted. Some keywords are
used by the blueprint code that can be imported, for example by using vRealize CloudClient blueprint
import functions. These keywords are considered reserved and are not available for properties that are
being upgraded. The keywords include but are not limited to cpu, storage, and memory.
Upgrade and Application Services
Application Services upgrade is not currently supported in the target vRealize Automation deployment.
Upgrade and Advanced Service Design
When you upgrade to the target vRealize Automation deployment, your Advanced Service Design items are
upgraded to XaaS elements.
XaaS components are available for use in the design canvas.
Upgrade and Blueprint Cost Information
As of 7.0, vRealize Automation cost proles are no longer supported and are not migrated into the target
deployment during upgrade. However, you can leverage the enhanced integration with vRealize Business to
manage your vRealize Automation resource costs.
vRealize Business is now tightly integrated with vRealize Automation and supports the following enhanced
costing features.
n
Unied location in vRealize Business to dene exible pricing policies for:
n
Infrastructure resource, machine, and application blueprints
n
All types of endpoints in vRealize Automation
n
Any operational cost, one time cost, and cost on custom properties
n
Role-based showback reports in vRealize Business
n
Fully leverage new features in vRealize Business
Before you upgrade, you can export your existing cost reports from your source vRealize Automation
instance for reference. After you complete your upgrade, you can install and congure vRealize Business to
handle costing.
Checklist for Upgrading vRealize Automation 6.2.4 or 6.2.5
When you perform an upgrade, you update all vRealize Automation components in a specic order.
The order of upgrade varies depending on whether you are upgrading a minimal environment or a
distributed environment with multiple vRealize Automation appliances.
Chapter 1 vRealize Automation 6.2.4 or 6.2.5 Prerequisites, Considerations, and Process
VMware, Inc. 13