Summary
In this chapter, we learned that WebSphere Application Server provides a level of abstraction to messaging configuration by allowing resources to be referenced by JNDI. We deployed a message-enabled application, which required a queue connection factory and queue destination, which it used to send and receive messages. Also, in this chapter, we discussed how to configure SiBus members to use either a file store or a data store and outlined the pros and cons of each.
We then covered how to install WebSphere MQ and learned how to create a queue manager and a queue. We then covered how to re-map our application's resource references to re-point the application to use MQ messaging subsystem, as opposed to the internal messaging subsystem.
There are many uses of messaging in enterprise applications and we have covered the key areas for configuring WAS to facilitate resources for message-enabled applications.
MQ link was explained through an example demonstration. We learned how to configure...
