VMware vCenter Orchestrator SOAP Plug-In 1.0 Release Notes

What's in the Release Notes

• Introduction to the VMware vCenter Orchestrator SOAP Plug-In
• Known Issues

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 release runs on VMware vCenter Orchestrator 4.1 and the subsequent update releases. For instructions about installing and configuring the plug-in, see Using the vCenter Orchestrator SOAP Plug-In 1.0.x.

Top of Page

Known Issues

The following issues are known limitations in the VMware vCenter Orchestrator SOAP Plug-In 1.0 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.

• Updating a SOAP host 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