http://prolifics.com/ This presentation takes a deep dive into the latest features of IBM WebSphere MQ and Message Broker to see how these new capabilities are changing the world. It examines how MQ and Message Broker can connect anything, anywhere and achieve universal connectivity with: - Enhanced file and messaging capabilities of IBM WebSphere Message Broker 8.0 and WebSphere MQ 7.5, including the ability to handle many formats (i.e. XML, CSV, etc.) - The ability of WebSphere MQ Telemetry Transport (MQTT) to connect through the web or through devices - An extended reach of WebSphere MQ via the new HTTP and FTP bridges - High Availability that makes the system more reliable than ever and allows WebSphere MQ clients to automatically reconnect

1. Connectivity for a Smarter Planet
How MQ and Message Broker will change the world
Many Thanks to Mark Taylor, Anthony O’Dowd & David Locke
Presented by: A.J. Aronoff
Connectivity Practice Director
Email: aj@prolifics.com
Desk: 646-201-4943

2. Agenda – Connectivity
 Universal Connectivity: The Path to the Future
 Latest features of MQ 7.5 and MB 8
• Enhanced file and messaging capabilities
• HTTP and FTP Bridges
 MQ Telemetry – MQ Without wires
• Smarter Planet:
– Technology for the Retail Industry
• Security and High Availability
2

3. Prolifics wins IBM Awards
AWARDS: SKILLS and RESOURCES:
 2012 Outstanding Business Agility Solution Award  Serviced over 1500 IBM software accounts in the past 8 years;
implemented over 300 portals
 2012 IBM Smart SOA Impact Award Winner
 Conducted migrations to WebSphere from other technologies for
 2012 Global WebSphere Community Customer over 140 clients encompassing more than 2,000 applications
Recognition Award Winner
 Prolifics boasts over 400 J2EE, WebSphere, ICS, Security, Business
 2012 ICS Award for Best Industry Oriented Social Analytics, ECM, Tivoli, Rational certifications for architecture,
Business Solution development, administration, and project management
 2012 IBM Awarding Client Excellence (ACE)  IBM’s highest technical rating (Level 5)
Award Winner  Highly Accredited - IBM Tivoli “AAA Accredited;” IBM Cloud
 2010 Impact Best BPM Solution Award Certified; Accredited with Ready for Rational; IBM Authorizations
for Security, Insurance, Finance, Healthcare & Life Sciences,
 2010 Lotus Best End-User Solution Award Banking, Energy & Utilities, Social Business and Enterprise Content
Management.
 2010 Lotus Best Industry Solution Award
 8 Technical Staff are "IBM Champions"
 2009 Rational Solution Award
 Prolifics has worked with internal development teams multiple
 2008 Outstanding SOA Solution Award times for the development of IBM technologies.
 2008 Overall Technical Excellence Award  Strategic relationship gains internal access to IBM’s resources,
labs, and product development teams
 2007 Overall Technical Excellence Award
 2007 Impact SOA Process Solution Award
 2006 Best Portal Solution Lotus Award
 2005 5-Star Partner Award
3

4. by doing great work with Great Customers
Financial Services
Healthcare Government
Retail & Distribution Utilities
Insurance Education
4

5. IBM MQ Connectivity for a Smarter & Secure Planet
A Universal Message Bus providing connectivity to, from and within your Enterprise to
access data wherever it exists to support your business
Provides a comprehensive range of
Messaging capabilities
to support your Business
requirements for data integration:
-- Messaging integration patterns
-- Reliability and availability QoS
Files
Data
Apps
Events
Sensors
Processes
Mobile
Cloud
Mainframe
Services
Partners
-- Managed File Transfer
-- SOA foundation
-- EDA foundation
Provides appropriate data access
and data privacy controls to help
meet audit and regulatory Universal Connectivity
requirements
Provides a range of messaging on-ramps appropriate to your business needs and
developer skills
Provides a range of messaging topologies and deployments to meet your business and
IT needs
CSS: F S

6. WebSphere MQ V7.5: Content Summary
 For Windows, Unix and Linux
WebSphere MQ V7.5
Announced: 24 April 2012
Availability: 20 June 2012
New Feature Benefits Details
Makes it easier to deploy systems Combines several products into a single package
Integrated Installation
Simpler licensing Common experience
Improves ease-of-use
Enhanced Clustering Split Cluster Transmission Queue
Improves application isolation
Java Application
Makes it easier to distinguish applications Applications no longer to all have the same name
Identification
Provides a level of message protection even
Interception in the SVRCONN still protects messages before
AMS channel interception when application environment cannot run
hitting queues
AMS
No longer a requirement for an enterprise database
FTE Logger Options Can write FTE audit records to flat file
Easier to read data immediately
CSS: F S

7. WebSphere MQ V7.1: Feature Summary
WebSphere MQ V7.1
Announced: 4 October 2011
New Feature Benefits Availability: 11 November 2011
Details
Multi-Version Install Unix and Windows support for multiple versions of MQ V7.x (AND
Makes it easier to deploy and upgrade
one copy of MQ V7.0.1) down to fixpack levels.
capability on Distributed systems and stage version to version
Relocatable installation support.
platforms migration
Applications can connect to any Qmgr
IP address Authorisation capability
Simplified Configuration
Additional crypto algorithms
Enhanced Security
More granular authorisation for non-local queues
Enhanced Authorisation and Auditing
Application Activity Reports
Cloud Support Simplifies and support Cloud deployments Additional HVE images
Authorisation on Cluster Q rather than XMIT Q on Dist. Platforms
Enhanced Clustering Improves ease-of-use
Bind-on-Group Support
MQ Pub/Sub Topic space can now map to multicast Group
New messaging QoS provides low latency
Multicast capability with high fan-out capability
Addresses
Provides direct interoperability with MQ LLM
Further exploitation of z196 Code contention reduced to improve multi-processor linear scaling
Improved scalability and Use of MQ Datasets rather than DB2 significantly improves “large”
availability on z/OS Customer control over CF storage use message capability
CF Connectivity Loss improvements Structure rebuild capability for CF Connectivity Loss scenarios
Improved Performance on
Improved multiprocessor exploitation Various code improvements
Dist platforms
8 CSS: F S

8. WebSphere MQ
WebSphere MQ V7.5 MQ Server (Queue manager)
+ MQ TT Gateway
+ Advanced Message Security
+ Managed File Transfer Service
+ MQ Explorer with built-in
 Integrated Messaging Offering
AMS & managed file transfer
MQ Client
 Single install, packaging & tooling for all Messaging options + AMS Enablement
+ MQ TT Clients
 Reduce time to value, simplify usage Managed File Transfer Agent
+ AMS Enablement
Multi-Language Documentation
+ Security (AMS) sections
 What‟s being delivered? + Managed File Transfer sections
 Integration of MQ with MQ FTE, MQ AMS and MQ Telemetry
 Single install, common integrated tooling and management, WebSphere MQ
simplified licensing and entitlements
 Updated MQ Explorer tooling for all platforms MQ Server (Queue manager)
 More complete, easy to use messaging infrastructure, MQ Client
enabling you to gain full range of messaging, swiftly & easily
MQ Documentation
Advanced Message Security
 All messaging functions & capabilities
Advanced Msg Security
available to all customers, new and existing
AMS Documentation
with rich choice of qualities of service
 Removal of charge for MQ XA client File Transfer Edition
 Reduced pricing metric for standard MQ Telemetry client
FTE Server
• Lower cost for larger numbers of clients
FTE Client
FTE Docs + tools
CSS: F S

9. Simplifying access to WebSphere MQ V7.5 capabilities
 Flexible configurations seamless
selection of enhanced security,
managed file transfer and Telemetry
capabilities in one package
 Rapid exploitation of new
technologies built-in integration of
applications on any platform, any
devices spanning mainframe to
mobile and cloud
 Seamless, single console shared
backbone for all messaging
solutions, mobile/device integration,
application messaging and managed
file transfers
 Enhanced utilization of
messaging through use
Managed File Transfer solutions
over the messaging backbone

10. MQ FTE
Quick Overview
Directory Monitoring
FTP & SFTP Bridging agents
File to Message - Message to File
11

11. FTP Spaghetti Infrustructure (haphazard growth)
X Unreliable transport mechanisms
Each link in a chain reduces reliability
X No central set-up, logging or monitoring
X Poor documentation of overall system
X Expensive, one-off solutions
X High maintenance costs
(60 – 70% of a company‟s IT budget)
X Lack of business agility

12. MQ FTE allows you to
…go from this
…to this

13. Ideal File Transfer Infrastructure Automation
&
Documented, Centralized
Standardized Set-up
Solutions
Reliable
Transport Reliable
Reliable Transport
Transport
Event based
Centralized Centralized
Monitoring Logging
Reliable
Reliable Transport
Transport
Reliable
Reliable
Transport
Transport

14. MQ FTE: Use Case 1: Directory Monitor
•Three sub directories with the same names of three destination FTE Agents
•When a file with an extension of “doc” is added to one of the sub directories
• The Resource monitor detects the file, and
• creates a file transfer request for the file where the destination agent has the
same name as the sub directory.
http://www.ibm.com/developerworks/websphere/library/techarticles/0910_bonney/0910_bonney.html
•A company in Florida is using the above system and planning to scale up further
FTE Receiving Agent
Resource OfficeA
/incoming/monitor
Monitor
FTE Receiving Agent
OfficeB
/A /B /C FTE Sending Agent
1.Doc FTE Receiving Agent
OfficeC
15

15. MQ FTE 7.0.2 Protocol Bridge
Support for transferring files located on FTP and SFTP servers
 The source or destination for a transfer can be an FTP or an SFTP server
Fully integrated into graphical, command line and XML scripting interfaces
 Just looks like another FTE agent…
Enables incremental modernization of (S)FTP-based Legacy solutions
 This helps ease migration from a non-managed (FTP or SFTP) network to a managed network
based on WebSphere MQ File Transfer Edition. (I.E. less rip & replace).
 Ensures reliability of transfers across FTP/SFTP with checkpoint restart
 Provides auditability of transfers across FTP/SFTP to central audit log
Files exchanged between FTE and FTP/SFTP
FTE FTP
MQ FTE FTP
FTE FTP / SFTP FTP
network network
FTE FTP
Bridging FTP/SFTP
Agent Server
Protocol FTP
Bridge Server
Audit Agent
information

16. Two Implementation Options Available
 Support Pac MA0Y & WMQ V7: HTTP Bridge implemented as Servlet
 Suitable for deployment to existing J2EE app. servers (WAS, Geronimo, JBOSS)
 Back end connectivity uses the WMQ JCA resource adapter and WMQ JMS
 JMS ConnectionFactory config determines if MQ connection uses client/bindings
mode
 Support Pac MA94: Standalone HTTP Listener
 Available for Windows, AIX, and Linux
 Client or bindings mode, Security exits
17

17. Options for converting data between files & messages
One file to one message
WMQ  One file becomes one message
FTE
One file to a group of messages The file can be split
WMQ based on:
FTE  Size
 Binary delimiter
One message to one file  Regular expression
WMQ  One message becomes one file
FTE
A group of messages (or all messages on the queue) to one file
 Optionally, a delimiter can be
WMQ inserted between each message
FTE used to compose the file
18

18. Customer Survey: Of the points below:
Which point(s) matters most to you?
Records complete and detailed audit log of entire file journey
 Auditable “What went where, when and to whom”
File contents not corrupted or partially transmitted
 Reliable Files only appear at destination whole and intact
Files content encrypted during transmission
 Secure File access authenticated and controlled
Eliminates need to manually detect problems and restart transfers
 Automated Providing scheduling and triggering for event-driven transfers
 Centralized Remote control and monitoring of file progress from anywhere
Able to deploy and re-configure file transfers instantaneously from anywhere
 Flexible Managing transfers end-to-end across a network – not just between 2 points
 Any file size No upper limit on the size of file that can be moved
 Integrated With SOA infrastructure: Messaging, ESBs, Governance, B2B and BPM
 Cost Provides a consolidated transport for moving both Files and Messages
Effective

19. Securing the Universal Messaging Bus
WebSphere MQ Advanced Message Security
What is it?
 New product - WebSphere MQ Advanced Message Security
 Replaces WebSphere MQ Extended Security Edition
 Component added to WebSphere MQ V7 or V6
Enhances MQ security processing
 Provides additional security services over and above base QM
 Designed to assist with requirements such as PCI DSS compliance
Application ---> Application protection for point-to-point messaging
Industry standard asymmetric cryptography used to protect individual messages
Uses Public Key Infrastructure (PKI) to protect MQ messages
 Uses digital certificates (X.509) for applications
Non-invasive
No changes required to MQ applications
Security policies used to define the security level required
 Administratively controlled policies applied to queues
• Command line
• Explorer

20. Message Level Protection
Enables secure message transfers at application level
Assurance that messages have not been altered in transit
When issuing payment information messages, ensure the payment amount does
not change before reaching the receiver
Assurance that messages originated from the expected source
When processing messages, validate the sender
Assurance that messages can only be viewed by intended recipient(s
When sending confidential information.

21. Interceptors

22. MQ AMS interceptors
MQ AMS functionality is implemented in interceptors.
There are no long running processes or daemons (Except in z/OS).
Existing MQ applications do not require changes.
Three interceptors are provided:
1.Server interceptor for local (bindings mode) MQI API & Java applications.
Implemented as queue manager API exit.
2. MQI API client interceptor for remote (client mode) MQ API applications.
MQ AMS interceptor imbedded in MQ client code.
3. Java client interceptor for remote (client mode) MQ JMS and MQ classes
for java applications (J2EE and J2SE).
MQ AMS interceptor imbedded in MQ java client code.
MQ V7.0 java client required.
SupportPac MQC7 WebSphere MQ V7.0 clients.

23. MQ & MQTT: Connectivity to, from & within an Enterprise
The path to the future
 A Universal Message Bus for access to Enterprise
Regional Office
data wherever it exists to support your
business
 Provides a comprehensive range of
Messaging capabilities to support your
Business requirements for data
integration Sensor
e.g. RFID
 Managed File Transfer
 Messaging integration patterns Branch
Outlet
 Reliability and availability QoS
 SOA foundation
Retail
 Provides appropriate data access Store
and data privacy controls to help
meet audit and regulatory requirements
 WMQ Telemetry is one step in
extending the reach of WMQ to a wider
Pervasive
world of data relevant to your business Device
Refinery
 Recent technology demonstration of MQ
Web Messaging using HTML5
Petrol Mobile
WebSockets continues this progress Forecourt Phone
24 CSS: F S

24. MQTT: Key Features
 Open published spec designed for the
• Minimized on-the-wire format
world of “devices”
 Smallest possible packet size is 2
 Invented by IBM and Euro tech
bytes
 MQTT client code (C and Java)
donated to the Eclipse "Paho" M2M  No application message headers
project • Reduced complexity/footprint
 Clients: C=30Kb; Java=100Kb
 Three qualities of service:
 0 – at most once delivery • Simple / minimal pub/sub messaging
 1 – assured delivery but may be duplicated semantics
 2 – once and once only delivery
• Asynchronous (“push”) delivery
 In-built constructs to support loss of Simple set of verbs
contact between client and server.
 Connect, publish, subscribe and
 “Last will and testament” to publish a disconnect.
message if the client goes offline.
 Stateful “roll-forward” semantics &
“durable” subscriptions.

25. MQTT: Key Features (cont.)
 240,000 concurrent clients tested with <5%
CPU on a single IBM WebSphere MQ queue
manager
 “Would have gone higher but the Lab ran
out of load testing client machine”
 By comparison:
 Apache Web Servers max out at 25,000
connections
 Direct connection between your enterprise and
devices
 Network: TLS/SSL
 Authentication: JAAS
 Authorization: OAM

26. MQ Telemetry Implementation
 New WebSphere MQ Telemetry component – also known as
MQXR („eXtended Reach‟)
 Now included in MQ 7.1 and MQ 7.5
 Fully integrated/interoperable with WMQ
 MQTT messages translated to standard MQ messages
 Administration included as part of MQ explorer
 Telemetry Channels enable MQTT connections to the queue
manager
 Supports MQTTv3 protocol (which is the most common one in use)
27

27. Mobile Is Driving Changes to the Traditional Web
One of the problems we experienced was long latency when sending a message. The method
we were using to send was reliable but slow, & there were limitations on how much we could
improve it. With just a few weeks until launch, we ended up building a new mechanism that
maintains a persistent connection to our servers. To do this without killing battery life, we used a
protocol called MQTT. MQTT is specifically designed for applications like sending telemetry data
to & from space probes, so it is designed to use bandwidth & batteries sparingly. By maintaining
an MQTT connection & routing messages through our chat pipeline, we were able to often
achieve phone-to-phone delivery in the hundreds of milliseconds, rather than multiple seconds.
- Building Facebook Messenger by Lucy Zhang (tinyurl.com/makingfbmessenger)
28

28. MQTT: Business Scenarios
Scenario Key Industries Example
Automated Chemical & Petroleum Solution provider enables smart metering of home
Metering Energy & Utilities energy by using MQ Telemetry technology
Distribution Supply Retailers Distributors Shipping company improves customer loyalty by
Chain and Consumer products providing up-to-the-moment detailed tracking
Logistics Transportation information for cargo
Industrial Tracking Automotive Transportation company improves customer safety
& Visibility Industrial manufacturing and satisfaction with improved tracking of fleet
Aerospace
Defense
Healthcare Pharmaceutical companies Manufacturing company automates inventory
Personal & checking to improve management of stock and
Resource Tracking optimize production rates
Location Health trials Medical organization uses MQ Telemetry to track
Awareness and Hospitals health of at-risk patients to increase safety and
Safety Nursing Homes quality of patient care
Executive Alerting Chemical & Petroleum Hospital uses MQ Telemetry to track expensive
Energy & Utilities surgery equipment to maximize utilization and
Homeland Defense reduce waiting lists
29

29.                                

Retail: RFID: Solution Architecture
                      
 
  
30                 

 
   
      


30.                             
     
        
       

Home Pace Maker Monitoring Solution
  

    
   
       
       
       
     
                          

         
                                               
 
•    Monitor large numbers  of  patient‟s  pace   makers in their home
                                          
•   Collect diagnostics  and periodically dial health care provider
                           
•    Immediately dial if               detected
       
      abnormality         

•      Often  over  “old”  –  very  slow, fragile dial  up connections
             
               
                       
        
• Remove need for patient to visit to clinic on fixed interval
• Clinician  only sees patients with problems
        
  
                

31

31. Message Broker 8 Summary: Themes
 Simple & Productive
 Making it easier and quicker to develop and manage MB solutions
• Learn, Develop, Deploy, Manage, Migrate quickly and easily
 Universal & Independent
 Connecting MB to a range of different systems
• Universal connectivity includes standards, de facto standards, industry and custom
systems
 Industry Specific & Relevant
 Provide industry connectivity packs to solve domain specific problems
• Industry specific nodes, solution-oriented patterns & user-oriented tooling
 Dynamic & Managed
 Allow the creation of dynamic and governed solutions
• Design solutions for easy, flexible change with appropriate control
 High Performing & Scalable
 Provide a platform and technology neutral connectivity option
• Work on widest possible range of hardware, software & virtualized environments
32

32. Easy Data Modeling with DFDL
 Simple & powerful standard for data modeling
 New standard for binary, text & industry data formats
• Logical structure with physical annotations
• e.g. endian, ASCII/EBCDIC, padding, justify
 Data Format Description Language (DFDL)
• For use in IBM and non-IBM products
• forge.gridforum.org/projects/dfdl-wg
 Built-in facilities to model data easily
 Quick wizards for (e.g.) CSV, record oriented data
 Auto-model importers (e.g.) COBOL copybooks
 DFDL editor for power users
• Create logical model & physical refinements
 Test parsing and test data generation
 Test whether sample data fits with DFDL definition
• Parse trace provide success & error case explanation
• Auto-generate test data for test & debug scenarios
 All broker nodes can exploit new DFDL parser
 Configure as existing XML, JSON, MRM, MIME... parsers
 • Interacts with message tree in usual manner
 Excellent performance characteristics
• (e.g.)element type, size, structural complexity, etc.
• Supports streaming, partial parsing, etc.
33

33. Graphical Transformations
 IBM Graphical Data Mapper (GDM)
 Visually map & transform source to target data
• Code-free, high performing & scalable
 GDM designed for whole IBM product set
• e.g. Full map exchange with MDM Server V9
• Mapping Script Language(MSL)format
 Simple & powerful graphical mapping experience
 Apply transformations to single and multiple elements
• Conditionals (if then else), Loops(for each), Functions(target=f(source)) & more!
 Database mapping sources and targets for routing and enrichment scenarios
• Broad data base support(Oracle,DB2,SQLServer,Sybase,Informix...)
 Complements and supports existing transformation languages
• Call user defined transformation in Java, SQL, XPath, .NET...
  Simple deployment, high performing & scalable
 Maps can be deployed with solution BAR file or stand-alone
 JIT compile means technology advances improves existing, deployed solutions
• Source deploy + runtime compilation = enhanced performance
34

34. Enhanced Patterns Support
 User Defined Patterns
 Add your own patterns to Patterns Explorer
• Complements IBM supplied patterns
 Create reusable assets according to best practices
• Typically performed with Enterprise Architect
• Generated Flow always create conforming logic
 Generate pattern starting from an existing message flow
 Identify key message flow (node) properties
 Create pattern parameters & property mappings
 Create pattern documentation and help; Preview
 Add your pattern to Patterns Explorer for reuse
 User-defined subflows for black-box style reuse
 Create user-defined node packages from subflows
 Implementation remains opaque
 Excellent for library style node reuse
 Distribute & share via any Library Control System
 Patterns Explorer Expansion
 1-way MQ reliable invocation of Web Service Includes error handling
35

35. Why use Patterns?
A pattern in Message Broker is a template that generates one or more production
ready projects. All the projects that a pattern creates share a set of common
properties.
 Creates top-down, parameterized connectivity solutions
• Web Service façades, message oriented processing, queue-to-file
 Reduces common problems in flow development
• “Brilliant People Solve Problems - Geniuses Prevents Them” A. Einstein.
 Communicates best practices to the Broker community
 Complements existing bottom-up construction for connectivity
 Reduces time-to-value for solution development
 Patterns are a first class citizen in Message Broker
 Patterns have bubbled right to the top in the navigator view!
36

36. WebSphere MQ V7.1: Feature Summary
WebSphere MQ V7.1
Announced: 4 October 2011
New Feature Benefits Availability: 11 November 2011
Details
Multi-Version Install Unix and Windows support for multiple versions of MQ V7.x (AND
Makes it easier to deploy and upgrade
one copy of MQ V7.0.1) down to fixpack levels.
capability on Distributed systems and stage version to version
Relocatable installation support.
platforms migration
Applications can connect to any Qmgr
IP address Authorisation capability
Simplified Configuration
Additional crypto algorithms
Enhanced Security
More granular authorisation for non-local queues
Enhanced Authorisation and Auditing
Application Activity Reports
Cloud Support Simplifies and support Cloud deployments Additional HVE images
Authorisation on Cluster Q rather than XMIT Q on Dist. Platforms
Enhanced Clustering Improves ease-of-use
Bind-on-Group Support
MQ Pub/Sub Topic space can now map to multicast Group
New messaging QoS provides low latency
Multicast capability with high fan-out capability
Addresses
Provides direct interoperability with MQ LLM
Further exploitation of z196 Code contention reduced to improve multi-processor linear scaling
Improved scalability and Use of MQ Datasets rather than DB2 significantly improves “large”
availability on z/OS Customer control over CF storage use message capability
CF Connectivity Loss improvements Structure rebuild capability for CF Connectivity Loss scenarios
Improved Performance on
Improved multiprocessor exploitation Various code improvements
Dist platforms
37 CSS: F S

37. Scalability & Performance – Distributed platforms
 Performance measured and improved for a range of scenarios
 Hardware capabilities have evolved over years to have more CPUs, more
memory etc
 MQ topologies have evolved to have more clients and larger/fewer queue
managers
 “Fastest MQ ever”: better performance than V6 and V7
 Multicast faster than traditional non-persistent
 Over 5x for one-many publications
 Performance reports to be released on availability
CSS: F S
CSS: F S

38. Channel Access Policy (1)
SET CHLAUTH(*) TYPE(ADDRESSMAP) ADDRESS(‘*’) USERSRC(NOACCESS)
“We must make sure our system is completely locked down”
CSS: F

39. Channel Access Policy (2)
SET CHLAUTH(*) TYPE(ADDRESSMAP) ADDRESS(‘*’) USERSRC(NOACCESS)
SET CHLAUTH(BPCHL.*) TYPE(SSLPEERMAP) SSLPEER(‘O=Bank of Shetland’) MCAUSER(BANK123)
SET CHLAUTH(BPCHL.*) TYPE(SSLPEERMAP) SSLPEER(‘O=Bank of Orkney’) MCAUSER(BANK456)
“Our Business Partners must all connect using SSL, so we will
map their access from the certificate DNs”
CSS: F

40. Channel Access Policy (3)
SET CHLAUTH(*) TYPE(ADDRESSMAP) ADDRESS(‘*’) USERSRC(NOACCESS)
SET CHLAUTH(BPCHL.*) TYPE(SSLPEERMAP) SSLPEER(‘O=Bank of Shetland’) MCAUSER(BANK123)
SET CHLAUTH(BPCHL.*) TYPE(SSLPEERMAP) SSLPEER(‘O=Bank of Orkney’) MCAUSER(BANK456)
SET CHLAUTH(SYSTEM.ADMIN.SVRCONN) TYPE(ADDRESSMAP)
ADDRESS(‘9.20.1-30.*’) MCAUSER(ADMUSER)
“Our Administrators connect in using MQ Explorer, but don‟t
use SSL. We will map their access by IP Address”
CSS: F

41. Channel Access Policy (4)
SET CHLAUTH(*) TYPE(ADDRESSMAP) ADDRESS(‘*’) USERSRC(NOACCESS)
SET CHLAUTH(BPCHL.*) TYPE(SSLPEERMAP) SSLPEER(‘O=Bank of Shetland’) MCAUSER(BANK123)
SET CHLAUTH(BPCHL.*) TYPE(SSLPEERMAP) SSLPEER(‘O=Bank of Orkney’) MCAUSER(BANK456)
SET CHLAUTH(SYSTEM.ADMIN.SVRCONN) TYPE(ADDRESSMAP)
ADDRESS(‘9.20.1-30.*’) MCAUSER(ADMUSER)
SET CHLAUTH(TO.CLUS.*) TYPE(QMGRMAP)
QMNAME(CLUSQM*) MCAUSER(CLUSUSR) ADDRESS(‘9.30.*’)
“Our internal cluster doesn‟t use SSL, but we must ensure only
the correct queue managers can connect into the cluster”
CSS: F

42. MQ High Availability: Multi-Instance Queue Managers
1. Normal MQ MQ
Execution Client Client
network
192.168.0.1 192.168.0.2
Machine A Machine B
QM1 QM1
Active can fail-over Standby
instance instance
QM1
networked storage
Owns the queue manager data

43. Multi-Instance Queue Managers
2. Disaster MQ MQ
Strikes Client Client
network
Connections
broken from
clients
192.168.0.1 192.168.0.2
Machine A Machine B
QM1 QM1
Active locks freed Standby
instance instance
QM1
networked storage

44. Multi-Instance Queue Managers
3. Standby MQ MQ
Connections
Comes to Life Client Client still broken
network
192.168.0.2
Machine B
QM1
Active
instance
QM1
networked storage
Owns the queue manager data

45. Multi-Instance Queue Managers
4. Recovery MQ MQ
Complete Client Client Clients reconnected.
Processing
continues.
network
192.168.0.2
Machine B
QM1
Active
instance
QM1
networked storage
Owns the queue manager data

46. Multi-Instance Queue Managers: How it Looks
 As a graphical example, SupportPac MS0P V7.0.1

47. Message Broker H.A. using MQ 7.0.1 multi instance queue managers
 Message Broker exploits MQ 7.0.1 multi-instance queue manager capability
 Active and stand-by queue managers
 Start multiple instances of a queue manager on different machines
 One is “active” instance; other is “standby” instance
 Shared data is held in shared networked storage but owned by active instance
 Exploitation by Message Broker
 If standby instance of the queue manager becomes active, then
the newly active MQ instance will start message broker once MQ recovery is
complete

48. Automatic Client Reconnection
 Client library provides necessary reconnection logic on detection of a
failure
 Hides failure from application code
QM1
Application
QM2
MQ Client
QM3

49. Automatic Client Reconnection
 Tries to hide queue manager failures by restoring current state automatically
 For example, if MQPUT returns error, client reruns MQCONN/MQOPEN/MQPUT
internally
 Uses the list of addresses in CONNAME to find queue manager
 MQSERVER environment variable also understands list
 MQSERVER=SYSTEM.DEF.SVRCONN/TCP/host1(1414),host2(1414)
 Can reconnect to the same or different Queue Manager
 Re-opens queues and other qmgr objects, re-establishes subscriptions
 Reconnection interval is backed off exponentially on each unsuccessful retry
 Total timeout is configurable – default 30 minutes.

50. Universal Messaging with WebSphere MQ
Any skills Any platform
Any QoS
Any network Any speed
Any data Any delivery level
Any device
Universal Messaging
51 CSS: F S

51. 52