Plug-In Package
Overview
A plug-in package
is a ZIP archive file that contains all of the plug-in modules in your solution
along with a package manifest.
The package manifest describes deployment
information for each plug-in module using XML metadata. The
vSphere Client
Extension Manager uses this metadata to install and deploy each
plug-in module in the plug-in package. To create a plug-in package, you must create a
ZIP archive file with the following structure:
- At the root level, add aplugin-package.xmlfile to the root folder.
- At the root level, add apluginsfolder.
- Inside thepluginsfolder, add one WAR files containing the plug-in UI modules.
- Inside thepluginsfolder, add zero or more JAR files, one for each Java service component created for your plug-in.
- Inside thepluginsfolder, add zero or more JAR files, one for each third party Java library used by your plug-in.
You can use any text or XML editor to create the
plugin-package.xml
file. Each WAR file or JAR file must contain an
OSGi-compliant
META-INF/MANIFEST.MF
file that describes the bundle. 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