Imports and import bindings

Imports define interactions between Service Component Architecture (SCA) modules and service providers. Imports let SCA modules access external services, (services that are outside the SCA module) as if they were local. Import bindings define the specific way that an external service is accessed.

SCA modules are not required to have imports, if they do not need to access external services. Mediation modules are types of SCA modules.

Interfaces and bindings

An SCA module import needs at least one interface, and an SCA module import has only one binding.
  • Interfaces.
    • Import interfaces are abstract definitions. They define access points.
    • Import interfaces are defined using Web Services Description Language (WSDL), an XML language for describing Web services.
    • An SCA module can have many import interfaces.
  • Bindings.
    • Import bindings are concrete definitions. They specify the physical mechanism that SCA modules use to access an external service.

Supported import bindings

enterprise service bus supports the following import bindings.
  • Web Service Bindings
    • Web Service bindings allow you to access web services.
    • The supported protocols are SOAP/HTTP and SOAP/JMS.
  • SCA Bindings
    • SCA bindings connect SCA modules to other SCA modules.
    • SCA bindings are also referred to as default bindings.
  • Java Message Service (JMS) 1.1 Bindings
    • JMS bindings allow interoperability with the WebSphere Application Server default messaging provider.
    • JMS can exploit various transport types, including TCP/IP and HTTP(S).
    • The JMS Message class and its five subtypes (Text, Bytes, Object, Stream, and Map) are automatically supported.
  • WebSphere MQ JMS Bindings
    • WebSphere MQ JMS bindings allow interoperability with WebSphere MQ based JMS providers.
    • You might have WebSphere MQ JMS bindings if you want to use WebSphere MQ as a JMS provider.
    • The JMS Message class and its five subtypes (Text, Bytes, Object, Stream, and Map) are automatically supported.
  • WebSphere MQ Bindings
    • WebSphere MQ bindings allow interoperability with WebSphere MQ.
    • You might have WebSphere MQ bindings if you want to communicate with native WebSphere MQ applications.
    • You can use WebSphere MQ bindings only with remote queue managers via a WebSphere MQ client connection; you cannot use them with local queue managers.
  • WebSphere Adapter Bindings
    • WebSphere adapters bindings enable interaction with Enterprise Information Systems (EIS).

Last updated: Wed 06 Dec 2006 07:08:08

(c) Copyright IBM Corporation 2005, 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)