IBM BPM, V8.0.1, All platforms > Get started with IBM BPM > Key concepts > Bindings > Binding types

Generic JMS bindings

The Generic JMS binding provides connectivity to third-party JMS 1.1 compliant providers. The operation of the Generic JMS bindings is similar to that of JMS bindings.

The service provided through a JMS binding allows a Service Component Architecture (SCA) module to make calls or receive messages from external systems. The system can be an external JMS system.

The Generic JMS binding provides integration with non-JCA 1.5-compliant JMS providers that support JMS 1.1 and implement the optional JMS Application Server Facility. The Generic JMS binding supports those JMS providers (including Oracle AQ, TIBCO, SonicMQ, WebMethods, and BEA WebLogic) that do not support JCA 1.5 but do support the Application Server Facility of the JMS 1.1 specification. The WebSphere embedded JMS provider (SIBJMS), which is a JCA 1.5 JMS provider, is not supported by this binding; when using that provider, use the JMS bindings.

Use this Generic binding when integrating with a non-JCA 1.5-compliant JMS-based system within an SCA environment. The target external applications can then receive messages and send messages to integrate with an SCA component.

Binding types


Related concepts:
Limitations of the JMS, MQ JMS, and generic JMS bindings


Related tasks:
Enabling event sequencing: Generic JMS exports