Orchestrator allows integration with management and administration solutions through its open plug-in architecture. You use the Orchestrator client to run and create plug-in workflows and access the plug-in API.
Overview of Plug-Ins Orchestrator plug-ins must include a standard set of components and must adhere to a standard architecture. These practices help you to create plug-ins for the widest possible variety of external technologies.
Contents and Structure of a Plug-In Orchestrator plug-ins must contain a standard set of components and conform to a standard file structure. For a plug-in to conform to the standard file structure, it must include specific folders and files.
Orchestrator Plug-In API Reference The Orchestrator plug-in API defines Java interfaces and classes to implement and extend when you develop the IPluginAdaptor and IPluginFactory implementations to create a plug-in.
Elements of the vso.xml Plug-In Definition File The vso.xml file contains a set of standard elements. Some of the elements are mandatory while others are optional. Each element has attributes that define values for the objects and operations you map to Orchestrator objects and operations.
Best Practices for Orchestrator Plug-In Development You can improve certain aspects of the Orchestrator plug-ins that you develop by understanding the structure and content of plug-ins, as well as by understanding how to avoid specific problems.