Remote Plug-in Life Cycle
Remote plug-in content becomes visible
in the vSphere Client after you prepare and register the plug-in with a vCenter Server
instance.
The plug-in displays when you connect a browser
to the vSphere Client URL of a vCenter Server instance, or of a vCenter Server linked to the
instance where the plug-in is registered, and log in.
A remote plug-in has the following life cycle
stages:
- Build
- The plug-in developer assembles necessary resources and builds the package(s) to implement the remote plug-in.
- Run
- The plug-in developer starts the plug-in manifest server.
- Registration
- The plug-in developer registers the plug-in as a vCenter Server extension, using the ExtensionManager managed object of the vCenter Server instance.
- Discovery
- A vCenter Server instance discovers a new plug-in registration, or a new version registration.
- Deployment
- A vCenter Server instance downloads the plug-in manifest file, verifies certification and compatibility, and configures its reverse proxy to route server requests.
- Use
- The browser downloads plug-in resources from a back-end server into an iFrame of the vSphere Client user interface, and the plug-in user interface operates in conjunction with the back-end server or servers.
- Uninstallation
- The developer unregisters the plug-in, and all linked vCenter Server instances delete the routing configuration.