5.5.2
Table Of Contents
- Using VMware vCenter Orchestrator Plug-Ins
- Contents
- Using VMware vCenter Orchestrator Plug-Ins
- Introduction to Orchestrator Plug-Ins
- Configure the Orchestrator Plug-Ins
- Using the vCenter Server Plug-In
- Configuring the vCenter Server Plug-In
- vCenter Server Plug-In Scripting API
- Using the vCenter Server Plug-In Inventory
- Access the vCenter Server Plug-In Workflow Library
- vCenter Server Plug-In Workflow Library
- Batch Workflows
- Cluster and Compute Resource Workflows
- Custom Attributes Workflows
- Datacenter Workflows
- Datastore and Files Workflows
- Datacenter Folder Management Workflows
- Host Folder Management Workflows
- Virtual Machine Folder Management Workflows
- Guest Operation Files Workflows
- Guest Operation Processes Workflows
- Power Host Management Workflows
- Basic Host Management Workflows
- Host Registration Management Workflows
- Networking Workflows
- Distributed Virtual Port Group Workflows
- Distributed Virtual Switch Workflows
- Standard Virtual Switch Workflows
- Resource Pool Workflows
- Storage Workflows
- Storage DRS Workflows
- Basic Virtual Machine Management Workflows
- Clone Workflows
- Linked Clone Workflows
- Linux Customization Clone Workflows
- Tools Clone Workflows
- Windows Customization Clone Workflows
- Device Management Workflows
- Move and Migrate Workflows
- Other Workflows
- Power Management Workflows
- Snapshot Workflows
- VMware Tools Workflows
- Using the Configuration Plug-In
- Using the vCO Library Plug-In
- Using the SQL Plug-In
- Using the SSH Plug-In
- Using the XML Plug-In
- Using the Mail Plug-In
- Using the Net Plug-In
- Using the Enumeration Plug-In
- Using the Workflow Documentation Plug-In
- Using the HTTP-REST Plug-In
- Using the SOAP Plug-In
- Using the AMQP Plug-In
- Using the SNMP Plug-In
- Using the Active Directory Plug-In
- Using the Dynamic Types Plug-In
- Configuring and Using the Multi-Node Plug-In
- Using the PowerShell Plug-In
- Using the PowerShell Plug-In Inventory
- Configuring the PowerShell Plug-In
- Running PowerShell Scripts
- Generating Actions
- Passing Invocation Results Between Actions
- PowerCLI Integration with the PowerShell Plug-In
- Sample Workflows
- Access the PowerShell Plug-In API
- Working with PowerShell Results
- Examples of Scripts for Common PowerShell Tasks
- Troubleshooting
- Index
Generate an Action for a PowerShell Cmdlet
You can run a workflow to generate an action for a PowerShell cmdlet and parameter set that you provide.
With this action, you can use PowerShell functionality in Orchestrator. You can optionally generate a
sample workflow that can run the generated action.
You can use a large set of data types with the PowerShell script engine. The data types that you can use
include primitive types such as Integer, Boolean, Char, any type available from the .NET assembly, or user-
defined types. When generating actions based on PowerShell cmdlet definitions, the input and output
cmdlet parameters are represented by types that the Orchestrator platform supports. The PowerShell plug-
in defines the type mappings. In general, primitive types are mapped to the corresponding Orchestrator
types, and complex types are represented by the PowerShellRemotePSObject object.
Prerequisites
n
Verify that you are logged in to the Orchestrator client as an administrator.
n
Verify that you have a connection to a PowerShell host from the Inventory view.
Procedure
1 Click the Workflows view in the Orchestrator client.
2 In the workflows hierarchical list, select Library > PowerShell > Generate and navigate to the Generate
an action for a PowerShell cmdlet workflow.
3 Right-click the Generate an action for a PowerShell cmdlet workflow and select Start workflow.
4 Select a PowerShell cmdlet to run when using the action that you generate.
5 Select a parameter set for the cmdlet.
The parameter set definition values appear in the Parameter set definition text box.
NOTE You cannot modify the parameter set definition values by editing the string in the Parameter set
definition text box. You can review the string for information about the parameters that the parameter
set contains.
6 In the Name text box, type a name for the action that you want to generate.
7 Select an existing module in which to generate the action.
8 Select whether to generate a workflow.
Option Description
Yes
Generates a sample workflow that can run the generated action. You
should select a folder in which to generate the workflow.
NOTE The name of the generated workflow consists of the predefined
string Execute Cmdlet and the name of the generated action.
No
A sample workflow is not generated.
9 Click Submit to run the workflow.
What to do next
You can integrate the generated action in custom workflows.
Using VMware vCenter Orchestrator Plug-Ins
122 VMware, Inc.