You can add an endpoint and configure the PowerShell plug-in to connect to a running PowerShell host, so that you can call PowerShell scripts and cmdlets from vRealize Orchestrator actions and workflows, and work with the result.
Before you begin
Verify that you have access to a Windows PowerShell host. For more information about Microsoft Windows PowerShell, see the Windows PowerShell documentation.
Log in to the vRealize Automation console as a tenant administrator.
- Select .
- Click the New icon ().
- Select PowerShell from the Plug-in drop-down menu.
- Click Next.
- Enter a name and, optionally, a description.
- Click Next.
- Specify the PowerShell host details.
- Enter the name of the host in the Name text box.
- Enter the IP address or the FDQN of the host in the Host/IP text box.
- Select the PowerShell host type to which the plug-in connects.
Enter the port number to use for communication with the host in the Port text box under the PowerShell host details.
Select a transport protocol from the Transport protocol drop-down menu.Note:
If you use the HTTPS transport protocol, the certificate of the remote PowerShell host is imported to the vRealize Orchestrator keystore.
Select the authentication type from the Authentication drop-down menu.Note:
To use Kerberos authentication, enable it on the WinRM service. For information about configuring Kerberos authentication, see Using the PowerShell Plug-In.
- Enter the credentials for a shared session communication with the PowerShell host in the User name and Password text boxes.
- Click Finish.
You added an Windows PowerShell host as an endpoint. XaaS architects can use the XaaS to publish PowerShell plug-in workflows as catalog items and resource actions.