The vCenter Extension vService simplifies the installation and deployment of extensions. By integrating an extension with the vCenter Extension vService you can deploy extensions from the vSphere Web Client without having to enter the connection parameters of the vCenter Server on which you install the extension, or provide the login credentials for that vCenter Server instance.
The vCenter Extension vService performs the following functions for solutions that you integrate with it.
■
|
Provides the extension with the connection parameters of the vCenter Server instance. |
■
|
For example, to deploy the EAM Sample Solution you provide the IP address and login credentials in the eamri.properties file, which requires you to update the solution for every vCenter Server instance on which you install it. By integrating an extension with the vCenter Extension vService, you avoid this manual step.
■
| To integrate a virtual machine with the vCenter Extension vService, you must deliver the extension in an Open Virtualization Format (OVF) package, add sections to the OVF descriptor file, and provide in the guest operating system a script that connects to the vCenter Extension vService. |
■
| If you configure the virtual machine that runs an extension to use the vCenter Extension vService, you can deploy the extension directly in the vSphere Web Client. |
■
| The vCenter Extension vService XML Schema defines the <vServiceEnvironmentSection> in the OVF environment of the virtual machine that contains the extension. It also defines the RegisterExtension function that registers the extension with vCenter Server. |