5.1
Table Of Contents
- Developing with VMware vCenter Orchestrator
- Contents
- Developing with VMware vCenter Orchestrator
- Developing Workflows
- Key Concepts of Workflows
- Phases in the Workflow Development Process
- Access Rights for the Orchestrator Client
- Testing Workflows During Development
- Creating and Editing a Workflow
- Provide General Workflow Information
- Defining Attributes and Parameters
- Workflow Schema
- Obtaining Input Parameters from Users When a Workflow Starts
- Requesting User Interactions While a Workflow Runs
- Add a User Interaction to a Workflow
- Set the User Interaction security.group Attribute
- Set the timeout.date Attribute to an Absolute Date
- Calculate a Relative Timeout for User Interactions
- Set the timeout.date Attribute to a Relative Date
- Define the External Inputs for a User Interaction
- Define User Interaction Exception Behavior
- Create the Input Parameters Dialog Box for the User Interaction
- Respond to a Request for a User Interaction
- Calling Workflows Within Workflows
- Running a Workflow on a Selection of Objects
- Developing Long-Running Workflows
- Configuration Elements
- Workflow User Permissions
- Validating Workflows
- Running Workflows
- Generate Workflow Documentation
- Use Workflow Version History
- Restore Deleted Workflows
- Develop a Simple Example Workflow
- Create the Simple Workflow Example
- Create the Schema of the Simple Workflow Example
- Create the Simple Workflow Example Zones
- Define the Parameters of the Simple Workflow Example
- Define the Simple Workflow Example Decision Bindings
- Bind the Action Elements of the Simple Workflow Example
- Bind the Simple Workflow Example Scripted Task Elements
- Define the Simple Workflow Example Exception Bindings
- Set the Read-Write Properties for Attributes of the Simple Workflow Example
- Set the Simple Workflow Example Parameter Properties
- Set the Layout of the Simple Workflow Example Input Parameters Dialog Box
- Validate and Run the Simple Workflow Example
- Develop a Complex Workflow
- Create the Complex Workflow Example
- Create a Custom Action for the Complex Workflow Example
- Create the Schema of the Complex Workflow Example
- Create the Complex Workflow Example Zones
- Define the Parameters of the Complex Workflow Example
- Define the Bindings for the Complex Workflow Example
- Set the Complex Workflow Example Attribute Properties
- Create the Layout of the Complex Workflow Example Input Parameters
- Validate and Run the Complex Workflow Example
- Scripting
- Orchestrator Elements that Require Scripting
- Limitations of the Mozilla Rhino Implementation in Orchestrator
- Using the Orchestrator API
- Access the Scripting Engine from the Workflow Editor
- Access the Scripting Engine from the Action or Policy Editor
- Access the Orchestrator API Explorer
- Use the Orchestrator API Explorer to Find Objects
- Writing Scripts
- Add Parameters to Scripts
- Accessing the Orchestrator Server File System from JavaScript and Workflows
- Accessing Java Classes from JavaScript
- Accessing Operating System Commands from JavaScript
- Exception Handling Guidelines
- Orchestrator JavaScript Examples
- Developing Actions
- Creating Resource Elements
- Creating Packages
- Index
You updated a resource element that the Orchestrator server contains.
Add a Resource Element to a Workflow
Resource elements are external objects that you can import to the Orchestrator server for workflows to use as
attributes when they run. For example, a workflow can use an imported XML file that defines a map to convert
one type of data to another, or a script that defines a function, when it runs.
Prerequisites
Verify that you have the following objects in your Orchestrator server:
n
An image, script, XML, or HTML file, or any other type of object imported into Orchestrator as a resource
element.
n
A workflow that requires the resource element as an attribute.
Procedure
1 From the drop-down menu in the Orchestrator client, select Design.
2 Click the Workflows view.
3 Expand the hierarchical tree viewer to navigate to the workflow that requires the resource element as an
attribute.
4 Right-click the workflow and select Edit.
5 On the General tab, right-click in the attributes pane and select Add attribute.
6 Click the attribute name and type a new name for the attribute.
7 Click Type to set the attribute type.
8 In the Select a type dialog box, type resource in the Filter box to search for an object type.
Option Action
Define a single resource element as
an attribute
Select ResourceElement from the list.
Define a folder that contains multiple
resource elements as an attribute
Select ResourceElementCategory from the list.
9 Click Value and type the name of the resource element or category of resource elements in the Filter text
box.
10 From the proposed list, select the resource element or a folder containing resource elements and click
Select.
11 Click Save and close to exit the editor.
You added a resource element or folder of resource elements as an attribute in a workflow.
Add a Resource Element to a Web View
Resource elements are external objects that you can import into the Orchestrator server for Web views to use
as Web view attributes. Web view attributes identify objects with which Web view components interact.
Prerequisites
Verify that you have the following objects in your Orchestrator server:
n
An image, script, XML, or HTML file, or any other type of object imported into Orchestrator as a resource
element.
Developing with VMware vCenter Orchestrator
140 VMware, Inc.