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 vRealize Orchestrator. You can optionally generate a sample workflow that runs 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 vRealize Orchestrator platform supports. The PowerShell plug-in defines the type mappings. In general, primitive types are mapped to the corresponding vRealize Orchestrator types, and complex types are represented by the PowerShellRemotePSObject object.
- Verify that you are logged in to the vRealize Orchestrator Client as an administrator.
- Verify that you have a connection to a PowerShell host from the Inventory view.
- In the vRealize Orchestrator Client, navigate to and enter the powershell and generate tags in the workflow search box.
- Locate the Generate an action for a PowerShell cmdlet workflow and click Run.
- On the Cmdlet tab, select a PowerShell cmdlet to run when using the action that you generate.
- 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.
- On the Action tab, in the Name text box, enter a name for the action that you want to generate, and select an existing module in which to generate the action.
- On the Workflow tab, select whether to generate a workflow.
Option Description Yes Generates a sample workflow that can run the generated action. You must 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.
- Click Run.
What to do next
You can integrate the generated action in custom workflows.