Ibm mq appliance slideshare

Introduction to the IBM MQ Appliance
Anthony Beardsmore (Development Lead)
abeards@uk.ibm.com
July 2015

2 © 2015 IBM Corporation
Please Note
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.

Overview
• IBM has released an IBM MQ Appliance, GA’d March 13th
• Built using the latest DataPower appliance hardware and OS
• Firmware includes the MQ V8 product and capabilities (latest fix level)
– Participates in MQ networks or clusters
– Existing MQ applications connect as clients, with no code changes
• Two models, to suit different uses and performance requirements
• Familiar administration concepts and security model, existing tools and
experience translate seamlessly – plus some great new options
• Built-in High Availability - without external dependencies (shared file
systems or shared disks)

Why an Appliance?
• Fixed hardware specification allows IBM to simplify and tune the firmware
– Having fewer POVs makes it easier to deploy and manage
– Less performance tuning should be needed
• Standardisation accelerates deployment
– Repeatable and fast, less configuration/tuning required
– Post-deployment resource definition or lock down before deployment
• “Hub” pattern separates messaging from applications/middleware
– Organisational independence from application teams
– Improved availability, due to reduction of downtime
– Predictable performance, simpler capacity planning
• Simplified ownership
– Self-contained: avoids dependencies on other resources/teams
– Licensing: Simpler than calculating licensing costs (e.g. by PVU)
– Security: Easier to assess for security compliance audit

Expected uses of the IBM MQ Appliance
How an appliance may help to achieve the following messaging requirements
Messaging Hub One or more dedicated messaging servers to which
applications connect
Messaging Outpost A messaging server located in a remote location with
limited skills and facilities
Messaging Gateway A dedicated server that handles all traffic from a remote
messaging system
Messaging Partner A messaging server located in a business partner that
needs to resilient and safe connectivity to your MQ
infrastructure

IBM MQ Appliance capabilities
• This section describes the main capabilities and distinguishing
characteristics of the appliance
• Administration
• Security
• Connectivity
• High Availability
• External Storage (statement of direction)
• Performance and Capacity
• Key differences between MQ Appliance and installable MQ

Administration
• Command-line Interface
– Appliance CLI supports appliance-specific commands such as configuring
network interfaces, importing certificates, …
– Appliance CLI also offers a familiar subset of MQ control commands
– You can also use MQSC scripts
• Web UI
– Browser-based UI for administering the appliance
– Avoids maintenance of rich client installations
– Very convenient for proofs-of-concept and application developer use
• MQ Explorer
– Essential for existing administrators
• PCF
– Supports remote administration using all of the existing MQ tools

Command Line Interface

Web UI and MQ Console

Security
• An appliance administrator can be authorised to perform MQ administration
– Can separate roles of appliance administrator and messaging administrator
– Both are separate from messaging users
• The appliance supports secure connectivity over SSL/TLS
– Certificates can be imported to the appliance
• The appliance supports scalable security administration
– For a small number of messaging users, you can define them locally
– For larger communities, you can use an off-board repository
• Using external LDAP repository
• Authorization checks can include group memberships from LDAP
• Messaging user ids don’t need to be defined in each server/appliance
• “MQ Internet Pass-Thru” (MS81: MQIPT) may be used in front of appliance queue
managers (as for software MQ) to provide DMZ tunnelling or proxy
– interested in customer feedback on integrating this kind of functionality in a
future version of the appliance

Connectivity
• The IBM MQ Appliance will support a number of protocols for message
transmission
• The first version of the appliance will support
– 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

High Availability
• IBM MQ Appliances can be deployed in HA pairs
– Primary instance of queue manager runs on one
– Secondary instance on the other for HA protection
• Primary and secondary work together
– Operations on primary automatically replicated to secondary
– 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
Primary Secondary

External Storage (statement of direction)
• In a future version of the appliance IBM intends to support fibre channel
connection to external storage, enabling additional capabilities:
1. External volume may be used to expand storage for SLAs with very long
outage tolerances
– e.g. consuming application offline for weekend maintenance
2. Use of an external volume for queue manager’s recovery logs and data
files
– Continues to support HA pair for local availability
– External volume can also be replicated for out-of-region recovery by
a remote appliance configured to use mirror
Primary
OOR standby
Secondary
[a]synchronous
replication

Performance and Capacity

The IBM MQ Appliance will be 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 latest firmware level (8.0.03),
– Includes scenario driven examples and M2000A/B comparisons.

Key differences compared to installable MQ
• “Hub” pattern; no applications deployed to the appliance
– Applications must connect as remote clients
• No user exits can be run on the appliance
– Our intention is to add configurable capabilities to support the needs of
many customers’ exits, reducing the need for exits
– If you currently customise MQ with exits we’d like to talk…
• A pair of appliances can be used for High Availability
– With no shared file system or shared disk
• Authentication and authorisation via on-board or central repository
• Command-line interface on the appliance is not a general-purpose shell
– Has familiar commands for things you need
– e.g. no runmqlsr, because MQ listeners run under QM control

Summary
• The MQ appliance is available now
• Two models, to suit different uses and performance requirements
• Existing MQ features with simple deployment and administration
– Including built-in HA support
– Without customisation via exits
• Expected uses:
– Messaging hub – consolidate messaging and separate applications
– Messaging outpost – easily deploy remote messaging server
– Messaging gateway – managed endpoint for inbound connectivity
– Messaging partner – confidently deploy remote connectivity

Ibm mq appliance slideshare

Recommended

More Related Content

What's hot (20)

Viewers also liked (20)

Similar to Ibm mq appliance slideshare (20)

Ibm mq appliance slideshare