The document discusses the IBM MQ Appliance, which provides IBM MQ V8 in an appliance form factor for scalable and secure messaging. Key capabilities of the MQ Appliance include:
1) Rapid deployment of queue managers on the appliance with built-in high availability and disaster recovery capabilities that do not require external dependencies.
2) Simplified maintenance through firmware updates that bundle appliance, operating system, and MQ fixpack updates together.
3) Secure administration through local and web-based interfaces, and encryption of messaging using built-in MQ Advanced Message Security.
1. Session #3456: Expanding your
options with the IBM MQ Appliance
Leif Davidsen – Senior Offering Manager, IBM Messaging
Anthony Beardsmore – IBM MQ Appliance Architect
3. • The scalability and security of IBM MQ V8 in a physical appliance form factor
• Rapid, reliable, simple, secure exchange of data across applications, systems and services
• Convenience, fast time-to-value, and low total cost of ownership of an appliance
• Use as a messaging hub to extend connectivity within your enterprise, in branch offices, factories or stores
What’s new in IBM MQ Appliance M2000
Integrates seamlessly into MQ networks and clusters
Simple out of the box High-Availability and Disaster Recovery with paired connectivity to other
appliances
Simpler maintenance with fixpacks delivered as certified firmware updates onto a locked down appliance
Appliance delivered pre-optimized for maximum performance out-of-the-box
New MQ Console to provide a browser-based user interface offering personalized monitoring and
configuration
General Availability: March 13th
2015
IBM MQ Appliance M2000
3
4. IBM MQ Appliance offers:
Optimized solutions to meet the needs of these use cases
Differentiation compared to MQ software deployment approaches
2 price points to meet different deployment-based business needs
What do you want to do?
Consolidate
my MQ
infrastructure
into an “MQ
Hub” for
lower TCO
Deploy to
remote
premises, e.g.
Branch,
Factory,
Warehouse
Deploy to
business
partner,
e.g. Dealer,
Broker
4
4
5. Challenges
Mixture of platforms
and versions
Complex dependencies
Migrations difficult –
lack of standardization
Application downtime
impacts other
applications
Consolidate my MQ infrastructure into a “MQ Hub” for
lower TCO
Objectives
Reduce TCO
Reduce footprint
Standardise
deployments
Build 'hub' -
concentrate
expertise
5
Benefits
Easy to deploy
Simplified maintenance
Familiar administration
Separates applications
from Infrastructure
Supports existing MQ
definitions, concepts
and security model
HA avoiding external
dependencies
6. Challenges
Avoiding single
points of failure
Outside assistance
needed – lack of
local skills and
resources
Deploy to a remote premises
Objectives
Resilient
connectivity to
remote location
Robust and secure
Flexibility, minimal
time to value at
new sites
Benefits
Standardization
makes ‘pre-canned’
rollout simpler
Remote configuration
and management
High availability
requires no
additional systems or
skills
6
7. Challenges
Partner may not have
MQ or MQ skills today
Time to build and
deploy
Configuration needs to
meet our standards
Downtime directly
effects business
relationship
Deploying to business partner: Appliances as ‘Gateways’
Objectives
Extend connectivity
to external business
partner
Rapid onboarding
Control and limit
access
QOS expectations
from both parties
Benefits
Easy to deploy
Simplified maintenance
Ability to preconfigure a very
standard system both helps
ensure standards applied
and speed deployment
HA avoiding external
dependencies
7
9. Prebuilt for Hub pattern – no Apps on device
No additional software installation
No user Exits in MQ
Monitoring agents must be remote
High Availability out-of-the-box
Single Firmware update for whole appliance
Firmware update inc. appliance and MQ Fixpack
Can be rolled back as an single unit
Controlled administration environment
Web, MQ Explorer and MQSC/cmd-line admin of MQ
IBM MQ Appliance IBM MQ V8 on Custom Server
Key Differences with Appliance Form-factor
DIY Hub or Generic server – Apps + Middleware
Install any software
Build & maintain your own custom extensions
Add local monitoring agents
Needs HA Cluster SW or Network Storage for HA
Custom tuning for each layer (OS/Middleware)
Discrete maintenance for each layer
MQ Fixpacks;OS maintenance, security patches etc.
Generic OS shell for local administration
MQ Explorer and MQSC/cmd-line administration of MQ 9
10. QM1 QM2 QM3
QM1 QM2 QM3
Fully synchronous
replication (HA) or asynchronous (DR)
• No persistent data loss
on failure (HA mode)
• No external storage
• No additional skills
required
• Manual control of failover
for migration/maintenance
• Queue manager level
active/passive (i.e. both
appliances can run
workload)
Designed to be configured in seconds with no external dependencies
Availability options in the MQ Appliance
10
11. IBM MQ Appliance M2000
• Optimized messaging, right out of the box
• Secure your business with High Availability built-in
• Lower your TCO with simpler maintenance, and
lower data storage space and power requirements
• Deploy to partners and remote premises, without
requiring local MQ expertise
IBM Integration Bus V10
• Increased flexibility with separate deployment for MQ
• Install in minutes
• New patterns to rapidly create mobile integrations
• Flexible cloud deployment options
The Complete Messaging and Integration Solution
11
13. Lets really simplify it…
An MQ Appliance is a box where you create and
run queue managers…
Application
Application
Application
Application
Application
13
14. Physical configuration
2x Management 1GB Ethernet
(also IPMI)
Display
(includes
capacity and
version
information)
Serial / KVM connection
N.B. REQUIRED for initial setup
General purpose 1GB Ethernet
(MQ Application traffic)
General purpose 10GB Ethernet
(SPF+)
(MQ Application traffic)
2x 1GB Ethernet:
HA or general purpose
10 GB Ethernet (SPF+):
HA or general purpose
HBA (unused)
14
15. M2000(mqcli)#crtmqm test
Pleasewait while64GB filesystemis initialized for queuemanager 'test'.
IBM MQAppliancequeuemanager created.
Thequeuemanager is associatedwith installation'MQAppliance'.
Creating or replacing default objects for queuemanager 'test'.
Defaultobjects statistics : 83created. 0replaced. 0failed.
Completing setup.
Setup completed.
M2000(mqcli)#strmqm test
IBM MQAppliancequeuemanager 'test' starting.
Thequeuemanager is associatedwith installation'MQAppliance'.
5log records accessed onqueuemanager 'test' during thelog replayphase.
Log replayfor queue manager 'test' complete.
Transaction manager state recovered for queue manager 'test'.
IBM MQAppliancequeuemanager 'test' startedusing V8.0.0.4.
M2000(mqcli)#runmqsc test
5724-H72(C) Copyright IBM Corp.1994, 2014.
Starting MQSC for queuemanager test.
Serial/SSH
HTTP
M2000(mqcli)#crtmqm test
Please waitwhile64GBfilesystemis initialized for queue manager 'test'.
IBM MQ Appliancequeuemanager created.
The queuemanager is associatedwith installation'MQAppliance'.
Creating or replacing default objects for queuemanager 'test'.
Default objects statistics : 83created. 0replaced. 0failed.
Completing setup.
Setupcompleted.
M2000(mqcli)#strmqm test
IBM MQ Appliancequeuemanager 'test' starting.
The queuemanager is associatedwith installation'MQAppliance'.
5log records accessedonqueuemanager 'test' during the log replayphase.
Log replayfor queue manager 'test' complete.
Transactionmanager staterecoveredfor queue manager 'test'.
IBM MQ Appliancequeuemanager 'test' startedusing V8.0.0.4.
M2000(mqcli)#runmqsc test
5724-H72(C) CopyrightIBM Corp. 1994, 2014.
Starting MQSC for queuemanager test.
MQ Channel (PCF)
New for
Version 8!
New for
Appliance
Administration
15
16. Much more detail in…
3458A
The IBM MQ
Appliance:
Administration
Simplified
Mandalay Bay
NORTH - South
Pacific Ballroom I
Tue, 23-Feb 01:15
PM - 02:15 PM
Aka… the session right after this!
16
17. M2000(mqcli)#crtmqmtest
Pleasewait while64GBfilesystem is initializedfor queuemanager 'test'.
IBM MQAppliancequeuemanager created.
Thequeue manager is associatedwithinstallation'MQAppliance'.
Creating or replacing default objects for queuemanager 'test'.
Default objects statistics : 83 created. 0replaced.0failed.
Completing setup.
Setupcompleted.
M2000(mqcli)#strmqmtest
IBM MQAppliancequeuemanager 'test' starting.
Thequeue manager is associatedwithinstallation'MQAppliance'.
5log records accessedonqueuemanager 'test' during thelog replayphase.
Log replay for queuemanager 'test' complete.
Transaction manager staterecovered for queuemanager 'test'.
IBM MQAppliancequeuemanager 'test' startedusing V8.0.0.4.
M2000(mqcli)#runmqsc test
5724-H72(C) Copyright IBM Corp. 1994,2014.
Starting MQSC for queuemanager test.
M2000(mqcli)#crtmqmtest
Pleasewait while 64GBfilesystem is initializedfor queuemanager 'test'.
IBM MQ Appliancequeue manager created.
Thequeue manager is associatedwithinstallation'MQAppliance'.
Creating or replacing default objects for queuemanager 'test'.
Default objects statistics : 83 created.0 replaced. 0failed.
Completing setup.
Setupcompleted.
M2000(mqcli)#strmqmtest
IBM MQ Appliancequeue manager 'test' starting.
Thequeue manager is associatedwithinstallation'MQAppliance'.
5log records accessedonqueuemanager 'test' during thelog replayphase.
Log replayfor queuemanager 'test' complete.
Transactionmanager staterecoveredfor queuemanager 'test'.
IBM MQ Appliancequeue manager 'test' startedusing V8.0.0.4.
M2000(mqcli)#runmqsc test
5724-H72(C) Copyright IBM Corp. 1994, 2014.
Starting MQSC for queue manager test.
M2000(mqcli)#crtmqmtest
Pleasewait while64GBfilesystem is initializedfor queuemanager 'test'.
IBM MQAppliancequeuemanager created.
Thequeue manager is associatedwithinstallation'MQAppliance'.
Creating or replacing default objects for queuemanager 'test'.
Default objects statistics : 83 created. 0replaced.0failed.
Completing setup.
Setupcompleted.
M2000(mqcli)#strmqmtest
IBM MQAppliancequeuemanager 'test' starting.
Thequeue manager is associatedwithinstallation'MQAppliance'.
5log records accessedonqueuemanager 'test' during thelog replayphase.
Log replay for queuemanager 'test' complete.
Transaction manager staterecovered for queuemanager 'test'.
IBM MQAppliancequeuemanager 'test' startedusing V8.0.0.4.
M2000(mqcli)#runmqsc test
5724-H72(C) Copyright IBM Corp. 1994,2014.
Starting MQSC for queuemanager test.
Administrative
user repository
Messaging user
repository
Administrators are always
defined locally on the
appliance and can connect
via SSH or WebUI to
administer all aspects of
the system
Messaging Users may be
defined locally or in LDAP
repository (choice per QM),
and remote applications
always connect with these
credentials.
Secure administration
17
18. Traditional MQ
(software)
Queue
Manager
Application
Application
M2000(mqcli)# crtmqm test
Please wait while 64GBfile system is initializedfor queue manager 'test'.
IBM MQ Appliancequeue manager created.
The queuemanager is associatedwithinstallation'MQAppliance'.
Creating or replacing defaultobjects for queuemanager 'test'.
Default objects statistics :83created. 0replaced. 0failed.
Completing setup.
Setupcompleted.
M2000(mqcli)# strmqm test
IBM MQ Appliancequeue manager 'test' starting.
The queuemanager is associatedwithinstallation'MQAppliance'.
5log records accessedonqueue manager 'test' during the log replayphase.
Log replayfor queuemanager 'test' complete.
Transactionmanager staterecoveredfor queuemanager 'test'.
IBM MQ Appliancequeue manager 'test' startedusing V8.0.0.4.
M2000(mqcli)# runmqsc test
5724-H72(C) Copyright IBM Corp. 1994, 2014.
Starting MQSC for queue manager test.
New certificate
management commands
TLS (SSL) on channels
End to end and at-rest
encryption using AMS built
in and included as standard
Secure messaging
18
19. Secure updates
Mq-appliance-
8.0.0.3.scrypt3
Visit fix central to
download appliance
updates to a local
server ready to deploy
Updates are supplied as a
simple single file download,
signed and secure, and are the
only thing which can be installed
on the appliance hardware. Copy to appliance – update,
and reboot. All driver, system
and MQ updates are applied
as a single operation
19
20. Log database
or file
The MQ Appliance can be the Queue
Manager to provide both regular MQ Queue
Manager capabilities
No other MQ server deployment needed
Also Coordination Queue Manager
capabilities
No files are stored on the appliance
No MQ MFT Agent needed on the
appliance to support this
Highly available and robust
Secure with MQ AMS entitlement built in
– Content encrypted based on policies
Applications exchanging file data
Agent Agent Agent
“Coordination”
Queue Manager
Commands
Using MQ MFT and the MQ Appliance
20
21. • The IBM MQ Appliance supports a number of protocols for message transmission
• Today:
– MQ client protocol – for connectivity from applications
•Client libraries available in the usual places, not shipped with the appliance
– MQ server protocol – for connectivity with other queue managers
•This will support sender-receiver channels and server-requester channels,
including cluster flows
• Subject to customer interest we may add further protocols such as
– MQTT – for internet of things and mobile/web messaging
– AMQP – for MQ Light API client connectivity
Connectivity
21
22. QM1 QM2 QM3
QM1 QM2 QM3
Fully synchronous
replication
Key design points:
-No (persistent) message loss
-No external dependencies
-Transparent to application
HA Overview
22
24. DR Replication
Asynchronous
(10 Gb Ethernet)
• New function in 8.0.0.4 update
• Provides for longer distance recovery
than HA
• e.g. Out Of Region standby site
• Still ultimately requires high
bandwidth connectivity as all
persistent data fully mirrored
• But - asynchronous so better choice
than HA for higher latency, ‘bursty’ or
‘lossy’ networks)
• Also means most recent messages are
potentially lost on failover, and application logic
must consider
• Manual interaction required to trigger
failover/fail back.
Disaster Recovery
24
25. Disaster Recovery – Flexible topologies
Production appliance
Off-site DR appliance
Asynchronous
replication
Flexible Config
•As with HA, configuration is per queue manager – though with DR there is no
concept of a ‘group’.
•Each QM independently configures replication to a particular appliance.
•E.g. could configure single ‘DR’ site covering live appliances at multiple sites
Mixed Test/DR appliance
Production appliance
25
26. Much more detail in…
3465A
Deploying a Highly
Available
Messaging Hub
Using the IBM MQ
Appliance
Mandalay Bay
NORTH - South
Pacific Ballroom I
Thu, 25-Feb 10:30
AM - 11:20 AM
26
27. Monitoring MQ on the appliance
Typically, third party (or other IBM
product) tooling will already support
MQ appliance queue managers
without changes.
This image shows Tivoli Remote
Agent displaying queue and channel
information from an appliance queue
manager.
Various third party vendors have
already explicitly confirmed support
(check with vendor for specific
product information).
But there are also appliance specific features…
27
28. • To create, click hotspot
Configure the widget
Display appliance resource use
Platform-wide or queue manager
CPU, Disk, memory, etc
Select:
Resource class/type/element
Queue manager(s) to monitor
Choose Resource class
CPU
Data stores
API Usage stats
Monitoring System Resources
Chart ‘widgets’ and new API
28
29. Monitoring applications
Classic use cases for dedicated/specialised exit code is
addressed by enhanced application ‘activity trace’ –
dynamic publish subscribe API for inspection of
application MQ activity.
Which applications make use of
which resources (e.g. queues)
What is coming in off this set of
channels right now?
How can I keep an audit log of all
messages put by a particular
application?
29
31.
The IBM MQ Appliance is available in two models, to suit a range of performance and
capacity requirements
– They’re not sold on a PVU basis – but approximately 420 & 1400 PVU
• Appliance is dedicated to running messaging server workload
– No other workload (applications or middleware)
– Performance should be predictable
– Capacity planning should be easier
• Firmware comes pre-tuned for maximum messaging performance
– Placement of workload, resource utilisation, etc.
• Performance report MPA1 now available
– Based on firmware level 8.0.0.3,
– Includes scenario driven examples and M2000A/B comparisons.
• Performance report MPA2 now available
– HA and DR, including over increased latency connections
Performance and capacity reports
31
32. Dedicated appliance KnowledgeCenter – particularly covers differences from
software MQ installations
http://www-01.ibm.com/support/knowledgecenter/SS5K6E/welcome
GitHub community with example remote configuration scripts
https://github.com/ibm-messaging/mq-appliance
RedBook (draft at time of writing), particularly useful for first time setup and
hardware configuration
http://www.redbooks.ibm.com/Redbooks.nsf/RedpieceAbstr
acts/sg248283.html
Online
32
34. • Hybrid Integration Strategy
• Cloud Integration
• Accelerating Digital Business
• Integration Bus
• IBM MQ
• API Management
• BPM / ODM
• DataPower
• CICS
• WAS
Spend time with IBM experts, at the home of many of IBM's software products. This summit is by
invitation only - a limited seating engagement for executives and architects who would like to learn how to
harness IBM connectivity and application integration solutions to deliver access to data, applications and
information regardless of platform, device or data formats - across both on-premises and cloud
environments.
Learn more about how we are transforming our technologies using Hybrid Cloud to enable you to harness
your existing assets to achieve greater capacity, efficiency and integration across platforms, whilst retaining
the security, capability and resiliency you would expect from IBM.
• Discover and influence IBM's strategy for key messaging and integration technologies, including, IBM
MQ, IBM Integration Bus and IBM API Management
• Engage in technical sessions and one-on-one interactions with top IBM Hursley Lab architects and
senior executives to refine your 2016 strategic plans
• Expand your network with industry-leading peers from other companies
• Plus learn about other IBM technology, such as IBM intelligent business process management solutions
(BPM & ODM), DataPower gateways, CICS and WebSphere Application Server on-premise and cloud
This event is conducted under a Non-Disclosure agreement, so we will be able to share product directions
with you.
Hursley: a visit to talk about
The IBM Hursley Lab is the largest
software development facility in Europe;
situated in a beautiful 100 acre park with
a historic setting. Attendees stay in the
local city of Winchester which is a vibrant
heritage destination with many
attractions and classical architecture
including a magnificent cathedral.
Enjoy the award-winning pubs and
restaurants and a tempting array of
independent shops.
Be part of the conversation
Keep up to date with the latest
information, join the conversations
and help to shape the event to meet
your interests. Use #IBMhursum in
your Tweets to keep in touch.
#IBMhursum
European & North American
Hursley Summit 2016
Integration across applications, data and processes for mobile and cloud
May 10 – 12 & May 16 - 19 | IBM Hursley Lab
#IBMhursum
36. Notices and Disclaimers Con’t.
36
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.
37. 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.
Editor's Notes
So what’s important to know as a one chart summary for the MQ Appliance? Essentially this is MQ – but delivered as a state of the art physical appliance. And it delivers MQ V8 – such that the MQ Appliance can deploy, connect and integrate seamlessly into existing MQ environments – or indeed be the only MQ provider in an environment – it works either way.
SO the MQ Appliance offers the same rapid, reliable, simple and secure messaging between applications systems and services.
But it does this with an appliance form factor which obviously means there are some differences in deployment, operation and maintenance of the MQ Appliance as compared to software-based MQ.
In this presentation we will be covering some of the differences of MQ on the Appliance and MQ as software – but we will also ensure we highlight the importance of how closely related these deployment options for MQ are.
I have already mentioned that the MQ Appliance integrates seamlessly in to MQ networks and clusters.
However there are a number of key new benefits from the appliance.
One of these is a new high availability configuration with the appliance able to be directly paired to another appliance to form a High Availability group – this removes a lot of existing complexity of setting up HA – but still provides failover for business continuity – we think that this is one of the areas that will be of strong interest to customers – we know most people run in production with high availability – and in our early design discussions with customers about the appliance this was an area that we received a lot of guidance about – that HA should be a self-contained solution in an appliance – it should not depend on being able to set up a shared disk environment – which can be fairly complex – something we are trying to get away from with the appliance.
As another ‘self-contained aspect’ of the MQ appliance there is a new tooling interface – called the MQ Console.
While you can still use the existing MQ Explorer and scripting tools like MQSC – the new MQ Console is browser based – so doesn’t require installing and can be used to customize your view of what is going on in the appliance.
Another benefit to call out at this point is that as an appliance you have the MQ capability supplied along with the firmware layer of the appliance itself. There is a single maintenance fixpack that will be provided with any updates that will provide a consistent updated image applied in a single operation – keeping both MQ and the underlying hardware and OS current.
Finally as a key point, MQ is used in lots of different ways – but clients are always keen to understand whether they have deployed and configured MQ to get the best out of it. With the MQ appliance you get the best performance out of the box with no tuning required.
So – that’s a quick fire summary of the MQ Appliance – lets explore some of these points and others in more detail
We will explore 3 core use cases that we have heard about from many customers about how they intend to use the appliance
We tend to refer to them by shorthand names – but to be fair they describe a multitude of different use cases which we hang on a few short descriptors.
IBM MQ Appliance can be used if you want to:
Consolidate your MQ infrastructure. Reducing or simplifying the number of machines that you use, and cut costs. This is typically looking at the deployment of MQ in the data center, perhaps as part of a new architecture or deploying for a new project. We sometime refer to this as building a messaging hub – something that fits the MQ Appliance vey well
Deploy to remote premises – we refer to this as the messaging outpost – putting MQ in a location where it would provide benefits but deploying MQ on a server might not always be simple or cost effective, either initially or in the longer term
Deploy with a business partner, who might not have MQ skills but who needs to exchange MQ messages with your business. Therefore MQ is required in the partner environment but without having to burden the partner with the need to build skills and maintain the infrastructure
So lets look in a little more detail at these three – and also one more to come
The MQ Appliance comes in two different models to suit both the enterprise and the branch needs, however if over time having deployed the branch model you find you need the extra capability for an enterprise appliance there is a trade up part available so you do not need to buy a new appliance, you can simply increase the capacity in the existing branch model.
Both appliances seamlessly integrate with existing MQ networks and clusters, have simple out of the box high availability when paired to a second appliance. There is a new MQ console which is a browser based user interface for administration, monitoring and configuration. Fixpacks are delivered as certified firmware updates making maintenance simpler and they both support advanced message security and can move files between managed file transfer endpoints.
When it comes to the appliance there are 2 models that can be purchased – both are in fact the same physical model – but to meet differing deployment needs IBM is offering 2 price points – with the only difference between the models being the number of processor cores that are made available for use. This limitation will restrict the total messaging throughput potential and therefore for smaller workloads the M2000B is available – and for larger workloads the M2000A is available at a higher price. It is possible to buy the M2000B and then later if you find you need greater capacity to buy the ‘Additional Capacity Option part number which will enable the remainder of the cores to be turned on, without the need to replace the appliance or even needing to reconfigure.
In all other aspects the 2 appliances are the same – there is no restriction on the number of Queue Managers that can be defined and run – however clearly IBM would expect that larger workloads would be deployed on the M2000A – and more Queue Managers might be defined there. However equally a single large Queue Manager could also run on the appliance. And if multiple Queue Managers are defined, then be aware as each consumes an amount of resource on the appliance, defining too many will cause the appliance to run potentially inefficiently. IBM would expect that perhaps no more than 6 Queue Managers would be the maximum to be run for maximum throughput.
Both models of appliance also include all the features of the appliance including the built-in MQ AMS function for end to end encryption and the new simple High Availability feature.
The performance and expected throughputs of the 2 models of the appliance will be described in a performance guide that will be available within the next week or so – this will call out some of the demonstrated measurements of work for the appliance and help to offer sizing guidance for which appliance to use for any workload or deployment use case
So whatever your workload or use case there should be a MQ Appliance that you can review and select. But lets first look at the expected use cases
Primary instance of queue manager runs on one appliance
Secondary instance on the other for HA protection
Primary and secondary work together
Operations on primary automatically replicated to secondary
All persistent messages logged at both nodes before return to application
Appliances monitor one another and perform local restart/failover
Easier to set up than other HA solutions (no shared file system/shared disks)
Supports manual failover, e.g. for rolling upgrades
Replication is synchronous over Ethernet, for 100% fidelity
Routable but not intended for long distances
Ensure all elements of routing redundant if not using direct cables
There are many other potential usage scenarios for the MQ Appliance – but those give you a start about thinking about how the MQ appliance could benefit your organization.
Now the rest of the presentation will dive a little deeper into the key functions of the MQ Appliance – calling out once more some of the differences between MQ as software and the MQ Appliance – and ensuring those new capabilities are better understood
Finally in this use case section there is another deployment example where the MQ Appliance could be used. I think I have mentioned that the MQ Appliance is absolutely locked down. No code can be installed on it – other than IBM certified updates. No applications can be installed and no files can be written to the appliance. However this doesn’t mean the MQ Appliance can’t participate in a MQ Managed File Transfer scenario.
For MQ MFT file data can be moved over the MQ network as MQ Messages. For this to happen MQ MFT Agents are deployed where the files reside – and where you want to move file data to. But between those points you need MQ Queue Managers, both to provide the MQ infrastructure and to provide a ‘co-ordination queue manager’ which manages the file movements.
Once again – files are not being moved as files – but the contents of files can be moved as MQ messages – with the same qualities of service – over a MQ network. And there is no reason why the MQ Appliance can’t be used as the ‘drop-in’ MQ capability needed to support the MQ Managed File Transfer scenario.
I will reiterate there are no files stored on the MQ Appliance – it is acting as a MQ Queue Manager here – and the MQ Appliance can provide the only MQ Queue Manager capability needed. And as already described, the MQ Advanced Message Security function is built-in – so the data being exchanged between these endpoints can be, according to policies, encrypted so that the message contents – which are the file contents are securely exchanged without needing additional programming or coding at either end.
There are many other potential usage scenarios for the MQ Appliance – but those give you a start about thinking about how the MQ appliance could benefit your organization.
Now the rest of the presentation will dive a little deeper into the key functions of the MQ Appliance – calling out once more some of the differences between MQ as software and the MQ Appliance – and ensuring those new capabilities are better understood