Learning more about the Service Integration Bus (SIB) Java Message Service (JMS)

 

Getting background information on JMS

What is Messaging?
The term messaging, in the generic sense, is usually used to describe the exchange of information between two interested parties. In the context of computer science, messaging can be used to loosely describe a broad range of mechanisms used to communicate data. For example, e-mail and instant
messaging are two communication mechanisms that could be described using the term messaging. In both cases, information is exchanged between two parties, but the technology used to achieve the exchange is different. There are two messaging types that define the mode of interaction between the
sending and receiving applications:

Synchronous messaging
Synchronous messaging involves tightly coupled processes, where the sending and receiving applications communicate directly and both must be available in order for the message exchange to occur.

Asynchronous messaging
Asynchronous messaging involves loosely coupled processes, where the sending and receiving applications communicate through a messaging provider. The sending application is able to pass the data to the messaging provider and then continue with its processing. The receiving application is
able to connect to the messaging provider, possibly at some later point in time, to retrieve the data.

What is JMS?
WebSphere Application Server supports asynchronous messaging through the use of the Java Message Service (JMS). The JMS API is the standard Java API for accessing enterprise messaging systems from Java programs. In other words, it is a standard API that sending and receiving applications written in Java can use to access a messaging provider to create, send, receive, and read messages. WebSphere Application Server V7.0, V8.0 and V8.5 supports JMS 1.1 applications.
Support for JMS 2.0 was added in WebSphere Application Server V9.0.

What is Service Integration Bus?
Service integration is a set of technologies that provides asynchronous messaging services. Application servers or clusters of application servers in a WebSphere Application Server cell can cooperate to provide asynchronous messaging services. Service integration provides asynchronous messaging services, and a group of servers or clusters that cooperate in this way is called a service integration bus. The application servers or server clusters in a bus are known as bus members. You can also add bus members that are WebSphere MQ servers; service integration uses these bus members to write messages to, and read messages from, WebSphere MQ queues.

Different service integration buses can, if required, be connected. This allows applications that use one bus (the local bus) to send messages to destinations in another bus (a foreign bus). Note, though, that applications cannot receive messages from destinations in a foreign bus.

Messaging engines
Each service integration server or cluster bus member contains a component called a messaging engine that processes messaging send and receive requests and that can host destinations. To host queue-type destinations, the messaging engine includes a message store where, if necessary, it can hold messages until consuming applications are ready to receive them, or preserve messages in case the messaging engine fails.

If the bus member is a server cluster, it can have additional messaging engines to provide high availability or workload sharing characteristics. If the bus member is a WebSphere MQ server, it does not have a messaging engine, but it lets you access WebSphere MQ queues directly from WebSphere
MQ queue managers and (for WebSphere MQ for z/OS®) queue-sharing groups.


Messaging providers
WebSphere Application Server applications invoke asynchronous messaging services by using the Java Messaging Service (JMS) application programming interface (API) to interface to a messaging provider. WebSphere Application Server supports a variety of JMS messaging providers, including service integration (which is the default messaging provider) and WebSphere MQ as an external JMS messaging provider.

Additional Resources:
Types of messaging providers
Service Integration
Comparison of WebSphere Application Server and WebSphere MQ messaging

BLOGS:
Commonly used wsadmin scripts for WebSphere Application Server SIBus
Common reasons for "CWSIT0103E: No messaging engine was found" Exceptions in Service Integration Bus and their likely solutions in WebSphere Application Server
Deleting messages from a datastore
Few Service Integration performance/best practices tips
Finishing off your WebSphere Application Server Messaging Engine startup problems
10 things every WebSphere Service Integration Bus user must be aware of
Recovering Failed SIBus Transactions in WebSphere Application Server
Security with WebServices Gateway for SIBus
Service Integration Bus enhancements in WASv8.5
SIBus Messaging Engine startup performance improvements in WAS v8.5
The most commonly used Service Integration Bus custom properties in WebSphere Application Server
WebSphere Application Server Service Integration Technology Message store problems and solutions
WebSphere Application Server Service Integration Technology Message flow problems and solutions
What are the Service Integration Technology enhancements in WebSphere Application Server 8.5 ?


WSTEs:
Ask the Experts Replay: Understanding WAS V8.5 Publish Subscribe
Ask the Experts Replay: Service Integration Bus Scalability Best Practices
Webcast replay: Service Integration Bus and Stuck Messages
Webcast replay: Troubleshooting of Messaging Engine failover issues.
Webcast replay: Top 5 Service Intergration Bus Problems and Solutions
Webcast: Service Integration Bus Link Configuration and Troubleshooting
Webcast Replay: Service Integration Bus Best Practices in WebSphere Application Server
Webcast Replay: New Enhancements to the SIBus in WebSphere Application Server V8.5
Webcast replay: WebSphere Application Server: Understanding Message Driven Beans (MDBs) in Service Integration Bus
Webcast replay: WebSphere Application Server - Service Integration Bus Messaging Engine Data Store Connectivity Problems and Solutions
Webcast Replay: Understanding Service Integration Bus JMS Messaging in WebSphere Liberty:
Webcast replay: External messaging clients for the Service Integration Bus in WebSphere Application Server
Webcast replay: SSL Configuration of the Java EE Application Client and the WebSphere Application Server V7 Service Integration Bus