You must provide information about an extension when you register it with vCenter Server.

A description of the extension

A unique identifier for the extension

Version information

URLs to any server or client interfaces that the extension exposes

An email address for the extension administrator

Any additional metadata that the extension defines, for example, URLs to the the company and product Web sites, the managed object reference (MoRef) of the virtual machine or vApp in which the solution is running, and so on

Definitions of the tasks, events, faults, and privileges that the extension adds to vCenter Server

Localization data for the task, event, fault, and privilege descriptions

A public key which vCenter Server uses to register the extension in the registry of the vCenter Server system on which it is running

1

An extension communicates with vCenter Server across a network, so you can use any programming language to create the program that manages an extension.

2

You must provide information about the vCenter Server instance to which you connect an extension. You set the details of the connection to vCenter Server in the client-side stub of the extension.

3

Every extension that you register with vCenter Server must have a unique extension key that vCenter Server uses to identify the extension.

4

You provide product information about an extension by setting properties when you instantiate the Extension object in the program that manages the extension. The product information that you set appears in the vSphere client.

5

When you develop extensions, the vSphere client can appear in different languages in different locales. You can set information that appears in the vSphere client, for example, the extension name, as resources that can be translated.

6

If an extension manages virtual machines or vApps, you can identify those virtual machines or vApps as being managed by that extension. You can add icons to the objects that the extension manages that appear in the vCenter inventory, and warn users if they try to perform actions on those objects.

7

You can set properties in the ExtManagedEntityInfo data object to define how the vSphere client displays the different types of virtual machines and vApps that an extension deploys.

8

If a solution deploys different types of virtual machine or vApp, you can provide a description for each type by setting the ExtManagedEntityInfo description property.

9

When you develop an extension, the best practise is to provide a means of unregistering the extension from vCenter Server.