5.5
Table Of Contents
- Developing Web Views for VMware vCenter Orchestrator
- Contents
- Developing Web Views for VMware vCenter Orchestrator
- Web View Overview
- Weboperator Web View
- Web View Development Tasks to Perform in Orchestrator
- Create a Web View Skeleton
- Export a Web View as a Template
- Create a Web View from a Template
- Define a Web View Template as a Resource Element
- Create a Web View from a Resource Element Template
- Export Web View Files to a Working Folder
- Configure the Server for Web View Development
- Import Web View Files from a Working Folder
- Create a Web View Attribute
- Add a Resource Element to a Web View
- Disable Web View Development Mode
- Publish a Web View
- File Structure of a Web View
- Web View Home Page
- Web View Components
- Tapestry Web View Components
- Creating Tapestry Web View Components
- Orchestrator Tapestry Component Library
- vco:DisplayProperty Component
- vco:IfMemberOf Component
- vco:IncludeJavascript Component
- vco:IncludeStylesheet Component
- vco:IncludeWorkflowHeader Component
- vco:ListPane Component
- vco:Login Component
- vco:PageAccessControl Component
- vco:TaskAction Component
- vco:WebformContainer Component
- vco:WorkflowLink Component
- Accessing Server Objects from URLs
- Create a Simple Web View Using the Default Template
- Import the Default Web View Template
- Export the Virtual Machine Manager Web View to a Working Folder
- Provide Unique Component Names
- Configure the Server for Web View Development
- Edit the Virtual Machine Manager Web View Home Page
- Add a vco:ListPane Component to the Web View Home Page
- Define the Web View Attributes for the vco:ListPane Component
- Create a Web View Component to Display Virtual Machine Information
- Create a Web View Tab by Using the Menu Component
- Add Links to Run Workflows from a Web View by Using the vco:WorkflowLink Component
- Customize the Web View Interface
- Publish the Virtual Machine Manager Web View
- Index
Add a Tapestry Component in an HTML Page
You add Tapestry components to a Web view by adding a jwcid attribute to an HTML tag in a Web page.
The jwcid attribute references a Web view component.
You can add a jwcid attribute to any HTML tag. You can add references to components from the
Orchestrator Web view component library, to components from the Tapestry Standard, or to custom
components that you create.
Prerequisites
Create a Web view in the Orchestrator client and exported its contents to a working directory.
Procedure
1 Open an HTML page of a Web view in an HTML editor.
2 Add an arbitrary tag to the HTML file, in the position at which the Web view component is to appear in
the page.
For example, add the following arbitrary tag in the appropriate position in the HTML file:
<vco>
3 Add to the arbitrary tag a jwcid attribute that references a Web view component.
For example, the following jwcid attribute adds the vco:DisplayProperty component from the
Orchestrator library to the Web view.
<vco jwcid="@vco:DisplayProperty">
The vco:DisplayProperty component obtains and displays the properties of an object that is in the
server in the Web view.
4 Add the additional properties that the component requires to the arbitrary HTML tag.
For example, the following Web view component displays the MyVirtualMachine virtual machine Name
property in a Web view.
<vco jwcid="@vco:DisplayProperty" name="Name" property="MyVirtualMachine"/>
You added a reference to a Web view component to a Web page in a Web view.
Creating Tapestry Web View Components
With Orchestrator, you can create custom Tapestry Web view components to perform orchestration
functions from Web pages. A Tapestry Web view component conforms to the Tapestry Framework standard
version 4.0.
A Tapestry Web view component must contain a component specification file and a component template.
IMPORTANT The Tapestry component template file and the component specification must have the same
name. For example, if you name a component template MyComponent.html, you must name the associated
component specification MyComponent.jwc. Web view components that you use in different Web views that
run in the same server must have unique names.
Developing Web Views for VMware vCenter Orchestrator
26 VMware, Inc.