7.1

Table Of Contents
Table 442. Plug-Ins Included by Default in vRealize Orchestrator (Continued)
Plug-In Purpose
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 send and receive capabilities in
workows.
Enumeration Provides common enumerated types that can be used in workows by
other plug-ins.
Workow documentation Provides workows that let you generate information in PDF format about
a workow or a workow category.
HTTP-REST Lets you manage REST Web services by providing interaction between
vCenter Orchestrator and REST hosts.
SOAP Lets you manage SOAP Web services by providing interaction between
vCenter Orchestrator and SOAP hosts.
AMQP Lets you interact with Advanced Message Queuing Protocol (AMQP)
servers also known as brokers.
SNMP Enables vCenter Orchestrator to connect and receive information from
SNMP-enabled systems and devices.
Active Directory Provides interaction between vCenter Orchestrator and Microsoft Active
Directory.
vCO WebOperator A Web view that lets you to access the workows in the
vRealize Orchestrator library and interact with them across a network by
using a Web browser.
Dynamic Types Lets you dene dynamic types and create and use objects of these dynamic
types.
PowerShell Lets you manage PowerShell hosts and run custom PowerShell operations.
Multi-Node Contains workows for hierarchical orchestration, management of
Orchestrator instances, and scale-out of Orchestrator activities.
vRealize Automation (only in the instance
embedded in vRealize Automation)
Lets you create and run workows for interaction between
vRealize Orchestrator and vRealize Automation.
For more information about the vRealize Orchestrator plug-ins that VMware develops and distributes, see
the VMware vRealize ™ Orchestrator ™ Documentation landing page.
Creating Custom Resources
A custom resource maps a vRealize Orchestrator object type as an XaaS resource so that you can create
blueprints and resource actions.
For example, you create a custom resource based on VC:virtual machine so that you can create blueprints to
provision vCenter Server virtual machines and are add resource actions to run on the machines.
Add a Custom Resource
You create a custom resource to dene the XaaS item for provisioning.
By creating a custom resource, you map an object type exposed through the API of a vRealize Orchestrator
plug-in as a resource. You create a custom resource to dene the output parameter of an XaaS blueprint for
provisioning and to dene an input parameter of a resource action.
During the process of creating a custom resource, on the Details Form page, you can specify the elds of the
read-only form for the resource that displays information on the details view of a provisioned item. See
“Designing a Custom Resource Form,” on page 324.
Chapter 4 Providing On-Demand Services to Users
VMware, Inc. 309