Release date: 20 AUG 2019 | ESXi build 14351029, SDK build 14379537
For GA of vSphere 6.7 Update 3. Last document update: 20 AUG 2019
Check frequently for additions and updates to these release notes.

Overview

The vSphere Web Services SDK supports the development of applications that use the vSphere API to manage virtual machines and virtual infrastructure components such as datacenters, datastores, resource pools, and networks.

This SDK release for vSphere 6.7 Update 3 includes no new vSphere APIs. See the vSphere Web Services API Reference for features added in Updates 1 and 2.

Distribution Kit

The vSphere Web Services SDK is distributed as part of the vSphere Management SDK, a related collection of vSphere SDKs. When you extract the contents of the distribution kit, the vSphere WSSDK is contained in the SDK sub-directory:

VMware-vSphere-SDK-6.7.0-buildNumber.zip
    SDK
        eam
        sms-sdk
        spbm
        ssoclient
        vsphere-ws
	vslm

New in This Release

Virtual Storage Lifecycle Management SDK
Virtual Storage Lifecycle Management (VSLM) is a set of APIs to manage First Class Disk, also called Improved Virtual Disk. The downloadable vSphere Management SDK includes VSLM WSDL, generated bindings, sample programs, and an API reference manual for VSLM, all in a folder parallel with SMS, SPBM, and vSphere Web Services. (See Distribution Kit)
Online vSphere Web Services API Reference
The vSphere Management SDK was updated for vSphere 6.7 Update 1, but not for Update 2. For vSphere 6.7 Update 3, the online vSphere Web Services API reference includes summaries of types added or changed in both Update 1 and Update 2, and columns for 6.7.1 and 6.7.2 in the API Versions reference table. There were no vSphere API changes for Update 3, only VSLM enhancements.

Deprecations

Several properties and types defined for the API were deprecated in vSphere API 6.5 and 6.7.x. You can see all the objects and types with indicators showing when they were added and/or deprecated by clicking “API Versions Reference” in the VMware vSphere API Reference manual.

Known Issues

The following known issues was discovered after vSphere Web Services SDK 6.7 release. For known issues previously discovered, see the vSphere Web Services SDK 6.7 Release Notes.

Java GetVMFiles sample mishandles VM names containing special characters.
Under the JAXWS samples, the GetVMFiles.java program does not properly handle special characters in VM name passed as parameter.

Documentation Issues

VirtualMachine.CloneVM_Task method failure.
The VMware vSphere API Reference does not document a limitation with regard to VirtualMachineCloneSpec:

When VirtualMachine.CloneVM_Task fails, it produces the following error: &ldquot;The specified delta disk format 'nativeFormat' is not supported.&rdquot; The vCenter Server returns the error when you:
(1) Create a VAAI NAS native linked clone VM that uses nativeFormat for the delta disk format VirtualMachineCloneSpec.location.disk.diskBackingInfo.deltaDiskFormat, or
(2) Create a second-level clone from the first clone, and the disk for the second-level clone is on a different datastore. If you do not specify seSparseFormat or redoLogFormat for the second-level clone delta disk format, the clone operation fails.
If you are using a VM clone with a native delta disk format, you must specify either seSparseFormat or redoLogFormat for any clones that you create from the original native clone when the second-level clone is on a different datastore.
The fault parameter is required for the SetTaskState method.
The VMware vSphere API Reference does not document this limitation with regard to the SetTaskState method:

If you specify an error state when you call the SetTaskState method, you must also specify the fault parameter in the calling sequence.
The seSparse virtual disk type is intended for internal use only.
The documentation does not specify internal use only for VirtualDiskType.seSparse.

Resolved Issues

None in this update release.