Introduction to the MQ Appliance

Transcription

1 Introduction to the MQ Appliance Mark Taylor IBM Hursley Copyright IBM Corporation 2016

2 Overview

3 IBM MQ Appliance General Availability: March 13 th 2015 The scalability and security of IBM MQ 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 in the IBM MQ Appliance ü 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 2

4 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 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 3

5 Consolidate MQ infrastructure into Hub for lower TCO Objectives Reduce TCO Reduce footprint Standardise deployments Build 'hub' - concentrate expertise Challenges Mixture of platforms and versions Complex dependencies Migrations difficult lack of standardization Application downtime impacts other applications 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 Deploy to a remote premises Objectives Resilient connectivity to remote location Robust and secure Flexibility, minimal time to value at new sites Challenges Avoiding single points of failure Outside assistance needed lack of local skills and resources Benefits Standardization makes pre-canned rollout simpler Remote configuration and management High availability requires no additional systems or skills

7 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 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 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

8 Machine Types 2015 release was the M announcement of the M2001

9 Which MQ Appliance is right for you? IBM MQ Appliance M2001A (for Enterprise) High-end solution for enterprise consolidation use case Capable of handling large MQ workloads for persistent and non-persistent messaging Host multiple Queue Managers to act as a messaging hub A replacement for multiple separate MQ servers Built-in High Availability when paired to a 2 nd appliance and off-site disaster recovery to another Appliance Supports MQ AMS, and can be used to move MQ MFT files between MFT endpoints IBM MQ Appliance M2001B (Branch etc.) Lower-end solution for branch office or factory deployment Same software and hardware as the Enterprise appliance, but processor usage limited Designed to meet lower messaging throughput requirements Supports all features of M2001A, including High Availability, Disaster Recovery and MQ AMS Trade-up part available from M2001B capacity to M2001A capacity Easily deploy and maintain MQ messaging in minutes!

10 Key Differences with Appliance Form-factor Apps Tuning MQ / Middleware OS IBM MQ Appliance 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 Hardware IBM MQ V8 on Custom Server 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

11 Availability options in the MQ Appliance Designed to be configured in seconds with no external dependencies QM1 QM2 QM3 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) Fully synchronous replication (HA) or asynchronous (DR) QM1 QM2 QM3

12 The Complete Messaging and Integration Solution IBM MQ Appliance M2001 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

13 MQ Appliance key capabilities

14 Lets really simplify it An MQ Appliance is a box where you create and run queue managers Queue manager 1 Queue manager 2 Queue manager 3 Application Application Application Application Queue manager 4 Application

15 Physical configuration 2x Management 1GB Ethernet (also IPMI) 2x 1GB Ethernet: HA or general purpose 10 GB Ethernet (SPF+): HA or general purpose Display (includes capacity and version information) HBA (unused) Serial / KVM connection N.B. REQUIRED for initial setup General purpose 1GB Ethernet (MQ Application traffic) General purpose 10GB Ethernet (SPF+) (MQ Application traffic)

16 Hardware Update ( M2001 ) Initial results show up to around 3x performance improvement for some (heavily persistent) messaging workloads Combined HA and DR consumes both currently provided 10GB interfaces This will be addressed by replacing the 2 port NMC module with a revised adapter giving 4x10GB ports 1.2 TB HDDs replaced by 3.2 TB SSDs Same RAID 1 configuration Minimum of two spare ports available for MQ/application use which may also be aggregated for availability and bandwidth Notes: 1. A and B capacity (CPU) options will remain as today 2. Customers with M2000 models contact IBM sales representative for migration options.

17 M2000(mqcli)# crtm qm te s t Please wait while 64 GB file system is initialized for queue manager 'test'. IB M M Q A p p lia n c e q u e u e m a n a g e r c re a te d. The queue m anager is associated w ith installation 'MQAppliance'. Creating or replacing default objects for queue manager 'test'. Default objects statistics : 83 created. 0 replaced. 0 failed. Completing setup. Setup completed. M2000(mqcli)# strm qm te s t IB M M Q A p p lia n c e q u e u e m a n a g e r 'te s t' s ta rtin g. The queue m anager is associated w ith installation 'MQAppliance'. 5 log records accessed on queue manager 'test' during the log replay phase. Log replay for queue manager 'test' complete. Transaction m anager state recovered for queue m anager 'test'. IB M M Q A p p lia n c e q u e u e m a n a g e r 'te s t' s ta rte d u s in g V M2000(mqcli)# ru n m q sc te s t H72 (C) Copyright IBM Corp. 1994, Starting MQSC for queue manager test. M2000(mqcli)# crtmqm test Please wait while 64 GB file system is initialized for queue manager 'test'. IB M M Q A p p lia n c e q u e u e m a n a g e r c re a te d. The queue m anager is associated w ith installation 'M QAppliance'. Creating or replacing default objects for queue manager 'test'. Default objects statistics : 83 created. 0 replaced. 0 failed. Completing setup. Setup completed. M2000(mqcli)# strmqm test IB M M Q A p p lia n c e q u e u e m a n a g e r 'te s t' s ta rtin g. The queue m anager is associated w ith installation 'M QAppliance'. 5 log records accessed on queue manager 'test' during the log replay phase. Log replay for queue manager 'test' complete. Transaction m anager state recovered for queue m anager 'test'. IB M M Q A p p lia n c e q u e u e m a n a g e r 'te s t' s ta rte d u s in g V M2000(mqcli)# runmqsc test H72 (C) Copyright IBM Corp. 1994, Starting MQSC for queue manager test. Administration Serial/SSH New for Appliance HTTP MQ Channel (PCF) New for Version 8!

18 Web UI and MQ Console

19 M2000(mqcli)# crtmqm test Please wait while 64 GB file system is initialized for queue manager 'test'. IB M M Q A p p lia n c e q u e u e m a n a g e r c re a te d. The queue m anager is associated w ith installation 'M QAppliance'. Creating or replacing default objects for queue manager 'test'. Default objects M2000(mqcli)# statistics : 83 created. crtmqm test 0 replaced. 0 failed. Completing setup. Please wait while 64 GB file system is initialized for queue manager 'test'. Setup completed. IB M M Q A p p lia n c e q u e u e m a n a g e r c re a te d. The queue m anager is associated w ith installation 'M QAppliance'. M2000(mqcli)# Creating strmqm or test replacing default objects for queue manager 'test'. IB M M Q A p p lia Default n c e q uobjects e u e mm2000(mqcli)# astatistics n a g e r 'te: s83 t' s ta created. crtm rtinqm g. te0 sreplaced. t 0 failed. The queue m anager Completing is associated setup. Please wait w ith while installation 64 GB 'Mfile QAppliance'. system is initialized for queue manager 'test'. 5 log records Setup accessed completed. on IB queue M M Q manager A p p lia n c'test' e q u during e e m athe n a glog e r creplay a te d phase.. Log replay for queue manager The 'test' queue complete. m anager is associated w ith installation 'MQAppliance'. Transaction mm2000(mqcli)# anager state Creating recovered strmqm or test for replacing queue mdefault anager objects 'test'. for queue manager 'test'. IB M M Q A p p lia IBnM c e MqQ u ea up e p lia mdefault an nc ae gqe uobjects r e'te u e s t' msa statistics nrte a gd e r u'te s in: sg 83 t' sv ta created. 8 rtin.0 g replaced. 0 failed. The queue m anager Completing is associated setup. w ith installation 'M QAppliance'. M2000(mqcli)# 5 log runmqsc records test Setup accessed completed. on queue manager 'test' during the log replay phase H72 (C) Log Copyright replay for IBM queue Corp. manager 1994, 'test' complete. Starting MQSC Transaction for queue manager M2000(mqcli)# test. state recovered strm qm tefor s t queue m anager 'test'. IB M M Q A p p lia IBnM c e MqQ u ea up e p lia m an nc ae gqe ur e'te u e s t' msatan rte a gd e r u'te s ins g t' sv ta8 rtin.0 g.4.. The queue m anager is associated w ith installation 'MQAppliance'. M2000(mqcli)# 5 log runmqsc records test accessed on queue manager 'test' during the log replay phase H72 (C) Log Copyright replay for IBM queue Corp. manager 1994, 'test' complete. Starting MQSC Transaction for queue manager test. state recovered for queue m anager 'test'. IB M M Q A p p lia n c e q u e u e m a n a g e r 'te s t' s ta rte d u s in g V M2000(mqcli)# ru n m q sc te s t H72 (C) Copyright IBM Corp. 1994, Starting MQSC for queue manager test. Secure administration Administrators are always defined locally on the appliance and can connect via SSH or WebUI to administer all aspects of the system Administrative user repository Messaging Users may be defined locally or in LDAP repository (choice per QM), and remote applications always connect with these credentials. Messaging user repository

20 M2000(mqcli)# crtm qm te s t Please wait while 64 GB file system is initialized for queue manager 'test'. IB M M Q A p p lia n c e q u e u e m a n a g e r c re a te d. The queue m anager is associated w ith installation 'MQAppliance'. Creating or replacing default objects for queue manager 'test'. Default objects statistics : 83 created. 0 replaced. 0 failed. Completing setup. Setup completed. M2000(mqcli)# strm qm te s t IB M M Q A p p lia n c e q u e u e m a n a g e r 'te s t' s ta rtin g. The queue m anager is associated w ith installation 'MQAppliance'. 5 log records accessed on queue manager 'test' during the log replay phase. Log replay for queue manager 'test' complete. Transaction m anager state recovered for queue m anager 'test'. IB M M Q A p p lia n c e q u e u e m a n a g e r 'te s t' s ta rte d u s in g V M2000(mqcli)# ru n m q sc te s t H72 (C) Copyright IBM Corp. 1994, Starting MQSC for queue manager test. Secure messaging New certificate management commands Application TLS (SSL) on channels End to end and at-rest encryption using AMS built in and included as standard Application Traditional MQ (software) Queue Manager

21 Secure updates 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. Mq-appliance scrypt3 Copy to appliance update, and reboot. All driver, system and MQ updates are applied as a single operation

22 Using MQ MFT and the MQ Appliance The MQ Appliance can be the Queue Manager to provide both regular MQ Queue Manager capabilities No other MQ server deployment needed Applications exchanging file data Agent Agent Agent 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 Commands Coordination Queue Manager Log database or file

23 Connectivity The 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

24 Connect MQ Light apps directly to MQ Appliance Messaging that application developers will love to use, helping them make responsive applications that scale easily Very simple messaging API Support in variety of languages and runtimes; Node.js, Python, Java, etc MQ support through a new channel type AMQP now ( ) also available on the Appliance. Similar in style to an MQTT channel QMgr.NET QMgr MQTT JMS Supports the subset of the AMQP 1.0 Oasis specification required for MQ Light applications MQ Light applications interoperable with all other MQ applications QMgr C COBOL All share the same topic space

25 HA Overview QM1 QM2 QM3 Fully synchronous replication Key design points: - No (persistent) message loss - No external dependencies - Transparent to application QM1 QM2 QM3

26 HA When things go wrong QM1 QM2 QM3 QM1 QM2 QM3

27 Disaster Recovery New function in 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. DR Replication Asynchronous (10 Gb Ethernet)

28 Disaster Recovery for HA groups HA Replication Synchronous (10Gb Ethernet) introduced DR but with one major restriction appliances and the queue managers they host can participate either in HA Groups, or DR but not both at the same time will improve upon this - by using two network links one HA partner (per appliance) and one DR recovery site (per queue manager) may be configured DR Replication Asynchronous (10 Gb Ethernet) The DR appliance is asynchronously updated from whichever HA node is active Note that this does still not (yet) allow symmetrical HA pair to HA pair replication

29 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

30 Monitoring System Resources Chart widgets and new API Display appliance resource use Platform-wide or queue manager CPU, Disk, memory, etc To create, click hotspot Configure the widget Select: Resource class/type/element Queue manager(s) to monitor Choose Resource class CPU Data stores API Usage stats

31 Monitoring applications 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? 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.

32 Performance and capacity reports Two appliance models suit a range of performance and capacity needs Appliance is dedicated to running messaging server workload With no other workload, performance should be predictable Capacity planning should be easier Firmware comes pre-tuned for maximum messaging performance Placement of workload, resource utilisation, etc. Performance reports MPA1 and MPA2 available MPA1 includes scenario driven examples MPA2 covers HA and DR configurations Updated for M2001A/B

33 Find out more

34 Online Dedicated appliance KnowledgeCenter particularly covers differences from software MQ installations GitHub community with example remote configuration scripts RedBook, particularly useful for first time setup and hardware configuration acts/sg html