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
Web View Home Page 5
All Web views must contain a file named default.html, that you must save at the root of the Web view
working folder. The default.html file is the home page of the Web view.
The default.html file is the point of entry to a Web view. The default Web view template that Orchestrator
provides contains a skeleton default.html file that you can adapt and extend. The following code extract
shows the contents of the default.html file from the default Web view template.
<vco jwcid="@layout/MyBorder" section="literal: home" title="Home">
<!-- Content of the homepage -->
<h2 style="margin-left: 16px; margin-top: 0px; padding-top:18px;">
Welcome to the default Web view template
</h2>
<p style="margin-left: 16px;">
This Web view template is a base for your own Web view development.
</p>
</vco>
Table 5‑1. Contents of the Web View Template default.html File
Code Description
<vco></vco> tags
You can insert Web view components in any type of HTML
tag. The Web view template wraps all its content in <vco>
tags, to show that this code is specific to Orchestrator.
jwcid="@layout/MyBorder" A reference to the MyBorder Web view component from
the default Web view template. The MyBorder component
defines the borders of the Web view pages.
title="Home"
The title that appears in the title bar of the Web view home
page.
The rest of the code in the default.html file is standard HTML. You can extend and adapt the content of the
home page by adding HTML code and add functions to the page by adding Web view components.
VMware, Inc.
23