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
Bind vCAC60 Workflows to Specific Pods and Pools in vCloud Automation
Center
To expose a workflow through the vCloud Automation Center service catalog, the administrator must use
vCloud Automation Center to bind the workflow to a specific pod and pool.
Workflows exposed through vCloud Automation Center can be customized using the vCloud Automation
Center form editor interface. You can hide fields or re-arrange them and add cosmetic improvements to fit
into the organization service catalog. Add the blueprint for the specific workflow and customize as needed.
You can convert any workflow field to a text box or provide values to display so that users can select from a
drop-down list.
Prerequisites
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.
n
Verify that a connection has been made to the View pod by running the Add View Pod in
Configuration workflow. See “Configure the Connection to a View Pod,” on page 13.
n
Verify that vCloud Automation Center is configured to communicate with the vCenter Orchestrator
server so that the vCenter Orchestrator workflows are available.
n
Verify that you have the pod alias name and the pool IDs. You specified the pod alias when you
performed the procedure described in “Configure the Connection to a View Pod,” on page 13. The pool
IDs are the desktop or application pool IDs, as shown in View Administrator.
Procedure
1 Log in to vCloud Automation Center as an administrator.
2 Select Advanced Services > Service Blueprints.
3 Click the Add Blueprint (+) icon.
4 Navigate through the vCenter Orchestrator workflow library and select a workflow from the Library >
Horizon > Workflows > vCAC60 folder.
5 Click Next, and specify the workflow name and description that will appear in the vCloud Automation
Center service catalog.
6 Click Next, and on the Blueprint Form tab, edit the PodAlias field.
a Click in the PodAlias text box and click the Edit (pencil) icon.
b In the Edit Form Field - PodAlias dialog box, click the Constraints tab and configure the following
fields.
Option Action
Value
Select Constant and supply the pod alias that you configured when
you ran the Add View Pod in Configuration workflow.
Visible
Verify that No is selected.
c Click Submit.
Chapter 4 Making the Workflows Available in vSphere Web Client and vCloud Automation Center
VMware, Inc. 35