Exports define interactions between Service Component Architecture (SCA)
modules and
service requesters. SCA modules use
exports to offer services to others. Export bindings define the specific
way that an SCA module is
accessed by service requesters.
Interfaces and bindings
An
SCA module export
needs at least one interface.
- Export interfaces are abstract definitions that define a set of
operations using Web Services Description Language (WSDL), an XML
language for describing Web services. An SCA module can have
many export interfaces.
- Export bindings are concrete definitions that specify the physical
mechanism that service requesters use to access a service. Usually,
an SCA module export
has one binding specified. An export with no binding specified is
interpreted by the run time as an export with an SCA binding.
Supported export bindings
WebSphere® ESB supports
the following export bindings:
- Web Service bindings permit exports to be invoked as Web services.
The supported protocols are SOAP/HTTP and SOAP/JMS. A Web services
binding that uses SOAP/JMS, supports JMS using the default WebSphere
Application Server default messaging provider in a point-to-point
configuration. The SOAP/JMS binding does not support: generic JMS,
MQ JMS, or the JMS broadcast mode.
- 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 permit
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 permit interoperability
with WebSphere MQ based JMS providers. The JMS
Message class and its five subtypes (Text, Bytes, Object, Stream,
and Map) are automatically supported. If you want to use WebSphere MQ as a JMS provider you might
have WebSphere MQ JMS bindings.
- WebSphere MQ bindings permit interoperability
with WebSphere MQ. A remote (or client) connection
is the type of connection needed to connect to an MQ queue manager
on a remote machine. A local (or bindings) connection is a direct
connection to WebSphere MQ. This can only be used for
a connection to a MQ queue manager on the same machine. WebSphere MQ will permit both types of
connection, But MQ bindings only support the "remote" (or "client")
connection.
- Generic JMS bindings permit interoperability with third-party
JMS providers that integrate with the WebSphere Application Server
using the JMS Application Server Facility (ASF).
- WebSphere Adapters bindings permit interaction
with Enterprise Information Systems (EIS).
- HTTP bindings permit exports to be accessed using the HTTP protocol.