7.0.1
Table Of Contents
- Upgrading from vRealize Automation 7.0 to 7.0.1
- Contents
- Updated Information
- Upgrading vRealize Automation
- Preparing to Upgrade vRealize Automation
- Updating the vRealize Automation Appliance
- Upgrading the IaaS Server Components
- 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
- Ensure Deployed Virtual Machines Register With Software Service
- Restore Changes to Logging
- Troubleshooting the Upgrade
- 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 During Runtime
- Log In Fails After Upgrade
- Catalog Items Appear in the Service Catalog But Are Not Available to Request
Restore Embedded vRealize Orchestrator Endpoint
If you add an embedded vRealize Orchestrator endpoint to a vRealize Automation 6.x deployment and
upgrade to vRealize Automation 7.0, you must make changes to the vRealize Orchestrator endpoint URL
to restore the connection.
In vRealize Automation 6.x, the URL for the embedded vRealize Orchestrator is https://hostname:
8281/vco. In vRealize Automation 7.0, the URL for an embedded vRealize Orchestrator changes to
https://hostname/vco. Because the 6.x URL does not change when you upgrade to 7.0, the system
cannot find vRealize Orchestrator. Perform the following steps to fix this problem.
Prerequisites
n
Log in to the vRealize Automation console as an IaaS administrator.
Procedure
1 Select Infrastructure > Endpoints > Endpoints.
2 On the Endpoints page, point to the vRealize Orchestrator endpoint, and select Edit from the context
menu.
3 In the Address text box, edit the vRealize Orchestrator endpoint URL to remove :8281.
4 Click OK.
5 Manually start data collection on the vRealize Orchestrator, and verify that the collection is
successful.
Configure an External PostgreSQL Database to Merge
into an Embedded PostgreSQL Environment
After you upgrade the master node in the vRealize Automation appliance you can optionally configure the
external PostgreSQL database to merge into an embedded PostgreSQL master node.
This is the last task in the upgrade process. You can perform this task anytime after upgrade is finished.
This task is not required if it is not applicable to your deployment environment.
Prerequisites
Verify that the master node in the vRealize Automation appliance is upgraded.
Procedure
1 Select your master vRealize Automation appliance as described in the knowledge base article at
http://kb.vmware.com/kb/2105809.
2 Use SSH to log in to the primary virtual appliance.
Upgrading from vRealize Automation 7.0 to 7.0.1
VMware, Inc. 32