SlideShare a Scribd company logo
1 of 73
What's new in IBM Messaging 
Morag Hughson - hughson@uk.ibm.com 
IBM Hursley - UK
IBM Messaging – Market segments 
Deliver Messaging Backbone for Enterprise 
Focus on traditional MQ values, rock-solid enterprise-class service, 
ease-of-operation, breadth of platform coverage, availability, z/OS 
exploitation 
Capture Big Data from Mobile and Internet of Things 
Focus on Internet-scale events, m2m device enablement, zero-admin, 
security and privacy, feed into real-time analytics, 
location-based notifications 
Enable Developers to build more scalable, responsive 
applications 
Focus on new app dev use cases, breadth of languages, ease-of-deployment, 
lightweight services, integration with developer 
© 2014 IBM Corporation 
frameworks
Multi-platform 
Common criteria 
Multiple cluster 
XMIT queue 
Hypervisors 
Integrated 
Messaging 
V7.1 
V7.5 
IBM MQ 
Advanced 
1990s 2000s 2010s 
© 2014 IBM Corporation 
JMS 
MQI 
Assured 
delivery 
IBM 
MQSeries 
Mobile 
.NET 
Eclipse 
JMS 1.1 
RCMS 
IBM MQ Low 
Latency 
V1.1 
V2 
V5 V5.1 
V5.3 
V2.1 
V5.2 
V6 
V7 
V7.0.1 
SSL 
SOAP 
XML 
IBM MQ 
Managed File 
Transfer 
IBM MQTT 
HTTP 
AJAX 
REST 
Web 2.0 
Managed 
File Transfer 
Pub/sub 
IBM MQ 
Everyplace 
IBM MQ 
Advanced 
Message 
Security 
System Pattern 
Application Pattern 
IBM MQ 
Advanced for 
Developers 
IBM 
MessageSight 
Multi-instance 
QMGR 
V8 
Timeline 
20th 
Anniversary of 
MQ at IMPACT
WebSphere MQ V7.1: Feature Summary (Nov 2011) 
New Feature Benefits Details 
© 2014 IBM Corporation 
Multi-Version Install capability on 
Distributed platforms 
Makes it easier to deploy and upgrade 
systems and stage version to version 
migration 
Unix and Windows support for multiple versions of MQ V7.x (AND 
one copy of MQ V7.0.1) down to fixpack levels. 
Relocatable installation support. 
Applications can connect to any Qmgr 
Enhanced Security 
Simplified Configuration 
Enhanced Authorisation and Auditing 
IP address Authorisation capability 
Additional crypto algorithms 
More granular authorisation for non-local queues 
Application Activity Reports 
Cloud Support Simplifies and support Cloud deployments Additional HVE images 
Enhanced Clustering Improves ease-of-use 
Authorisation on Cluster Q rather than XMIT Q on Dist. Platforms 
Bind-on-Group Support 
Multicast capability New messaging QoS provides low latency 
with high fan-out capability 
MQ Pub/Sub Topic space can now map to multicast Group 
Addresses 
Provides direct interoperability with MQ LLM 
Improved scalability and 
availability on z/OS 
Further exploitation of z196 
Customer control over CF storage use 
CF Connectivity Loss improvements 
Code contention reduced to improve multi-processor linear scaling 
Use of MQ Datasets rather than DB2 significantly improves “large” 
message capability 
Structure rebuild capability for CF Connectivity Loss scenarios 
Improved Performance on Dist 
platforms 
Improved multiprocessor exploitation Various code improvements
WebSphere MQ V7.5: Feature Summary (June 2012) 
© 2014 IBM Corporation 
 For Windows, Unix and Linux 
New Feature Benefits Details 
Integrated Installation 
Makes it easier to deploy systems 
Simpler licensing 
Combines several products into a single package 
Common experience 
Enhanced Clustering 
Improves ease-of-use 
Improves application isolation 
Split Cluster Transmission Queue 
Java Application Identification Makes it easier to distinguish applications Applications no longer to all have the same name 
AMS channel interception 
Provides a level of message protection even 
when application environment cannot run 
AMS 
Interception in the SVRCONN still protects messages before 
hitting queues 
FTE Logger Options Can write FTE audit records to flat file 
No longer a requirement for an enterprise database 
Easier to read data immediately
2013 Updates
WebSphere MQ: Feature Summary (2013) 
 Updates to pricing and function during 2013 
New Feature Benefits Details 
© 2014 IBM Corporation 
MQ 7.1 Value Unit Edition 
introduced for z/OS 
One time charge (OTC) pricing for zNALC 
workloads 
Queue managers supporting qualified workloads on System z New 
Application License Charge (zNALC) LPARs 
Includes WebSphere MQ Client Attach, allowing free-of-charge 
connections from MQ Clients to z/OS 
SHA-2 CipherSpecs for SSL/TLS 
on z/OS 
Stronger hashing algorithms 
Required/recommended by some authorities 
Available from V7.1 GA on distributed platforms 
Now also available on z/OS 7.1, with two APARs* 
Internet PassThru (MS81) refresh 
Updates to SOE and crypto algorithms 
Consistent SSL/TLS support and certificate DN 
attributes with MQ V7.1 
Uses JRE-provided Java Secure Sockets Extension (JSSE) 
Support for SHA-2 and elliptic curve encryption, in line with US NIST 
standard SP800-131A recommendation 
MQ JCA RA support in WAS 
Liberty profile 
MQ 7.5.0.2 RA is easily configured in Liberty 
Connects to any supported version of MQ 
Liberty profile expects resource providers (database, messaging) to 
supply provider-specific classes 
Configure “wmqJmsClient.rar.location” variable in server.xml 
MQ 7.1 Extended Transactional 
client for HP NSS platform 
MQ V7.1 function for NonStop applications 
accessing MQ on other systems 
Free and fully supported 
Supports C/C++, COBOL, pTAL, JMS 
Supports Guardian and OSS applications including OSS multi-threaded 
applications 
Available as SupportPac MAT1 
*APAR OA39422 needed on z/OS V1R13 for System SSL 
*APAR PM77341 for MQ on z/OS V7.1
© 2014 IBM Corporation 
SHA-2 Support 
 Stronger algorithms are now available and recommended 
 In many cases available pre-V8 
 V7.1 GA on Distributed platforms 
 V7.1 on z/OS via APAR 
 APAR OA39422 needed on z/OS V1R13 for System SSL 
 APAR PM77341 for MQ on z/OS V7.1 
 Various other ‘parts’ of MQ via Service Stream 
 See technote http://www.ibm.com/support/docview.wss?uid=swg21639606 
 Changes also rolled into V8 
 CipherSpecs include:- 
 ECDHE_RSA_AES_128_CBC_SHA256 
 ECDHE_RSA_AES_256_CBC_SHA384 
 TLS_RSA_WITH_AES_128_CBC_SHA256 
 TLS_RSA_WITH_AES_256_CBC_SHA256 
 TLS_RSA_WITH_NULL_SHA256
N 
O 
T 
E 
S 
© 2014 IBM Corporation 
SHA-2 Support 
 SHA-2 stands for Secure Hash Algorithm 2. This is the generic name for a family of 
hash functions SHA-224, SHA-256, SHA-384, and SHA-512; the numbers refer to 
the bit-size of the generated hash value. 
 The hashing algorithms historically supported by WebSphere MQ channel 
cipherSpecs (SSLCIPH) were MD5 and SHA-1. These are no longer regarded as 
adequately secure due to successful attacks on them which have been widely 
publicized, and because NIST (the American National Institute of Standards and 
Technology) has mandated (http://csrc.nist.gov/groups/ST/hash/policy.html) that 
both MD5 and SHA-1 no longer be used. So we have had considerable customer 
pressure for provision of “SHA-2 support.” 
 This support is in MQ V8, but also in earlier releases by applying appropriate fix 
pacs for the platform or component on MQ where you are interested in using it. A 
technote at http://www.ibm.com/support/docview.wss?uid=swg21639606 details 
exactly which fix pacs or APARs are required in each case.
Internet Pass-Thru – SupportPac MS81 
 Previous MQIPT 2.0 release was in 2008 
 Many new operating systems have been released since then 
 New cryptographic algorithms since then 
 Redesigned to use the JRE-provided Java Secure Sockets Extension (JSSE) 
 Previously used a separate SSL implementation 
 This gives consistent SSL/TLS support 
 Also has consistent certificate DN attributes with MQ V7.1 
 US NIST standard SP800-131A recommends: 
 Support for SHA-2 (e.g. SHA-256, SHA-384 and SHA-512) 
 Elliptic Curve encryption 
© 2014 IBM Corporation
© 2014 IBM Corporation 
MQ V7.1 VUE for z/OS 
 MQ Value Unit Edition product introduced for z/OS 
 One time charge (OTC) pricing for zNALC partition workloads 
 OTC price metric instead of MLC 
 Run new workloads that are qualified to run on System z New Application License 
Charge (zNALC) LPARs 
 Includes code and entitlement for WebSphere MQ Client Attach, allowing free-of-charge 
connections from MQ Clients to z/OS
© 2014 IBM Corporation 
JMS in Liberty Profile 
 WAS Liberty profile does not include a copy of the MQ JMS client 
 For consistency with other resource providers such as databases 
 Provider specific classes come from the resource provider 
 The RA provided with MQ can be easily configured in Liberty 
 Define one variable in server.xml to tell the wmqJmsClient-1.1 where the client is 
variable name=wmqJmsClient.rar.location 
value=${shared.resource.dir}/wmq/wmq.jmsra.rar/ 
 Requires the MQ 7.5.0.2 rar or a fix on top of 7.5.0.1 
 More information is at 
 https://www.ibmdw.net/wasdev/2013/06/14/using-websphere-mq-with-the-liberty-profile/ 
 http://www-01.ibm.com/support/docview.wss?uid=swg21633761
New client support for HP NSS (aka Tandem) 
 Extended Transactional client support at an MQ V7.1 release level 
 Full MQ V7.1 function for NonStop applications accessing MQ on other systems 
© 2014 IBM Corporation 
 Client is free and fully supported 
 C / C++ extended transactional client 
 Cobol 
 pTAL support 
 JMS client 
 Supports both Guardian and OSS applications 
 including OSS multi-threaded applications 
 Available as SupportPac MAT1
© 2014 IBM Corporation 
Now available
Reuse is not just for code 
 Another new book where the MQ chapter may look familiar 
© 2014 IBM Corporation
End of Service for old platforms and versions 
 MQ V7.0.0 and V7.0.1 for multiplatforms – EOM, EOS effective September 2015 
 V7.0 will have had more than 7 years of support 
 MQ V7.0.1 for z/OS – EOM, EOS effective September 2015 
© 2014 IBM Corporation 
 V7.0 .0 already out of service
2013 enhancements: Developer 
Enhancement Benefits Details 
MQ Advanced for 
Developers – free for devt 
Development use only edition 
use!! 
Free of charge 
Full MQ Advanced V7.5 functionality 
Available free of charge for development use only 
Download from developerWorks, MQdev community 
Best effort community assistance 
© 2014 IBM Corporation 
IBM MessageSight for 
Developers – free for devt 
use!! 
Development use only edition 
Free of charge 
Virtual MessageSight image, updated to V1.1 
Available free of charge for development use only 
Download from developerWorks, IBM Messaging 
community 
Best effort community assistance 
Mosquitto - Open source 
MQTT server 
Simple, open access to get on-board 
with MQTT and MQTT-SN 
Proposed Eclipse Mosquitto project for open-source 
MQTT server for lightweight devt use 
MQTT-SN (MQTT for sensor networks) specification 
available 
IBM MQ Light – alpha 
release 
Straight forward, easy to use 
messaging API for writing 
scalable and responsive 
applications 
Download and feedback via developerWorks community 
Available free of charge for development use 
Currently new API available in Java, more languages to 
come 
Regular updates planned introducing new features and 
responding to feedback
Simplifying Development for developer-led Messaging Applications 
 “MQ Light” - a new messaging form factor, easy for developers 
 Straightforward download and unzip – zero install 
 Simple Web UI– no need to be an infrastructure specialist 
 Focus on your application – using simplified messaging API 
 Support for popular languages and tooling with seamless 
migration from development into production 
 MQ Light runtime not for advanced messaging uses cases, 
enterprise backbone or highly available/scalable apps 
© 2014 IBM Corporation 
IBM MQ Light 
Developer coding in 
JavaScript, Java, Python, 
Ruby, C#, PHP 
Builds messaging into applications 
using preferred IDE or CLI 
and tests in developer sandbox 
C7: Messaging 
in the Cloud 
with 
IBM MQ Light 
and 
IBM Bluemix 
A35: How to 
Develop 
Responsive 
Applications 
with 
IBM MQ Light 
(Lab) AL6: 
Developing a 
First 
Application 
with 
IBM MQ Light
Download “MQ Light” alpha and try it today 
https://www.ibmdw.net/messaging/mq-light 
© 2014 IBM Corporation
2013 enhancements: Internet of Things, mobile  m2m 
Enhancement Benefits Details 
© 2014 IBM Corporation 
IBM MessageSight V1.1 
High-performance, reliable, and 
scalable messaging - designed 
specifically for M2M and Mobile 
scenarios 
Balance mobile workloads across your enterprise 
application server clusters 
Single sign-on from mobile devices to your enterprise 
apps 
Disconnected app notification that messages are waiting 
IBM Internet of Things Cloud 
– statement of direction 
Fully cloud hosted solution for 
internet of things 
Freemium, PAYG  custom 
pricing 
Scalable connectivity for small and large numbers of 
devices 
Uses industry-standard, MQTT transport 
Registration of devices for access to the cloud service 
offering 
Ability for devices to produce and consume events and 
messages in near real-time 
Mobile Messaging clients Updated clients for mobile 
platforms Updated clients for Android, iOS  hybrid mobile apps
IBM MessageSight – a messaging Appliance 
 Extends the IBM Messaging family with a secure, easy to deploy appliance-based 
messaging server, optimized to address the massive scale requirements of 
machine to machine (m2m) and mobile use cases 
 A million connections, and millions 
© 2014 IBM Corporation 
of messages per second 
 Exploits hardware acceleration for 
performance 
 Designed to sit at the edge of the 
enterprise 
 Can extend your existing messaging infrastructure or 
used standalone 
 Complements MQ - provides an offload/accelerator for 
edge of enterprise scenarios 
A8: 
Introduction to 
IBM 
MessageSight 
 Supports familiar APIs with a mixture of standard and high-speed protocols
IBM MessageSight V1.1 - Major enhancements 
© 2014 IBM Corporation 
 Mobile to Enterprise 
 Balance mobile workloads across your enterprise application server clusters 
 Single sign-on from mobile devices to your enterprise apps 
 Disconnected app notification that messages are waiting 
 Security 
 Implements the Federal government recommendations with NIST SP 800-131A strengthened 
security 
 Uses client certificate identity for authentication and authorization 
 Developer Operations 
 New “at-a-glance” system dashboard 
 Flexible work environments supported with remote monitoring of MessageSight from client 
devices 
 Virtual MessageSight image speeds mobile and machine-to-machine app development
2014 Updates
MQLight Service for BlueMix Open Beta 
IBM’s fully managed cloud messaging service 
The same straightforward experience as MQ Light, aimed at developers 
available as a fully managed public cloud service in BlueMix 
Push application into BlueMix and use 
© 2014 IBM Corporation 
Integrated into the 
BlueMix experience 
Simple API for node.js 
JMS API for Java 
Elastic MQ 
Development 
focused tooling 
Develop cloud application 
using node, java, etc 
Develop offline 
using MQ Light 
Elastic MQ
IBM MQ V8 delivering best in class enterprise messaging 
© 2014 IBM Corporation 
Platforms  
Standards 
Security Scalability System z exploitation 
64-bit for all platforms 
Userid authentication 
via OS  LDAP 
Multiplexed client 
performance 
64-bit buffer pools in MQ for 
z/OS means less paging, 
more performance 
Support for JMS 2.0 User-based 
authorisation for Unix 
Queue manager 
vertical scaling 
Performance and capacity 
Improved support for 
.Net and WCF 
AMS for IBM i  z/OS 
Publish/Subscribe 
improvements 
Performance enhancements 
for IBM Information Replicator 
(QRep) 
Changes to runmqsc 
DNS Hostnames in 
CHLAUTH records 
Routed 
publish/subscribe 
Exploit zEDC compression 
accelerator 
SHA-2 for z, i  NSS 
Multiple certificates 
per queue manager 
Multiple Cluster 
Transmit Queue on all 
platforms 
SMF and shared queue 
enhancements
2014 Updates – MQ V8 
N 
O 
T 
E 
S 
 The rest of this presentation goes into details about MQ V8 
© 2014 IBM Corporation
© 2014 IBM Corporation 
MQ V8 Dates 
 Announce: 22 April 2014 
 Availability: 
23 May 2014 (eGA Distributed) 
13 June 2014 (z/OS and pGA Distributed)
MQ platform and product consistency 
 64-bit server support for all queue manager platforms 
 Completion of platform coverage by adding Windows 64-bit engine 
 Applications can still be 32-bit 
 Requires Windows 7 or later 
 Client only package for 32-bit platforms 
 Queue Manager requires 64-bit 
 Integration of AMS and MFT capabilities into z/OS and IBM i platforms 
 Previously separately installable products 
 Following the model used by MQ V7.5 on distributed for closer integration 
 Both features still separately licensed 
© 2014 IBM Corporation 
 AMS 
 Starts automatically with Queue Manager 
 Reduced overhead (now only one started task 
instead of 2) 
 Policies and their administration remain unchanged 
 Client Attach Feature no longer needed on z/OS 
 Single price includes support for clients 
 MFT 
 Now looks more natural for a z/OS person 
 Closer integration with standard system facilities 
such as ARM 
 Started task templates 
 Supported JCL provided instead of samples 
 Job info logged to JCL task
MQ platform and product consistency 
N 
O 
T 
E 
S 
 This release has all the Distributed queue managers fully supporting 64-bit 
operations. The final remaining platform had been Windows, but now the queue 
manager runs as 64-bit processes. Existing 32-bit applications continue to work of 
course, but this should bring additional capacity and scalability to the queue 
managers on that OS. The lowest level of Windows now supported is Windows 7; 
older versions are not supported. A client-only package for 32-bit versions of 
Windows is provided, but the qmgr requires the 64-bit OS. 
 Another big feature of V7.5 was the closer integration of AMS and File Transfer 
(MFT). As we will see later, this pattern has been followed on z/OS and IBM i. On 
z/OS the features are still separately licensed, but are better integrated than 
previously. 
 On z/OS, the CAF has been removed both as an installable feature and as a 
licensing option. All V8 queue managers are now capable of having any number of 
MQ clients directly connected. For customers who previously used the lack of a 
CAF to block client connections, we would strongly recommend they look at the 
other security-related controls such as CHLAUTH and SSL/TLS, or MAXINST 
values, to continue to prohibit clients. If you extend the number of directly-attached 
clients in your environment, make sure you first evaluate things such as CPU costs, 
performance, capacity etc. 
© 2014 IBM Corporation
© 2014 IBM Corporation 
JMS 2.0 
 Long-awaited update from JMS 1.1 standard 
 JMS 2.0 – JSR 343 Java Message Service (JMS 2.0) 
 Final release on 21 May 2013. 
 https://java.net/projects/jms-spec/pages/JMS20FinalRelease 
 New Messaging Features 
 Delivery Delay 
 Asynchronous Send 
 Subscriptions can be shared across a messaging provider 
 API Changes 
 Use of java.lang.AutoCloseable 
 Simplified API [combined connection/session] 
 Session doesn't need parameters (for Java EE) 
 Java 7 prereq 
http://www.slideshare.net 
/calanais/ibm-mq-v8-and-jms- 
20 
 Java EE 7 prereq for use of the Resource Adapter in Application Servers
N 
O 
T 
E 
S 
© 2014 IBM Corporation 
JMS 2.0 
 The JMS 2.0 specification now requires JMS providers to implement both P2P and Pub-Sub. 
 The following new messaging features have been added in JMS 2.0: 
– Delivery delay: a message producer can now specify that a message must not be delivered until after a specified time interval. 
– New send methods have been added to allow an application to send messages asynchronously. 
– JMS providers must now set the JMSXDeliveryCount message property. 
 The following change has been made to aid scalability: 
– Applications are now permitted to create multiple consumers on the same durable or non-durable topic subscription. In previous versions of JMS 
only a single consumer was permitted. 
 Several changes have been made to the JMS API to make it simpler and easier to use: 
– Connection, Session and other objects with a close method now implement the java.jang.AutoCloseable interface to allow them to be used in a 
Java SE 7 try-with-resources statement. 
– A new simplified API has been added which offers a simpler alternative to the standard API, especially in Java EE applications. 
– New methods have been added to create a session without the need to supply redundant arguments. 
– Although setting client ID remains mandatory when creating an unshared durable subscription, it is optional when creating a shared durable 
subscription. 
– A new method getBody has been added to allow an application to extract the body directly from a Message without the need to cast it first to an 
appropriate subtype. 
 New methods have been added to Session which return a MessageConsumer on a durable topic 
subscription. Applications could previously only obtain a domain-specific TopicSubscriber, even though its 
use was discouraged. 
 The specification has been clarified in various places. 
 JMS 2.0 implementations require Java 7 for the runtime. They also require Java EE 7 for use of the 
Resource Adapter in Application Servers. Not all App Servers currently support Java EE 7. However, as 
with all client implementations, older versions of the RA still work when communicating to an MQ V8 queue 
manager.
© 2014 IBM Corporation 
.Net enhancements 
 MQ .Net classes can now use SSL without needing the C client installed 
 A secure fully-managed .Net implementation 
 Uses Windows native certificate stores 
 For MQ .NET classes (aka Base .NET Classes) SSL properties can be set at 
 MQEnvironment.cs 
 Hashtable properties (input parameter to MQQueueManager constructor) 
 For XMS .NET, SSL properties can be set as ConnectionFactory properties 
 WCF interface extended to non-SOAP, non-JMS messages 
 Making it easier for apps using WCF to communicate with any other MQ application
.Net enhancements: SSL 
N 
O 
T 
E 
S 
 MQ .NET in unmanaged mode has supported the use of 
SSL since MQ v6.0.1. It was based on the C Client (and 
GSKit). 
 In V8 MQ .NET Managed mode now supports SSL based 
on Microsoft SSLStreams/Security kit. 
 There are some limitations when using SSL with Managed 
.NET. 
 CipherSpec setting can be made only at Windows Group 
policy (gpedit.msc). 
– CipherSpec set on client channel is used only to determine SSLProtocol. 
– Make sure you set same cipherspec on Windows group policy and client 
© 2014 IBM Corporation 
channel to make sure correct protocol version is flowed. 
 KeyRepository uses Windows Key Store only. 
– Set value as *SYSTEM for accessing certificates under Computer 
Account 
– Set value as *USER for accessing certificates under User account 
 FIPS can be enabled only from Windows group policy. 
 KEYRESET is not supported by Microsoft SSLStreams 
– This limitation is overridden by using KEYRESETCOUNT and Client 
Auto Reconnect feature of MQ. 
– Application can set KEYRESETCOUNT during connection, once the 
number of bytes sent/received reaches the count, connection will be 
forcibly broken. If Client Auto Reconnect facility is enabled, connection 
will be automatically reconnected. 
 No managed way to support Cryptographic hardware 
 Product samples have been updated to demonstrate SSL 
Connections. These can be found in 
WebSphere MQtoolsdotnetsamplescsbaseSimple 
 Additional model for sending MQ messages from WCF 
applications 
– Both SOAP/JMS and MQMessaging can be used 
 SOAP/JMS 
– Supported since MQ v7.0.1 
– Based on XMS .NET and makes JMS-like calls for MQI 
– Uses JMS nomenclature for URI(jms:) and Bindings 
– Now also supports “wmq:” style of URI 
– Uses MA93 supportpac specification for URI format/syntax 
– Messages can be delivered only to SOAP enabled Client/Service 
 MQMessaging 
– New in MQ V8.0 
– Transmits MQ Messages over the WCF Channel without any SOAP 
headers 
– Use “wmq:” style of URI 
– Uses MA93 supportpac specification for URI format/syntax 
– Messages can be delivered to SOAP or NON-SOAP MQ applications
© 2014 IBM Corporation 
Changes to runmqsc 
 Can now be run by any user (not just mqm group) 
 Can take a userid/password for authentication: new -u flag 
 Can now connect as a client to remote systems: new -c flag 
 Client channel definitions located by MQSERVER - MQCHLLIB - MQCHLTAB 
 Can act as standalone program to create local CCDT: new -n flag 
 Does not connect to queue manager; commands subset to update local channel definition file 
 Ease of use 
 Customisable prompt 
using environment 
variable 
 New exit and quit“ 
synonyms for end 
$ ls –l runmqsc 
-r-xr-xr-x 1 mqm mqm 25930 06 Mar 04:46 runmqsc 
$ export MQPROMPT=MQ +MQ_INSTALLATION_NAME+  
$ runmqsc –u metaylor QM1 
5724-H72 (C) Copyright IBM Corp. 1994, 2014. 
Enter password: 
****** 
Starting MQSC for queue manager QM1. 
MQ Installation5 DIS QMGR 
…
Changes to runmqsc 
N 
O 
T 
E 
S 
 This release introduces a number of changes to the runmqsc program 
 Firstly, it is now exectuable by any user, not just members of the mqm group. Security controls still apply of 
course, but the security is checked on each individual command. This makes it easier to have MQ 
administrators who have been granted full access to objects, but who are not in the mqm group. 
 Another reason for making runmqsc world-executable was to make it usable on machines which do not 
have queue managers installed. It is now installed even on client-only systems, and it can be run either as a 
client program connecting directly to a remote queue manager, or as a completely standalone program to 
permit local creation of the Client Channel Definition Table. So you can create and modify a CCDT with no 
queue manager access at all. 
 The program is one of several that have been updated to accept a userid for authentication. If the –u flag is 
given, then a password is requested. Note that the password is read from stdin so that it can be redirected 
from a file if necessary. If you also use scripts piped into runmqsc, then you can group commands to avoid 
having to put the password in the same script as the MQSC commands. 
– Unix: (cat password.stash ; cat script.mqsc) | runmqsc –u userid QM1 
– Windows: (type password.stash  type script.mqsc) | runmqsc –u userid QM1 
 There are also a couple of usability enhancements. Firstly, there are some synomyms added to complete 
an MQSC session – END, QUIT and EXIT can all be used so you don't have to try them all. Different 
scripting environments for different products typically use one of these commands, and it's annoying to have 
to remember which goes with which. 
 Secondly, you can now make it easier to see that you are in an MQSC command environment and some 
details of the current environment by setting the MQPROMPT environment variable. Replaceable inserts 
are recognised such as date and time, and installation-specific details. These are the same variable 
subsitutions as available for SERVICE objects. 
© 2014 IBM Corporation
MQ Security - Authentication 
© 2014 IBM Corporation 
 Verify userid and password 
 Typically supplied in MQI CSP structure or from channel security exit 
 Or JMS createConnection(user,pass) method 
 New client exit and tool provided to help unchanged applications insert passwords 
 Can verify against operating system 
 Including PassPhrase for z/OS 
 Can verify against LDAP repository on Distributed platforms 
 Enabling centralised identity control 
 Still constrained to 12 character userids 
 With LDAP, supplied username may be long (eg an email address or full DN) 
 But must have an associated 12 character shortname 
 Independent configuration for local bindings and clients 
 Ignored, Optional, Required, Required for admin id 
A22: New 
IBM MQ V8 
Security 
Features
MQ Security - Authentication 
N 
O 
T 
E 
S 
 Applications can now be authenticated with a userid/password. This can be provided explicitly 
by the application as parameters in the MQCONNX verb or equivalent. This builds on features 
originally implemented in the MQI for MQ v6, but which were never exploited until now. 
 Also, to support client applications, a security exit is provided that can add the 
userid/password to a connection request if it is not supplied by the app. The exit reads the 
qmgr name from an ini file; the file contains the userid and a protected form of the password – 
ie not plaintext. The protection of the password is done by a tool that is also provided. 
 When V8 clients connect to V8 qmgrs, the userid/password information is protected against 
casual wire-sniffing, even when SSL/TLS is not used. This protection is not as strong as a full 
TLS-encrypted session, which is preferred, but is better than sending data in the clear. 
Obviously both the client and the qmgr must be at V8 for this protection to work; older clients 
can still send passwords but they are not protected. 
 Authentication is performed against the local OS (all platforms) or against an LDAP directory 
(Distributed only). Some operating systems may integrate LDAP services into their local user 
registry, in the same way as NIS, but when this is done transparently MQ does not know 
about it explicitly and can use the OS authentication method. 
 Using a central LDAP server means that passwords can be set in a single place. For example, 
we have used IBM's LDAP services (BluePages) to authenticate userids. When using LDAP, 
there is lots of flexibility in what the userid is – in BluePages it is generally the email address 
– but there must be a field in the schema to return a short name that can fit into the 12 
character MQMD.UserIdentifier field. This short name is also used for authorisation and must 
be locally defined to the OS so that permissions can be calculated. 
 There are various configuration rules for different modes of connection, to specify whether a 
password is required, optional or ignored. 
© 2014 IBM Corporation
MQ Security - Authorisation 
$ crtmqm –oa user QMU 
---------------- 
Service: 
© 2014 IBM Corporation 
 Make Unix OAM userid-based 
 Optional configuration 
 Consistent with other platforms 
 Will no longer add primary group 
to authorities during setmqaut 
 Chosen at queue manager creation 
or by editing qm.ini 
 Default is still group-based authorisations 
 Delete Authority record by SID 
Name=AuthorizationService 
EntryPoints=14 
SecurityPolicy=User 
 Solve problem of orphaned authorities when Windows id is deleted
MQ Security - Authorisation 
N 
O 
T 
E 
S 
 One further point of consistency in this release is making the Unix authorisation model the 
same as for Windows – permissions can now be set for individual users, and not just groups. 
So running a command such as setmqaut –t qmgr –p usr1 +connect works for just that user, 
and not the primary group. 
 This is configured by either creating the queue manager with the -oa user option or by 
editing the ini file as shown for existing queue managers – restarting the queue manager sets 
it to work in the new mode. The change is deliberately not dynamic, and requires the restart, 
because it is so fundamental to how the queue manager permissions operate, and is not 
something we would expect to be done frequently. 
 All existing permissions are left unchanged when you switch to user-mode authorisations, so 
the group permissions that have been set remain, but new permissions can be set for the 
users. 
 The user-based model is not the default for new queue managers; to keep compatibility with 
older systems, the default is still the group-based model. 
 One final security feature is specifically for Windows, to deal with situations where users have 
been deleted from the system but their MQ permissions have not been deleted from the OAM. 
You can now use the setmqaut command to delete permissions based on SID instead of 
name, and this will remove the orphaned entries. 
© 2014 IBM Corporation
MQ Security - CHLAUTH 
 Use DNS hostnames in CHLAUTH records 
 Not allowed in TYPE(BLOCKADDR) 
 Used in TYPE(ADDRESSMAP) instead of an IP address 
 Also as an address restrictor on any other mapping type, instead of an IP address, e.g. 
 SET CHLAUTH(‘*’) TYPE(SSLPEERMAP) 
SSLPEER(‘CN=“Morag Hughson”’) ADDRESS(‘*.ibm.com’) MCAUSER(HUGHSON) 
 Must ensure DNS can reverse look-up IP address - Hostname 
 Also we provide a way to disable reverse lookup 
 ALTER QMGR REVDNS(ENABLED|DISABLED) 
 CHLAUTH also hooks into other security features in V8 
 Granular connection authentication control with CHCKCLNT on CHLAUTH rules 
 Better Certificate DN filtering with SSLCERTI on CHLAUTH rules 
© 2014 IBM Corporation 
A31: IBM MQ 
CHLAUTH 
rules – with 
MQ V8 updates
MQ Security - CHLAUTH 
N 
O 
T 
E 
S 
 The CHLAUTH rules that were introduced in V7.1 have been extended to meet the 
most frequently-requested enhancement – the ability to use hostnames in the rules 
as well as IP addresses. Names can be used all the same rules, and in the same 
way, as IP addresses with the one exception of the listener blocking which is still 
only address-based. 
 The hostnames can include wildcard patterns such as *.example.com. The 
matching is simple string-based; the . characters are not treated as special 
separators. 
© 2014 IBM Corporation
MQ Security - Certificates 
 Configurable default certificate label for qmgrs and clients 
 Instead of ibmwebspheremqqmgr or ibmwebspheremquserid“ 
 ALTER QMGR CERTLABL('My certificate name') 
© 2014 IBM Corporation 
 Channel-level certificates 
 To support different business partners using different CAs. 
 For queue managers and C clients 
 Not Java yet, because Java 7 JSSE does not fully support SNI 
 Both ends must be V8 
 Per Channel Certificate 
 ALTER CHANNEL … CERTLABL('This channel certificate') 
 Certificate Matching 
 SET CHLAUTH('*') 
TYPE(SSLPEERMAP) 
SSLPEER('CN=Morag Hughson') 
SSLCERTI('CN=IBM CA') 
MCAUSER('hughson') 
A22: New 
IBM MQ V8 
Security 
Features
MQ Security - Certificates 
N 
O 
T 
E 
S 
 The label used to find the queue manager or client's certificate in the SSL keystore 
is now configurable. This gives more flexibility in naming, and can even permit 
sharing of the keystore between multiple queue managers if you wish. On z/OS, 
there is in addition a configuration attribute for the QSG-related certificate 
(traditionally ibmwebspheremqqsgname. 
 A further extension for certificate use is designed for scenarios where you may wish 
to use different certificates when communicating with different partners. A common 
reason for this is when a queue manager is used for both internal-facing channels 
and for connections to a partner, who may have different certificate requirements, 
such as using a different CA. You can now configure a different certificate label to 
be used on individual channels. The implementation of this requires both ends of 
the channel to be at MQ V8, as there has to be cooperation between the sending 
side and the receiving side of the channel. And it is not available in all 
environments; in particular, Java clients cannot currently participate as the standard 
JSSE provider does not yet support the Server Name Indication (SNI) flows that go 
alongside the socket setup calls. 
© 2014 IBM Corporation
Pub/sub scalability - cluster behaviour before V8 
 All queue managers in a cluster know everything and need to be able to connect 
© 2014 IBM Corporation 
to anyone 
CLUS1 
FR 
TOPIC(T1) CLUSTER(CLUS1) 
Sub to T1 
Pub to T1 
Queue manager 
CLUSQMGR knowledge 
Channel 
Proxy subscription
Pub/sub scalability - cluster behaviour before V8 
N 
O 
T 
E 
S 
 Every queue manager is aware of every subscribed topic string and queue 
manager in the cluster 
 It’s very easy to end up with a fully interconnected cluster 
 The load per queue manager is proportional to the total number of queue 
managers in the cluster 
 Many systems in larger clusters are not designed to support such a configuration 
 Imagine what is happening in a busy cluster with hundreds of queue managers or 
more 
© 2014 IBM Corporation
Pub/sub scalability - cluster behaviour with V8 
FR 
© 2014 IBM Corporation 
 New concept of routed topics 
 Configure subset of queue managers to know everything and connect to 
everyone 
 Publications sent via these 
queue managers 
Queue manager 
CLUSQMGR knowledge 
Channel 
Proxy subscription 
CLUS1 
TOPIC(TOPIC1) CLUSTER(CLUS1) 
Sub to T1 
Pub to T1 
A16: Using 
IBM MQ 
Pub/Sub in an 
MQ network
N 
O 
T 
E 
S 
© 2014 IBM Corporation 
Routed topics 
 Publish/subscribe across a cluster previously required direct connectivity between all 
publishing queue managers and subscribing queue managers. 
 Now routing via intermediary queue managers in the cluster is possible 
– The aim is to allow topologies where queue manager-to-queue manager connectivity and knowledge is restricted 
 With DIRECT pub/sub: 
– Direct publication routing 
– Every queue manager must scale with the size of the system 
 With ROUTED pub/sub 
– The load on the majority of queue managers is independent from the size of the system 
– Publications may incur additional hops 
 Messages published on topic host routed topics are similar to messages put to clustered 
queues: 
– Think of a routed topic def as a clustered queue and a publisher to the topic as an app putting to that queue 
– Each message published is sent to one of the topic host queue managers, and from there onto the queue managers 
where subscriptions exist 
– Messages are workload balanced across all topic hosts with available channels from the publishing queue manager to the 
topic hosts 
– Unavailable topic hosts are avoided 
– Workload balancing behaviour is as for a clustered queue using all default settings (CLWLPRTY, CLWLRANK, etc.) 
except for DEFBIND, which is effectively set to NOT_FIXED 
– Each individual message is ‘evenly’ workload balanced across topic hosts 
– Workload balancing is based on the cluster channel rather than the topic (as for queues), so channel workload 
balancing control still applies (CLWLPRTY, CLWLRANK, CLWLWGHT)
Configuration of routed topics 
 Topic routing is configured in the TOPIC object definition 
CLUSTER(clustername) 
CLROUTE(DIRECT|TOPICHOST) 
© 2014 IBM Corporation 
 Uses the CLROUTE property: 
DEFINE TOPIC(topic) 
 DIRECT: Provides V7 behaviour, publications travel directly from publishing queue managers 
to subscribing queue managers 
 TOPICHOST: publications travel via a topic hosting queue manager 
 New function in MQ V8 
Only V8 queue managers can participate in routed clustered publish/subscribe 
Full repositories must also be at V8 
Older queue managers are not told of the routed topic definitions and therefore 
behave as if the topic was not clustered. 
All V7 queue managers can continue to participate in direct clustered pub/sub
Improved pub/sub status reporting 
 Additional display attributes on DISPLAY PUBSUB. 
 Permits detection of unexpected growth in topics/subscriptions 
 Can gauge the magnitude of a DISPLAY TPSTATUS/SUB/SBSTATUS command. 
© 2014 IBM Corporation 
DISPLAY PUBSUB ALL 
3 : DISPLAY PUBSUB ALL 
AMQ8723: Display pub/sub status details. 
QMNAME(QMGR3) 
TYPE(LOCAL) 
STATUS(ACTIVE) 
SUBCOUNT(241) 
TPCOUNT(105)
General pub/sub improvements 
 More efficient handling of subscriptions for popular topic sub-trees and dynamic 
subscriptions 
 MQ V7.x behaviour sends out individual proxy subscriptions 
 MQ V8 topic object with PROXYSUB set to FORCE 
 Generates a single wildcarded subscription 
 Disables individual proxy subs for topic strings lower in the topic tree 
 Better pub/sub error handling in multi-queue manager environments 
 Selectors are evaluated on the message as published, before modification by the 
publish operation, for delivery to each subscriber 
 More efficient handling of large numbers of topics 
 Linear scaling to at least a million topics 
© 2014 IBM Corporation
General pub/sub improvements 
N 
O 
T 
E 
S 
 In a publish/subscribe hierarchy, or cluster, proxy subscriptions are used to indicate 
which queue managers in the topology publications need to be propagated to for 
remote subscribers. If applications have short-lived subscriptions the delay 
incurred propagating the proxy subscriptions to all queue managers can result in 
some remote publications not being delivered. PROXYSUB(FORCE) can be 
specified on a topic to force all publications to be propagated to all remote queue 
managers. This avoids this problem at the expense of propagating messages even 
when there are no subscribers connected to a queue manager. In version 8 using 
PROXYSUB(FORCE) also significantly reduces the overhead of propagating proxy 
subscriptions for a given topic node. 
 Internal topic tree management has been enhanced for large numbers of topics. 
Performance should scale linearly up to at least a million topics. 
 The DISPLAY PUBSUB command has also been enhanced to report the total 
number of topics and subscribers. This can be used to detect growth in these and 
help determine the potential impact of a wildcard in a DISPLAY 
TOPIC/SUB/TPSTATUS/SBSTATUS command. 
© 2014 IBM Corporation
Distributed Performance 
 Improvements to distributed queue manager scaling 
 Improve efficiency 
 Less targeted at internal benchmarks – hopefully more realistic scenarios 
 Better exploitation of wider SMP machines 
© 2014 IBM Corporation 
 Multiplexed client performance 
 Increase the performance of multiplexed client channels (SHRCONV  0) 
 Especially for SHRCONV=1 
 Other areas that helped: 
 Cache alignment for internal structures 
 Extended 64-bit exploitation for locking primitives 
 RFH2 handling, particularly for waiting-getter 
 Fewer copies of data are needed 
 Better compiler optimisations 
 Faster data conversion (especially for 1208) 
 Many messages are in 1208 codepage 
 Optimised handling when the queue manager needs to convert them
Performance improvements 
N 
O 
T 
E 
S 
 A number of enhancements have been implemented in version 8 to improve the vertical 
scaling of queue managers on the distributed platforms. Some of these improvements are 
listed on the previous slide. 
 We’ve also updated the focus of our performance testing to be less reliant on some internal 
benchmarks that do not represent realistic customer workloads. Although each customer 
workload is different, so guarantees are not possible, the performance improvements in 
version 8 are more likely to be relevant to real-world scenarios. 
 Prior to version 7 each client conversation uses a separate socket and channel instance. If 
clients establish multiple conversations using different threads this can create a large demand 
for sockets on the server. Each channel instance also requires storage on the queue 
manager. 
 In version 7 support was added to allow client conversations to share the same 
socket/channel instance. This can significantly reduce the resource overhead associated with 
these connections. Support for bi-directional communication was also introduced that 
supports new capabilities, such as heartbeats, read-ahead and asynchronous message 
consumption. 
 However, if multiple conversations share the same socket, contention can arise if the total 
workload for the conversations exceeds the capacity of the socket. Additionally, an overhead 
is also introduced to serialize access when sending and receiving TCP/IP data. 
 SHARECNV(0) disables all version 7 enhancements. SHARECNV(1) can be used to disable 
only conversation sharing. Unfortunately, in version 7 the latter incurs a notable performance 
overhead as a result of enabling the other version 7 capabilities. In version 8, support for 
SHARECNV(1) has been optimized to achieve parity with SHARECNV(0). 
© 2014 IBM Corporation
Multiple cluster transmission queues 
 Multiple cluster transmission queues added in V7.5 
 Support for z/OS and IBM i added in V8 
 Benefits of using multiple transmission queues 
© 2014 IBM Corporation 
 Separation of message traffic 
 With a single transmission queue, pending messages for one channel can interfere with 
those for another, especially when messages build up on the queue 
 Management of messages 
 Use of queue concepts such as MAXDEPTH are not useful when using a single 
transmission queue for all cluster-sender channels 
 System monitoring 
 Tracking the number of messages processed by a cluster-sender channel is not possible 
using queue monitoring if a single transmission queue is shared by multiple channels, 
although some information is available using channel status
Multiple cluster transmission queues 
N 
O 
T 
E 
S 
 Support for multiple cluster transmission queues was added on the distributed 
platforms in version 7.5. Version 8 adds support for this capability on z/OS and 
IBM i. 
 A different transmission queue can now be used by each cluster-sender channel, or 
a subset of cluster-sender channels, instead of all channels using 
SYSTEM.CLUSTER.TRANSMIT.QUEUE. 
 The introduction of multiple cluster transmission queues is not designed to improve 
performance, but to provide a capability to isolate message traffic. 
– It is quicker to assess the impact of an issue if traffic is separated for different applications. 
– If a queue manager is a member of multiple clusters, a different transmission queue can be used for 
each cluster. This can prevent a build up of messages for one cluster, that results in a full page set or 
MAXDEPTH being reached, impacting the other clusters. 
– If messages for different applications are sent over different cluster channels* a problem for one 
application can be prevented from impacting others. 
 * This can be achieved by using a separate cluster for each application, which may 
overlap with other clusters, or hosting the target queues for each application on 
different cluster queue managers. 
© 2014 IBM Corporation
Configuring cluster transmission queues 
 DEFCLXQ queue manager attribute 
 Default transmission queue for cluster-sender channels 
 SCTQ 
 Use SYSTEM.CLUSTER.TRANSMIT.QUEUE 
© 2014 IBM Corporation 
 CHANNEL 
 Create a permanent-dynamic transmission queue per cluster-sender channel called 
SYSTEM.CLUSTER.TRANSMIT.channel name 
 CLCHNAME queue attribute 
 Set on a manually defined transmission queue 
 Generic name for channels that should use it 
 DEFINE QLOCAL(CLUSTER.XMITQ1) USAGE(XMITQ) CLCHNAME(‘AAA.*’) … 
 Most specific match is used by a channel 
A17: Managing 
work-loads, 
scaling and 
availability with 
IBM MQ 
clusters
Configuring cluster transmission queues 
N 
O 
T 
E 
S 
 The transmission queue to use for each channel can be configured in two ways: 
 A manually defined transmission queue can be configured using the CLCHNAME 
attribute. The value of this attribute is a generic, or specific, name for the channels 
that should use it. The mapping is defined on the transmission queue instead of the 
channel because the channel’s definition is determined from the cluster-receiver 
definition on the remote queue manager. If a channel’s name matches multiple 
CLCHNAME values the most specific match is used to determine which transmission 
queue to use. 
 If no matching queue is found the queue manager uses the default transmission 
queue setting, specified by the DEFCLXQ queue manager attribute, to determine 
which transmission queue to use. This attribute indicates whether to use 
SYSTEM.CLUSTER.TRANSMIT.QUEUE or to create a permanent-dynamic 
transmission queue called SYSTEM.CLUSTER.TRANSMIT.channel name. 
© 2014 IBM Corporation
MQ for z/OS: 64-bit bufferpools 
© 2014 IBM Corporation 
 64-bit buffer pools in MQ for z/OS 
 Allows large numbers of messages to be cached before writing to pagesets 
 Allows MQ to exploit the vast amount of storage on today's machines 
 Improves performance of putting/getting messages by 
minimizing disk I/O 
 Minimizes administrative overhead of managing buffer pools 
 Buffer pool LOCATION attribute says where it is located relative to the bar 
 BELOW: The default. Buffer pool is located below the bar in 31 bit storage 
 ABOVE: Buffer pool is located above the bar in 64 bit storage 
 This can be altered dynamically 
 Storage can be pinned based on pageclass attribute 
Z1: 
IBM MQ for 
z/OS V8 
Latest Features 
Deep Dive
Buffer pool problems before V8 
N 
O 
T 
E 
S 
 There is not much space below the bar for buffer pools once queue manager code 
and data is taken into account. Maximum 1.6GB available for buffer pools 
depending on common area 
 Putting/getting messages into the buffer pool works at 'memory' speed, 
putting/getting messages from the page set works at 'disk' speed 
 For scenarios where several applications read and/or write large number of 
messages to the same buffer pool a lot of time is spent getting pages from page set 
into buffer pool and getting pages from buffer pool into page set 
© 2014 IBM Corporation 
– This is detrimental for performance 
 A maximum of 16 buffer pools are supported while up to 100 page sets are 
supported 
 This can result in a lot of time spent tuning buffer pool sizes and the relationship 
between queues, buffer pools and page sets 
 These problems are resolved by allowing bufferpools to be defined in 64-bit space, 
above the bar
MQ for z/OS: 64-bit bufferpools 
 Buffer pools above the bar can (theoretically) use up to 16 EB storage 
DATA 
© 2014 IBM Corporation 
 Increased maximum size of pool to 
999,999,999 buffers 
 Was 500,000 
DATA 
CODE 
Buffer Pool 
Buffer 
Pool 
Buffer 
Pool 
Buffer Pool 
16 EB 
2 GB BAR 
Up to 1.6 GB 
Available 
Queue Manager Address Space 
Buffer 
Pool 
 Allows up to 100 buffer pools 
 Was 16 
 Can have a 1-1 page set – buffer pool mapping
MQ for z/OS: 64-bit bufferpools 
N 
O 
T 
E 
S 
 64-bit bufferpools can now theoretically use a huge amount of storage 
 Having the same number of pools and pagesets makes it much simpler to monitor 
and control the usage of these resources 
 SMF 115, subtype 215 
– Up to 100 buffer pools are now supported. However there is not enough space for 100 buffer manager 
statistics records (QPST) in the existing SMF 115, subtype 2, record 
– If OPMODE(NEWFUNC,800) is specified in system parameters then an SMF 115, subtype 215, record 
will be cut for buffer manager statistics. The SMF 115, subtype 2, record will still contain the self-defining 
section for buffer manager but it will be all zeros 
– If OPMODE(COMPAT,800) is specified in system parameters then buffer manager statistics will 
continue to be in SMF 115, subtype 2. 
© 2014 IBM Corporation
MQ for z/OS: Performance and Capacity 
© 2014 IBM Corporation 
 Log RBA constraint relief 
 Already improved messages to warn of approaching RBA 
 Now widening RBA field from 6 to 8 bytes 
 At 100MB/sec this will now take about 5578 years to fill 
 Support for LP64 batch/RRS C applications 
 Performance enhancements for IBM Information Replicator (QRep) and similar 
application patterns 
 Read-ahead and changes to deferred write processing allows MQ to increase sustainable data 
rates 
 General improvements to channel performance
Log RBA extensions 
N 
O 
T 
E 
S 
 WebSphere MQ for z/OS V7 implements a 6 byte Log RBA (Relative Byte Address) 
– This give an RBA range of 0 to x'FFFFFFFFFFFF' (= 255TB) 
– Some customers are now reaching this limit in 12 months 
 If we reach the end of the Log RBA range (i.e. “wrap”): 
– Queue Manager terminates and requires a cold start – a disruptive outage 
– Potential for loss of persistent data 
© 2014 IBM Corporation 
 To avoid an outage: 
– Run CSQUTIL RESETPAGE, at regular planned intervals, to RESET the LOG RBA 
 With current maintenance, MQ V7.x issues warning messages when approaching maximum 
– Then terminates, to prevent loss of data, if log RBA reaches x'FFF800000000'. 
 V8 increases size of Log RBA to 8 bytes 
– Upper limit on logical log will be 64K times bigger 
– Format of BSDS and log records will change to accommodate 8 byte RBAs, URIDs will become 8 bytes long 
– Like DB2, the control point for new function is a BSDS conversion utility 
– Run the new CSQJUCNV utility 
– utility will check that entire QSG is at correct level 
– copies data from old primary / secondary BSDS pair to new primary / secondary pair 
 All V8 queue managers can read data in both the old and new formats 
 All V8 queue managers and utilities will display all log RBAs as 8 bytes 
 V8 will ONLY write in new format, once BSDS has been converted
N 
O 
T 
E 
S 
© 2014 IBM Corporation 
LP64 Support 
 Externalising technology previously used by Broker and JMS 
 Limited to C language (no 64bit COBOL) 
– LP64 compile option 
– Supported by cmqc.h 
 Restricted environments 
– Batch, TSO, USS 
– CICS and IMS do not support 64bit apps 
 Must use sidedeck  DLL, not stubs: 
– csqbmq2x (uncoordinated batch  USS) 
– csqbrr2x (RRS coordinated, srrcmit()) 
– csqbri2x (RRS coordinated, MQCMIT)
Performance improvements 
N 
O 
T 
E 
S 
 QRep has implemented a common application pattern – basically a single-stream 
reading or writing of messages. That program, and others that follow the same 
pattern, can benefit from some of the performance enhancements in MQ. For 
example, fetching data for the next message from a pageset at the same time as 
for the current message (readahead) can reduce the I/O operations and hence 
reduce CPU and increase throughput. 
© 2014 IBM Corporation
MQ for z/OS: Other features 
 Exploitation of zEDC compression accelerator 
 SMF 
 Channel compression (zlibfast option) can be useful when using SSL 
 Support for Flash Express feature on zEC12 and zBC12 servers 
 Improves resiliency of Coupling Facility with cost-effective standby capacity to handle overflow 
© 2014 IBM Corporation 
of shared queues 
 Messages 63K fully held in Flash 
 Messages 63K have pointers in Flash, body in SMDS just as for traditional CF structures 
 SMF enhancements 
 Channel statistics allow better monitoring and tuning of 
channel behaviour 
 Correlation of MQ and CICS statistics 
 Message suppression 
A4: IBM MQ for 
z/OS: 
Performance 
and 
Accounting 
 Up to 16 message numbers (particularly X500,X501) can be defined to be excluded 
 Removes cost of writing WTO messages which are then ignored 
 Can now differentiate between messages for client channels and other types
MQ for z/OS: Other features 
N 
O 
T 
E 
S 
 A number of internal performance improvements have been implemented in version 
8, including some internal optimisations in the channel initiator. 
 Some changes have been introduced to significantly improve performance for IBM 
Information Replicator (QREP). This product is used to replicate DB2 logs from one 
system to another. It is used for disaster recovery and in IBM’s active-active 
solution for z/OS. The improvements made for this type of workload include 
support for pre-fetching pages from page sets in to buffers and optimizations to the 
algorithm used to write data to page sets too. These improvements are likely to 
also benefit other customer workloads. 
 If you configure channel compression using MSGCOMP(ZLIBFAST) and you are 
running on suitable zEC12 hardware, a zEDC card is exploited if available. This 
can improve performance as well as reducing CPU activity. 
 Another improvement, although not strictly for performance, is the introduction of a 
new system parameter, EXCLMSG, that allows you to suppress up to 16 console 
messages. This can be used to reduce ‘noise’ on the console. It is preferable to 
using the z/OS Message Processing Facility (MPF) to suppress messages, 
because using this parameter avoids the CPU overhead of generating the message 
and issuing the WTO. 
© 2014 IBM Corporation
IBM has a 20 year track record of innovation in Messaging 
Multi-platform 
Common criteria 
Multiple cluster 
XMIT queue 
Hypervisors 
Integrated 
Messaging 
V7.1 
V7.5 
IBM MQ 
Advanced 
1990s 2000s 2010s 
© 2014 IBM Corporation 
JMS 
MQI 
Assured 
delivery 
IBM 
MQSeries 
Mobile 
.NET 
Eclipse 
JMS 1.1 
RCMS 
IBM MQ Low 
Latency 
V1.1 
V2 
V5 V5.1 
V5.3 
V2.1 
V5.2 
V6 
V7 
V7.0.1 
SSL 
SOAP 
XML 
IBM MQ 
Managed File 
Transfer 
IBM MQTT 
HTTP 
AJAX 
REST 
Web 2.0 
Managed 
File Transfer 
Pub/sub 
IBM MQ 
Everyplace 
IBM MQ 
Advanced 
Message 
Security 
System Pattern 
Application Pattern 
V8 
IBM MQ 
Advanced for 
Developers 
IBM 
MessageSight 
Multi-instance 
QMGR 
20th 
Anniversary of 
MQ at IMPACT
And continues to invest in all Messaging markets 
 Enterprise Messaging where MQ continues to lead 
 Messaging for Mobile and the Internet of Things 
 Supporting Cloud deployments with Messaging services 
 Helping developers use Application Messaging to create better 
© 2014 IBM Corporation 
applications
For Additional Information 
© 2014 IBM Corporation 
 IBM Training 
 http://www.ibm.com/training 
 IBM WebSphere 
 http://www.ibm.com/software/websphere/ 
 http://www.ibm.com/software/products/ibm-mq 
 IBM developerWorks 
 http://www.ibm.com/developerworks/websphere 
 https://www.ibm.com/developerworks/community/blogs/messaging 
 WebSphere forums and community 
 http://www.ibm.com/developerworks/websphere/community/
For Additional Information about IBM MQ V8 
© 2014 IBM Corporation 
 https://www.ibm.com/developerwo 
rks/community/blogs/messaging/e 
ntry/where_can_i_find_mq_v8_inf 
ormation 
 https://www.google.co.uk/search? 
q=MQDev+MQ+V8+information
IBM MQ Sessions this week 
10:30 9:00 - 10:00 - 11:30 11:45 - 12:45 14:00 - 15:00 15:15 - 16:15 16:45 - 17:45 
© 2014 IBM Corporation 
Session A35: How to 
Develop Responsive 
Applications with IBM 
MQ Light 
Speaker: Rob Nicholson 
Room 27 
Session A9: WebSphere MQ 
for z/OS: The Inside Story 
Speaker: Damon Cross 
Room 6 
Session A16: Using 
IBM MQ Pub/Sub in 
an MQ network 
Speaker: David Ware 
Room 6 
Session A21: What's 
New in IBM Messaging 
Speaker: Morag Hughson 
Room 8 
Lab AL6: Developing a First Application with 
IBM WebSphere MQ Light 
Speakers: Robert Nicholson, Alex Ross 
Room 7b 
Friday 
Session A18: Using Publish 
/Subscribe with IBM MQ 
Speaker: David Ware 
Room 27 
Session A3: WebSphere 
MQ for z/OS: Shared 
Queues 
Speaker: Alex Ross 
Room 6 
Session A22: New IBM 
MQ V8 Security 
Features 
Speaker: Morag Hughson 
Room 01 
Thursday 
Lab IL5: DataPower-MQ Connectivity Deep Dive 
(Hands-On) 
Speaker: Robin Wiley 
Room 7b 
Session A17: Managing 
work-loads, scaling and 
availability with IBM MQ 
clusters 
Speaker: David Ware 
Room 6 
Session C7: 
Messaging in the 
Cloud with IBM MQ 
Light and IBM Bluemix 
Speaker: Rob Nicholson 
Room 27 
Session Z5: 
WebSphere MQ for 
z/OS: Security 
Speaker: Damon Cross 
Room 02 
Wednesday 
Session Z1: WebSphere MQ 
for z/OS V8: Latest Features 
Deep Dive 
Speaker: Damon Cross 
Room 6 
Session I26: DataPower- 
MQ Connectivity Deep 
Dive (Theory) 
Speaker: Robin Wiley 
Room 27 
Session A4: WebSphere 
MQ for z/OS: Performance 
and Accounting 
Speaker: Alexander Ross 
Room 8 
Session A31: IBM MQ 
CHLAUTH rules – with 
MQ V8 updates 
Speaker: Morag Hughson 
Room 02 
Opening General Session- IBM Digital 
Experience and WebSphere Technical 
University 
Tuesday 
10:30 - 12:00 13:15 - 14:15 14:30 - 15:30 16:00 - 17:00 17:15 - 18:15
Questions  Answers

More Related Content

What's hot

IBM MQ Clustering (2017 version)
IBM MQ Clustering (2017 version)IBM MQ Clustering (2017 version)
IBM MQ Clustering (2017 version)MarkTaylorIBM
 
Secure Your Messages with IBM MQ Advanced Message Security
Secure Your Messages with IBM MQ Advanced Message SecuritySecure Your Messages with IBM MQ Advanced Message Security
Secure Your Messages with IBM MQ Advanced Message SecurityMorag Hughson
 
IBM WebSphere MQ V8 Security Features: Deep Dive
IBM WebSphere MQ V8 Security Features: Deep DiveIBM WebSphere MQ V8 Security Features: Deep Dive
IBM WebSphere MQ V8 Security Features: Deep DiveMorag Hughson
 
WMQ Toolbox: 20 Scripts, One-liners, & Utilities for UNIX & Windows
WMQ Toolbox: 20 Scripts, One-liners, & Utilities for UNIX & Windows WMQ Toolbox: 20 Scripts, One-liners, & Utilities for UNIX & Windows
WMQ Toolbox: 20 Scripts, One-liners, & Utilities for UNIX & Windows T.Rob Wyatt
 
3429 How to transform your messaging environment to a secure messaging envi...
3429   How to transform your messaging environment to a secure messaging envi...3429   How to transform your messaging environment to a secure messaging envi...
3429 How to transform your messaging environment to a secure messaging envi...Robert Parker
 
What's new in IBM MQ Messaging
What's new in IBM MQ MessagingWhat's new in IBM MQ Messaging
What's new in IBM MQ MessagingMarkTaylorIBM
 
MQ Security Overview
MQ Security OverviewMQ Security Overview
MQ Security OverviewMarkTaylorIBM
 
IBM MQ - better application performance
IBM MQ - better application performanceIBM MQ - better application performance
IBM MQ - better application performanceMarkTaylorIBM
 
HHM-2833: Where is My Message?: Using IBM MQ Tools to Work Out What Applicati...
HHM-2833: Where is My Message?: Using IBM MQ Tools to Work Out What Applicati...HHM-2833: Where is My Message?: Using IBM MQ Tools to Work Out What Applicati...
HHM-2833: Where is My Message?: Using IBM MQ Tools to Work Out What Applicati...Matt Leming
 
IBM WebSphere MQ: Managing Workloads, Scaling and Availability with MQ Clusters
IBM WebSphere MQ: Managing Workloads, Scaling and Availability with MQ ClustersIBM WebSphere MQ: Managing Workloads, Scaling and Availability with MQ Clusters
IBM WebSphere MQ: Managing Workloads, Scaling and Availability with MQ ClustersDavid Ware
 
IBM MQ: Managing Workloads, Scaling and Availability with MQ Clusters
IBM MQ: Managing Workloads, Scaling and Availability with MQ ClustersIBM MQ: Managing Workloads, Scaling and Availability with MQ Clusters
IBM MQ: Managing Workloads, Scaling and Availability with MQ ClustersDavid Ware
 
Websphere MQ (MQSeries) fundamentals
Websphere MQ (MQSeries) fundamentalsWebsphere MQ (MQSeries) fundamentals
Websphere MQ (MQSeries) fundamentalsBiju Nair
 
IBM MQ Online Tutorials
IBM MQ Online TutorialsIBM MQ Online Tutorials
IBM MQ Online TutorialsBigClasses.com
 
IBM MQ for z/OS The Latest and Greatest Enhancements
IBM MQ for z/OS The Latest and Greatest EnhancementsIBM MQ for z/OS The Latest and Greatest Enhancements
IBM MQ for z/OS The Latest and Greatest EnhancementsPete Siddall
 
IBM MQ v8 and JMS 2.0
IBM MQ v8 and JMS 2.0IBM MQ v8 and JMS 2.0
IBM MQ v8 and JMS 2.0Matthew White
 
Where is my MQ message on z/OS?
Where is my MQ message on z/OS?Where is my MQ message on z/OS?
Where is my MQ message on z/OS?Matt Leming
 
Where is My Message
Where is My MessageWhere is My Message
Where is My MessageMatt Leming
 
IBM MQ - Comparing Distributed and z/OS platforms
IBM MQ - Comparing Distributed and z/OS platformsIBM MQ - Comparing Distributed and z/OS platforms
IBM MQ - Comparing Distributed and z/OS platformsMarkTaylorIBM
 
IBM WebSphere MQ: Using Publish/Subscribe in an MQ Network
IBM WebSphere MQ: Using Publish/Subscribe in an MQ NetworkIBM WebSphere MQ: Using Publish/Subscribe in an MQ Network
IBM WebSphere MQ: Using Publish/Subscribe in an MQ NetworkDavid Ware
 

What's hot (20)

IBM MQ Clustering (2017 version)
IBM MQ Clustering (2017 version)IBM MQ Clustering (2017 version)
IBM MQ Clustering (2017 version)
 
Secure Your Messages with IBM MQ Advanced Message Security
Secure Your Messages with IBM MQ Advanced Message SecuritySecure Your Messages with IBM MQ Advanced Message Security
Secure Your Messages with IBM MQ Advanced Message Security
 
IBM WebSphere MQ V8 Security Features: Deep Dive
IBM WebSphere MQ V8 Security Features: Deep DiveIBM WebSphere MQ V8 Security Features: Deep Dive
IBM WebSphere MQ V8 Security Features: Deep Dive
 
WMQ Toolbox: 20 Scripts, One-liners, & Utilities for UNIX & Windows
WMQ Toolbox: 20 Scripts, One-liners, & Utilities for UNIX & Windows WMQ Toolbox: 20 Scripts, One-liners, & Utilities for UNIX & Windows
WMQ Toolbox: 20 Scripts, One-liners, & Utilities for UNIX & Windows
 
3429 How to transform your messaging environment to a secure messaging envi...
3429   How to transform your messaging environment to a secure messaging envi...3429   How to transform your messaging environment to a secure messaging envi...
3429 How to transform your messaging environment to a secure messaging envi...
 
What's new in IBM MQ Messaging
What's new in IBM MQ MessagingWhat's new in IBM MQ Messaging
What's new in IBM MQ Messaging
 
MQ Security Overview
MQ Security OverviewMQ Security Overview
MQ Security Overview
 
IBM MQ - better application performance
IBM MQ - better application performanceIBM MQ - better application performance
IBM MQ - better application performance
 
HHM-2833: Where is My Message?: Using IBM MQ Tools to Work Out What Applicati...
HHM-2833: Where is My Message?: Using IBM MQ Tools to Work Out What Applicati...HHM-2833: Where is My Message?: Using IBM MQ Tools to Work Out What Applicati...
HHM-2833: Where is My Message?: Using IBM MQ Tools to Work Out What Applicati...
 
IBM WebSphere MQ: Managing Workloads, Scaling and Availability with MQ Clusters
IBM WebSphere MQ: Managing Workloads, Scaling and Availability with MQ ClustersIBM WebSphere MQ: Managing Workloads, Scaling and Availability with MQ Clusters
IBM WebSphere MQ: Managing Workloads, Scaling and Availability with MQ Clusters
 
IBM MQ: Managing Workloads, Scaling and Availability with MQ Clusters
IBM MQ: Managing Workloads, Scaling and Availability with MQ ClustersIBM MQ: Managing Workloads, Scaling and Availability with MQ Clusters
IBM MQ: Managing Workloads, Scaling and Availability with MQ Clusters
 
Websphere MQ (MQSeries) fundamentals
Websphere MQ (MQSeries) fundamentalsWebsphere MQ (MQSeries) fundamentals
Websphere MQ (MQSeries) fundamentals
 
WebSphere MQ tutorial
WebSphere MQ tutorialWebSphere MQ tutorial
WebSphere MQ tutorial
 
IBM MQ Online Tutorials
IBM MQ Online TutorialsIBM MQ Online Tutorials
IBM MQ Online Tutorials
 
IBM MQ for z/OS The Latest and Greatest Enhancements
IBM MQ for z/OS The Latest and Greatest EnhancementsIBM MQ for z/OS The Latest and Greatest Enhancements
IBM MQ for z/OS The Latest and Greatest Enhancements
 
IBM MQ v8 and JMS 2.0
IBM MQ v8 and JMS 2.0IBM MQ v8 and JMS 2.0
IBM MQ v8 and JMS 2.0
 
Where is my MQ message on z/OS?
Where is my MQ message on z/OS?Where is my MQ message on z/OS?
Where is my MQ message on z/OS?
 
Where is My Message
Where is My MessageWhere is My Message
Where is My Message
 
IBM MQ - Comparing Distributed and z/OS platforms
IBM MQ - Comparing Distributed and z/OS platformsIBM MQ - Comparing Distributed and z/OS platforms
IBM MQ - Comparing Distributed and z/OS platforms
 
IBM WebSphere MQ: Using Publish/Subscribe in an MQ Network
IBM WebSphere MQ: Using Publish/Subscribe in an MQ NetworkIBM WebSphere MQ: Using Publish/Subscribe in an MQ Network
IBM WebSphere MQ: Using Publish/Subscribe in an MQ Network
 

Viewers also liked

Prabowo subianto
Prabowo subiantoPrabowo subianto
Prabowo subiantosimon-id
 
Presentation communication skills 3 janis
Presentation communication skills 3 janisPresentation communication skills 3 janis
Presentation communication skills 3 janisJānis Deksnis
 
Comparatives
Comparatives Comparatives
Comparatives elharala
 
Give peace a chance
Give peace a chanceGive peace a chance
Give peace a chanceelharala
 
Ac fbrewingessentials cbury506060
Ac fbrewingessentials cbury506060Ac fbrewingessentials cbury506060
Ac fbrewingessentials cbury506060Cerianne Bury
 
C paton seawater greenhouse somalia uk
C paton seawater greenhouse somalia ukC paton seawater greenhouse somalia uk
C paton seawater greenhouse somalia ukJoy Elliott
 
E gurinova research gardenzf mendel slovakia
E gurinova research gardenzf mendel slovakiaE gurinova research gardenzf mendel slovakia
E gurinova research gardenzf mendel slovakiaJoy Elliott
 
Περιμένοντας ή διαμορφώνοντας το μέλλον; (in Greek)
Περιμένοντας ή διαμορφώνοντας το μέλλον; (in Greek)Περιμένοντας ή διαμορφώνοντας το μέλλον; (in Greek)
Περιμένοντας ή διαμορφώνοντας το μέλλον; (in Greek)Sergios Dimitriadis
 
K denhen schmutz weeds and invasive plants cafs uk
K denhen schmutz weeds and invasive plants cafs ukK denhen schmutz weeds and invasive plants cafs uk
K denhen schmutz weeds and invasive plants cafs ukJoy Elliott
 
MODEL'S 3rd Issue
MODEL'S 3rd IssueMODEL'S 3rd Issue
MODEL'S 3rd Issuefandyyy
 
L owen resilient short food chains cafs uk
L owen resilient short food chains cafs ukL owen resilient short food chains cafs uk
L owen resilient short food chains cafs ukJoy Elliott
 

Viewers also liked (17)

Prabowo subianto
Prabowo subiantoPrabowo subianto
Prabowo subianto
 
Presentation communication skills 3 janis
Presentation communication skills 3 janisPresentation communication skills 3 janis
Presentation communication skills 3 janis
 
Comparatives
Comparatives Comparatives
Comparatives
 
Give peace a chance
Give peace a chanceGive peace a chance
Give peace a chance
 
Ac fbrewingessentials cbury506060
Ac fbrewingessentials cbury506060Ac fbrewingessentials cbury506060
Ac fbrewingessentials cbury506060
 
Snu raz
Snu razSnu raz
Snu raz
 
Sunu (1)
Sunu (1)Sunu (1)
Sunu (1)
 
Sunu (1)
Sunu (1)Sunu (1)
Sunu (1)
 
Ch02 shabab
Ch02 shababCh02 shabab
Ch02 shabab
 
C paton seawater greenhouse somalia uk
C paton seawater greenhouse somalia ukC paton seawater greenhouse somalia uk
C paton seawater greenhouse somalia uk
 
E gurinova research gardenzf mendel slovakia
E gurinova research gardenzf mendel slovakiaE gurinova research gardenzf mendel slovakia
E gurinova research gardenzf mendel slovakia
 
Cöv
CövCöv
Cöv
 
Περιμένοντας ή διαμορφώνοντας το μέλλον; (in Greek)
Περιμένοντας ή διαμορφώνοντας το μέλλον; (in Greek)Περιμένοντας ή διαμορφώνοντας το μέλλον; (in Greek)
Περιμένοντας ή διαμορφώνοντας το μέλλον; (in Greek)
 
Phlebotomy 2
Phlebotomy 2Phlebotomy 2
Phlebotomy 2
 
K denhen schmutz weeds and invasive plants cafs uk
K denhen schmutz weeds and invasive plants cafs ukK denhen schmutz weeds and invasive plants cafs uk
K denhen schmutz weeds and invasive plants cafs uk
 
MODEL'S 3rd Issue
MODEL'S 3rd IssueMODEL'S 3rd Issue
MODEL'S 3rd Issue
 
L owen resilient short food chains cafs uk
L owen resilient short food chains cafs ukL owen resilient short food chains cafs uk
L owen resilient short food chains cafs uk
 

Similar to What's New in IBM Messaging

What's New in IBM MQ - Version 8
What's New in IBM MQ - Version 8What's New in IBM MQ - Version 8
What's New in IBM MQ - Version 8MarkTaylorIBM
 
InterConnect 2016: What's new in IBM MQ
InterConnect 2016: What's new in IBM MQInterConnect 2016: What's new in IBM MQ
InterConnect 2016: What's new in IBM MQDavid Ware
 
Cisco Evolving virtual switching to applications & cloud
Cisco Evolving virtual switching to applications & cloudCisco Evolving virtual switching to applications & cloud
Cisco Evolving virtual switching to applications & cloudsolarisyougood
 
Spirent HyperScale Test Solution
Spirent HyperScale Test SolutionSpirent HyperScale Test Solution
Spirent HyperScale Test SolutionMalathi Malla
 
Cozystack: Free PaaS platform and framework for building clouds
Cozystack: Free PaaS platform and framework for building cloudsCozystack: Free PaaS platform and framework for building clouds
Cozystack: Free PaaS platform and framework for building cloudsAndrei Kvapil
 
What's New In MQ 9.2 on z/OS
What's New In MQ 9.2 on z/OSWhat's New In MQ 9.2 on z/OS
What's New In MQ 9.2 on z/OSMatt Leming
 
Cóndor solución empresarial para entornos empresariales de KEMP Technologies
Cóndor solución empresarial para entornos empresariales de KEMP TechnologiesCóndor solución empresarial para entornos empresariales de KEMP Technologies
Cóndor solución empresarial para entornos empresariales de KEMP TechnologiesPeter Diaz
 
Understanding Platform as a Service
Understanding Platform as a ServiceUnderstanding Platform as a Service
Understanding Platform as a ServicePaul Fremantle
 
Todays Mq Infrastructure And Tomorrows
Todays Mq Infrastructure And TomorrowsTodays Mq Infrastructure And Tomorrows
Todays Mq Infrastructure And Tomorrowsgaborvodics
 
Planning for MQ in the cloud MQTC 2017
Planning for MQ in the cloud MQTC 2017Planning for MQ in the cloud MQTC 2017
Planning for MQ in the cloud MQTC 2017Robert Parker
 
E2EVC SCVMM / Windows Azure Pack
E2EVC SCVMM / Windows Azure PackE2EVC SCVMM / Windows Azure Pack
E2EVC SCVMM / Windows Azure PackMichael Rüefli
 
IBM MQ What's new - Sept 2022
IBM MQ What's new - Sept 2022IBM MQ What's new - Sept 2022
IBM MQ What's new - Sept 2022David Ware
 
CTU June 2011 - Microsoft System Center Virtual Machine Manager 2012
CTU June 2011 - Microsoft System Center Virtual Machine Manager 2012CTU June 2011 - Microsoft System Center Virtual Machine Manager 2012
CTU June 2011 - Microsoft System Center Virtual Machine Manager 2012Spiffy
 
MQ What's New Beyond V8 - V8003 level
MQ What's New Beyond V8 - V8003 levelMQ What's New Beyond V8 - V8003 level
MQ What's New Beyond V8 - V8003 levelMarkTaylorIBM
 
MQ Support for z/OS Connect
MQ Support for z/OS ConnectMQ Support for z/OS Connect
MQ Support for z/OS ConnectMatt Leming
 
Expanding your options with the IBM MQ Appliance - IBM InterConnect 2016
Expanding your options with the IBM MQ Appliance - IBM InterConnect 2016Expanding your options with the IBM MQ Appliance - IBM InterConnect 2016
Expanding your options with the IBM MQ Appliance - IBM InterConnect 2016Leif Davidsen
 
Spirent TestCenter Virtual on OracleVM
Spirent TestCenter Virtual on OracleVMSpirent TestCenter Virtual on OracleVM
Spirent TestCenter Virtual on OracleVMMalathi Malla
 
CloudStack DC Meetup - Apache CloudStack Overview and 4.1/4.2 Preview
CloudStack DC Meetup - Apache CloudStack Overview and 4.1/4.2 PreviewCloudStack DC Meetup - Apache CloudStack Overview and 4.1/4.2 Preview
CloudStack DC Meetup - Apache CloudStack Overview and 4.1/4.2 PreviewChip Childers
 

Similar to What's New in IBM Messaging (20)

What's New in IBM MQ - Version 8
What's New in IBM MQ - Version 8What's New in IBM MQ - Version 8
What's New in IBM MQ - Version 8
 
IBM What's New in MQ V8
IBM What's New in MQ V8IBM What's New in MQ V8
IBM What's New in MQ V8
 
InterConnect 2016: What's new in IBM MQ
InterConnect 2016: What's new in IBM MQInterConnect 2016: What's new in IBM MQ
InterConnect 2016: What's new in IBM MQ
 
Cisco Evolving virtual switching to applications & cloud
Cisco Evolving virtual switching to applications & cloudCisco Evolving virtual switching to applications & cloud
Cisco Evolving virtual switching to applications & cloud
 
Spirent HyperScale Test Solution
Spirent HyperScale Test SolutionSpirent HyperScale Test Solution
Spirent HyperScale Test Solution
 
Cozystack: Free PaaS platform and framework for building clouds
Cozystack: Free PaaS platform and framework for building cloudsCozystack: Free PaaS platform and framework for building clouds
Cozystack: Free PaaS platform and framework for building clouds
 
What's New In MQ 9.2 on z/OS
What's New In MQ 9.2 on z/OSWhat's New In MQ 9.2 on z/OS
What's New In MQ 9.2 on z/OS
 
Cóndor solución empresarial para entornos empresariales de KEMP Technologies
Cóndor solución empresarial para entornos empresariales de KEMP TechnologiesCóndor solución empresarial para entornos empresariales de KEMP Technologies
Cóndor solución empresarial para entornos empresariales de KEMP Technologies
 
Understanding Platform as a Service
Understanding Platform as a ServiceUnderstanding Platform as a Service
Understanding Platform as a Service
 
Todays Mq Infrastructure And Tomorrows
Todays Mq Infrastructure And TomorrowsTodays Mq Infrastructure And Tomorrows
Todays Mq Infrastructure And Tomorrows
 
Planning for MQ in the cloud MQTC 2017
Planning for MQ in the cloud MQTC 2017Planning for MQ in the cloud MQTC 2017
Planning for MQ in the cloud MQTC 2017
 
E2EVC SCVMM / Windows Azure Pack
E2EVC SCVMM / Windows Azure PackE2EVC SCVMM / Windows Azure Pack
E2EVC SCVMM / Windows Azure Pack
 
IBM MQ What's new - Sept 2022
IBM MQ What's new - Sept 2022IBM MQ What's new - Sept 2022
IBM MQ What's new - Sept 2022
 
MQ Messaging
MQ MessagingMQ Messaging
MQ Messaging
 
CTU June 2011 - Microsoft System Center Virtual Machine Manager 2012
CTU June 2011 - Microsoft System Center Virtual Machine Manager 2012CTU June 2011 - Microsoft System Center Virtual Machine Manager 2012
CTU June 2011 - Microsoft System Center Virtual Machine Manager 2012
 
MQ What's New Beyond V8 - V8003 level
MQ What's New Beyond V8 - V8003 levelMQ What's New Beyond V8 - V8003 level
MQ What's New Beyond V8 - V8003 level
 
MQ Support for z/OS Connect
MQ Support for z/OS ConnectMQ Support for z/OS Connect
MQ Support for z/OS Connect
 
Expanding your options with the IBM MQ Appliance - IBM InterConnect 2016
Expanding your options with the IBM MQ Appliance - IBM InterConnect 2016Expanding your options with the IBM MQ Appliance - IBM InterConnect 2016
Expanding your options with the IBM MQ Appliance - IBM InterConnect 2016
 
Spirent TestCenter Virtual on OracleVM
Spirent TestCenter Virtual on OracleVMSpirent TestCenter Virtual on OracleVM
Spirent TestCenter Virtual on OracleVM
 
CloudStack DC Meetup - Apache CloudStack Overview and 4.1/4.2 Preview
CloudStack DC Meetup - Apache CloudStack Overview and 4.1/4.2 PreviewCloudStack DC Meetup - Apache CloudStack Overview and 4.1/4.2 Preview
CloudStack DC Meetup - Apache CloudStack Overview and 4.1/4.2 Preview
 

Recently uploaded

Why Choose Brain Inventory For Ecommerce Development.pdf
Why Choose Brain Inventory For Ecommerce Development.pdfWhy Choose Brain Inventory For Ecommerce Development.pdf
Why Choose Brain Inventory For Ecommerce Development.pdfBrain Inventory
 
Big Data Bellevue Meetup | Enhancing Python Data Loading in the Cloud for AI/ML
Big Data Bellevue Meetup | Enhancing Python Data Loading in the Cloud for AI/MLBig Data Bellevue Meetup | Enhancing Python Data Loading in the Cloud for AI/ML
Big Data Bellevue Meetup | Enhancing Python Data Loading in the Cloud for AI/MLAlluxio, Inc.
 
Sales Territory Management: A Definitive Guide to Expand Sales Coverage
Sales Territory Management: A Definitive Guide to Expand Sales CoverageSales Territory Management: A Definitive Guide to Expand Sales Coverage
Sales Territory Management: A Definitive Guide to Expand Sales CoverageDista
 
online pdf editor software solutions.pdf
online pdf editor software solutions.pdfonline pdf editor software solutions.pdf
online pdf editor software solutions.pdfMeon Technology
 
IA Generativa y Grafos de Neo4j: RAG time
IA Generativa y Grafos de Neo4j: RAG timeIA Generativa y Grafos de Neo4j: RAG time
IA Generativa y Grafos de Neo4j: RAG timeNeo4j
 
Leveraging DxSherpa's Generative AI Services to Unlock Human-Machine Harmony
Leveraging DxSherpa's Generative AI Services to Unlock Human-Machine HarmonyLeveraging DxSherpa's Generative AI Services to Unlock Human-Machine Harmony
Leveraging DxSherpa's Generative AI Services to Unlock Human-Machine Harmonyelliciumsolutionspun
 
Transforming PMO Success with AI - Discover OnePlan Strategic Portfolio Work ...
Transforming PMO Success with AI - Discover OnePlan Strategic Portfolio Work ...Transforming PMO Success with AI - Discover OnePlan Strategic Portfolio Work ...
Transforming PMO Success with AI - Discover OnePlan Strategic Portfolio Work ...OnePlan Solutions
 
Introduction-to-Software-Development-Outsourcing.pptx
Introduction-to-Software-Development-Outsourcing.pptxIntroduction-to-Software-Development-Outsourcing.pptx
Introduction-to-Software-Development-Outsourcing.pptxIntelliSource Technologies
 
Your Vision, Our Expertise: TECUNIQUE's Tailored Software Teams
Your Vision, Our Expertise: TECUNIQUE's Tailored Software TeamsYour Vision, Our Expertise: TECUNIQUE's Tailored Software Teams
Your Vision, Our Expertise: TECUNIQUE's Tailored Software TeamsJaydeep Chhasatia
 
eAuditor Audits & Inspections - conduct field inspections
eAuditor Audits & Inspections - conduct field inspectionseAuditor Audits & Inspections - conduct field inspections
eAuditor Audits & Inspections - conduct field inspectionsNirav Modi
 
Kawika Technologies pvt ltd Software Development Company in Trivandrum
Kawika Technologies pvt ltd Software Development Company in TrivandrumKawika Technologies pvt ltd Software Development Company in Trivandrum
Kawika Technologies pvt ltd Software Development Company in TrivandrumKawika Technologies
 
OpenChain Webinar: Universal CVSS Calculator
OpenChain Webinar: Universal CVSS CalculatorOpenChain Webinar: Universal CVSS Calculator
OpenChain Webinar: Universal CVSS CalculatorShane Coughlan
 
Deep Learning for Images with PyTorch - Datacamp
Deep Learning for Images with PyTorch - DatacampDeep Learning for Images with PyTorch - Datacamp
Deep Learning for Images with PyTorch - DatacampVICTOR MAESTRE RAMIREZ
 
Optimizing Business Potential: A Guide to Outsourcing Engineering Services in...
Optimizing Business Potential: A Guide to Outsourcing Engineering Services in...Optimizing Business Potential: A Guide to Outsourcing Engineering Services in...
Optimizing Business Potential: A Guide to Outsourcing Engineering Services in...Jaydeep Chhasatia
 
Enterprise Document Management System - Qualityze Inc
Enterprise Document Management System - Qualityze IncEnterprise Document Management System - Qualityze Inc
Enterprise Document Management System - Qualityze Incrobinwilliams8624
 
20240319 Car Simulator Plan.pptx . Plan for a JavaScript Car Driving Simulator.
20240319 Car Simulator Plan.pptx . Plan for a JavaScript Car Driving Simulator.20240319 Car Simulator Plan.pptx . Plan for a JavaScript Car Driving Simulator.
20240319 Car Simulator Plan.pptx . Plan for a JavaScript Car Driving Simulator.Sharon Liu
 
ARM Talk @ Rejekts - Will ARM be the new Mainstream in our Data Centers_.pdf
ARM Talk @ Rejekts - Will ARM be the new Mainstream in our Data Centers_.pdfARM Talk @ Rejekts - Will ARM be the new Mainstream in our Data Centers_.pdf
ARM Talk @ Rejekts - Will ARM be the new Mainstream in our Data Centers_.pdfTobias Schneck
 
Growing Oxen: channel operators and retries
Growing Oxen: channel operators and retriesGrowing Oxen: channel operators and retries
Growing Oxen: channel operators and retriesSoftwareMill
 
Streamlining Your Application Builds with Cloud Native Buildpacks
Streamlining Your Application Builds  with Cloud Native BuildpacksStreamlining Your Application Builds  with Cloud Native Buildpacks
Streamlining Your Application Builds with Cloud Native BuildpacksVish Abrams
 

Recently uploaded (20)

Why Choose Brain Inventory For Ecommerce Development.pdf
Why Choose Brain Inventory For Ecommerce Development.pdfWhy Choose Brain Inventory For Ecommerce Development.pdf
Why Choose Brain Inventory For Ecommerce Development.pdf
 
Big Data Bellevue Meetup | Enhancing Python Data Loading in the Cloud for AI/ML
Big Data Bellevue Meetup | Enhancing Python Data Loading in the Cloud for AI/MLBig Data Bellevue Meetup | Enhancing Python Data Loading in the Cloud for AI/ML
Big Data Bellevue Meetup | Enhancing Python Data Loading in the Cloud for AI/ML
 
Sales Territory Management: A Definitive Guide to Expand Sales Coverage
Sales Territory Management: A Definitive Guide to Expand Sales CoverageSales Territory Management: A Definitive Guide to Expand Sales Coverage
Sales Territory Management: A Definitive Guide to Expand Sales Coverage
 
online pdf editor software solutions.pdf
online pdf editor software solutions.pdfonline pdf editor software solutions.pdf
online pdf editor software solutions.pdf
 
IA Generativa y Grafos de Neo4j: RAG time
IA Generativa y Grafos de Neo4j: RAG timeIA Generativa y Grafos de Neo4j: RAG time
IA Generativa y Grafos de Neo4j: RAG time
 
Leveraging DxSherpa's Generative AI Services to Unlock Human-Machine Harmony
Leveraging DxSherpa's Generative AI Services to Unlock Human-Machine HarmonyLeveraging DxSherpa's Generative AI Services to Unlock Human-Machine Harmony
Leveraging DxSherpa's Generative AI Services to Unlock Human-Machine Harmony
 
Transforming PMO Success with AI - Discover OnePlan Strategic Portfolio Work ...
Transforming PMO Success with AI - Discover OnePlan Strategic Portfolio Work ...Transforming PMO Success with AI - Discover OnePlan Strategic Portfolio Work ...
Transforming PMO Success with AI - Discover OnePlan Strategic Portfolio Work ...
 
Introduction-to-Software-Development-Outsourcing.pptx
Introduction-to-Software-Development-Outsourcing.pptxIntroduction-to-Software-Development-Outsourcing.pptx
Introduction-to-Software-Development-Outsourcing.pptx
 
Your Vision, Our Expertise: TECUNIQUE's Tailored Software Teams
Your Vision, Our Expertise: TECUNIQUE's Tailored Software TeamsYour Vision, Our Expertise: TECUNIQUE's Tailored Software Teams
Your Vision, Our Expertise: TECUNIQUE's Tailored Software Teams
 
eAuditor Audits & Inspections - conduct field inspections
eAuditor Audits & Inspections - conduct field inspectionseAuditor Audits & Inspections - conduct field inspections
eAuditor Audits & Inspections - conduct field inspections
 
Kawika Technologies pvt ltd Software Development Company in Trivandrum
Kawika Technologies pvt ltd Software Development Company in TrivandrumKawika Technologies pvt ltd Software Development Company in Trivandrum
Kawika Technologies pvt ltd Software Development Company in Trivandrum
 
OpenChain Webinar: Universal CVSS Calculator
OpenChain Webinar: Universal CVSS CalculatorOpenChain Webinar: Universal CVSS Calculator
OpenChain Webinar: Universal CVSS Calculator
 
Deep Learning for Images with PyTorch - Datacamp
Deep Learning for Images with PyTorch - DatacampDeep Learning for Images with PyTorch - Datacamp
Deep Learning for Images with PyTorch - Datacamp
 
Optimizing Business Potential: A Guide to Outsourcing Engineering Services in...
Optimizing Business Potential: A Guide to Outsourcing Engineering Services in...Optimizing Business Potential: A Guide to Outsourcing Engineering Services in...
Optimizing Business Potential: A Guide to Outsourcing Engineering Services in...
 
Enterprise Document Management System - Qualityze Inc
Enterprise Document Management System - Qualityze IncEnterprise Document Management System - Qualityze Inc
Enterprise Document Management System - Qualityze Inc
 
20240319 Car Simulator Plan.pptx . Plan for a JavaScript Car Driving Simulator.
20240319 Car Simulator Plan.pptx . Plan for a JavaScript Car Driving Simulator.20240319 Car Simulator Plan.pptx . Plan for a JavaScript Car Driving Simulator.
20240319 Car Simulator Plan.pptx . Plan for a JavaScript Car Driving Simulator.
 
ARM Talk @ Rejekts - Will ARM be the new Mainstream in our Data Centers_.pdf
ARM Talk @ Rejekts - Will ARM be the new Mainstream in our Data Centers_.pdfARM Talk @ Rejekts - Will ARM be the new Mainstream in our Data Centers_.pdf
ARM Talk @ Rejekts - Will ARM be the new Mainstream in our Data Centers_.pdf
 
Growing Oxen: channel operators and retries
Growing Oxen: channel operators and retriesGrowing Oxen: channel operators and retries
Growing Oxen: channel operators and retries
 
Salesforce AI Associate Certification.pptx
Salesforce AI Associate Certification.pptxSalesforce AI Associate Certification.pptx
Salesforce AI Associate Certification.pptx
 
Streamlining Your Application Builds with Cloud Native Buildpacks
Streamlining Your Application Builds  with Cloud Native BuildpacksStreamlining Your Application Builds  with Cloud Native Buildpacks
Streamlining Your Application Builds with Cloud Native Buildpacks
 

What's New in IBM Messaging

  • 1. What's new in IBM Messaging Morag Hughson - hughson@uk.ibm.com IBM Hursley - UK
  • 2. IBM Messaging – Market segments Deliver Messaging Backbone for Enterprise Focus on traditional MQ values, rock-solid enterprise-class service, ease-of-operation, breadth of platform coverage, availability, z/OS exploitation Capture Big Data from Mobile and Internet of Things Focus on Internet-scale events, m2m device enablement, zero-admin, security and privacy, feed into real-time analytics, location-based notifications Enable Developers to build more scalable, responsive applications Focus on new app dev use cases, breadth of languages, ease-of-deployment, lightweight services, integration with developer © 2014 IBM Corporation frameworks
  • 3. Multi-platform Common criteria Multiple cluster XMIT queue Hypervisors Integrated Messaging V7.1 V7.5 IBM MQ Advanced 1990s 2000s 2010s © 2014 IBM Corporation JMS MQI Assured delivery IBM MQSeries Mobile .NET Eclipse JMS 1.1 RCMS IBM MQ Low Latency V1.1 V2 V5 V5.1 V5.3 V2.1 V5.2 V6 V7 V7.0.1 SSL SOAP XML IBM MQ Managed File Transfer IBM MQTT HTTP AJAX REST Web 2.0 Managed File Transfer Pub/sub IBM MQ Everyplace IBM MQ Advanced Message Security System Pattern Application Pattern IBM MQ Advanced for Developers IBM MessageSight Multi-instance QMGR V8 Timeline 20th Anniversary of MQ at IMPACT
  • 4. WebSphere MQ V7.1: Feature Summary (Nov 2011) New Feature Benefits Details © 2014 IBM Corporation Multi-Version Install capability on Distributed platforms Makes it easier to deploy and upgrade systems and stage version to version migration Unix and Windows support for multiple versions of MQ V7.x (AND one copy of MQ V7.0.1) down to fixpack levels. Relocatable installation support. Applications can connect to any Qmgr Enhanced Security Simplified Configuration Enhanced Authorisation and Auditing IP address Authorisation capability Additional crypto algorithms More granular authorisation for non-local queues Application Activity Reports Cloud Support Simplifies and support Cloud deployments Additional HVE images Enhanced Clustering Improves ease-of-use Authorisation on Cluster Q rather than XMIT Q on Dist. Platforms Bind-on-Group Support Multicast capability New messaging QoS provides low latency with high fan-out capability MQ Pub/Sub Topic space can now map to multicast Group Addresses Provides direct interoperability with MQ LLM Improved scalability and availability on z/OS Further exploitation of z196 Customer control over CF storage use CF Connectivity Loss improvements Code contention reduced to improve multi-processor linear scaling Use of MQ Datasets rather than DB2 significantly improves “large” message capability Structure rebuild capability for CF Connectivity Loss scenarios Improved Performance on Dist platforms Improved multiprocessor exploitation Various code improvements
  • 5. WebSphere MQ V7.5: Feature Summary (June 2012) © 2014 IBM Corporation For Windows, Unix and Linux New Feature Benefits Details Integrated Installation Makes it easier to deploy systems Simpler licensing Combines several products into a single package Common experience Enhanced Clustering Improves ease-of-use Improves application isolation Split Cluster Transmission Queue Java Application Identification Makes it easier to distinguish applications Applications no longer to all have the same name AMS channel interception Provides a level of message protection even when application environment cannot run AMS Interception in the SVRCONN still protects messages before hitting queues FTE Logger Options Can write FTE audit records to flat file No longer a requirement for an enterprise database Easier to read data immediately
  • 7. WebSphere MQ: Feature Summary (2013) Updates to pricing and function during 2013 New Feature Benefits Details © 2014 IBM Corporation MQ 7.1 Value Unit Edition introduced for z/OS One time charge (OTC) pricing for zNALC workloads Queue managers supporting qualified workloads on System z New Application License Charge (zNALC) LPARs Includes WebSphere MQ Client Attach, allowing free-of-charge connections from MQ Clients to z/OS SHA-2 CipherSpecs for SSL/TLS on z/OS Stronger hashing algorithms Required/recommended by some authorities Available from V7.1 GA on distributed platforms Now also available on z/OS 7.1, with two APARs* Internet PassThru (MS81) refresh Updates to SOE and crypto algorithms Consistent SSL/TLS support and certificate DN attributes with MQ V7.1 Uses JRE-provided Java Secure Sockets Extension (JSSE) Support for SHA-2 and elliptic curve encryption, in line with US NIST standard SP800-131A recommendation MQ JCA RA support in WAS Liberty profile MQ 7.5.0.2 RA is easily configured in Liberty Connects to any supported version of MQ Liberty profile expects resource providers (database, messaging) to supply provider-specific classes Configure “wmqJmsClient.rar.location” variable in server.xml MQ 7.1 Extended Transactional client for HP NSS platform MQ V7.1 function for NonStop applications accessing MQ on other systems Free and fully supported Supports C/C++, COBOL, pTAL, JMS Supports Guardian and OSS applications including OSS multi-threaded applications Available as SupportPac MAT1 *APAR OA39422 needed on z/OS V1R13 for System SSL *APAR PM77341 for MQ on z/OS V7.1
  • 8. © 2014 IBM Corporation SHA-2 Support Stronger algorithms are now available and recommended In many cases available pre-V8 V7.1 GA on Distributed platforms V7.1 on z/OS via APAR APAR OA39422 needed on z/OS V1R13 for System SSL APAR PM77341 for MQ on z/OS V7.1 Various other ‘parts’ of MQ via Service Stream See technote http://www.ibm.com/support/docview.wss?uid=swg21639606 Changes also rolled into V8 CipherSpecs include:- ECDHE_RSA_AES_128_CBC_SHA256 ECDHE_RSA_AES_256_CBC_SHA384 TLS_RSA_WITH_AES_128_CBC_SHA256 TLS_RSA_WITH_AES_256_CBC_SHA256 TLS_RSA_WITH_NULL_SHA256
  • 9. N O T E S © 2014 IBM Corporation SHA-2 Support SHA-2 stands for Secure Hash Algorithm 2. This is the generic name for a family of hash functions SHA-224, SHA-256, SHA-384, and SHA-512; the numbers refer to the bit-size of the generated hash value. The hashing algorithms historically supported by WebSphere MQ channel cipherSpecs (SSLCIPH) were MD5 and SHA-1. These are no longer regarded as adequately secure due to successful attacks on them which have been widely publicized, and because NIST (the American National Institute of Standards and Technology) has mandated (http://csrc.nist.gov/groups/ST/hash/policy.html) that both MD5 and SHA-1 no longer be used. So we have had considerable customer pressure for provision of “SHA-2 support.” This support is in MQ V8, but also in earlier releases by applying appropriate fix pacs for the platform or component on MQ where you are interested in using it. A technote at http://www.ibm.com/support/docview.wss?uid=swg21639606 details exactly which fix pacs or APARs are required in each case.
  • 10. Internet Pass-Thru – SupportPac MS81 Previous MQIPT 2.0 release was in 2008 Many new operating systems have been released since then New cryptographic algorithms since then Redesigned to use the JRE-provided Java Secure Sockets Extension (JSSE) Previously used a separate SSL implementation This gives consistent SSL/TLS support Also has consistent certificate DN attributes with MQ V7.1 US NIST standard SP800-131A recommends: Support for SHA-2 (e.g. SHA-256, SHA-384 and SHA-512) Elliptic Curve encryption © 2014 IBM Corporation
  • 11. © 2014 IBM Corporation MQ V7.1 VUE for z/OS MQ Value Unit Edition product introduced for z/OS One time charge (OTC) pricing for zNALC partition workloads OTC price metric instead of MLC Run new workloads that are qualified to run on System z New Application License Charge (zNALC) LPARs Includes code and entitlement for WebSphere MQ Client Attach, allowing free-of-charge connections from MQ Clients to z/OS
  • 12. © 2014 IBM Corporation JMS in Liberty Profile WAS Liberty profile does not include a copy of the MQ JMS client For consistency with other resource providers such as databases Provider specific classes come from the resource provider The RA provided with MQ can be easily configured in Liberty Define one variable in server.xml to tell the wmqJmsClient-1.1 where the client is variable name=wmqJmsClient.rar.location value=${shared.resource.dir}/wmq/wmq.jmsra.rar/ Requires the MQ 7.5.0.2 rar or a fix on top of 7.5.0.1 More information is at https://www.ibmdw.net/wasdev/2013/06/14/using-websphere-mq-with-the-liberty-profile/ http://www-01.ibm.com/support/docview.wss?uid=swg21633761
  • 13. New client support for HP NSS (aka Tandem) Extended Transactional client support at an MQ V7.1 release level Full MQ V7.1 function for NonStop applications accessing MQ on other systems © 2014 IBM Corporation Client is free and fully supported C / C++ extended transactional client Cobol pTAL support JMS client Supports both Guardian and OSS applications including OSS multi-threaded applications Available as SupportPac MAT1
  • 14. © 2014 IBM Corporation Now available
  • 15. Reuse is not just for code Another new book where the MQ chapter may look familiar © 2014 IBM Corporation
  • 16. End of Service for old platforms and versions MQ V7.0.0 and V7.0.1 for multiplatforms – EOM, EOS effective September 2015 V7.0 will have had more than 7 years of support MQ V7.0.1 for z/OS – EOM, EOS effective September 2015 © 2014 IBM Corporation V7.0 .0 already out of service
  • 17. 2013 enhancements: Developer Enhancement Benefits Details MQ Advanced for Developers – free for devt Development use only edition use!! Free of charge Full MQ Advanced V7.5 functionality Available free of charge for development use only Download from developerWorks, MQdev community Best effort community assistance © 2014 IBM Corporation IBM MessageSight for Developers – free for devt use!! Development use only edition Free of charge Virtual MessageSight image, updated to V1.1 Available free of charge for development use only Download from developerWorks, IBM Messaging community Best effort community assistance Mosquitto - Open source MQTT server Simple, open access to get on-board with MQTT and MQTT-SN Proposed Eclipse Mosquitto project for open-source MQTT server for lightweight devt use MQTT-SN (MQTT for sensor networks) specification available IBM MQ Light – alpha release Straight forward, easy to use messaging API for writing scalable and responsive applications Download and feedback via developerWorks community Available free of charge for development use Currently new API available in Java, more languages to come Regular updates planned introducing new features and responding to feedback
  • 18. Simplifying Development for developer-led Messaging Applications “MQ Light” - a new messaging form factor, easy for developers Straightforward download and unzip – zero install Simple Web UI– no need to be an infrastructure specialist Focus on your application – using simplified messaging API Support for popular languages and tooling with seamless migration from development into production MQ Light runtime not for advanced messaging uses cases, enterprise backbone or highly available/scalable apps © 2014 IBM Corporation IBM MQ Light Developer coding in JavaScript, Java, Python, Ruby, C#, PHP Builds messaging into applications using preferred IDE or CLI and tests in developer sandbox C7: Messaging in the Cloud with IBM MQ Light and IBM Bluemix A35: How to Develop Responsive Applications with IBM MQ Light (Lab) AL6: Developing a First Application with IBM MQ Light
  • 19. Download “MQ Light” alpha and try it today https://www.ibmdw.net/messaging/mq-light © 2014 IBM Corporation
  • 20. 2013 enhancements: Internet of Things, mobile m2m Enhancement Benefits Details © 2014 IBM Corporation IBM MessageSight V1.1 High-performance, reliable, and scalable messaging - designed specifically for M2M and Mobile scenarios Balance mobile workloads across your enterprise application server clusters Single sign-on from mobile devices to your enterprise apps Disconnected app notification that messages are waiting IBM Internet of Things Cloud – statement of direction Fully cloud hosted solution for internet of things Freemium, PAYG custom pricing Scalable connectivity for small and large numbers of devices Uses industry-standard, MQTT transport Registration of devices for access to the cloud service offering Ability for devices to produce and consume events and messages in near real-time Mobile Messaging clients Updated clients for mobile platforms Updated clients for Android, iOS hybrid mobile apps
  • 21. IBM MessageSight – a messaging Appliance Extends the IBM Messaging family with a secure, easy to deploy appliance-based messaging server, optimized to address the massive scale requirements of machine to machine (m2m) and mobile use cases A million connections, and millions © 2014 IBM Corporation of messages per second Exploits hardware acceleration for performance Designed to sit at the edge of the enterprise Can extend your existing messaging infrastructure or used standalone Complements MQ - provides an offload/accelerator for edge of enterprise scenarios A8: Introduction to IBM MessageSight Supports familiar APIs with a mixture of standard and high-speed protocols
  • 22. IBM MessageSight V1.1 - Major enhancements © 2014 IBM Corporation Mobile to Enterprise Balance mobile workloads across your enterprise application server clusters Single sign-on from mobile devices to your enterprise apps Disconnected app notification that messages are waiting Security Implements the Federal government recommendations with NIST SP 800-131A strengthened security Uses client certificate identity for authentication and authorization Developer Operations New “at-a-glance” system dashboard Flexible work environments supported with remote monitoring of MessageSight from client devices Virtual MessageSight image speeds mobile and machine-to-machine app development
  • 24. MQLight Service for BlueMix Open Beta IBM’s fully managed cloud messaging service The same straightforward experience as MQ Light, aimed at developers available as a fully managed public cloud service in BlueMix Push application into BlueMix and use © 2014 IBM Corporation Integrated into the BlueMix experience Simple API for node.js JMS API for Java Elastic MQ Development focused tooling Develop cloud application using node, java, etc Develop offline using MQ Light Elastic MQ
  • 25. IBM MQ V8 delivering best in class enterprise messaging © 2014 IBM Corporation Platforms Standards Security Scalability System z exploitation 64-bit for all platforms Userid authentication via OS LDAP Multiplexed client performance 64-bit buffer pools in MQ for z/OS means less paging, more performance Support for JMS 2.0 User-based authorisation for Unix Queue manager vertical scaling Performance and capacity Improved support for .Net and WCF AMS for IBM i z/OS Publish/Subscribe improvements Performance enhancements for IBM Information Replicator (QRep) Changes to runmqsc DNS Hostnames in CHLAUTH records Routed publish/subscribe Exploit zEDC compression accelerator SHA-2 for z, i NSS Multiple certificates per queue manager Multiple Cluster Transmit Queue on all platforms SMF and shared queue enhancements
  • 26. 2014 Updates – MQ V8 N O T E S The rest of this presentation goes into details about MQ V8 © 2014 IBM Corporation
  • 27. © 2014 IBM Corporation MQ V8 Dates Announce: 22 April 2014 Availability: 23 May 2014 (eGA Distributed) 13 June 2014 (z/OS and pGA Distributed)
  • 28. MQ platform and product consistency 64-bit server support for all queue manager platforms Completion of platform coverage by adding Windows 64-bit engine Applications can still be 32-bit Requires Windows 7 or later Client only package for 32-bit platforms Queue Manager requires 64-bit Integration of AMS and MFT capabilities into z/OS and IBM i platforms Previously separately installable products Following the model used by MQ V7.5 on distributed for closer integration Both features still separately licensed © 2014 IBM Corporation AMS Starts automatically with Queue Manager Reduced overhead (now only one started task instead of 2) Policies and their administration remain unchanged Client Attach Feature no longer needed on z/OS Single price includes support for clients MFT Now looks more natural for a z/OS person Closer integration with standard system facilities such as ARM Started task templates Supported JCL provided instead of samples Job info logged to JCL task
  • 29. MQ platform and product consistency N O T E S This release has all the Distributed queue managers fully supporting 64-bit operations. The final remaining platform had been Windows, but now the queue manager runs as 64-bit processes. Existing 32-bit applications continue to work of course, but this should bring additional capacity and scalability to the queue managers on that OS. The lowest level of Windows now supported is Windows 7; older versions are not supported. A client-only package for 32-bit versions of Windows is provided, but the qmgr requires the 64-bit OS. Another big feature of V7.5 was the closer integration of AMS and File Transfer (MFT). As we will see later, this pattern has been followed on z/OS and IBM i. On z/OS the features are still separately licensed, but are better integrated than previously. On z/OS, the CAF has been removed both as an installable feature and as a licensing option. All V8 queue managers are now capable of having any number of MQ clients directly connected. For customers who previously used the lack of a CAF to block client connections, we would strongly recommend they look at the other security-related controls such as CHLAUTH and SSL/TLS, or MAXINST values, to continue to prohibit clients. If you extend the number of directly-attached clients in your environment, make sure you first evaluate things such as CPU costs, performance, capacity etc. © 2014 IBM Corporation
  • 30. © 2014 IBM Corporation JMS 2.0 Long-awaited update from JMS 1.1 standard JMS 2.0 – JSR 343 Java Message Service (JMS 2.0) Final release on 21 May 2013. https://java.net/projects/jms-spec/pages/JMS20FinalRelease New Messaging Features Delivery Delay Asynchronous Send Subscriptions can be shared across a messaging provider API Changes Use of java.lang.AutoCloseable Simplified API [combined connection/session] Session doesn't need parameters (for Java EE) Java 7 prereq http://www.slideshare.net /calanais/ibm-mq-v8-and-jms- 20 Java EE 7 prereq for use of the Resource Adapter in Application Servers
  • 31. N O T E S © 2014 IBM Corporation JMS 2.0 The JMS 2.0 specification now requires JMS providers to implement both P2P and Pub-Sub. The following new messaging features have been added in JMS 2.0: – Delivery delay: a message producer can now specify that a message must not be delivered until after a specified time interval. – New send methods have been added to allow an application to send messages asynchronously. – JMS providers must now set the JMSXDeliveryCount message property. The following change has been made to aid scalability: – Applications are now permitted to create multiple consumers on the same durable or non-durable topic subscription. In previous versions of JMS only a single consumer was permitted. Several changes have been made to the JMS API to make it simpler and easier to use: – Connection, Session and other objects with a close method now implement the java.jang.AutoCloseable interface to allow them to be used in a Java SE 7 try-with-resources statement. – A new simplified API has been added which offers a simpler alternative to the standard API, especially in Java EE applications. – New methods have been added to create a session without the need to supply redundant arguments. – Although setting client ID remains mandatory when creating an unshared durable subscription, it is optional when creating a shared durable subscription. – A new method getBody has been added to allow an application to extract the body directly from a Message without the need to cast it first to an appropriate subtype. New methods have been added to Session which return a MessageConsumer on a durable topic subscription. Applications could previously only obtain a domain-specific TopicSubscriber, even though its use was discouraged. The specification has been clarified in various places. JMS 2.0 implementations require Java 7 for the runtime. They also require Java EE 7 for use of the Resource Adapter in Application Servers. Not all App Servers currently support Java EE 7. However, as with all client implementations, older versions of the RA still work when communicating to an MQ V8 queue manager.
  • 32. © 2014 IBM Corporation .Net enhancements MQ .Net classes can now use SSL without needing the C client installed A secure fully-managed .Net implementation Uses Windows native certificate stores For MQ .NET classes (aka Base .NET Classes) SSL properties can be set at MQEnvironment.cs Hashtable properties (input parameter to MQQueueManager constructor) For XMS .NET, SSL properties can be set as ConnectionFactory properties WCF interface extended to non-SOAP, non-JMS messages Making it easier for apps using WCF to communicate with any other MQ application
  • 33. .Net enhancements: SSL N O T E S MQ .NET in unmanaged mode has supported the use of SSL since MQ v6.0.1. It was based on the C Client (and GSKit). In V8 MQ .NET Managed mode now supports SSL based on Microsoft SSLStreams/Security kit. There are some limitations when using SSL with Managed .NET. CipherSpec setting can be made only at Windows Group policy (gpedit.msc). – CipherSpec set on client channel is used only to determine SSLProtocol. – Make sure you set same cipherspec on Windows group policy and client © 2014 IBM Corporation channel to make sure correct protocol version is flowed. KeyRepository uses Windows Key Store only. – Set value as *SYSTEM for accessing certificates under Computer Account – Set value as *USER for accessing certificates under User account FIPS can be enabled only from Windows group policy. KEYRESET is not supported by Microsoft SSLStreams – This limitation is overridden by using KEYRESETCOUNT and Client Auto Reconnect feature of MQ. – Application can set KEYRESETCOUNT during connection, once the number of bytes sent/received reaches the count, connection will be forcibly broken. If Client Auto Reconnect facility is enabled, connection will be automatically reconnected. No managed way to support Cryptographic hardware Product samples have been updated to demonstrate SSL Connections. These can be found in WebSphere MQtoolsdotnetsamplescsbaseSimple Additional model for sending MQ messages from WCF applications – Both SOAP/JMS and MQMessaging can be used SOAP/JMS – Supported since MQ v7.0.1 – Based on XMS .NET and makes JMS-like calls for MQI – Uses JMS nomenclature for URI(jms:) and Bindings – Now also supports “wmq:” style of URI – Uses MA93 supportpac specification for URI format/syntax – Messages can be delivered only to SOAP enabled Client/Service MQMessaging – New in MQ V8.0 – Transmits MQ Messages over the WCF Channel without any SOAP headers – Use “wmq:” style of URI – Uses MA93 supportpac specification for URI format/syntax – Messages can be delivered to SOAP or NON-SOAP MQ applications
  • 34. © 2014 IBM Corporation Changes to runmqsc Can now be run by any user (not just mqm group) Can take a userid/password for authentication: new -u flag Can now connect as a client to remote systems: new -c flag Client channel definitions located by MQSERVER - MQCHLLIB - MQCHLTAB Can act as standalone program to create local CCDT: new -n flag Does not connect to queue manager; commands subset to update local channel definition file Ease of use Customisable prompt using environment variable New exit and quit“ synonyms for end $ ls –l runmqsc -r-xr-xr-x 1 mqm mqm 25930 06 Mar 04:46 runmqsc $ export MQPROMPT=MQ +MQ_INSTALLATION_NAME+ $ runmqsc –u metaylor QM1 5724-H72 (C) Copyright IBM Corp. 1994, 2014. Enter password: ****** Starting MQSC for queue manager QM1. MQ Installation5 DIS QMGR …
  • 35. Changes to runmqsc N O T E S This release introduces a number of changes to the runmqsc program Firstly, it is now exectuable by any user, not just members of the mqm group. Security controls still apply of course, but the security is checked on each individual command. This makes it easier to have MQ administrators who have been granted full access to objects, but who are not in the mqm group. Another reason for making runmqsc world-executable was to make it usable on machines which do not have queue managers installed. It is now installed even on client-only systems, and it can be run either as a client program connecting directly to a remote queue manager, or as a completely standalone program to permit local creation of the Client Channel Definition Table. So you can create and modify a CCDT with no queue manager access at all. The program is one of several that have been updated to accept a userid for authentication. If the –u flag is given, then a password is requested. Note that the password is read from stdin so that it can be redirected from a file if necessary. If you also use scripts piped into runmqsc, then you can group commands to avoid having to put the password in the same script as the MQSC commands. – Unix: (cat password.stash ; cat script.mqsc) | runmqsc –u userid QM1 – Windows: (type password.stash type script.mqsc) | runmqsc –u userid QM1 There are also a couple of usability enhancements. Firstly, there are some synomyms added to complete an MQSC session – END, QUIT and EXIT can all be used so you don't have to try them all. Different scripting environments for different products typically use one of these commands, and it's annoying to have to remember which goes with which. Secondly, you can now make it easier to see that you are in an MQSC command environment and some details of the current environment by setting the MQPROMPT environment variable. Replaceable inserts are recognised such as date and time, and installation-specific details. These are the same variable subsitutions as available for SERVICE objects. © 2014 IBM Corporation
  • 36. MQ Security - Authentication © 2014 IBM Corporation Verify userid and password Typically supplied in MQI CSP structure or from channel security exit Or JMS createConnection(user,pass) method New client exit and tool provided to help unchanged applications insert passwords Can verify against operating system Including PassPhrase for z/OS Can verify against LDAP repository on Distributed platforms Enabling centralised identity control Still constrained to 12 character userids With LDAP, supplied username may be long (eg an email address or full DN) But must have an associated 12 character shortname Independent configuration for local bindings and clients Ignored, Optional, Required, Required for admin id A22: New IBM MQ V8 Security Features
  • 37. MQ Security - Authentication N O T E S Applications can now be authenticated with a userid/password. This can be provided explicitly by the application as parameters in the MQCONNX verb or equivalent. This builds on features originally implemented in the MQI for MQ v6, but which were never exploited until now. Also, to support client applications, a security exit is provided that can add the userid/password to a connection request if it is not supplied by the app. The exit reads the qmgr name from an ini file; the file contains the userid and a protected form of the password – ie not plaintext. The protection of the password is done by a tool that is also provided. When V8 clients connect to V8 qmgrs, the userid/password information is protected against casual wire-sniffing, even when SSL/TLS is not used. This protection is not as strong as a full TLS-encrypted session, which is preferred, but is better than sending data in the clear. Obviously both the client and the qmgr must be at V8 for this protection to work; older clients can still send passwords but they are not protected. Authentication is performed against the local OS (all platforms) or against an LDAP directory (Distributed only). Some operating systems may integrate LDAP services into their local user registry, in the same way as NIS, but when this is done transparently MQ does not know about it explicitly and can use the OS authentication method. Using a central LDAP server means that passwords can be set in a single place. For example, we have used IBM's LDAP services (BluePages) to authenticate userids. When using LDAP, there is lots of flexibility in what the userid is – in BluePages it is generally the email address – but there must be a field in the schema to return a short name that can fit into the 12 character MQMD.UserIdentifier field. This short name is also used for authorisation and must be locally defined to the OS so that permissions can be calculated. There are various configuration rules for different modes of connection, to specify whether a password is required, optional or ignored. © 2014 IBM Corporation
  • 38. MQ Security - Authorisation $ crtmqm –oa user QMU ---------------- Service: © 2014 IBM Corporation Make Unix OAM userid-based Optional configuration Consistent with other platforms Will no longer add primary group to authorities during setmqaut Chosen at queue manager creation or by editing qm.ini Default is still group-based authorisations Delete Authority record by SID Name=AuthorizationService EntryPoints=14 SecurityPolicy=User Solve problem of orphaned authorities when Windows id is deleted
  • 39. MQ Security - Authorisation N O T E S One further point of consistency in this release is making the Unix authorisation model the same as for Windows – permissions can now be set for individual users, and not just groups. So running a command such as setmqaut –t qmgr –p usr1 +connect works for just that user, and not the primary group. This is configured by either creating the queue manager with the -oa user option or by editing the ini file as shown for existing queue managers – restarting the queue manager sets it to work in the new mode. The change is deliberately not dynamic, and requires the restart, because it is so fundamental to how the queue manager permissions operate, and is not something we would expect to be done frequently. All existing permissions are left unchanged when you switch to user-mode authorisations, so the group permissions that have been set remain, but new permissions can be set for the users. The user-based model is not the default for new queue managers; to keep compatibility with older systems, the default is still the group-based model. One final security feature is specifically for Windows, to deal with situations where users have been deleted from the system but their MQ permissions have not been deleted from the OAM. You can now use the setmqaut command to delete permissions based on SID instead of name, and this will remove the orphaned entries. © 2014 IBM Corporation
  • 40. MQ Security - CHLAUTH Use DNS hostnames in CHLAUTH records Not allowed in TYPE(BLOCKADDR) Used in TYPE(ADDRESSMAP) instead of an IP address Also as an address restrictor on any other mapping type, instead of an IP address, e.g. SET CHLAUTH(‘*’) TYPE(SSLPEERMAP) SSLPEER(‘CN=“Morag Hughson”’) ADDRESS(‘*.ibm.com’) MCAUSER(HUGHSON) Must ensure DNS can reverse look-up IP address - Hostname Also we provide a way to disable reverse lookup ALTER QMGR REVDNS(ENABLED|DISABLED) CHLAUTH also hooks into other security features in V8 Granular connection authentication control with CHCKCLNT on CHLAUTH rules Better Certificate DN filtering with SSLCERTI on CHLAUTH rules © 2014 IBM Corporation A31: IBM MQ CHLAUTH rules – with MQ V8 updates
  • 41. MQ Security - CHLAUTH N O T E S The CHLAUTH rules that were introduced in V7.1 have been extended to meet the most frequently-requested enhancement – the ability to use hostnames in the rules as well as IP addresses. Names can be used all the same rules, and in the same way, as IP addresses with the one exception of the listener blocking which is still only address-based. The hostnames can include wildcard patterns such as *.example.com. The matching is simple string-based; the . characters are not treated as special separators. © 2014 IBM Corporation
  • 42. MQ Security - Certificates Configurable default certificate label for qmgrs and clients Instead of ibmwebspheremqqmgr or ibmwebspheremquserid“ ALTER QMGR CERTLABL('My certificate name') © 2014 IBM Corporation Channel-level certificates To support different business partners using different CAs. For queue managers and C clients Not Java yet, because Java 7 JSSE does not fully support SNI Both ends must be V8 Per Channel Certificate ALTER CHANNEL … CERTLABL('This channel certificate') Certificate Matching SET CHLAUTH('*') TYPE(SSLPEERMAP) SSLPEER('CN=Morag Hughson') SSLCERTI('CN=IBM CA') MCAUSER('hughson') A22: New IBM MQ V8 Security Features
  • 43. MQ Security - Certificates N O T E S The label used to find the queue manager or client's certificate in the SSL keystore is now configurable. This gives more flexibility in naming, and can even permit sharing of the keystore between multiple queue managers if you wish. On z/OS, there is in addition a configuration attribute for the QSG-related certificate (traditionally ibmwebspheremqqsgname. A further extension for certificate use is designed for scenarios where you may wish to use different certificates when communicating with different partners. A common reason for this is when a queue manager is used for both internal-facing channels and for connections to a partner, who may have different certificate requirements, such as using a different CA. You can now configure a different certificate label to be used on individual channels. The implementation of this requires both ends of the channel to be at MQ V8, as there has to be cooperation between the sending side and the receiving side of the channel. And it is not available in all environments; in particular, Java clients cannot currently participate as the standard JSSE provider does not yet support the Server Name Indication (SNI) flows that go alongside the socket setup calls. © 2014 IBM Corporation
  • 44. Pub/sub scalability - cluster behaviour before V8 All queue managers in a cluster know everything and need to be able to connect © 2014 IBM Corporation to anyone CLUS1 FR TOPIC(T1) CLUSTER(CLUS1) Sub to T1 Pub to T1 Queue manager CLUSQMGR knowledge Channel Proxy subscription
  • 45. Pub/sub scalability - cluster behaviour before V8 N O T E S Every queue manager is aware of every subscribed topic string and queue manager in the cluster It’s very easy to end up with a fully interconnected cluster The load per queue manager is proportional to the total number of queue managers in the cluster Many systems in larger clusters are not designed to support such a configuration Imagine what is happening in a busy cluster with hundreds of queue managers or more © 2014 IBM Corporation
  • 46. Pub/sub scalability - cluster behaviour with V8 FR © 2014 IBM Corporation New concept of routed topics Configure subset of queue managers to know everything and connect to everyone Publications sent via these queue managers Queue manager CLUSQMGR knowledge Channel Proxy subscription CLUS1 TOPIC(TOPIC1) CLUSTER(CLUS1) Sub to T1 Pub to T1 A16: Using IBM MQ Pub/Sub in an MQ network
  • 47. N O T E S © 2014 IBM Corporation Routed topics Publish/subscribe across a cluster previously required direct connectivity between all publishing queue managers and subscribing queue managers. Now routing via intermediary queue managers in the cluster is possible – The aim is to allow topologies where queue manager-to-queue manager connectivity and knowledge is restricted With DIRECT pub/sub: – Direct publication routing – Every queue manager must scale with the size of the system With ROUTED pub/sub – The load on the majority of queue managers is independent from the size of the system – Publications may incur additional hops Messages published on topic host routed topics are similar to messages put to clustered queues: – Think of a routed topic def as a clustered queue and a publisher to the topic as an app putting to that queue – Each message published is sent to one of the topic host queue managers, and from there onto the queue managers where subscriptions exist – Messages are workload balanced across all topic hosts with available channels from the publishing queue manager to the topic hosts – Unavailable topic hosts are avoided – Workload balancing behaviour is as for a clustered queue using all default settings (CLWLPRTY, CLWLRANK, etc.) except for DEFBIND, which is effectively set to NOT_FIXED – Each individual message is ‘evenly’ workload balanced across topic hosts – Workload balancing is based on the cluster channel rather than the topic (as for queues), so channel workload balancing control still applies (CLWLPRTY, CLWLRANK, CLWLWGHT)
  • 48. Configuration of routed topics Topic routing is configured in the TOPIC object definition CLUSTER(clustername) CLROUTE(DIRECT|TOPICHOST) © 2014 IBM Corporation Uses the CLROUTE property: DEFINE TOPIC(topic) DIRECT: Provides V7 behaviour, publications travel directly from publishing queue managers to subscribing queue managers TOPICHOST: publications travel via a topic hosting queue manager New function in MQ V8 Only V8 queue managers can participate in routed clustered publish/subscribe Full repositories must also be at V8 Older queue managers are not told of the routed topic definitions and therefore behave as if the topic was not clustered. All V7 queue managers can continue to participate in direct clustered pub/sub
  • 49. Improved pub/sub status reporting Additional display attributes on DISPLAY PUBSUB. Permits detection of unexpected growth in topics/subscriptions Can gauge the magnitude of a DISPLAY TPSTATUS/SUB/SBSTATUS command. © 2014 IBM Corporation DISPLAY PUBSUB ALL 3 : DISPLAY PUBSUB ALL AMQ8723: Display pub/sub status details. QMNAME(QMGR3) TYPE(LOCAL) STATUS(ACTIVE) SUBCOUNT(241) TPCOUNT(105)
  • 50. General pub/sub improvements More efficient handling of subscriptions for popular topic sub-trees and dynamic subscriptions MQ V7.x behaviour sends out individual proxy subscriptions MQ V8 topic object with PROXYSUB set to FORCE Generates a single wildcarded subscription Disables individual proxy subs for topic strings lower in the topic tree Better pub/sub error handling in multi-queue manager environments Selectors are evaluated on the message as published, before modification by the publish operation, for delivery to each subscriber More efficient handling of large numbers of topics Linear scaling to at least a million topics © 2014 IBM Corporation
  • 51. General pub/sub improvements N O T E S In a publish/subscribe hierarchy, or cluster, proxy subscriptions are used to indicate which queue managers in the topology publications need to be propagated to for remote subscribers. If applications have short-lived subscriptions the delay incurred propagating the proxy subscriptions to all queue managers can result in some remote publications not being delivered. PROXYSUB(FORCE) can be specified on a topic to force all publications to be propagated to all remote queue managers. This avoids this problem at the expense of propagating messages even when there are no subscribers connected to a queue manager. In version 8 using PROXYSUB(FORCE) also significantly reduces the overhead of propagating proxy subscriptions for a given topic node. Internal topic tree management has been enhanced for large numbers of topics. Performance should scale linearly up to at least a million topics. The DISPLAY PUBSUB command has also been enhanced to report the total number of topics and subscribers. This can be used to detect growth in these and help determine the potential impact of a wildcard in a DISPLAY TOPIC/SUB/TPSTATUS/SBSTATUS command. © 2014 IBM Corporation
  • 52. Distributed Performance Improvements to distributed queue manager scaling Improve efficiency Less targeted at internal benchmarks – hopefully more realistic scenarios Better exploitation of wider SMP machines © 2014 IBM Corporation Multiplexed client performance Increase the performance of multiplexed client channels (SHRCONV 0) Especially for SHRCONV=1 Other areas that helped: Cache alignment for internal structures Extended 64-bit exploitation for locking primitives RFH2 handling, particularly for waiting-getter Fewer copies of data are needed Better compiler optimisations Faster data conversion (especially for 1208) Many messages are in 1208 codepage Optimised handling when the queue manager needs to convert them
  • 53. Performance improvements N O T E S A number of enhancements have been implemented in version 8 to improve the vertical scaling of queue managers on the distributed platforms. Some of these improvements are listed on the previous slide. We’ve also updated the focus of our performance testing to be less reliant on some internal benchmarks that do not represent realistic customer workloads. Although each customer workload is different, so guarantees are not possible, the performance improvements in version 8 are more likely to be relevant to real-world scenarios. Prior to version 7 each client conversation uses a separate socket and channel instance. If clients establish multiple conversations using different threads this can create a large demand for sockets on the server. Each channel instance also requires storage on the queue manager. In version 7 support was added to allow client conversations to share the same socket/channel instance. This can significantly reduce the resource overhead associated with these connections. Support for bi-directional communication was also introduced that supports new capabilities, such as heartbeats, read-ahead and asynchronous message consumption. However, if multiple conversations share the same socket, contention can arise if the total workload for the conversations exceeds the capacity of the socket. Additionally, an overhead is also introduced to serialize access when sending and receiving TCP/IP data. SHARECNV(0) disables all version 7 enhancements. SHARECNV(1) can be used to disable only conversation sharing. Unfortunately, in version 7 the latter incurs a notable performance overhead as a result of enabling the other version 7 capabilities. In version 8, support for SHARECNV(1) has been optimized to achieve parity with SHARECNV(0). © 2014 IBM Corporation
  • 54. Multiple cluster transmission queues Multiple cluster transmission queues added in V7.5 Support for z/OS and IBM i added in V8 Benefits of using multiple transmission queues © 2014 IBM Corporation Separation of message traffic With a single transmission queue, pending messages for one channel can interfere with those for another, especially when messages build up on the queue Management of messages Use of queue concepts such as MAXDEPTH are not useful when using a single transmission queue for all cluster-sender channels System monitoring Tracking the number of messages processed by a cluster-sender channel is not possible using queue monitoring if a single transmission queue is shared by multiple channels, although some information is available using channel status
  • 55. Multiple cluster transmission queues N O T E S Support for multiple cluster transmission queues was added on the distributed platforms in version 7.5. Version 8 adds support for this capability on z/OS and IBM i. A different transmission queue can now be used by each cluster-sender channel, or a subset of cluster-sender channels, instead of all channels using SYSTEM.CLUSTER.TRANSMIT.QUEUE. The introduction of multiple cluster transmission queues is not designed to improve performance, but to provide a capability to isolate message traffic. – It is quicker to assess the impact of an issue if traffic is separated for different applications. – If a queue manager is a member of multiple clusters, a different transmission queue can be used for each cluster. This can prevent a build up of messages for one cluster, that results in a full page set or MAXDEPTH being reached, impacting the other clusters. – If messages for different applications are sent over different cluster channels* a problem for one application can be prevented from impacting others. * This can be achieved by using a separate cluster for each application, which may overlap with other clusters, or hosting the target queues for each application on different cluster queue managers. © 2014 IBM Corporation
  • 56. Configuring cluster transmission queues DEFCLXQ queue manager attribute Default transmission queue for cluster-sender channels SCTQ Use SYSTEM.CLUSTER.TRANSMIT.QUEUE © 2014 IBM Corporation CHANNEL Create a permanent-dynamic transmission queue per cluster-sender channel called SYSTEM.CLUSTER.TRANSMIT.channel name CLCHNAME queue attribute Set on a manually defined transmission queue Generic name for channels that should use it DEFINE QLOCAL(CLUSTER.XMITQ1) USAGE(XMITQ) CLCHNAME(‘AAA.*’) … Most specific match is used by a channel A17: Managing work-loads, scaling and availability with IBM MQ clusters
  • 57. Configuring cluster transmission queues N O T E S The transmission queue to use for each channel can be configured in two ways: A manually defined transmission queue can be configured using the CLCHNAME attribute. The value of this attribute is a generic, or specific, name for the channels that should use it. The mapping is defined on the transmission queue instead of the channel because the channel’s definition is determined from the cluster-receiver definition on the remote queue manager. If a channel’s name matches multiple CLCHNAME values the most specific match is used to determine which transmission queue to use. If no matching queue is found the queue manager uses the default transmission queue setting, specified by the DEFCLXQ queue manager attribute, to determine which transmission queue to use. This attribute indicates whether to use SYSTEM.CLUSTER.TRANSMIT.QUEUE or to create a permanent-dynamic transmission queue called SYSTEM.CLUSTER.TRANSMIT.channel name. © 2014 IBM Corporation
  • 58. MQ for z/OS: 64-bit bufferpools © 2014 IBM Corporation 64-bit buffer pools in MQ for z/OS Allows large numbers of messages to be cached before writing to pagesets Allows MQ to exploit the vast amount of storage on today's machines Improves performance of putting/getting messages by minimizing disk I/O Minimizes administrative overhead of managing buffer pools Buffer pool LOCATION attribute says where it is located relative to the bar BELOW: The default. Buffer pool is located below the bar in 31 bit storage ABOVE: Buffer pool is located above the bar in 64 bit storage This can be altered dynamically Storage can be pinned based on pageclass attribute Z1: IBM MQ for z/OS V8 Latest Features Deep Dive
  • 59. Buffer pool problems before V8 N O T E S There is not much space below the bar for buffer pools once queue manager code and data is taken into account. Maximum 1.6GB available for buffer pools depending on common area Putting/getting messages into the buffer pool works at 'memory' speed, putting/getting messages from the page set works at 'disk' speed For scenarios where several applications read and/or write large number of messages to the same buffer pool a lot of time is spent getting pages from page set into buffer pool and getting pages from buffer pool into page set © 2014 IBM Corporation – This is detrimental for performance A maximum of 16 buffer pools are supported while up to 100 page sets are supported This can result in a lot of time spent tuning buffer pool sizes and the relationship between queues, buffer pools and page sets These problems are resolved by allowing bufferpools to be defined in 64-bit space, above the bar
  • 60. MQ for z/OS: 64-bit bufferpools Buffer pools above the bar can (theoretically) use up to 16 EB storage DATA © 2014 IBM Corporation Increased maximum size of pool to 999,999,999 buffers Was 500,000 DATA CODE Buffer Pool Buffer Pool Buffer Pool Buffer Pool 16 EB 2 GB BAR Up to 1.6 GB Available Queue Manager Address Space Buffer Pool Allows up to 100 buffer pools Was 16 Can have a 1-1 page set – buffer pool mapping
  • 61. MQ for z/OS: 64-bit bufferpools N O T E S 64-bit bufferpools can now theoretically use a huge amount of storage Having the same number of pools and pagesets makes it much simpler to monitor and control the usage of these resources SMF 115, subtype 215 – Up to 100 buffer pools are now supported. However there is not enough space for 100 buffer manager statistics records (QPST) in the existing SMF 115, subtype 2, record – If OPMODE(NEWFUNC,800) is specified in system parameters then an SMF 115, subtype 215, record will be cut for buffer manager statistics. The SMF 115, subtype 2, record will still contain the self-defining section for buffer manager but it will be all zeros – If OPMODE(COMPAT,800) is specified in system parameters then buffer manager statistics will continue to be in SMF 115, subtype 2. © 2014 IBM Corporation
  • 62. MQ for z/OS: Performance and Capacity © 2014 IBM Corporation Log RBA constraint relief Already improved messages to warn of approaching RBA Now widening RBA field from 6 to 8 bytes At 100MB/sec this will now take about 5578 years to fill Support for LP64 batch/RRS C applications Performance enhancements for IBM Information Replicator (QRep) and similar application patterns Read-ahead and changes to deferred write processing allows MQ to increase sustainable data rates General improvements to channel performance
  • 63. Log RBA extensions N O T E S WebSphere MQ for z/OS V7 implements a 6 byte Log RBA (Relative Byte Address) – This give an RBA range of 0 to x'FFFFFFFFFFFF' (= 255TB) – Some customers are now reaching this limit in 12 months If we reach the end of the Log RBA range (i.e. “wrap”): – Queue Manager terminates and requires a cold start – a disruptive outage – Potential for loss of persistent data © 2014 IBM Corporation To avoid an outage: – Run CSQUTIL RESETPAGE, at regular planned intervals, to RESET the LOG RBA With current maintenance, MQ V7.x issues warning messages when approaching maximum – Then terminates, to prevent loss of data, if log RBA reaches x'FFF800000000'. V8 increases size of Log RBA to 8 bytes – Upper limit on logical log will be 64K times bigger – Format of BSDS and log records will change to accommodate 8 byte RBAs, URIDs will become 8 bytes long – Like DB2, the control point for new function is a BSDS conversion utility – Run the new CSQJUCNV utility – utility will check that entire QSG is at correct level – copies data from old primary / secondary BSDS pair to new primary / secondary pair All V8 queue managers can read data in both the old and new formats All V8 queue managers and utilities will display all log RBAs as 8 bytes V8 will ONLY write in new format, once BSDS has been converted
  • 64. N O T E S © 2014 IBM Corporation LP64 Support Externalising technology previously used by Broker and JMS Limited to C language (no 64bit COBOL) – LP64 compile option – Supported by cmqc.h Restricted environments – Batch, TSO, USS – CICS and IMS do not support 64bit apps Must use sidedeck DLL, not stubs: – csqbmq2x (uncoordinated batch USS) – csqbrr2x (RRS coordinated, srrcmit()) – csqbri2x (RRS coordinated, MQCMIT)
  • 65. Performance improvements N O T E S QRep has implemented a common application pattern – basically a single-stream reading or writing of messages. That program, and others that follow the same pattern, can benefit from some of the performance enhancements in MQ. For example, fetching data for the next message from a pageset at the same time as for the current message (readahead) can reduce the I/O operations and hence reduce CPU and increase throughput. © 2014 IBM Corporation
  • 66. MQ for z/OS: Other features Exploitation of zEDC compression accelerator SMF Channel compression (zlibfast option) can be useful when using SSL Support for Flash Express feature on zEC12 and zBC12 servers Improves resiliency of Coupling Facility with cost-effective standby capacity to handle overflow © 2014 IBM Corporation of shared queues Messages 63K fully held in Flash Messages 63K have pointers in Flash, body in SMDS just as for traditional CF structures SMF enhancements Channel statistics allow better monitoring and tuning of channel behaviour Correlation of MQ and CICS statistics Message suppression A4: IBM MQ for z/OS: Performance and Accounting Up to 16 message numbers (particularly X500,X501) can be defined to be excluded Removes cost of writing WTO messages which are then ignored Can now differentiate between messages for client channels and other types
  • 67. MQ for z/OS: Other features N O T E S A number of internal performance improvements have been implemented in version 8, including some internal optimisations in the channel initiator. Some changes have been introduced to significantly improve performance for IBM Information Replicator (QREP). This product is used to replicate DB2 logs from one system to another. It is used for disaster recovery and in IBM’s active-active solution for z/OS. The improvements made for this type of workload include support for pre-fetching pages from page sets in to buffers and optimizations to the algorithm used to write data to page sets too. These improvements are likely to also benefit other customer workloads. If you configure channel compression using MSGCOMP(ZLIBFAST) and you are running on suitable zEC12 hardware, a zEDC card is exploited if available. This can improve performance as well as reducing CPU activity. Another improvement, although not strictly for performance, is the introduction of a new system parameter, EXCLMSG, that allows you to suppress up to 16 console messages. This can be used to reduce ‘noise’ on the console. It is preferable to using the z/OS Message Processing Facility (MPF) to suppress messages, because using this parameter avoids the CPU overhead of generating the message and issuing the WTO. © 2014 IBM Corporation
  • 68. IBM has a 20 year track record of innovation in Messaging Multi-platform Common criteria Multiple cluster XMIT queue Hypervisors Integrated Messaging V7.1 V7.5 IBM MQ Advanced 1990s 2000s 2010s © 2014 IBM Corporation JMS MQI Assured delivery IBM MQSeries Mobile .NET Eclipse JMS 1.1 RCMS IBM MQ Low Latency V1.1 V2 V5 V5.1 V5.3 V2.1 V5.2 V6 V7 V7.0.1 SSL SOAP XML IBM MQ Managed File Transfer IBM MQTT HTTP AJAX REST Web 2.0 Managed File Transfer Pub/sub IBM MQ Everyplace IBM MQ Advanced Message Security System Pattern Application Pattern V8 IBM MQ Advanced for Developers IBM MessageSight Multi-instance QMGR 20th Anniversary of MQ at IMPACT
  • 69. And continues to invest in all Messaging markets Enterprise Messaging where MQ continues to lead Messaging for Mobile and the Internet of Things Supporting Cloud deployments with Messaging services Helping developers use Application Messaging to create better © 2014 IBM Corporation applications
  • 70. For Additional Information © 2014 IBM Corporation IBM Training http://www.ibm.com/training IBM WebSphere http://www.ibm.com/software/websphere/ http://www.ibm.com/software/products/ibm-mq IBM developerWorks http://www.ibm.com/developerworks/websphere https://www.ibm.com/developerworks/community/blogs/messaging WebSphere forums and community http://www.ibm.com/developerworks/websphere/community/
  • 71. For Additional Information about IBM MQ V8 © 2014 IBM Corporation https://www.ibm.com/developerwo rks/community/blogs/messaging/e ntry/where_can_i_find_mq_v8_inf ormation https://www.google.co.uk/search? q=MQDev+MQ+V8+information
  • 72. IBM MQ Sessions this week 10:30 9:00 - 10:00 - 11:30 11:45 - 12:45 14:00 - 15:00 15:15 - 16:15 16:45 - 17:45 © 2014 IBM Corporation Session A35: How to Develop Responsive Applications with IBM MQ Light Speaker: Rob Nicholson Room 27 Session A9: WebSphere MQ for z/OS: The Inside Story Speaker: Damon Cross Room 6 Session A16: Using IBM MQ Pub/Sub in an MQ network Speaker: David Ware Room 6 Session A21: What's New in IBM Messaging Speaker: Morag Hughson Room 8 Lab AL6: Developing a First Application with IBM WebSphere MQ Light Speakers: Robert Nicholson, Alex Ross Room 7b Friday Session A18: Using Publish /Subscribe with IBM MQ Speaker: David Ware Room 27 Session A3: WebSphere MQ for z/OS: Shared Queues Speaker: Alex Ross Room 6 Session A22: New IBM MQ V8 Security Features Speaker: Morag Hughson Room 01 Thursday Lab IL5: DataPower-MQ Connectivity Deep Dive (Hands-On) Speaker: Robin Wiley Room 7b Session A17: Managing work-loads, scaling and availability with IBM MQ clusters Speaker: David Ware Room 6 Session C7: Messaging in the Cloud with IBM MQ Light and IBM Bluemix Speaker: Rob Nicholson Room 27 Session Z5: WebSphere MQ for z/OS: Security Speaker: Damon Cross Room 02 Wednesday Session Z1: WebSphere MQ for z/OS V8: Latest Features Deep Dive Speaker: Damon Cross Room 6 Session I26: DataPower- MQ Connectivity Deep Dive (Theory) Speaker: Robin Wiley Room 27 Session A4: WebSphere MQ for z/OS: Performance and Accounting Speaker: Alexander Ross Room 8 Session A31: IBM MQ CHLAUTH rules – with MQ V8 updates Speaker: Morag Hughson Room 02 Opening General Session- IBM Digital Experience and WebSphere Technical University Tuesday 10:30 - 12:00 13:15 - 14:15 14:30 - 15:30 16:00 - 17:00 17:15 - 18:15