Overview

This document explains VI client plug-in functionality as provided by the VMware 3.5 / VirtualCenter 2.5 platform.

You can find technical information about developing VI client plug-ins by reading the VI Client Plug-in Technote.

Frequently Asked Questions

Q: What are VI client plug-ins?
A: VI client plug-ins provide an experimental means of extending the VI Client when used in conjunction with VMware VirtualCenter. VI client plug-ins allow you to create custom menus and tabs within VirtualCenter that can be integrated with 3rd-party applications.

Q: What does it mean that VI client plug-ins are experimental?
A: Since the VI client plug-in API is experimental, it is subject to change in a future release of VMware Virtual Infrastructure.

Q: Where can I get technical information on VI client plug-ins?
A: Documentation for the VI client plug-in feature is available as a VMware tech note.

Q: I am trying to develop a VI client plug-in. How can I get support?
A: Support is available through the VMware VI client plug-in community.

Q: Will I be able to integrate my application with VMware VirtualCenter?
A: You may be able to integrate your application with VirtualCenter provided the following two conditions are met:

1. Your application must integrate with VMware VirtualCenter or VMware ESX using the VMware APIs.
2. Your application must have a web interface, or be distributed with a web server that is capable of communicating with VirtualCenter.

Q: How does this plug-in interface compare to the plug-in interface as documented on viplugins.com?
A: VI Client Plug-ins do not use client-side code. Instead, VI client plug-ins rely on an external web server to communicate with VMware VirtualCenter.

Q: If I install a plug-in, how does it affect my service contract?
A: A plug-in is considered third party software, as defined in the VMware Third Party Hardware and Software Support Policy.