Comparison of WAS and WebSphere MQ messaging

Network Deployment (Distributed operating systems), v8.0 > Applications > Messaging resources > Interoperation with WebSphere MQ

Comparison of WAS and WebSphere MQ messaging

If you are not already an established user of either WAS or WebSphere MQ, and you are considering whether the service integration platform or WebSphere MQ better meets your messaging needs, use this table to compare the main features of the two platforms.

Comparison of service integration and WebSphere MQ main features. The first column of this table lists the main features of service integration (the default messaging provider for WAS), and the second column lists the features of WebSphere MQ).

Service integration (the default messaging provider for WAS) WebSphere MQ
Closely integrated with WAS, and combines well with the Java EE Can connect to almost any platform, and 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 WebSphere MQ and WebSphere 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)
Cluster is integrated with WAS clustering for high availability and scalability WebSphere MQ clustering provides selective parallelism of clustered queues

If your existing or planned messaging environment involves both WebSphere MQ and WAS systems, the messaging platform that you choose for a given task does not necessarily determine which JMS messaging provider you should use. See Choosing messaging providers for a mixed environment.
Interoperation with WebSphere MQ
Interoperation with WebSphere MQ: Comparison of key features
Choosing messaging providers for a mixed environment

+
Search Tips | Advanced Search

Service integration (the default messaging provider for WAS)	WebSphere MQ
Closely integrated with WAS, and combines well with the Java EE	Can connect to almost any platform, and 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 WebSphere MQ and WebSphere 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)
Cluster is integrated with WAS clustering for high availability and scalability	WebSphere MQ clustering provides selective parallelism of clustered queues