Table 1‑1. Plug-Ins Installed with Orchestrator (Continued)
Plug-In Purpose Configuration
SSH 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. Supports keyboard-
interactive authentication. Optionally, the SSH plug-in can
provide remote file system browsing directly in the
Orchestrator client inventory.
See “Configure the SSH Plug-In,” on
page 57.
XML 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.
None
Mail 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,” on page 67.
Net Wraps the Jakarta Apache Commons Net Library. Provides
implementations of Telnet, FTP, POP3, and IMAP. The
POP3 and IMAP part is used for reading email. In
combination with the Mail plug-in, the Net plug-in
provides complete email sending and receiving capabilities
in workflows.
None
Workflow documentation Provides workflows that let you generate information in
PDF format about a workflow or a workflow category.
None
Enumeration Provides common enumerated types that can be used in
workflows by other plug-ins.
None
HTTP-REST Lets you manage REST Web services by providing
interaction between vCenter Orchestrator and REST hosts.
See “Configuring the HTTP-REST
Plug-In,” on page 79.
SOAP Lets you manage SOAP Web services by providing
interaction between vCenter Orchestrator and SOAP hosts.
See “Configuring the SOAP Plug-
In,” on page 85.
AMQP Lets you interact with Advanced Message Queuing
Protocol (AMQP) servers also known as brokers.
See “Configuring the AMQP Plug-
In,” on page 91.
SNMP Enables vCenter Orchestrator to connect and receive
information from SNMP-enabled systems and devices.
None
Active Directory Provides interaction between vCenter Orchestrator and
Microsoft Active Directory.
See “Configuring the Active
Directory Plug-In,” on page 103.
vCO WebOperator A Web view that lets you to access the workflows in the
Orchestrator library and interact with them across a
network by using a Web browser.
None
Dynamic Types Lets you define dynamic types and create and use objects
of these dynamic types.
See Chapter 18, “Using the Dynamic
Types Plug-In,” on page 107.
Multi-Node Contains workflows for hierarchical orchestration,
management of Orchestrator instances, and scale-out of
Orchestrator activities.
See Chapter 19, “Configuring and
Using the Multi-Node Plug-In,” on
page 109.
PowerShell Lets you manage PowerShell hosts and run custom
PowerShell operations.
See Chapter 20, “Using the
PowerShell Plug-In,” on page 117.
Plug-In Components
Each plug-in is a DAR file package. The DAR files are stored in Orchestrator_installation_path\app-
server\plugins on the Orchestrator server system. The components of each plug-in, such as workflow
categories and API modules, use different naming conventions.
Chapter 1 Introduction to Orchestrator Plug-Ins
VMware, Inc. 13