WAS service integration vs IBM MQ messaging

WAS service integration vs IBM MQ messaging

WAS service integration vs. IBM MQ for messaging.
If our existing or planned messaging environment involves both IBM MQ and WAS systems, the messaging platform chosen for a given task does not necessarily determine which JMS messaging provider we should use. For more information, see Choosing messaging providers for a mixed environment.

Service integration IBM MQ
Integrated with WAS. Combines well with Java EE Can connect to almost any platform. Supports a heterogeneous environment
Supports multiple languages through XMS clients and multiple platforms Supports multiple languages and multiple platforms
Limited tooling support, other than what is provided in WAS Has many Independent Software Vendor (ISV) tools
Provides strong performance for both persistent and non-persistent messages for JMS Supports JMS and non-JMS messaging interfaces, and provides strong performance for non-JMS applications
Designed for a maximum message size of about 40 megabytes on a 32-bit operating system (subject to heap usage) Supports large message sizes up to about 100 megabytes
Underpins WebSphere Enterprise Service Bus and WebSphere Process Server Underpins IBM MQ and IBM MQ File Transfer Edition
Included in a single administrative model for WAS, WebSphere Enterprise Service Bus, and WebSphere Process Server Can integrate existing infrastructure and applications (for example, CICS)
Clustering is integrated with WAS clustering for high availability and scalability IBM MQ clustering provides selective parallelism of clustered queues

Related:

Interoperation with IBM MQ: Comparison of key features
Choosing messaging providers for a mixed environment

Service integration	IBM MQ
Integrated with WAS. Combines well with Java EE	Can connect to almost any platform. Supports a heterogeneous environment
Supports multiple languages through XMS clients and multiple platforms	Supports multiple languages and multiple platforms
Limited tooling support, other than what is provided in WAS	Has many Independent Software Vendor (ISV) tools
Provides strong performance for both persistent and non-persistent messages for JMS	Supports JMS and non-JMS messaging interfaces, and provides strong performance for non-JMS applications
Designed for a maximum message size of about 40 megabytes on a 32-bit operating system (subject to heap usage)	Supports large message sizes up to about 100 megabytes
Underpins WebSphere Enterprise Service Bus and WebSphere Process Server	Underpins IBM MQ and IBM MQ File Transfer Edition
Included in a single administrative model for WAS, WebSphere Enterprise Service Bus, and WebSphere Process Server	Can integrate existing infrastructure and applications (for example, CICS)
Clustering is integrated with WAS clustering for high availability and scalability	IBM MQ clustering provides selective parallelism of clustered queues