The remote plug-in sample code is organized as a Maven project. You can locate certain important files in the project as follows.

Top-Level Directory

Figure 1. Remote Plug-in Sample Top-Level Directory
This screenshot shows the top four levels of the directory structure of the SDK.

The top-level directory, remote-plugin-sample, is located within the html-client-sdk/samples directory of the SDK zip file.

  • The libs subdirectory contains the external library vim25.jar, which must be installed as a local dependency during the project build and deploy process. The library allows access to vSphere managed objects. In vSphere 8.0 U2 the vim25.jar library was deleted from the Client SDK, so developers who don't have it must find it in the vSphere Management SDK.
  • Nested inside the src directory you can find a java directory, which contains Java source files for the sample plug-in server, at java/com/vmware/sample/remote/*.
  • Also nested inside the src directory you can find a ui directory, which contains source code for the sample plug-in UI, at ui/src/app/{model, service, views}/*.
  • To build the project, use the pom.xml file in the top-level directory of the remote plug-in sample, html-client-sdk/samples/remote-plugin-sample/pom.xml.