This presentation was given at Interconnect 2016. It starts by showing the interfaces within MQ for management and monitoring, and then shows how these are used within a cloud environment to control the delivery of a service-based messaging system.
2. Please Note:
1
• IBM’s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM’s sole
discretion.
• Information regarding potential future products is intended to outline our general product direction and it should not be relied on in
making a purchasing decision.
• The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any
material, code or functionality. Information about potential future products may not be incorporated into any contract.
• The development, release, and timing of any future features or functionality described for our products remains at our sole discretion.
• Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual
throughput or performance that any user will experience will vary depending upon many factors, including considerations such as the
amount of multiprogramming in the user’s job stream, the I/O configuration, the storage configuration, and the workload processed.
Therefore, no assurance can be given that an individual user will achieve results similar to those stated here.
3. Digital IT Enterprise IT
MQ cloud optionsIBM Message Hub
Cloud
On-Prem
Cloud
On-Prem
IBM MQ Appliance
Message Hub
Based on Apache Kafka
Message Hub
Based on Apache Kafka
Message Hub
Based on Apache Kafka
Public
(GA: Dec 2015)
Dedicated
(Target: 1Q 2016)
Local
(Coming soon!)
IBM MQ Light (API)
IBM MQ
IBM Messaging has Solutions to Suit All Needs
5. Queue
Manager
MQ Administration
ini files
OS commandsMQSC commands PCF commands
Events (async)
Status (polled)
OS configuration
These are all documented and supported
interfaces – it has encouraged a management
ecosystem over many years
Log files
6. IBM MQ - MQSC
• Command line interface
• V8 enhanced runmqsc
– Make it world-executable
– Enable direct client-connection
• MQSC intended for human consumption
– Parsable by eye, less easy in programs
– For example, DESCR('This is 'a' description with quote & paren(' )
– No guaranteed ordering in runmqsc, two-column output
• Despite awkwardness, basis for many script-based admin tools
– echo "DISPLAY Q(X) IPPROCS" | runmqsc QM1
• Same commands – different front-end (CSQUTIL) – for z/OS
Old Example: AIX smit panels
7. IBM MQ - PCF
• A "self-describing" MQ message used for administrative operations
• Your programs can send commands and get responses using PCF
– Equivalent to "DISPLAY QSTATUS" or "ALTER CHANNEL"
• MQ emits events in PCF format
– "Queue is getting full"
• PCF intended for programs – usually C or Java
– Can tell exactly what the parameter is for, its length and value
– But cannot easily be scripted
• Approximately one-one mapping between MQSC commands and PCF
• Remember that PCF invented before formats like JSON or XML
– And there are many MQ apps that are built on PCF
19. MQ Appliance Console
• Ships as part of the MQ Appliance
• Provides a subset of MQ Explorer functionality
• Also provides management of MQ Appliance specific capability such as
HA/DR configuration
MQ Appliance
QM1
QM2
Liberty
Appliance
Console
(in web browser)
PCF REST
20. Statement of direction
• IBM intends to deliver support for the new IBM MQ Console in IBM MQ
– IBM intends to add support to enable the IBM MQ Console to configure and
monitor IBM MQ as well as the IBM MQ Appliance. IBM intends to allow MQ
administrators to make more effective use of the IBM MQ Console in
environments in which both IBM MQ and the IBM MQ Appliance are installed
• http://ibm.biz/MQConsoleSOD
23. Background
• The MQ Light Bluemix service is provided by queue managers
• Each queue manager runs in a VM in SoftLayer and is created and
destroyed based on demand
• The hosting company (IBM) needs a way to monitor and manage those
queue managers
– To understand utilization
– To detect errors
25. Design
• Builds on existing monitoring infrastructure
• Uses common tools to parse and represent data
• Flexible generation of charts
• Only the data we need is captured, reducing system load
29. Detecting errors
• Need to be able to visualize error logs from all queue managers across
all VMs
• Spikes in log entries indicates potential problem
• Need to be able to filter and search data too
35. Summary
• Fundamental interfaces in MQ give the control and data
• Have been used to build a variety of scale of solution
• Can drive common modern toolkits for integration with other products
38. Notices and Disclaimers Con’t.
Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not
tested those products in connection with this publication and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products.
Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. IBM does not warrant the quality of any third-party products, or the
ability of any such third-party products to interoperate with IBM’s products. IBM EXPRESSLY DISCLAIMS ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING BUT
NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
The provision of the information contained h erein is not intended to, and does not, grant any right or license under any IBM patents, copyrights, trademarks or other intellectual
property right.
IBM, the IBM logo, ibm.com, Aspera®, Bluemix, Blueworks Live, CICS, Clearcase, Cognos®, DOORS®, Emptoris®, Enterprise Document Management System™, FASP®,
FileNet®, Global Business Services ®, Global Technology Services ®, IBM ExperienceOne™, IBM SmartCloud®, IBM Social Business®, Information on Demand, ILOG,
Maximo®, MQIntegrator®, MQSeries®, Netcool®, OMEGAMON, OpenPower, PureAnalytics™, PureApplication®, pureCluster™, PureCoverage®, PureData®,
PureExperience®, PureFlex®, pureQuery®, pureScale®, PureSystems®, QRadar®, Rational®, Rhapsody®, Smarter Commerce®, SoDA, SPSS, Sterling Commerce®,
StoredIQ, Tealeaf®, Tivoli®, Trusteer®, Unica®, urban{code}®, Watson, WebSphere®, Worklight®, X-Force® and System z® Z/OS, are trademarks of International Business
Machines Corporation, registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM
trademarks is available on the Web at "Copyright and trademark information" at: www.ibm.com/legal/copytrade.shtml.
39. Thank You
Your Feedback is Important!
Access the InterConnect 2016 Conference Attendee
Portal to complete your session surveys from your
smartphone,
laptop or conference kiosk.