VMware vCenter Orchestrator HTTP-REST Plug-In 1.0.3 Release Notes
VMware vCenter Orchestrator HTTP-REST Plug-In 1.0.3 | 13 Dec 2013 | Build 337
VMware vCenter Orchestrator 5.5 | 22 Sep 2013 | Build 1281930
VMware vCenter Orchestrator 5.1 | 10 Sep 2012 | Build 2725
VMware vCenter Orchestrator 4.2 | 24 Aug 2011 | Build 5277
Check frequently for additions and updates to these release notes.
What's in the Release Notes
The release notes cover the following topics:
Introduction to the VMware vCenter Orchestrator HTTP-REST Plug-In
The VMware vCenter Orchestrator HTTP-REST plug-in allows organizations to integrate their cloud provisioning and operations use cases with systems that offer RESTfull Web services. Provisioning a virtual machine or requesting a cloud-hosted IT service, often is part of a larger IT process that includes various management systems, such as service desk, change management, IP address management, CMDB, or configuration management. With the HTTP-REST plug-in, organizations can integrate vSphere and vCloud Director into automated processes that use third-party REST APIs. The workflow developers can create workflows in just a few clicks and hide the complexity of the underlying API.
The HTTP-REST plug-in supports multiple authentication methods to enable secure integration with most applications that expose a REST API.
The VMware vCenter Orchestrator HTTP-REST Plug-In 1.0.3 release runs on VMware vCenter Orchestrator 4.2, 5.1, and 5.5. For instructions about installing and configuring the plug-in, see Using the vCenter Orchestrator HTTP-REST Plug-In 1.0.x.
Top of Page
What's New in VMware vCenter Orchestrator HTTP-REST Plug-In 1.0.3
Version 1.0.3 of the HTTP-REST plug-in improves performance and adds vCloud Director 5.1 authentication support and support for invoking REST operations by using a proxy server. To upgrade the plug-in, you must install version 1.0.3 on top of your existing installation. You can download version 1.0.3 from the VMware vCenter Orchestrator HTTP-REST Plug-In download page.
Top of Page
Earlier Releases of the VMware vCenter Orchestrator HTTP-REST Plug-In
Features and issues from earlier releases of the HTTP-REST plug-in are described in the release notes for each release. To review release notes for earlier releases of the HTTP-REST plug-in, click one of the following links:
Top of Page
The following issues were resolved in the VMware vCenter Orchestrator HTTP-REST Plug-In 1.0.3 release:
RESTHostValidator constructor throws an exception when you provide URLs with local top-level domains (TLDs).
Top of Page
The following issues are limitations that are known to occur in the VMware vCenter Orchestrator HTTP-REST Plug-In 1.0.3 release:
- Attempts to add a schema to a host do not work over HTTPS connection
You cannot add an XSD shema to a REST host over an HTTPS connection. To associate an XSD schema with a REST host, you must provide the URL of the schema, or the schema content as text. The URL of the schema must not point to a secure HTTP server. The referenced dependency schema inside the URL must not be from a secure HTTP server.
- The import of hosts with same name from different packages might be problematic
If you import HTTP-REST plug-in configuration packages created with version 1.0 of the plug-in that contain different hosts with the same names, just one of the hosts appears in the inventory. All generated workflows from the packages bind to the loaded host.
Note: This issue does not occur with packages created with version 1.0.1 of the plug-in.
- Limited number of operation input parameters
You cannot specify more than 15 input parameters when you run the Invoke a REST operation workflow.
Workaround: Generate a new workflow from a REST operation for operations with more than 15 input parameters.
- Attempts to add a schema to a host might be slow
If you add an XSD schema to a host, the operation might take a considerable amount of time depending on the schema size, the number of imports, and the connection to the server hosting the schema.
- Attempts to generate a workflow from an operation with attached schema might be slow
When you generate a workflow from an operation that has an XSD schema attached to it for the first time, the operation might take a considerable amount of time.
- The usage of a schema might cause problems with arrays
When you generate a workflow from a POST or PUT operation that contains an array of elements as input, if an XSD schema is used to generate the presentation, the workflow shows only one element instead of an array.
- The update or clone of a REST host might be slow
Operations that involve updating or cloning a host might take a considerable amount of time, depending on the size of the data that is loaded for the presentation.
Top of Page