6.0
Table Of Contents
- Using the Horizon vCenter Orchestrator Plug-In
- Contents
- Using the Horizon vCenter Orchestrator Plug-In
- Introduction to the Horizon vCenter Orchestrator Plug-In
- Installing and Configuring the Horizon vCenter Orchestrator Plug-In
- Horizon vCenter Orchestrator Plug-In Functional Prerequisites
- Install the Horizon vCenter Orchestrator Plug-In
- Configure the Connection to a View Pod
- Assigning Delegated Administrators to Desktop and Application Pools
- Best Practices for Managing Workflow Permissions
- Set a Policy for De-Provisioning Desktop Virtual Machines
- Using Horizon vCenter Orchestrator Plug-In Workflows
- Making the Workflows Available in vSphere Web Client and vCloud Automation Center
- Exposing Horizon vCenter Orchestrator Plug-In Workflows in vSphere Web Client
- Exposing Horizon vCenter Orchestrator Plug-In Workflows in vCloud Automation Center
- Create Business Groups for Delegated Administrators and End Users
- Create Services for Delegated Administrators and End Users
- Create Entitlements for Delegated Administrators and End Users
- Bind vCAC60 Workflows to Specific Pods and Pools in vCloud Automation Center
- Configure the Catalog Item for the Workflow
- Index
5 Select (string)podAlias Horizon View Pod in the upper portion of the tab and edit its properties.
a In the lower portion of the tab, click the Properties tab, and in the Data Binding row, type the pod
name and enclose it with quotation marks; for example: "ViewPod1".
b Select and delete the Predefined answers property.
c Add the Default value property and type in the same pod name enclosed with quotation marks.
If you do not delete the Predefined answers property and set the Default value property, you might
see a drop-down list of pods in vSphere Web Client, even though the workflow is bound to one pod.
6 To bind the workflow to only one pool, select (string)poolId Desktop Pool ID in the upper portion of
the tab and edit its properties.
a In the lower portion of the tab, click the Properties tab, and in the Data Binding row, type the pool
ID and enclose it with quotation marks; for example, "DesktopPool".
b Select and delete the Predefined answers property.
c Add the Default value property and type in the same pool name enclosed with quotation marks.
If you do not delete the Predefined answers property and set the Default value property, you might
see a drop-down list of pods in vSphere Web Client, even though the workflow is bound to one pool.
When this workflow starts, the pod name and pool ID are already populated and cannot be changed.
What to do next
Create versions of the workflow in other languages.
Create Localized Versions of a Workflow for vSphere Web Client
To create the localization resources for vSphere Web Client, administrators can run the Clone Localization
Resources workflow, located in the Configuration folder.
Prerequisites
n
Bind the workflow to a pod and, optionally, to a pool. See “Bind vSphereWebClient Workflows to
Specific Pods and Pools in vCenter Orchestrator,” on page 30.
n
Verify that you have administrator credentials for the Orchestrator server. The account must be a
member of the vCenter Orchestrator Admin group configured to authenticate through vCenter Single
Sign-On.
Procedure
1 Log in to the Orchestrator client as an administrator, and select Design from the drop-down menu in
the upper-left portion of the screen.
2 Click the Resources view and navigate to the folder that contains the duplicated workflow that you
used to bind the workflow to a pod.
3 In that folder, create a subfolder and, for the folder name, specify the same name used for the
duplicated workflow.
The folder name must exactly match the duplicated workflow name and must be in the same folder as
the workflow.
4 Click the Workflows view and navigate to Library > Horizon > Configuration.
5 Expand the Configuration item, right-click the Clone localization resources workflow and select Start
workflow.
Chapter 4 Making the Workflows Available in vSphere Web Client and vCloud Automation Center
VMware, Inc. 31