Exports let a Service Component Architecture (SCA) module
offer a service to others; they define interactions between SCA modules and
service requesters. Export bindings define the specific way that an SCA module is
accessed by others.
Mediation modules are
types of SCA modules.
Interfaces and bindings
An
SCA module export
needs at least one interface.
- Interfaces.
- Export interfaces are abstract definitions. They define access points.
- Export interfaces are defined using Web Services Description Language
(WSDL), an XML language for describing Web services.
- An SCA module can
have many export interfaces.
- Bindings.
- Export bindings are concrete definitions. They specify the physical mechanism
that service requesters use to access a service.
- Typically, an SCA module export
has one binding specified. An export with no binding specified is interpreted
by the runtime as an export with an SCA binding.
Supported export bindings
WebSphere ESB supports
the following export 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).