This topic applies only to the IBM Business Automation Workflow Advanced configuration.

HTTP bindings overview

Edit online
Draft comment:
This topic only applies to BAW, and is located in the BAW repository. Last updated on 2025-03-13 12:15
Draft comment:
This topic was viewed 7 times since its publication
The HTTP binding provides connectivity to HTTP-hosted applications. It mediates communication between HTTP applications and allows existing HTTP-based applications to be called from a module.

HTTP import bindings

The HTTP import binding provides outbound connectivity from Service Component Architecture (SCA) applications to an HTTP server or applications.

The import invokes an HTTP endpoint URL. The URL can be specified in one of three ways:
  • The URL can be set dynamically in the HTTP headers by way of the dynamic override URL.
  • The URL can be set dynamically in the SMO target address element.
  • The URL can be specified as a configuration property on the import.
This invocation is always synchronous in nature.

Although HTTP invocations are always request-reply, the HTTP import supports both one-way and two-way operations and ignores the response in the case of a one-way operation.

HTTP export bindings

The HTTP export binding provides inbound connectivity from HTTP applications to an SCA application.

A URL is defined on the HTTP export. HTTP applications that want to send request messages to the export use this URL to invoke the export.

The HTTP export also supports pings.

HTTP bindings at run time

An import with an HTTP binding at run time sends a request with or without data in the body of the message from the SCA application to the external web service. The request is made from the SCA application to the external web service, as shown in Figure 1.
Figure 1. Flow of a request from the SCA application to the web application
Illustration of the request and optional response flow between an SCA application and a web application.

Optionally, the import with the HTTP binding can receive data back from the web application in a response to the request.

With an export, the request is made by a client application to a web service, as shown in Figure 2.
Figure 2. Flow of a request from the client application to the web service.
Illustration of the request and optional response flow between a web service and a client application.

The web service is a web application running on the server. The export is implemented in that web application as a servlet so the client sends its request to a URL address. The servlet passes the request to the SCA application in the runtime.

Optionally, the export may send data to the client application in response to the request.