4.0

Table Of Contents
3 Define Enumerations on page 206
You can define enumerations in the vso.xml file to set global values that apply to all objects of a certain
category.
4 Map Classes and Methods to Classes and Methods in the JavaScript API on page 206
Orchestrator monitors objects in the plugged-in application and performs operations on them by running
workflows, policies, and actions. You map in the vso.xml file the classes and methods from the plugged-
in technology and from the plug-in implementation to JavaScript classes and methods in the Orchestrator
JavaScript API.
Set Up the Global Plug-In Information
To create a plug-in, you must point Orchestrator to the relevant XML schema definition and the source files
for the application and plug-in. You must also define the behavior of the plug-in when Orchestrator starts and
provide a root object for the hierarchy of objects that the plug-in exposes.
Procedure
1 Create a file named vso.xml.
2 Set up the <module> element to provide basic information about the plug-in, including a pointer to the
Orchestrator plug-in XML schema definition.
The <module> element in the vso.xml file for the solar system example sets the plug-in name to
SolarSystem, sets the version number, and provides the path in the DAR archive to the icon that represents
this plug-in in the Orchestrator Inventory view and selection dialog boxes.
<?xml version="1.0" encoding="UTF-8"?>
<module xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="http://www.vmware.com/support/orchestrator/plugin-4-0.xsd"
name="SolarSystem" version="1.0.0" build-number="4" image="images/solarSystem-16x16.png">
3 Provide a description of the plug-in in the <description> element.
The following example shows a <description> element for the solar system.
<description>Example plug-in to a solar system application.</description>
4 Add a tab for the plug-in to the configuration interface by referencing the configuration adapter in the
<configuration> element.
The <configuration> element in the vso.xml file for the solar system example identifies an icon for the
solar system plug-in tab in the file structure of the DAR file, references the configuration adapter
implementation, and activates validation of the information that the user provides.
<configuration
icon="images/solarSystem_32x32.png"
adaptor-class=
"com.vmware.orchestrator.api.sample.solarsystem.config.SolarSystemConfigurationAdaptor"
configuration-war="o11nplugin-solarsystem-config.war"
validation="enabled" />
vCenter Orchestrator Developer's Guide
202 VMware, Inc.