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 Overview 1
A Web view is a package of Web pages, style sheets, icons, and banners that represent a complete Web site.
Web views can contain special Java Web Components (JWC) that add Orchestrator functions to the pages of
the Web views. For example, you can add components that allow users to run workflows from a browser.
Orchestrator Web views update content dynamically without obliging users to reload complete pages.
Orchestrator provides a library of Tapestry Framework 4.0 components to help you build customized Web
views to access Orchestrator functions from a Web browser. Tapestry components provide access to objects
in the Orchestrator server, such as the workflows in the library and the virtual machines in the inventory.
You can also insert Dojo 0.4.1 components into Web views.
Orchestrator provides a Web view template that you can use as the basis for developing Web views. The
Web view template contains skeleton HTML pages and Web view components that you can extend and
adapt. You can also export existing Web views to use as templates that you can adapt to create new Web
views.
You typically create or modify the pages of a Web view externally by using Web design tools. Creating or
modifying Web pages independently of Orchestrator allows you to separate the Web design process from
the process of developing Orchestrator Web view components. You import the Web view pages and
components into the Orchestrator server and complete the process of creating the Web view in the
Orchestrator client.
Developing Orchestrator Web views can require knowledge of some or all of the following Web
development technologies and standards. For documentation about the different technologies, consult the
Web sites of the organizations that maintain the standards.
n
Cascading stylesheets (CSS). See http://www.w3.org/Style/CSS/.
n
Ajax platform. See http://www.ajax.org/.
n
Dojo toolkit. See http://www.dojotoolkit.org/.
n
Java programming language. See http://www.oracle.com/technetwork/java/index.html.
n
Java Web Components (JWC) from the Tapestry Framework. See http://tapestry.apache.org/.
n
JavaScript Object Notation (JSON). See http://www.json.org/.
n
Object-Graph Navigation Language (OGNL). See http://www.opensymphony.com/ognl/.
NOTE Third-party URLs are subject to changes beyond the ability of VMware to control. If you find a URL
in VMware documentation that is out of date, notify VMware at docfeedback@vmware.com. You might be
able to locate a third-party document by searching from the third-party home page.
VMware, Inc.
7