Exports define interactions between Service Component Architecture (SCA) modules and
service requesters. Exports let SCA modules offer
services to others. Export bindings define the specific way that an SCA module is
accessed by service requesters.
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
enterprise service bus supports
the following export 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)