12. End of Service for older versions
WebSphere MQ 7.1
End of Service (Distributed) was April 2017
End of Service (z/OS VUE) was September 2017
End of Service (z/OS) was November 2017
20122009 2010 2011
MQ V7.0.1
WebSphere MQ 7.5
End of Service (Distributed) is April 2018
MQ FTE V7.0.x, MQ AMS 7.0.x & MQ HVE 7.0.1
EOS was September 2017
IBM MQ V8
EOS will be April 2020
MQ V7.1 MQ V7.5
MQ AMQ V7.0.1 MQ FTE V7.0.4
MQ HVE V7.0.1
NEW
13. Mix and Match
Both are available under
the same license.
Both can interoperate, just
like any previous version
of MQ.
Continuous Delivery
New CD versions of MQ
are released
approximately every four
months, incrementally
introducing new product
capabilities.
Intended for those that can
continually integrate.
Long Term Support
Approximately every two
years a new LTS version is
released, rolling up many
of the CD capabilities into
a release with 5+3 support
attached.
Required by those looking
for fixed function.
In 2016 MQ introduced
a dual Long Term
Support and a
Continuous Delivery
model
IBM MQ: long term support and continuous delivery
2016 2017 201820152014
V8.0.0 V9.0.0 LTS
V9.0.1 CD V9.0.2 CD V9.0.3 CD V9.0.4 CD V9.0.5 CD
IBM MQ Appliance
M2000
IBM MQ Appliance
M2001
NEW
Statement of Direction: With the next release of MQ, IBM intends to initiate deployment of a new LTS release cycle
MQ on IBM Cloud
15. MQ V9 Long Term Support
Advanced Message Security
AMS added a new high performance policy for
encryption, not signing. 3x-4x performance gains are
typical, if not more
Support for non-IBM JREs
Centralised hosting of CCDTs
Clients can automatically retrieve a remotely located
CCDT over HTTP or FTP when connecting. Enabler
for dynamically changing MQ configurations and a
simpler application setup
System topics
Distributed queue managers publish statistics and
application trace data to dynamic subscribers
Timetocomplete
QMGR1
MQI App
MQCONN(QMGR2)
? HTTP
server
CCDT
QMGR1
QMGR2
QMGR3
QMGR2 QMGR3
IBM MQ Advanced
16. Command recall and editing for runmqsc on Unix
When running runmqsc on Unix/Linux platforms you can now use cursor keys
– And common editing control sequences (emacs/vi modes)
– Much easier to fix bad typing
Similar to what has always been available on Windows
With a new capability of command completion
– Hit TAB to cycle through and accept possible keywords
17. Significantly reducing overheads of linear logging
Automatic log reuse
Linear log extents must be removed from the system to free
up space
You may choose to archive them before deleting
You can now create a queue manager where log extents are
automatically reused as soon as they are no longer required
for media recovery
Alternatively they can be automatically reused when no longer
required and have been marked as archived
Significant performance improvements over user managed
linear logging, comparable to circular logging
And in general
Extra information added to queue manager status on
log utilization to aid better log configurations
0
10000
20000
30000
40000
50000
60000
1 2 3 4 5 6 7 8 9 10 11
Persistent Message Throughput
9.0.2 Circular Logging
20. MQ HA Group
Node 2 Node 3Node 1
Synchronous data replication
Replicated Data Queue Managers
Linux only, MQ Advanced HA solution with no need
for a shared file system or HA cluster
MQ configures the underlying resources to make
setup and operations natural to an MQ user
Three-way replication for quorum support
Synchronous data replication for once and once
only transactional delivery of messages
Active/passive queue managers with automatic
takeover
Per queue manager control to support active/active
utilisation of nodes
Per queue manager IP address to provide simple
application setup
Supported on RHEL v7 x86-64 only
Monitoring
App
Network
New in V9.0.4 CD MQ Advanced for Linux
21. MQ HA Group
Node 2 Node 3Node 1
Synchronous data replication
Replicated Data Queue Managers
Monitoring
App
NetworkLinux only, MQ Advanced HA solution with no need
for a shared file system or HA cluster
MQ configures the underlying resources to make
setup and operations natural to an MQ user
Three-way replication for quorum support
Synchronous data replication for once and once
only transactional delivery of messages
Active/passive queue managers with automatic
takeover
Per queue manager control to support active/active
utilisation of nodes
Per queue manager IP address to provide simple
application setup
Supported on RHEL v7 x86-64 only
New in V9.0.4 CD MQ Advanced for Linux
22. Node 2Node 1
data replication
Replicated Data Queue Managers App
Manual failover
9.0.5 CD MQ Advanced adds the ability to build a
looser coupled pair of nodes for data replication but
no automatic failover, typically for Disaster
Recovery
Data replication can be
Asynchronous for systems separated by a high
latency network
Synchronous for systems on a low latency
network
No automatic takeover means no need for a third
node to provide a quorum
New in V9.0.5 CD MQ Advanced for Linux
23. Connecting Applications at Scale
Binding an application to a specific queue manager
restricts future changes, impacting availability,
scalability and maintenance of the system
Run applications remote from the queue managers,
connecting as MQ clients
For horizontal scaling, create groups of matching
queue managers and connect applications to the
group, not each queue manager
Now you can add and remove queue managers
without changing the application
Use one of multiple ways to map applications to
queue managers and their location. For example
Infrastructure level routing
Client Channel Definition Tables (CCDTs)
App App App
decoupled
CCDT
QM1
QM2
QM3
HTTP
server
V9.0.0 LTS
30. MQ events in JSON
Event messages can be formatted in JSON too
Queue full, authorization failures etc
The amqsevt sample extended in 9.0.5 to output
JSON format
Example: Feeding events to Splunk
38. Help and advice with MQ in the Cloud
It has always been important for MQ to run where it is
needed and integrated into the tools of your choice
For many that means clouds
We have been investigating and demonstrating
running MQ in various public and private clouds.
Using a variety of tooling for provisioning,
configuration and monitoring
And we’ve been sharing that information for everyone
to use
developer.ibm.com/messaging/mq-on-cloud
46. New MQI languages
The MQI API exposes the richest MQ
messaging capabilities, predominantly in C
and COBOL
New MQI wrappers available for GO and now
Node.JS
Provided as as-is open source, let us know if
there’s a need to take these further
github.com/ibm-messaging
developer.ibm.com/messaging/2017/11/10/ibm-mq-node-js