VUM plug-in is updated to support vRealize Orchestrator version 7.6 Java client and UI, up to vRO version 8.6.2, except versions 8.4.0 and 8.4.1.
7.6 (Java client)
Note: In versions 8.4.0/8.4.1 you will not be able to create a patch baseline.
VUM plug-in is updated to support vSphere API versions - 6.7, 7.0, 7.0 U1, 7.0 U2.
VUM plug-in is updated to support Update Manager API version 6.0 to 8.0. API version 8.0 is the latest vCenter 7.0 and API version 6.0 is vCenter 6.7
upgrade log4j to 2.17.1
Export compliance report workflow - the "Save as at" field now has an updated file location: "/var/run/vco/filename.xxx". The compliance report will be exported at location "/data/vco/var/run/vco/" for vRO version 8.x and at "/var/run/vco/filename.xxx" for vRO version 7.x.
VUM's EULA was changed to be the same as vRO's.
In order to use VUM plug-in in vRO 7.6, a mandatoryprerequisite is to update the vSphere plug-in to version 7.x.
The Export compliance report workflow is only supported in vRO versions 7.6 (UI and Java client), 8.6.0 and 8.6.1. It will not work for all other versions.
Deprecated method getVirutalApplicaneBaselines/getVirutalApplianceBaselines in VumObjectManager
Deprecated method removeAllVcenterWithVum in VumObjectManager
Deprecated method registerVcenterInctencesWithVum in VumObjectManager
Deprecated method removeVcenterWithVum in VumObjectManager
Deprecated method removeVcenterInstancesWithVum in VumObjectManager
Substituted method getVirutalApplicaneBaselines/getVirutalApplianceBaselines for getVirtualApplianceBaselines in VumObjectManager
Deprecated workflow "Add and Set default vCenter with Update Manager"
Deprecated workflow "Remove All configured servers"
New "Set a default vCenter with Update Manager" workflow
Bug fixing in workflows.
New plug-in use case
The main configuration workflows "Add and Set default vCenter with Update Manager" and "Remove All configured servers" have been deprecated. In the previous plug-in version, you'd first have to first run the vSphere workflow Add a vCenter server instance, then run the VUM Add and Set default vCenter with Update Manager workflow to register a host with Update Manager. In this version, the second step is not necessary. By default, all vCenter hosts added through the vSphere plug-in can also be used with Update Manager and will appear in the drop down menu in all VUM workflows. And vice versa, if you remove a vCenter host through the vSphere plug-in, it will also be removed from Update Manager.
There is also a mandatory step that needs to be done if you have vCenter servers, prior to version 7, attached to vCenter plugin and that is to import a VUM server certificate for each one of them with vRO's "Import a certificate from URL" workflow. As input parameter you need to set vCenter's URL and append port 8084 (ex. https://<vcenter_ip>:8084)
The new Set a default vCenter with Update Manager workflow is optional if you work with the orchestrator through the application (mandatory if you use the REST API directly). If you only have a single host registered through the vSphere plug-in, it will automatically be set as default in Update Manager. If you choose to set a default host, it will be pre-selected in all workflows. If you don't set a default host, you will have to select one every time.