Imports let a Service Component Architecture (SCA) module
access external services, (services that are outside the SCA module)
as if they were local. Imports define interactions between SCA modules and
service providers. 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
WebSphere ESB supports
the following import bindings.
- Web Service Bindings
- SCA Bindings
- SCA modules can
have SCA bindings. SCA bindings connect SCA modules to
other SCA modules.
- Java Message Service (JMS) 1.1 Bindings
- JMS allows interoperability with the WebSphere family.
- JMS can exploit various transport types, including: TCP/IP and HTTP(S).
- There are predefined JMS bindings that support JMS text messages containing
Business Object (BO) XML. The predefined JMS bindings also support JMS object
messages containing serialized Java Business Objects.
- You can use JMS custom bindings to support other types of JMS message.
However, custom bindings require some coding to translate the message.
- WebSphere Adapter Bindings
- WebSphere Adapters enable interaction with Enterprise Information Systems
(EIS).