vSphere Web Client SDK 6.0 Update 2 Release Notes

Updated on: 28 March 2016

vSphere Web Client SDK 6.0 Update 2 | 15 MARCH 2016 | Build 3633101

Check for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

What's New

The following features have been introduced to the vSphere Web Client SDK 6.0 Update 2:

HTML-Based Plug-Ins Forward Compatibility

To ensure that your HTML-based extensions are forward compatible with the vSphere Web Client, follow these guidelines:

  • Replace your current web-platform.js file with the one that is provided with the vSphere Web Client SDK Update 2.
    The initialization code of the web-platform.js JavaScript file is modified. All samples that are provided with the SDK and the project wizard are updated to comply with this change.

    The modified section is the following: 

    var WEB_PLATFORM = self.parent.WEB_PLATFORM;
if (!WEB_PLATFORM) {
   WEB_PLATFORM = self.parent.document.getElementById("container_app");
   self.parent.WEB_PLATFORM = WEB_PLATFORM;
}
  • You must apply the following changes to the projects that you created with vSphere Web Client SDK 6.0 and vSphere Web Client SDK 6.0 Update 1:
    • The names of the properties files must be suffixed with _en_US instead of -en_US.
    • The value of the REGEXP2 property which is located in the build-war.xml must be changed from \2-\1.properties to \2_\1.properties.
    • The viewResolvers property which is located in the bundle-context.xml must be removed to avoid conflicts.

Additional Features

The following additional features have been added since version 6.0 Update 1:

  • The WEB_PLATFORM.getVcSelectorInfo API is updated to always return the unique identifier (serviceGuid) for the specific vCenter Server instance. For more information about this update, see the Global View HTML-based example in the SDK.

  • The scripts that you must run to register with the vCenter Server instance, dev-setup.sh and dev-setup.bat, are updated to include the Data Service configuration file (ds.properties).

Earlier Releases of the vSphere Web Client SDK

Known Issue

The following problems have been identified in the vSphere Web Client SDK 6.0 Update 2.

  • New When you make Data Service queries, you see an exception in the vSphere Web Client log file
    The ds.properties file from your development setup contains the Data Service configuration properties and is missing properties that are required by the vSphere Web Client. As a result, the following exception is logged when you start the vSphere Web Client:
    com.vmware.cis.data.service.exception.InitializationException: Required configuration property `solutionUser.keyStorePassword' not found in config file `C:\ProgramData\VMware\vSphere Web Client\config\ds.properties'

    Workaround: Add the following properties to the ds.properties file:

    • For Windows:

      solutionUser.keyStorePath=C:/ProgramData/VMware/vSphere Web Client/store.jks
      solutionUser.keyStorePassword=vmw@re
      lookupService=https://VCENTER_IP/lookupservice/sdk
    • For Mac OS:

      solutionUser.keyStorePath=/var/lib/vmware/vsphere-client/store.jks
      solutionUser.keyStorePassword=vmw@re
      lookupService=https://VCENTER_IP/lookupservice/sdk

  • The log files of the Virgo server are missing on Japanese OS installations

    Workaround: To resolve this issue, you can try the following:

    1. Open the vSphereWebClient\configuration\serviceability.xml file with a Hex editor.

    2. Remove the first three invisible bytes (EF BB BF) and save the file.

    3. Restart the vSphere Web Client Service.

  • When a menu or a dialog overlaps an HTML view, the view becomes blank
    Log in to the vSphere Web Client by using Mozilla Firefox version 31.0 or earlier. When you open a menu or a dialog which overlaps an HTML view, the view is hidden temporary and is displayed as a blank pane. This issue has no functional impact and the view is restored once you close the menu or dialog.

    Workaround: Use another supported browser or a more recent version of Mozilla Firefox.

Resolved Issues

The following issues are resolved for the vSphere Web Client SDK 6.0 Update 2 release:

  • Some of the samples provided in the vSphere Web Client SDK cannot be deployed
    The manifest file of the vim25.jar library, which is located in the vsphere-client-sdk\libs SDK directory, is missing. As a result, the globalview and vsphere-wssdk plug-in examples fail to deploy.

    Workaround: Replace the vim25.jar library in the vSphere Web Client SDK 6.0 Update 1 with the one provided with the vSphere Web Client SDK version 6.0.

    This issue is resolved in this release.

  • If the target object was not previously displayed in another HTML view, the sendNavigationRequest API stops working.

    This issue is resolved in this release.

  • When you open a Flex component which overlap an HTML view, the view becomes invisible
    When you open a Flex component, such as a menu or dialog, which overlaps an HTML view, the view is temporary hidden.

    Workaround: None.

    This issue is resolved in this release.