IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Get started with IBM Integration Designer > SCA > Imports and exports
Selecting appropriate bindings
When you are creating an application, you need to know how to select the binding that is most appropriate to the needs of your application.
The bindings available in IBM Integration Designer provide a range of choices. In this list, you can determine which type of binding might be most suitable for the needs of your application.
Consider a SCA binding when these factors are applicable:
- All services are contained in modules; that is, there are no external services.
- You want to separate function into different SCA modules that interact directly with each other.
- The modules are tightly coupled.
Consider a Web Service binding when these factors are applicable:
- You need to access an external service over the Internet or provide a service over the Internet.
- The services are loosely coupled.
- Synchronous communication is preferred; that is, a request from one service can wait for a response from another.
- The protocol of the external service you are accessing or the service you want to provide is SOAP/HTTP or SOAP/JMS.
Consider an HTTP binding when these factors are applicable:
- You need to access an external service over the Internet or provide a service over the Internet and you are working with other web services such as GET, PUT, and DELETE.
- The services are loosely coupled.
- Synchronous communication is preferred; that is, a request from one service can wait for a response from another.
Consider an Enterprise JavaBeans (EJB) binding when these factors are applicable:
- The binding is for an imported service that is itself an EJB or that needs to be accessed by EJB clients.
- The imported service is loosely coupled.
- Stateful EJB interactions are not required.
- Synchronous communication is preferred; that is, a request from one service can wait for a response from another.
Consider an Enterprise Information Systems (EIS) binding when these factors are applicable:
- You need to access a service on an EIS system using a resource adapter.
- Synchronous data transmission is preferred over asynchronous.
Consider a Java Message Service (JMS) binding when these factors are applicable:
There are several types of JMS bindings. If you expect to exchange SOAP messages using JMS, consider the web service binding with the SOAP/JMS protocol. See Web service bindings.
- You need to access a messaging system.
- The services are loosely coupled.
- Asynchronous data transmission is preferred over synchronous.
Consider a Generic Java Message Service (JMS) binding when these factors are applicable:
- You need to access a non-IBM vendor messaging system.
- The services are loosely coupled.
- Reliability is more important than performance; that is, asynchronous data transmission is preferred over synchronous.
Consider an Message Queue (MQ) binding when these factors are applicable:
- You need to access a WebSphere MQ messaging system and need to use the MQ native functions.
- The services are loosely coupled.
- Reliability is more important than performance; that is, asynchronous data transmission is preferred over synchronous.
Consider an MQ JMS binding when these factors are applicable:
- You need to access a WebSphere MQ messaging system but can do so within a JMS context; that is, the JMS subset of functions is sufficient for your application.
- The services are loosely coupled.
- Reliability is more important than performance; that is, asynchronous data transmission is preferred over synchronous.
Related concepts:
Service import and export binding types