HTTP Client Connector

Note: Before working with the HTTP Client connector, you should be familiar with general process development.

The HTTP Client connector allows you to exchange data with HTTP-enabled servers via the HTTP or HTTPS (Hyper Text Transfer Protocol [Secure]) protocols.

The HTTP Client connector is not Web Services or SOAP. It can be used to get and send generic data (often in XML, but not necessarily) via HTTP(S) using basic HTTP commands. One popular use case is to exchange proprietary XML data via HTTP(S) in lieu of investing the time and effort to develop full-blown Web Services according to the SOAP specification.

The HTTP Client connector can be used to send or retrieve messages via HTTP(S), however, it cannot "listen" for outbound messages from another application. For this kind of real-time or event-based integration, use the Web Services Server connector.

Connector Configuration

Configuring a connector to communicate with an HTTP-enabled server requires the setup of two different components:

• HTTP Client Connection
• HTTP Client Operation

This design allows for reusability of the components, which contain connection settings such as URL, username, password, etc. Once your connection and connector operation are built, you will need to set up your connector within the process. Once the HTTP Client connector is configured properly within your process, Dell Boomi AtomSphere will be able to map to and from virtually any system using the connector to exchange data via HTTP.

Prerequisites

If you are connecting to a secure site (i.e., the URL begins with https) that does not use a certificate signed by a trusted root authority such as Verisign or Thawte, you will need to obtain a copy of the site's public certificate and import it into your AtomSphere account. Once imported, it will be applied implicitly whenever the connector connects to that site. However, if the site does use a certificate from a trusted root authority, you do not need to import the certificate; it will be applied automatically by AtomSphere.

See Also:

What is HTTP?