VMware vCenter Orchestrator Appliance Release Notes

What's in the Release Notes

• Introduction to the VMware vCenter Orchestrator Appliance
• Known Issues

Introduction to the VMware vCenter Orchestrator Appliance

VMware vCenter Orchestrator is now available as a preconfigured virtual appliance. This appliance significantly reduces the time and skills required to deploy vCenter Orchestrator and provides a low-cost alternative to the traditional Windows-based installation.

The vCenter Orchestrator appliance is distributed as an OVF (Open Virtual Machine Format). It is pre-built and pre-configured with Novell SUSE Linux Enterprise Server, PostgreSQL, and OpenLDAP, and it can be used with vCenter Server 4.1 and later.

The vCenter Orchestrator appliance offers great flexibility and uncompromised performance, making it ideal for any use case from lab evaluation to large-scale production use. The appliance offers all of the components included in the regular Windows-based installation, along with the flexibility to use either the pre-built directory services and database, or to use external ones like Active Directory or Oracle. What's more, the appliance has been certified to run at the same performance level as the traditional version.

The vCenter Orchestrator appliance makes it even faster, easier, and more affordable to integrate the VMware cloud stack, including vCenter Server and vCloud Director, with your IT processes and environment.

For instructions about deploying and using the Orchestrator appliance, see Using the vCenter Orchestrator Appliance.

Known Issues

The following issues are known limitations in the VMware vCenter Orchestrator 4.2 appliance release:

• New A generated URL requiring user interaction might lead to an error of the type: Error: 500
  When you run a workflow that sends an email with a URL requiring a user interaction, and you click the URL, it opens the weboperator Web view page with an error of the type: Error: 500.
  Workaround: To make the URL open the weboperator Web view correctly, add the com.vmware.o11n.webview.htmlescaping.disabled=true property to the vmo.properties file. By default, the vmo.properties file is located in /opt/vmo/app-server/server/vmo/conf.
• Usage of the Orchestrator client through Java WebStart if the Orchestrator appliance is behind Network Address Translation (NAT) is not supported
• Usage of the Orchestrator Client through Java WebStart if you have the Java Runtime Environment (JRE) 7 on your machine is not supported
  If the Java Runtime Environment (JRE) on your machine is of version 7, when you click the Start Orchestrator Client on the Orchestrator appliance home page, the Orchestrator client starts, but when you type in your credentials and the Orchestrator client attempts to connect to the server, the window disappears with no error.
• The Orchestrator configuration interface is not loaded properly in Internet Explorer 9
  When you log in to the Orchestrator configuration interface in Internet Explorer 9, and click a tab, the page that you see might contain missing styles or scripts, as well as broken links.
  
  Workaround: Open the Orchestrator configuration interface in a supported Web browser, such as Internet Explorer 7.0, Mozilla Firefox 3.0 (build 3.0.6 or later), or Mozilla Firefox 3.5.