4.2
Table Of Contents
- Developing with VMware vCenter Orchestrator
- Contents
- Developing with VMware vCenter Orchestrator
- Updated Information
- Developing Workflows
- Principal Phases in the Workflow Development Process
- Accessing the Orchestrator Client
- Testing Workflows During Development
- Workflow Editor
- 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
- Develop a Simple Example Workflow
- Create the Simple Workflow Example
- Define the Simple Workflow Example Parameters
- Create the Simple Workflow Example Schema
- Link the Simple Workflow Example Elements
- Create Workflow Zones
- Define the Simple Workflow Example Decision Bindings
- Bind the Simple Workflow Example Action Elements
- Bind the Simple Workflow Example Scripted Task Elements
- Define the Simple Example Workflow Exception Bindings
- Set the Simple Workflow Example Attribute Read-Write Properties
- 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
- Define the Complex Workflow Example Input Parameters
- Create a Custom Action For the Complex Workflow Example
- Create the Complex Workflow Example Schema
- Link the Complex Workflow Example Schema Elements
- Create the Complex Workflow Example Zones
- Define the Complex Workflow Example Bindings
- 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
What to do next
Import and edit a resource element.
Import an External Object to Use as a Resource Element
Workflows and Web views can require as attributes objects that you create independently of Orchestrator. To
use external objects as attributes in workflows or Web views, you import them to the Orchestrator server as
resource elements.
Prerequisites
An image file, script, XML template, HTML file, or other type of object to import.
Procedure
1 In the Orchestrator client, click the Resources view.
2 Right-click a resource folder in the hierarchical list or the root and select New folder to create a folder in
which to store the resource element.
3 Right-click the resource folder in which to import the resource element and select Import resources.
4 Select the resource to import and click Open.
Orchestrator adds the resource element to the folder you selected.
You imported a resource element into the Orchestrator server.
What to do next
Edit the general information of the resource element and set the user access permissions.
Edit the Resource Element Information and Access Rights
After you import an object into the Orchestrator server as a resource element, you can edit the resource
element's details and permissions.
Prerequisites
An image, script, XML, or HTML file, or any other type of object that you imported into Orchestrator as a
resource element.
Procedure
1 Right-click the resource element and select Edit.
2 Click the General tab and set the resource element name, version, and description.
3 Click the Permissions tab and click the Add access rights link to define permissions for a user group.
4 Type a user group name in the Filter text box.
5 Select a user group and click OK.
6 Right-click the user group and select Add access rights.
7 Check the appropriate check boxes to set the level of permissions for this user group and click OK.
Permissions are not cumulative. To allow a user to view the resource element, use it in their workflows
or Web views, and change the permissions, you must check all check boxes.
8 Click Save and Close to exit the editor.
You edited the general information about the resource element and set the user access rights.
Developing with VMware vCenter Orchestrator
124 VMware, Inc.