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

Imports and exports

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
The components used for Service Component Architecture (SCA) module to module and SCA module to external service invocation are called imports and exports. Imports and exports are represented from the point of view of the module.

A module exports its capability when it provides the ability for an external service or module to invoke an operation on a defined interface. Using exports, a module can be made available over a number of different transport protocols.

The module imports a function to use the ability of another entity (external service or module). Using imports, a module can interact with service providers across a variety of transport protocols. Figure 1 shows an import and export within an SCA module.
Figure 1. SCA module
Structure of an SCA module
Imports and exports also have the ability to interact with service providers across a variety of protocols and Application Programming Interfaces (APIs), such as:
  • SCA (used for SCA module to module)
  • Web service
  • JMS
  • MQ
  • HTTP
  • Enterprise JavaBeans
Figure 2 shows how module to module communication can be achieved using imports and exports. The StockQuote service exposes its implementation using an export. The PortfolioManager module invokes the StockQuote implementation using an import.
Figure 2. Module to module communication using imports and exports
how module to module communication can be achieved using imports and exports.
When imports and exports are bound to protocols such as JMS, Enterprise JavaBeans, or web services, the specific clients can invoke an SCA module, or an SCA module can invoke an existing Enterprise JavaBeans, JMS messaging engine or web service using the SCA programming model. A module can use different protocols to communicate, as displayed in Figure 3.
Figure 3. Module using different protocols to communicate
Module can use different protocols to communicate
Import and export bindings must be configured to control invocations, and to control how data is handled across SCA module bindings. These are the common configuration options available across bindings:
  • Function selectors
  • Data handlers
  • Fault selector
  • Fault handler
  • Context propagation
  • Exception handling