Date post: | 26-Jan-2017 |
Category: |
Software |
Upload: | timothy-mccormick |
View: | 206 times |
Download: | 0 times |
1 © 2014 IBM Corporation
3425: Using publish/subscribe to
integrate applications
Tim McCormick
IBM MQ Service Architect
2 © 2014 IBM Corporation
Agenda
• Publish/Subscribe in IBM MQ
• Administration of publish/subscribe
• Management of publish/subscribe
• Subscriptions and publications
• Integrating with MQ Light applications
3 © 2014 IBM Corporation
What is publish/subscribe?
4 © 2014 IBM Corporation
point-to-point
Message consumer
Message consumer
Message consumer
Message producer
How does it compare to point-to-point?
5 © 2014 IBM Corporation
point-to-point
Topic
Message consumer
Message consumer
Message consumer
Message producer
How does it compare to point-to-point?
publish/subscribeSubscription
Subscription
Subscription
Message consumer
Message consumer
Message consumer
Message producer
6 © 2014 IBM Corporation
But which subscriptions receive the messages?
Subscription
Subscription
Subscription
Subscription
Publisher
Publisher
Publisher
Subscription
Subscription
• Publishing and subscribing is based on ‘topics’
• Green messages go to green subscribers
• Orange messages go to orange subscribers
• But nobody wants a blue message!
Publisher
7 © 2014 IBM Corporation
Publish/Subscribe inIBM MQ
9 © 2014 IBM Corporation
Terminology in WebSphere MQMQ’s use of publish/subscribe terminology:
TopicThis can mean topic strings, topic objects and even topic nodes, not to mention JMS
topics!
PublisherA publisher is an application that puts messages to a topic as opposed to a queue.
A publisher can either open a topic object or a topic string.
PublicationA publication is simply a message that is put to a topic rather than a queue
SubscriptionA subscription is an artefact that exists on a queue manager that describes where copies of
messages published for a particular topic string are delivered to
A subscription identifies a queue for those messages
SubscriberA subscriber is an application that consumes messages from a subscription
10 © 2014 IBM Corporation
Topics
12 © 2014 IBM Corporation
It’s all about the topic tree
Price
Fruit
Apples Oranges
Vegetables
Potatoes
Topic string
Topic node
/Price/Fruit/Apples /Price/Fruit/Oranges /Price/Vegetables/Potatoes
14 © 2014 IBM Corporation
Price
Fruit
Apples Oranges
Subscription
/Price/Fruit/Oranges
•Subscriptions are attached to matching nodes in the topic tree
•Publications identify the relevant topic node
Publisher
/Price/Fruit/Oranges
•A copy of the publication is delivered to the queue identified by each matching subscription
Subscription
/Price/Fruit/Apples
Subscription
/Price/Fruit/Oranges
Subscription
/Price/Fruit/#
•Wildcarding subscriptions at the topic node level can receive messages from multiple topic strings
Matching publications to subscriptions
15 © 2014 IBM Corporation
Designing your topic tree structure
• Make it extendable.
• Avoid excessively wide or deep dynamic topic trees.
– Use structure where appropriate.
– Limit it to subscribable content.
is
my
first
topic
/This/is/my/first/topic /This/is/my/second/topic
second
topic
Topic1 Topic2 Topic3 Topic4 Topic1000
Topic1 Topic2 Topic3 Topic3 Topic1000
AppA AppB AppC
This
20 © 2014 IBM Corporation
configuration
21 © 2014 IBM Corporation
VEGOBJTOPICSTR(‘/Price/Vegetables’)
FRUITOBJTOPICSTR(‘/Price/Fruit’)
Topic Objects
Price
Fruit
Apples Oranges
Vegetables
Potatoes
SYSTEM.BASE.TOPICTOPICSTR(‘’)
You start with a base object defined for the ‘ ’ node … the rest are optional.
They provide hook points in the topic tree to configure specific pub/sub behaviour for a branch.
A dynamically created topic node inherits its attributes from administered topic objectsassociated with topic nodes above it in the topic tree.
Topic objects are a point of administration associated with a node in the topic tree.
23 © 2014 IBM Corporation
FRUITOBJPUB(ASPARENT)
DEFPSIST(YES)
…
Topic object attributes
Fruit
Oranges
SYSTEM.BASE.TOPICPUB(ENABLED)
DEFPSIST(NO)
…
Price
• Many attributes can be set on topic objects to effect a publisher or subscriber’s behaviour.
• Dynamic nodes inherit their behaviour from nodes above.
Create a topic object for topic string ‘/Price/Fruit’
DEFINE TOPIC(FRUITOBJ) TOPICSTR(‘/Price/Fruit’) DEFPSIST(YES)
Attributes default to inherit settings from above (e.g. ‘ASPARENT’).
(So by default, a new object does nothing)
Publish a message to topic string ‘/Price/Fruit/Oranges’
Are publications enabled?
What message persistence to use?
PUB = ?
PUB = ENABLED
PUB = ?
DEFPSIST = ?
DEFPSIST = YES
Publisher
PUB = ?
YES
ENABLED
26 © 2014 IBM Corporation
Managing topics
27 © 2014 IBM Corporation
Managing topics• Displaying topic object definitions
– This shows how administered topic objects are configured
5724-H72 (C) Copyright IBM Corp. 1994, 2014.Starting MQSC for queue manager QMGR1. DISPLAY
DISPLAY TOPIC(*)1 : DISPLAY TOPIC(*)
AMQ8633: Display topic details.TOPIC(FRUITOBJ) TYPE(LOCAL)
AMQ8633: Display topic details.TOPIC(SYSTEM.BASE.TOPIC) TYPE(LOCAL)
AMQ8633: Display topic details.TOPIC(SYSTEM.BROKER.ADMIN.STREAM) TYPE(LOCAL)
AMQ8633: Display topic details.TOPIC(SYSTEM.BROKER.DEFAULT.STREAM) TYPE(LOCAL)
AMQ8633: Display topic details.TOPIC(SYSTEM.BROKER.DEFAULT.SUBPOINT) TYPE(LOCAL)
AMQ8633: Display topic details.TOPIC(SYSTEM.DEFAULT.TOPIC) TYPE(LOCAL)
AMQ8633: Display topic details.TOPIC(VEGOBJ) TYPE(LOCAL)
DISPLAY TOPIC(FRUITOBJ)2 : DISPLAY TOPIC(FRUITOBJ)
AMQ8633: Display topic details.TOPIC(FRUITOBJ) TYPE(LOCAL)TOPICSTR(/Price/Fruit) DESCR(Price of fruit)CLUSTER( ) CLROUTE(DIRECT)DURSUB(ASPARENT) PUB(ASPARENT)SUB(ASPARENT) DEFPSIST(YES)DEFPRTY(ASPARENT) DEFPRESP(ASPARENT)ALTDATE(2015-02-03) ALTTIME(08.44.48)PMSGDLV(ASPARENT) NPMSGDLV(ASPARENT)PUBSCOPE(ASPARENT) SUBSCOPE(ASPARENT)PROXYSUB(FIRSTUSE) WILDCARD(PASSTHRU)MDURMDL( ) MNDURMDL( )MCAST(ASPARENT) COMMINFO( )USEDLQ(ASPARENT) CUSTOM( )
DISPLAY TOPIC(FRUITOBJ)2 : DISPLAY TOPIC(FRUITOBJ)
AMQ8633: Display topic details.TOPIC(FRUITOBJ) TYPE(LOCAL)TOPICSTR(/Price/Fruit) DESCR(Price of fruit)CLUSTER( ) CLROUTE(DIRECT)DURSUB(ASPARENT) PUB(ASPARENT)SUB(ASPARENT) DEFPSIST(YES)DEFPRTY(ASPARENT) DEFPRESP(ASPARENT)ALTDATE(2015-02-03) ALTTIME(08.44.48)PMSGDLV(ASPARENT) NPMSGDLV(ASPARENT)PUBSCOPE(ASPARENT) SUBSCOPE(ASPARENT)PROXYSUB(FIRSTUSE) WILDCARD(PASSTHRU)MDURMDL( ) MNDURMDL( )MCAST(ASPARENT) COMMINFO( )
USEDLQ(ASPARENT) CUSTOM( )
29 © 2014 IBM Corporation
Managing topics• Displaying the topic tree
– This shows how the topic nodes in the topic tree behave
5724-H72 (C) Copyright IBM Corp. 1994, 2014.Starting MQSC for queue manager QMGR1. DISPLAY
DISPLAY PUBSUB ALL1 : display PUBSUB all
AMQ8723: Display pub/sub status details.QMNAME(QMGR1) TYPE(LOCAL)STATUS(ACTIVE) SUBCOUNT(5)TPCOUNT(11)
DISPLAY TPSTATUS(‘#’) TOPICSTR WHERE(SUBCOUNT GT 0)22 : DISPLAY TPSTATUS('#') TOPICSTR where(SUBCOUNT GT 0)
AMQ8754: Display topic status details.TOPICSTR(/Price/Vegetables/Potatoes) SUBCOUNT(1)
AMQ8754: Display topic status details.TOPICSTR(/Price/Fruit/Oranges) SUBCOUNT(2)
AMQ8754: Display topic status details.TOPICSTR(/Price/Fruit/Apples) SUBCOUNT(1)
DISPLAY TPSTATUS('/Price/Fruit/Apples')23 : DISPLAY TPSTATUS('/Price/Fruit/Apples')
AMQ8754: Display topic status details.TOPICSTR(/Price/Fruit/Apples) ADMIN( )CLUSTER( )COMMINFO(SYSTEM.DEFAULT.COMMINFO.MULTICAST)MDURMDL(SYSTEM.DURABLE.MODEL.QUEUE)MNDURMDL(SYSTEM.NDURABLE.MODEL.QUEUE)CLROUTE(NONE) DEFPSIST(YES)DEFPRTY(0) DEFPRESP(SYNC)DURSUB(YES) PUB(ENABLED)SUB(ENABLED) PMSGDLV(ALLDUR)NPMSGDLV(ALLAVAIL) RETAINED(NO)MCAST(DISABLED) PUBCOUNT(0)SUBCOUNT(1) PUBSCOPE(ALL)SUBSCOPE(ALL) USEDLQ(YES)
V8
DISPLAY TPSTATUS('/Price/Fruit/Apples')23 : DISPLAY TPSTATUS('/Price/Fruit/Apples')
AMQ8754: Display topic status details.TOPICSTR(/Price/Fruit/Apples) ADMIN( )CLUSTER( )COMMINFO(SYSTEM.DEFAULT.COMMINFO.MULTICAST)MDURMDL(SYSTEM.DURABLE.MODEL.QUEUE)MNDURMDL(SYSTEM.NDURABLE.MODEL.QUEUE)CLROUTE(NONE) DEFPSIST(YES)DEFPRTY(0) DEFPRESP(SYNC)DURSUB(YES) PUB(ENABLED)SUB(ENABLED) PMSGDLV(ALLDUR)NPMSGDLV(ALLAVAIL) RETAINED(NO)MCAST(DISABLED) PUBCOUNT(0)SUBCOUNT(1) PUBSCOPE(ALL)SUBSCOPE(ALL) USEDLQ(YES)
31 © 2014 IBM Corporation
Applications
32 © 2014 IBM Corporation
Applications and topics
• When creating subscriptions or opening topics to publish on, do I use a
topic string or a topic object?
– A topic string. No, a topic object. No, both. Actually, er, any of them!
• So which should I use?
– Using the topic string is probably the easiest, it’s closest to what the application is
expecting
• Sub( - , ‘/Price/Fruit/Apples’ ) →
– Using a topic object maps the operation to the topic string of that topic object
• Sub( FRUITOBJ, ‘’ ) →
– If you use both, you get both!
• The topic string is appended to the topic string of the object
• Sub( FRUITOBJ, ‘Apples’ ) →
/Price/Fruit/Apples
/Price/Fruit
/Price/Fruit/Apples
33 © 2014 IBM Corporation
Subscriptions
34 © 2014 IBM Corporation
Subscription types
• There are many different types of subscriptions:
• Administered or application created
• Durable or non-durable
• Managed or unmanaged subscription queues
• These different aspects of a subscription can be combined, don’t
assume it’s one or the other…
35 © 2014 IBM Corporation
Subscription types
Admin
Application
Subscription creation and deletion
Application created subscriptions Applications use an API to dynamically create and delete subscriptions
Administratively created subscriptions An administrator defines subscriptions that can be accessed by applications
Applications can either use the publish/subscribe APIs to access these subscriptions or access their
associated queue using point-to-point APIs.
37 © 2014 IBM Corporation
Subscription types
Admin
Application
Subscription lifetime
Durable subscriptions The lifetime of the subscription is independent of any application
Non-durable subscriptions The lifetime of the subscription is bounded by the creating application
Subscriptions are automatically deleted when the application closes
Durable Non-durable
Admin
Application
39 © 2014 IBM Corporation
Subscription types
Subscription queue management
A subscription maps a topic to a queue. The queue relationship is either explicit or
implicit…
Managed subscription queue The subscription automatically creates and deletes a queue for the use of queuing any matching
publications.
Unmanaged subscription queue When the subscription is created the name and location of an existing queue must be provided by you.
Admin
Application
Durable Non-durable
Admin
Application
Managed Unmanaged
Durable Non-durable Durable Non-durable
Admin
Application(Not JMS) (Not JMS)
41 © 2014 IBM Corporation
Accessing a subscription’s messages
Via the subscription
• An application opens the subscription
– A true pub/sub application
• Works with managed and unmanaged subscription queues
• Limited to one attached consuming application at a time
– Unless you’re using JMS cloned/shared subscriptions
• Generally better pub/sub status feedback
Via the queue
• An application opens the queue associated with the subscription
– This is really a point-to-point application
• Only works with unmanaged subscription queues
• Allows more freedom in what can be done
– For example, multiple concurrent consuming applicationspossible from any API
Consumingapplication
Subscription
Subscription
queue
Unmanaged queue
Consumingapplication
Consumingapplication
Consumingapplication
44 © 2014 IBM Corporation
Managing subscriptions• Displaying subscriptions
– This shows the subscriptions on a queue manager
5724-H72 (C) Copyright IBM Corp. 1994, 2014.Starting MQSC for queue manager QMGR1. DISPLAY
DISPLAY SUB(*) TOPICSTR1 : DISPLAY SUB(*) TOPICSTR
AMQ8096: WebSphere MQ subscription inquired.SUBID(414D5120514D4752312020202020202007183D5320002306)SUB(SUB1) TOPICSTR(/Price/Fruit/Apples)
AMQ8096: WebSphere MQ subscription inquired.SUBID(414D5120514D4752312020202020202004183D5310000006)SUB(SYSTEM.DEFAULT.SUB) TOPICSTR()
AMQ8096: WebSphere MQ subscription inquired.SUBID(414D5120514D4752312020202020202007183D5320002312)SUB(SUB3) TOPICSTR(/Price/Vegetables/Potatoes)
SUBID(414D5120514D4752312020202020202007183D532000230C)SUB(SUB2) TOPICSTR(/Price/Fruit/Oranges)
DISPLAY SUB(SUB1)2 : DISPLAY SUB(SUB1)
AMQ8096: WebSphere MQ subscription inquired.SUBID(414D5120514D4752312020202020202007183D5320002306)SUB(SUB1) TOPICSTR(/Price/Fruit/Apples)TOPICOBJ( )DEST(SYSTEM.MANAGED.DURABLE.533D180705230020)DESTQMGR(QMGR1) PUBAPPID( )SELECTOR( ) SELTYPE(NONE)USERDATA( )PUBACCT(16010515000000DEA960DF651724E4B97C192FE803000000000B)DESTCORL(414D5120514D4752312020202020202007183D5320002306)DESTCLAS(MANAGED) DURABLE(YES)EXPIRY(UNLIMITED) PSPROP(MSGPROP)PUBPRTY(ASPUB) REQONLY(NO)SUBSCOPE(ALL) SUBLEVEL(1)SUBTYPE(ADMIN) VARUSER(ANY)WSCHEMA(TOPIC) SUBUSER(xxxx)CRDATE(2014-04-03) CRTIME(09:19:15)ALTDATE(2014-04-03) ALTTIME(09:19:15)
DISPLAY SBSTATUS(SUB1)3 : DISPLAY SBSTATUS(SUB1)
AMQ8099: WebSphere MQ subscription status inquired.SUB(SUB1)SUBID(414D5120514D4752312020202020202007183D5320002306)SUBUSER(xxxx) RESMDATE(2014-04-03)RESMTIME(09:19:15) LMSGDATE( )LMSGTIME( )ACTCONN(000000000000000000000000000000000000000000000000)DURABLE(YES) MCASTREL( , )NUMMSGS(0) SUBTYPE(ADMIN)TOPICSTR(/Price/Fruit/Apples)
DISPLAY QLOCAL(SYSTEM.MANAGED.DURABLE.533D180705230020)
46 © 2014 IBM Corporation
Publishing
51 © 2014 IBM Corporation
Retained publications
Price
Fruit
Apples Oranges
Subscription
/Price/Fruit/Oranges
Publisher
/Price/Fruit/Oranges
Subscription
/Price/Fruit/Oranges
When a message is published to a topic string, it is delivered to each matching subscription
registered at that time.
Subscriptions created after that point will not receive the message
only newly published ones.
Unless publications are retained
52 © 2014 IBM Corporation
Retained publications
• When a message is published to a topic string, it is delivered to each matching subscription
registered at that time.
• Subscriptions created after that point will not receive the message
only newly published ones.
• Unless publications are retained
• Every time a message is published, the most recent
publication for each topic string is retained by the
queue manager.
• When a new subscription is created, any
matching retained message is
delivered to it.
• Take care, using
retained can be subtle
• Don’t confuse it with persistent publications
Price
Fruit
Apples Oranges
Subscription
/Price/Fruit/Oranges
Publisher
/Price/Fruit/Oranges
Subscription
/Price/Fruit/Oranges
67 © 2014 IBM Corporation
Using MQ Light applications
68 © 2014 IBM Corporation
New AMQP channel type
• Adds a channel type of “AMQP”
• Support a subset of the AMQP 1.0 Oasis specification
• Interoperable with MQ FAP and MQTT applications
• Available from 8.0.0.4
69 © 2014 IBM Corporation
Interoperability
• AMQP to/from MQ and MQTT
Published AMQP messages MQPUT
to an MQ topic
Consumed AMQP messages MQGET
from an MQSUB
MQ apps can publish to AMQP clients by MQPUT to the same
topic string
MQ apps can consume AMQP
messages by subscribing to matching topic
pattern
warehouse/item/372837 warehouse/item/#
orders/electrical/# orders/electrical/wiring
70 © 2014 IBM Corporation
Integrating MQ Light with MQ
• Requires a ‘fresh’ 8.0.0.4 install
– You cannot use a 8.0.0.0 queue manager upgraded by fix pack to 8.0.0.4
• Create AMQP channels
• Use TPROOT to partition applications where desirable
– Use the same way as setting TOPICSTR on topic objects for MQ applications
– MQLight application subscribes to /mytopic
• With TPROOT unset, real subscription is /mytopic
• Set TPROOT to /amqp and the real subscription is to /amqp/mytopic
71 © 2014 IBM Corporation
Questions & Answers
72 © 2014 IBM Corporation
Notices and Disclaimers
72
Copyright © 2016 by International Business Machines Corporation (IBM). No part of this document may be reproduced or transmitted in any form without written permission from IBM.
U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM.
Information in these presentations (including information relating to products that have not yet been announced by IBM) has been reviewed for accuracy as of the date of initial publication and could include unintentional technical or typographical errors. IBM shall have no responsibility to update this information. THIS DOCUMENT IS DISTRIBUTED "AS IS" WITHOUT ANY WARRANTY, EITHER EXPRESS OR IMPLIED. IN NO EVENT SHALL IBM BE LIABLE FOR ANY DAMAGEARISING FROM THE USE OF THIS INFORMATION, INCLUDING BUT NOT LIMITED TO, LOSS OF DATA, BUSINESS INTERRUPTION, LOSS OF PROFIT OR LOSS OF OPPORTUNITY. IBM products and services are warranted according to the terms and conditions of the agreements under which they are provided.
Any statements regarding IBM's future direction, intent or product plans are subject to change or withdrawal without notice.
Performance data contained herein was generally obtained in a controlled, isolated environments. Customer examples are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual performance, cost, savings or other results in other operating environments may vary.
References in this document to IBM products, programs, or services does not imply that IBM intends to make such products, programs or services available in all countries in which IBM operates or does business.
Workshops, sessions and associated materials may have been prepared by independent session speakers, and do not necessarily reflect the views of IBM. All materials and discussions are provided for informational purposes only, and are neither intended to, nor shall constitute legal or other guidance or advice to any individual participant or their specific situation.
It is the customer’s responsibility to insure its own compliance with legal requirements and to obtain advice of competent legal counsel as to the identification and interpretation of any relevant laws and regulatory requirements that may affect the customer’s business and any actions the customer may need to take to comply with such laws. IBM does not provide legal advice or represent or warrant that its services or products will ensure that the customer is in compliance with any law
73 © 2014 IBM Corporation
Notices and Disclaimers Con’t.
73
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.
74 © 2014 IBM Corporation
Thank YouYour Feedback is Important!
Access the InterConnect 2016 Conference Attendee Portal to complete your session surveys from your
smartphone,
laptop or conference kiosk.
75 © 2014 IBM Corporation
Monday
10:30-11:30 3592 New MQ features
3452 Managing applications
12:00-13:00 2835 MQ on z/OS and Distributed
15:00-16:00 3470 Latest MQ z/OS features
2833 Where is my message?
3544 MQ Light in an MQ infrastructure
16:30-17:30 3573 Hybrid cloud messaging
2941 MQ Advanced
Tuesday
08:30-09:30 3540 The MQ Light API
12:00-13:00 3456 The IBM MQ Appliance
13:15-14:15 3499 Introducing Message Hub
3458 MQ Appliance administration
14:30-15:30 6432 MQ updates and futures (InnerCircle)
2849 Messaging feedback roundtable
16:00-17:00 3544 MQ Light in an MQ infrastructure
3513 MQ hands on lab
Wednesday
08:30-09:30 3602 Managing your MQ environment
12:00-13:00 3613 Designing MQ self service
6408 Hybrid messaging roadmap (InnerCircle)
13:15-14:00 3416 HA and DR with MQ
3433 Why secure your messaging?
15:45-16:30 3429 Securing MQ
2847 Meet the messaging experts
16:00-17:00 3508 MQ Light hands on lab
16:45-17:30 2275 Migrating to the IBM MQ Appliance
Thursday
08:30-09:15 3420 MQ Clustering
2931 Business agility with self service MQ
09:30-10:15 3479 MQ z/OS clusters and shared queue
3450 Optimising MQ applications
2849 Messaging feedback roundtable
10:30-11:15 3465 MQ Appliance high availability
3481 MQ z/OS messaging connectivity
11:30-12:15 3474 Active-active messaging
3537 Monitoring and managing MQ
3425 MQ publish/subscribe
Find us at the EXPO:
Hybrid Integration peds 65-68
Check out the Hybrid Messaging sub topic under the
Hybrid Integration topic for further customer and business partner
sessions
Hybrid Messaging from the IBM experts at InterConnect 2016 Sunday
14:30-15:30 6408 Hybrid messaging roadmap (InnerCircle)