Orchestrator includes a collection of default plug-ins. Each plug-in exposes an external product API to the Orchestrator platform. Plug-ins provide inventory classes, extend the scripting engine with new object types, and publish notification events from the external system. Each plug-in can also provide a library of workflows that represents the typical use cases of the integrated product in an automated fashion.
You can see the list of available plug-ins from the Plug-ins tab in the Orchestrator configuration interface. Plug-ins that require configuration add separate tabs to the interface.
|
Provides access to the vCenter Server 5.1 API, so that you can incorporate all of the vCenter Server objects and functions into the management processes that you use Orchestrator to automate. |
See http://www.vmware.com/support/orchestrator/doc/vco_vsphere51_api/index.html. |
See http://www.vmware.com/support/orchestrator/doc/vco_vsphere51_api/index.html. |
|||
|
Provides workflows that act as basic building blocks for customization and automation of client processes. The workflow library includes templates for lifecycle management, provisioning, disaster recovery, hot backup, and many other standard processes. Sources of library processes are accessible and can be copied and edited. |
See Developing with VMware vCenter Orchestrator, Using the Orchestrator API. |
See Developing with VMware vCenter Orchestrator, Using the Orchestrator API. |
|||
|
Java Database Connectivity (JDBC) API is the industry standard for database-independent connectivity between the Java programming language and a wide range of databases. The databases include SQL databases and other tabular data sources, such as spreadsheets or flat files. The JDBC API provides a call-level API for SQL-based database access from workflows. |
|||||
|
Provides an implementation of the Secure Shell v2 (SSH-2) protocol. Allows remote command and file transfer sessions with password and public key-based authentication in workflows. Optionally, the SSH plug-in can provide remote file system browsing directly in the vCO inventory. |
|||||
|
A complete Document Object Model (DOM) XML parser that you can implement in workflows. Alternatively, you can use the ECMAScript for XML (E4X) implementation in the Orchestrator JavaScript API. |
|||||
|
Uses Simple Mail Transfer Protocol (SMTP) to send email from workflows. |
Set the default values for the EmailMessage object to use. See Define the Default SMTP Connection. |
||||
|
Wraps the Jakarta Apache Commons Net Library. Provides implementations of Telnet, FTP, and POP3. The POP3 part allows reading email. In combination with the Mail plug-in, the Net plug-in provides full email sending and receiving capabilities in workflows. |
|||||
|
Provides workflows that allow you to generate information in PDF format about a workflow or a workflow category. |
|||||
|
Provides common enumerated types that can be used in workflows by other plug-ins. |
|||||
|
A Web view that allows you to access the workflows in the Orchestrator library and interact with them across a network by using a Web browser. |
Each plug-in is a DAR file package. The DAR files are stored in Orchestrator_installation_path\app-server\server\vmo\plugins on the Orchestrator server system. The components of each plug-in, such as workflow categories and API modules, can use different naming conventions.