1. SCA: The SCA binding, which is the default, lets your service communicate with services in other SCA You use an import with an SCA binding to access a service in another SCA module. You use an export with an SCA binding to offer a service to other SCA modules.

2. Web service: A Web service binding lets you access an external service using interoperable SOAP messages and qualities of service. You can ALSO use Web service bindings to include attachments as part of the SOAP message.

The Web service binding can use a transport protocol of either SOAP/HTTP (SOAP over HTTP) or SOAP/JMS (SOAP over JMS). Regardless of the transport (HTTP or JMS) used to convey the SOAP messages, Web service bindings always handle request/response interactions synchronously.

1. HTTP: The HTTP binding lets you access an external service using the HTTP protocol, where non-SOAP messages are used, or where direct HTTP access is required. This binding is used when you are working with Web services that are based on the HTTP model (that is, services that use well-known HTTP interface operations such as GET, PUT, DELETE, and so on).

2. EnterpriseJavaBeans (EJB): EJB bindings let SCA components interact with services provided by Java EE business logic RUNNING on a Java EE server.

3. EIS: The EIS (enterprise information system) binding, when used with a JCA RESOURCE adapter, lets you access services on an enterprise information system or make your services available to the EIS.

4. JMS bindings: Java Message Service (JMS), generic JMS, and WebSphere MQ JMS (MQ JMS) bindings are used for interactions with messaging systems, where asynchronous communication through message queues is critical for reliability.

An export with one of the JMS bindings watches a queue for the arrival of a message and asynchronously SENDS the response, if any, to the reply queue. An import with one of the JMS bindings builds and sends a message to a JMS queue and watches a queue for the arrival of the response, if any.

1. JMS: The JMS binding lets you accessthe WebSphere-embedded JMS provider.

2. Generic JMS: The generic JMS binding lets you access a non-IBM vendor messaging system.

3. MQ JMS: The MQ JMS binding lets you access the JMS subset of a WebSphere MQ messaging system. You would use this binding when the JMS subset of functions is sufficient for your application.

4. MQ: The WebSphere MQ binding lets you communicate with MQ native applications, bringing them into the service oriented architecture framework and providing access to MQ-specific header information. You would use this binding when you need to use MQ native functions.

1. SCA: The SCA binding, which is the default, lets your service communicate with services in other SCA You use an import with an SCA binding to access a service in another SCA module. You use an export with an SCA binding to offer a service to other SCA modules.

2. Web service: A Web service binding lets you access an external service using interoperable SOAP messages and qualities of service. You can also use Web service bindings to include attachments as part of the SOAP message.

The Web service binding can use a transport protocol of either SOAP/HTTP (SOAP over HTTP) or SOAP/JMS (SOAP over JMS). Regardless of the transport (HTTP or JMS) used to convey the SOAP messages, Web service bindings always handle request/response interactions synchronously.

1. HTTP: The HTTP binding lets you access an external service using the HTTP protocol, where non-SOAP messages are used, or where direct HTTP access is required. This binding is used when you are working with Web services that are based on the HTTP model (that is, services that use well-known HTTP interface operations such as GET, PUT, DELETE, and so on).

2. EnterpriseJavaBeans (EJB): EJB bindings let SCA components interact with services provided by Java EE business logic running on a Java EE server.

3. EIS: The EIS (enterprise information system) binding, when used with a JCA resource adapter, lets you access services on an enterprise information system or make your services available to the EIS.

4. JMS bindings: Java Message Service (JMS), generic JMS, and WebSphere MQ JMS (MQ JMS) bindings are used for interactions with messaging systems, where asynchronous communication through message queues is critical for reliability.

An export with one of the JMS bindings watches a queue for the arrival of a message and asynchronously sends the response, if any, to the reply queue. An import with one of the JMS bindings builds and sends a message to a JMS queue and watches a queue for the arrival of the response, if any.

1. JMS: The JMS binding lets you accessthe WebSphere-embedded JMS provider.

2. Generic JMS: The generic JMS binding lets you access a non-IBM vendor messaging system.

3. MQ JMS: The MQ JMS binding lets you access the JMS subset of a WebSphere MQ messaging system. You would use this binding when the JMS subset of functions is sufficient for your application.

4. MQ: The WebSphere MQ binding lets you communicate with MQ native applications, bringing them into the service oriented architecture framework and providing access to MQ-specific header information. You would use this binding when you need to use MQ native functions.