6.1

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 vRealize Orchestrator,” on page 39.
n
Verify that you have administrator credentials for the Orchestrator server. The account must be a
member of the vRealize 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.
6 Complete the form that appears.
Option Action
Source Workflow
Click Not Set and select the original workflow that you duplicated to bind
the workflow to a pod.
Target Workflow
Click Not Set and select the workflow that you duplicated.
7 Click Submit to run the workflow.
If the workflow completes successfully, you can go to the Resources view, expand the folder you created,
and see the properties files that were created for each language.
Exposing Horizon vRealize Orchestrator Plug-In Workflows in
vRealize Automation
vRealize Automation provides a service catalog with a request and approval engine that allows fine-grained
control of workflows through entitlement and auditing.
Administrators can add service and machine blueprints by browsing through Orchestrator > Library >
Horizon and selecting a specific workflow. You can use standard vRealize Automation procedures to
publish and entitle through Catalog Management. Because entitlement is usually very specific when the
workflow is used in vRealize Automation, you must bind the workflow to a particular View pod or desktop
or application pool.
Chapter 4 Making the Workflows Available in vSphere Web Client and vRealize Automation
VMware, Inc. 41