vSphere Web Client Extension Points contains the complete list of extension points published by the vSphere Web Client, the required extension definition type, and a brief description of the resulting extension.
|
|
|
|
|
|
Object workspace extension points follow the format vsphere.core.${objectType}.${view}. The ${objectType} placeholder corresponds to the type of vSphere object, and the ${view} placeholder corresponds to the specific view. For example, the extension point vsphere.core.cluster.manageViews is the extension point for the Manage tab view for Cluster objects. The following names are valid ${objectType} values.
■
|
dvs: DistributedVirtualSwitch object
|
■
|
vm: VirtualMachine object
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The extension point names follow the format vsphere.core.${objectType}.list.columns, where the ${objectType} placeholder corresponds to the type of vSphere object. The following names are valid ${objectType} values.
■
|
dvs: DistributedVirtualSwitch object
|
■
|
vm: VirtualMachine object
|
|
|
|
|
|
|
Extension Templates in the vSphere Web Client SDK contains the Extension Templates included with the vSphere Web Client SDK.
|
|
|
Creates a complete object workspace for a given custom object type. When you create an instance iof the objectViewTemplate, the vSphere Web Client generates an extension point for each of the standard object workspace tabs, subtabs, and views.
The objectViewTemplate creates extension points in the format {namespace}.{extension point name}. For a custom object called a Rack, for example, one extension point might be com.myExtension.Rack.monitorViews.
See vSphere Web Client Extension Points for the full list of object workspace extension points. Note that a given tab or sub-tab does not appear in the vSphere Web Client user interface unless you explicitly create an extension that references that tab’s extension point.
|
|
Creates a standard Summary tab with an optional header at the top, and a main area that can contain one or more Portlet data views.
You must supply a namespace, and can optionally supply a summaryHeaderView, for the summaryViewTemplate. You must create an instance of the objectViewTemplate before creating a summaryViewTemplate instance.
The summaryViewTemplate creates the extension point {namespace}.summarySectionViews. When you create data view extensions at this extension point, they data views appear as Portlets in the Summary tab.
|
|
namespace: a unique identifier used to avoid name-clashes with other extensions
title: the custom object text label
icon: the custom object icon resource
objectType: the vSphere type name for the custom object
listViewId: the data view that appears when the user clicks the collection node, usually an object list
parentUid: the object collection node’s parent node in the Object Navigator control
|