IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Services and service-related functions > Access external services with messaging systems

Java Message Service (JMS)

JMS is a standard API for sending and receiving messages. It allows components based on the Java™ Platform, Enterprise Edition (Java EE) to create, send, receive, and read messages.

This section examines the JMS programming model. The section then shows how a JMS message maps to SCA artifacts; that is, how a message maps to a business object and how input and output from a JMS client maps to an interface's operations. Data bindings and an important function called the function selector are discussed. You are then led through the generation of a JMS import and export binding and presented with some standard applications that make use of the JMS binding.

• Java Message Service (JMS) programming model
  The JMS programming model is discussed in this section.
• JMS features
  Several features of JMS bindings and how SCA artifacts work with them are discussed.
• Work with JMS bindings
  JMS bindings can be generated for imports and exports with either a one-way operation or request-response operation. All cases are discussed in this section.
• JMS, MQ JMS and generic JMS bindings
  The bindings for JMS, MQ JMS and generic JMS are examined.
• Create applications with JMS bindings
  Building applications that use the JMS bindings are shown in this section.
• JMS imports and exports at run time
  The sequence of the methods used at run time is discussed.
• Limitations of the JMS, MQ JMS and generic JMS bindings
  The JMS and MQ JMS bindings have some limitations.

Access external services with messaging systems

Related concepts:
WebSphere MQ Java Message Service (MQ JMS)
Generic JMS
WebSphere MQ (WMQ)

Related reference:
Mapping a message to an SCA interface
Recommendations when using messaging bindings
Language support in non-EIS bindings