VMware vCenter Orchestrator SOAP Plug-In 1.0.3 Release Notes
VMware vCenter Orchestrator SOAP Plug-In 1.0.3 | 13 Dec 2013 | Build 334
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 SOAP Plug-In
The VMware vCenter Orchestrator SOAP plug-in allows organizations to integrate their cloud provisioning and operations use cases with systems that offer 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 SOAP plug-in, organizations can integrate vSphere and vCloud Director into automated processes that use third-party-system SOAP APIs.
The SOAP plug-in provides the ability to query a URI or import a target application’s WSDL directly into the Orchestrator client. This enables workflow developers to browse the WSDL and create workflows from SOAP operations.
The SOAP plug-in supports SSL authentication to provide secure communication with third-party systems.
The VMware vCenter Orchestrator SOAP 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 SOAP Plug-In 1.0.x.
Top of Page
What's New in VMware vCenter Orchestrator SOAP Plug-In 1.0.3
Version 1.0.3 of the SOAP plug-in improves performance and adds support for invoking SOAP 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 SOAP plug-in download page.
Top of Page
Earlier Releases of the VMware vCenter Orchestrator SOAP Plug-In
Features and issues from earlier releases of the SOAP plug-in are described in the release notes for each release. To review release notes for earlier releases of the SOAP plug-in, click one of the following links:
Top of Page
The following issues were resolved in the VMware vCenter Orchestrator SOAP Plug-In 1.0.3 release:
- When you send a request by using basic HTTP authentication to a remote host that expects preemptive authentication, you receive an HTTP 401 error.
SOAPHostManager.getHosts() method returns an empty list after you restart the Orchestrator server.
- Parameters that contain the
. character in their names might cause issues.
SOAPHostValidator constructor rejects top-level domains (TLDs) with more than 4 characters.
- Resolving imported schemas might cause issues.
- If you run the Add a SOAP host workflow multiple times simultaneously, you might receive the
Cannot convert to object, reason : Unable to perform operation 'find' error message.
SOAPRequest.setInHeader method cannot set a header value for some custom SOAP headers.
- When you try to add a SOAP host, you might receive the
XmlSchemaAttributeGroupRef cannot be cast to org.apache.ws.commons.schema.XmlSchemaAttribute error message.
Top of Page
The following issues are limitations that are known to occur in the VMware vCenter Orchestrator SOAP plug-in 1.0.3 release:
- Relative path imports prevent host addition
You cannot add hosts if you use raw XML content that contains relative path imports.
- Limited number of operation input parameters
You cannot specify more than 15 input parameters when you run the Invoke a SOAP operation workflow.
Workaround: Generate a new workflow from a SOAP operation for operations with more than 15 input parameters.
- SOAP host updates might be slow
If you update a host with a large WSDL file, the operation might take a considerable amount of time.
- SOAP 1.1 has higher priority than SOAP 1.2
If the service from your WSDL file defines two ports for different SOAP versions, one for SOAP 1.1 and one for SOAP 1.2, the port for SOAP 1.1 is used.
- Port priority inside services with multiple ports
If the service from your WSDL file defines two or more ports for the same SOAP version, the first port from the WSDL file might not be the used.
- Supported WSDL style/use models
The plug-in supports Document/literal and RPC/literal WSDL models.
Top of Page