7.2

Table Of Contents
n
If you are upgrading a distributed environment congured with an embedded PostgreSQL database,
examine the les in the pgdata directory on the master host before you upgrade the replica hosts.
Navigate to the PostgreSQL data folder on the master host at /var/vmware/vpostgres/current/pgdata/.
Close any opened les in the pgdata directory and remove any les with a .swp sux. Verify that all
les in this directory have correct ownership: postgres:users.
n
If you installed a Common Components Catalog component, you must uninstall it before you upgrade.
For information about how to uninstall, install, and upgrade Common Components Catalog
components, see the Common Components Catalog Installation Guide.
Considerations About Upgrading to This vRealize Automation Version
vRealize Automation 7 introduced various functional changes during and after the upgrade process that
you must consider before you upgrade your vRealize Automation deployment to the new version.
N New vRealize Automation features introduce several enhancements along with the ability to
upgrade or migrate to the new version. For recommendations and guidance before you begin the upgrade
process, visit the vRealize Automation Upgrade Assistance Program web page at
hp://www.vmware.com/products/vrealize-automation/upgrade-center before you begin the upgrade
process.
Review the considerations in the subtopics before you upgrade.
Upgrade and Identity Appliance Specifications
You congure 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 28 .
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 denition 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.
Chapter 1 vRealize Automation 6.2.4 or 6.2.5 Prerequisites, Considerations, and Process
VMware, Inc. 9