4.1

factory = new SolarSystemFactory();
}
return factory;
}
3 Set the plug-in name.
The IPluginAdaptor.setPluginName() method gets the name from the vso.xml file.
The solar system adapter uses the pluginName variable to set the name of the plug-in.
public void setPluginName(String pluginName) {
SolarSystemAdapter.pluginName = pluginName;
}
4 (Optional) Install any licenses that Orchestrator requires to access the plugged-in technology.
You obtain licenses by calling the IPluginAdaptor.installLicenses() method to instantiate an array of
PluginLicense objects.
public void installLicenses(PluginLicense[] licenses) throws
PluginLicenseException {
}
5 (Optional) Uninstall an existing plug-in factory.
A plug-in creates a factory instance for every client session that opens between Orchestrator and a plugged-
in technology. You can remove unnecessary plug-in factories to clean up the Orchestrator server by calling
the IPluginAdaptor.uninstallPluginFactory() method.
The solar system plug-in does not implement the IPluginAdaptor.uninstallPluginFactory() method.
You can uninstall factories by implementing a function in the uninstallPluginFactory() method
declaration.
public void uninstallPluginFactory(IPluginFactory plugin) {
}
You instantiated the IPluginFactory implementation, set the name for the plug-in, obtained any licenses that
the plug-in connection requires, and potentially defined a function to remove old factory instances from the
server.
What to do next
Instantiate event generators and publishers.
Manage Plug-In Events
The plug-in adapter manages the events that occur in the plugged-in technology by defining event generators
and event publishers.
Prerequisites
n
Create a public constructor that implements the IPluginAdaptor interface.
n
Instantiate the plug-in factory.
Chapter 7 Developing Plug-Ins
VMware, Inc. 183