Build and Deploy the
vSphere HTML SDK Sample Plug-in
The
vSphere Client
SDK contains a sample plug-in that demonstrates the use of several extension
points. Use this procedure after you modify the sample.
Before you modify the sample,
see
vSphere Client SDK
Setup for instructions to install and configure all required components.
In particular, you need the following tools installed:
- nodejs, versions 6.9.x to 11.15.x, inclusive
- npm5.x.x
- Angular-CLI
For the vSphere 8.0 release, local
plug-ins must be upgraded as follows:
- Local plug-ins must be FIPS-compliant. See https://developer.vmware.com/docs/13385/preparing-local-plug-ins-for-fips-compliance
- Local plug-ins must bundle third-party libraries and installthem in a separate directory. See https://vdc-download.vmware.com/vmwb-repository/dcr-public/77dd6491-bb96-47f3-8c2e-a5a4655f078b/b916bc3c-0168-4487-a9e5-c89b50373c18/Local-Plugins-Library-Isolation.pdf
Also you must set the
following environment variables:
- Set the environment variableANT_HOMEto your Apache Ant folder.
- Set the environment variableVSPHERE_SDK_HOMEto your vSphere Client SDK folder.
After you modify the sample plug-in, you must re-build
and re-deploy it. To build the html-sample, do the following steps from the command
line.
- In a command shell, change to thehtml-sample-uidirectory.cd samples/html-sample-ui
- Build the modified sample.On a MacOS system, run./build-plugin-package.sh.On a Windows system, runbuild-plugin-package.bat.The build output is insamples/html-sample-ui/target.
- Copy the output folders to the plugin-packages directory, confirming that you want to replace existing files.cp -r samples/html-sample-ui/target vsphere-ui/plugin-packagesThevsphere-ui/plugin-packagesdirectory is where local plug-ins are picked up automatically when the server starts.