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
File Structure of a Web View 4
When you develop a Web view, you must save the collection of Web pages and Web view components that
comprise the Web view to a working folder. The Web view working folder must conform to basic file-
naming and file-structuring rules.
You can name the working folder in which you develop the Web view pages and components any name
that is appropriate. The working folder must contain the following file and folder at its root.
Table 4‑1. Web view file structure
File Description
<WebView_Folder>\default.html
The home page of the Web view. All Web views must
include a default.html file at the root of the working
folder.
<WebView_Folder>\components\
Contains the JWC files and the associated HTML templates
of the Web view components. The components folder must
be at the root of the working folder.
IMPORTANT If you create more than one Web view to run in the same Orchestrator server, you must save the
Web view components in subfolders inside the components folder, to avoid conflicts between identically
named components. Alternatively, create all Web view components with a unique name.
The default.html file and the components folder are the only mandatory elements that a Web view must
contain. You can add other files and folders in the Web view folder and organize the files and folders in any
way. You can include HTML files that are not Web view component templates anywhere in the Web view
folder.
VMware, Inc.
21