Attaching a binding to a service
Service consumers are able to access information services using multiple technologies for program interoperability. These technologies are called bindings.
Bindings transfer messages between a service and a client. They are comprised of two parts: the format (SOAP, for example) and the transport method (HTTP, for example). The EJB binding defines both the format and the transport method.
IBM® InfoSphere® Information Services Director allows the same service to support multiple bindings. Bindings improve the utility of services and increase the likelihood of reuse and adoption across the enterprise.
The application that you develop to use services determines which binding you want to attach to that service. Many factors affect which binding you choose. For example, the EJB and Text Over JMS bindings are easier to implement if your application is written in Java because EJB and JMS are Java specifications that do not have native implementations in C# or C++. The other bindings (REST2 and SOAP Over HTTP) are common specifications that most languages can use easily.
Binding support
Binding | Network Deployment | Liberty profile | Not supported in Version 11.3 |
---|---|---|---|
REST | X | ||
REST2 | ✓ | ✓ | |
SOAP over HTTP | ✓ | ✓ | |
Text over HTTP | ✓ | ✓ | |
EJB | ✓ | ||
Text over JMS | ✓ | ||
SOAP over JMS | X |