Web Services SOAP Client Connector

Note: Before working with the Web Services SOAP Client connector, you should be familiar with general Process Development

The Web Services SOAP Client Connector is a generic Connector that enables you to easily integrate with any web-based or on-premise application that exposes a SOAP web services interface. The Connector browses the list of services or messages supported by the specific web service in real time (those defined in the WSDL). The types of messages are only limited by the web service itself.

To the extent possible, the technical details of this connection such as SOAP headers, error handling, HTTPS authentication, XML syntax, etc. are all abstracted from the user to make implementation quick and easy. The connector operates in a request/response manner and does not support "listening" for outbound messages from the web service application.

Note: Although web services is a standard, there are a number of ways it can actually be implemented, some more generically than others. Consequently the Connector works best with web services that adhere to the WS-I Basic Profile 1.1 specification. See the Supported Versions section below for more information

Review the Common Applications listing below to see applications that our user base can integrate with this connector.

Connector Configuration

Configuring a connector to communicate with a web services requires the setup of two different components:

This design allows for reusability of the components, which contain connection settings such as user name, password, etc. Once your connection and connector operation are built, you will need to set up your connector within the process model. When your connector is configured properly within your process, Boomi AtomSphere will be able to map to and from virtually any system using the Web Services SOAP Client Connector to retrieve data from or send data to the application.

Supported Versions

Any web service implementation that follows the WS-I Basic Profile 1.1 specification, such as Apache Axis, .Net, StrikeIron, etc. Also referred to as "document" or "literal" style.
- Document-Literal
- RPC-Literal
Web services that use WS-Security with the simple user name/password option for authentication

Current Limitations

RPC/SOAP-Encoded styles are not supported.
No ability to set values in SOAP Headers.
No choreographed calls or session persistence. Every call must be an independent, self-contained action. This is most relevant to authentication. If the web services requires authentication, the necessary credentials like user name and password must be able to be passed within the request itself.
If the web service uses SSL, it must use a trusted root certificate. Proprietary certificates are not supported at this time.
The WSDL and associated schemas must be accessible via a publicly- or locally-accessible URL. If the WSDL is a local URL, a local Atom must be installed. File upload of the WSDL and/or XSD schemas is not supported.

Prerequisites

The URL to connect to the web service and WSDL. The URL to the WSDL is usually the same as the web service with "?WSDL" appended.

The web service URL is typically different than the URL you go to log into the user interface.

Common Applications

The Web Services SOAP Client Connector allows you develop integrations against a variety of SOAP-enabled applications. The list below includes common applications that our user base has integrated. Review any of the links to see integration Best Practices and development tips.

Siebel

Additional Resources:

WS-I Basic Profile 1.1 Specification
W3Schools Web Services Tutorial
Apache Axis
.Net