Post on 22-Jan-2017
Anthony Beardsmore, IBM Systems GroupIBM MQ Appliance Architect
Introduction to the MQ ApplianceAnd what’s new in 2016
2 © 2015 IBM Corporation
PleaseNote
IBM’sstatementsregardingitsplans,directions,andintentaresubjecttochangeorwithdrawalwithoutnoticeatIBM’ssolediscretion.Informationregardingpotentialfutureproductsisintendedtooutlineourgeneralproductdirectionanditshouldnotbereliedoninmakingapurchasingdecision.
Theinformationmentionedregardingpotentialfutureproductsisnotacommitment,promise,orlegalobligationtodeliveranymaterial,codeorfunctionality.Informationaboutpotentialfutureproductsmaynotbeincorporatedintoanycontract.Thedevelopment,release,andtimingofanyfuturefeaturesorfunctionalitydescribedforourproductsremainsatoursolediscretion.
PerformanceisbasedonmeasurementsandprojectionsusingstandardIBMbenchmarksinacontrolledenvironment.Theactualthroughputorperformancethatanyuserwillexperiencewillvarydependinguponmanyfactors,includingconsiderationssuchastheamountofmultiprogrammingintheuser’sjobstream,theI/Oconfiguration,thestorageconfiguration,andtheworkloadprocessed.Therefore,noassurancecanbegiventhatanindividualuserwillachieveresultssimilartothosestatedhere.
3 © 2015 IBM Corporation© 2015 IBM Corporation
IntroducingtheIBMMQAppliance,newin2015
ThescalabilityandsecurityofIBMMQV8IntegratesseamlesslyintoMQnetworksandclustersFamiliaradministrationmodelforadministratorswithMQskills
Theconvenience,fasttime-to-valueandlowtotalcostofownershipofanappliance
Idealforuseasamessaginghubrunningqueuemanagersaccessedbyclients,ortoextendMQconnectivitytoaremotelocation
FamiliarfeelforexistingMQusers– applicationinterfaces,administration,networking/clustering,security….
Plusnewappliancespecificfeatures– e.g.builtinhighavailability
4 © 2015 IBM Corporation
Introduction/OverviewNotes
Versions/Levels: The appliance firmware embeds MQ V8 – so all the industry leading messaging features you would expect, including full support for latest additions – new pub/sub features, user and channel security updates, etc.Dates: GA March 13 2015, and we have released the first and third fixpackalready (skipped FixPack 2 align appliance and MQ version – at 8.0.0.3), with more expected this year.
5 © 2015 IBM Corporation
Or,toreallysimplifyit…
• Aboxwhereyoucreateandrunqueuemanagers…
Queue manager 1 Queue manager 2 Queue manager 3
ApplicationApplication
Application
ApplicationApplication
Queue manager 4
6 © 2015 IBM Corporation
Notes
Some people might not ‘get’ an appliance. This slide says it all!
The appliance is a dedicated system, which you install in your data center, to do one job (messaging) and do it well.
No user code ever runs on the appliance, solely the MQ firmware itself.
Applications always connect as clients over traditional MQ channels, as can other queue managers (appliance or otherwise).
You can configure ‘as many queue managers as you wish’ on an appliance (in practice we expect to see only low double figures at most, for manageability and best performance).
7 © 2015 IBM Corporation
IBMMQApplianceoffers:Optimizedsolutions tomeettheneedsoftheseusecases
DifferentiationcomparedtoMQsoftwaredeploymentapproaches
2pricepointstomeetdifferentdeployment-basedbusinessneeds
Whatdoyouwanttodo?
Consolidate my MQ infrastructure into an “MQ Hub”
for lower TCO
Deploy to a business
partner, e.g. Dealer, Broker
Deploy to remote premises, e.g.
Branch, Factory, Warehouse
8 © 2015 IBM Corporation
Notes
• “Hub”messaging(mostapplicationsclients,largecentralisedMQservers)isbecomeanextremelycommonmodel,andappliancedesignedtofitwellintothisusecase– supportingallthetraditionalMQtoolingandinterfaceswhileaddingusefulfeaturessuchasselfcontainedHA
• NOTalwaysappropriate– someapplicationsreallydoneedtraditionallocalqueuemanageronthesamesystem,fortheavailability,storeandforwardcharacteristicswhichthatprovides.
• Otherusecasesfortheappliance(remotedeployments,businesspartners,gateways)generallyhavecommonthemesofwishingtodeployMQinenvironmentswithfewerskillsorresources(hardware,networkstorage,OSexpertise)whilemaintainingstandardscomplianceandsecurity,availabilityetc.
9 © 2015 IBM Corporation
Challenges
Mixture of platforms and versions
Complex dependencies
Migrations difficult – lack of standardization
Application downtime impacts other applications
Consolidate my MQ infrastructure into an “MQ Hub” for lower TCO
Objectives
Reduce TCO
Reduce footprint
Standardise deployments
Build 'hub' - concentrate expertise
Benefits
Easy to deploySimplified maintenanceFamiliar administrationSeparates applications from InfrastructureSupports existing MQ definitions, concepts and security modelHA avoiding external dependencies
10 © 2015 IBM Corporation
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
11 © 2015 IBM Corporation
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 deploySimplified maintenance
Ability to preconfigure a very standard system both helps ensure standards applied and speed deployment
HA avoiding external dependencies
12 © 2015 IBM Corporation
Notes:WhyanAppliance?
• FixedhardwarespecificationallowsIBMtosimplifyandtunethefirmware– Havingfewervariablesmakesiteasiertodeployandmanage– Lessperformancetuningshouldbeneeded
• Standardisationacceleratesdeployment– Repeatableandfast,lessconfiguration/tuningrequired– Post-deploymentresourcedefinitionorlockdownbeforedeployment
• “Hub”patternseparatesmessagingfromapplications/middleware– Organisationalindependencefromapplicationteams– Improvedavailability,duetoreductionofdowntime– Predictableperformance,simplercapacityplanning
• Simplifiedownership– Self-contained:avoidsdependenciesonotherresources/teams– Licensing:Simplerthancalculatinglicensingcosts(e.g.byPVU)– Security:Easiertoassessforsecuritycomplianceaudit
13 © 2015 IBM Corporation
IBMMQAppliancecapabilities• Administration
• Security
• Connectivity
• HighAvailability
• ExternalStorage(statementofdirection)
• PerformanceandCapacity
• KeydifferencesbetweenMQApplianceandinstallableMQ
14 © 2015 IBM Corporation
Administration
M 2000( mqcl i ) # crt mqm t estPl ease w ai t w hi l e 64 G B fi le syst em i s ini ti al ized f or queue manager 't est '.I BM M Q Appl i ance queue manager creat ed.The queue manager i s associ at ed w i t h inst al l ati on 'M QAppl i ance'.Creat i ng or repl aci ng def aul t obj ect s f or queue manager 't est '.Def aul t obj ect s st at i st i cs : 83 created. 0 repl aced. 0 f ai led.Compl et i ng set up.Set up compl et ed.
M 2000( mqcl i ) # st rmqm t estI BM M Q Appl i ance queue manager 't est ' st art i ng.The queue manager i s associ at ed w i t h inst al l ati on 'M QAppl i ance'.5 l og records accessed on queue manager 't est ' dur i ng t he l og repl ay phase.Log repl ay f or queue manager 't est ' compl et e.Transact i on manager st at e recovered f or queue manager 't est '.I BM M Q Appl i ance queue manager 't est ' st art ed usi ng V8. 0. 0. 4.
M 2000( mqcl i ) # runmqsc t est5724- H72 ( C) Copyri ght I BM Corp. 1994, 2014.
St art i ng M Q SC f or queue manager t est .
Serial/SSHHTTP
M 2000( mqcl i ) # crt mqm t estPl ease w ai t w hi l e 64 G B fi le syst em i s ini ti al ized f or queue manager 't est '.I BM M Q Appl i ance queue manager creat ed.The queue manager i s associ at ed w i t h inst al l ati on 'M QAppl i ance'.Creat i ng or repl aci ng def aul t obj ect s f or queue manager 't est '.Def aul t obj ect s st at i st i cs : 83 created. 0 repl aced. 0 f ai led.Compl et i ng set up.Set up compl et ed.
M 2000( mqcl i ) # st rmqm t estI BM M Q Appl i ance queue manager 't est ' st art i ng.The queue manager i s associ at ed w i t h inst al l ati on 'M QAppl i ance'.5 l og records accessed on queue manager 't est ' dur i ng t he l og repl ay phase.Log repl ay f or queue manager 't est ' compl et e.Transact i on manager st at e recovered f or queue manager 't est '.I BM M Q Appl i ance queue manager 't est ' st art ed usi ng V8. 0. 0. 4.
M 2000( mqcl i ) # runmqsc t est5724- H72 ( C) Copyri ght I BM Corp. 1994, 2014.
St art i ng M Q SC f or queue manager t est .
MQ Channel (PCF)
New for Version 8!
New for Appliance
15 © 2015 IBM Corporation
Administration
• Command-lineInterface– ApplianceCLIsupportsappliance-specificcommandssuchasconfiguring
networkinterfaces,importingcertificates,…– ApplianceCLIalsooffersafamiliarsubsetofMQcontrolcommands– YoucanalsouseMQSCscripts
• WebUI– Browser-basedUIforadministeringtheappliance– Avoidsmaintenanceofrichclientinstallations– Veryconvenientforproofs-of-conceptandapplicationdeveloperuse
• MQExplorer– Essentialforexistingadministrators
• PCF– SupportsremoteadministrationusingalloftheexistingMQtools
16 © 2015 IBM Corporation
CommandLineInterface
login: adminPassword: *******
Welcome to IBM MQ Appliance M2000B console configuration.Copyright IBM Corporation 1999-2015
Version: MQ00.8.0.0.3 build mq-rel.265326 on Aug 12, 2015 11:10:38 AMSerial number: 7800537
M2000# mqcliM2000(mqcli)# dspmqverName: IBM MQ ApplianceVersion: 8.0.0.3Level: p800-L150812.2BuildType: IKAP - (Production)Platform: IBM MQ ApplianceMaxCmdLevel: 802
17 © 2015 IBM Corporation
Notes:
• KeypointisthatmajorityofcommandswilllookveryfamiliartoMQadministrators.
• Followingslideshowsoneslightdifference– preallocationofthe(tunable)64GBstorageforthequeuemanager,makingiteasiertosupportmanyqueuemanagersonasystemwithouttheminterferingwitheachother.
18 © 2015 IBM Corporation
CommandLineInterfaceM2000(mqcli)# crtmqm testPlease wait while 64 GB file system is initialized for queue manager 'test'.IBM MQ Appliance queue manager created.The queue manager is associated with 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)# strmqm testIBM MQ Appliance queue manager 'test' starting.The queue manager is associated with installation 'MQAppliance'.5 log records accessed on queue manager 'test' during the log replay phase.Log replay for queue manager 'test' complete.Transaction manager state recovered for queue manager 'test'.IBM MQ Appliance queue manager 'test' started using V8.0.0.4.
M2000(mqcli)# runmqsc test5724-H72 (C) Copyright IBM Corp. 1994, 2014.Starting MQSC for queue manager test.
19 © 2015 IBM Corporation
CLI:Notes
Access: Accessible over SSH or local serial connection. SSH can be limited to particular interface (IP address) if desiredFunctionality:NOT a traditional OS ‘shell’. All function of appliance is available through CLI (the only exception is initial license acceptance). Most system configuration aspects will be familiar to DataPower users, as inherited from the underlying platform.MQ configuration is achieved using new ‘sub shell’ for MQ specific tasks (sometimes referred to as the ‘mqcli’.) Within this environment, most traditional MQ commands (e.g. crtmqm, strmqm, runmqsc… ) function exactly as they would on Windows/Unix/Linux platforms.Some tasks can currently ONLY be achieved in the CLI, where support not yet available in MQ Console (Web UI)Help is available in all areas of the CLI with ‘help’ command.
20 © 2015 IBM Corporation
WebUIandMQConsole
21 © 2015 IBM Corporation
WebUI
• Onlyontheappliance(atpresent),providesbothMQand‘system’administrationtools
• Profilebased(configurationsavedperuser)– canimportandexport
• Createyourowndashboardlayoutsforthethingsyouneedtosee• E.g.developermighthaveparticularsetofqueuemanagers/queuesthey
workwith,sysadminmighthaveparticularsetofmonitoringcharts
• Newchartsfeaturesgiverichsetofperformanceandresourcemonitoringdata– alsoavailableprogrammatically(sampleincludedinMQclientsupportpack)
22 © 2015 IBM Corporation
Security– UsersM 2000( mqcl i ) # crt mqm t estPl ease w ai t w hi l e 64 G B fi le syst em i s ini ti al ized f or queue manager 't est '.I BM M Q Appl i ance queue manager creat ed.The queue manager i s associ at ed w i t h inst al l ati on 'M QAppl i ance'.Creat i ng or repl aci ng def aul t obj ect s f or queue manager 't est '.Def aul t obj ect s st at i st i cs : 83 created. 0 repl aced. 0 f ai led.Compl et i ng set up.Set up compl et ed.
M 2000( mqcl i ) # st rmqm t estI BM M Q Appl i ance queue manager 't est ' st art i ng.The queue manager i s associ at ed w i t h inst al l ati on 'M QAppl i ance'.5 l og records accessed on queue manager 't est ' dur i ng t he l og repl ay phase.Log repl ay f or queue manager 't est ' compl et e.Transact i on manager st at e recovered f or queue manager 't est '.I BM M Q Appl i ance queue manager 't est ' st art ed usi ng V8. 0. 0. 4.
M 2000( mqcl i ) # runmqsc t est5724- H72 ( C) Copyri ght I BM Corp. 1994, 2014.St art i ng M Q SC f or queue manager t est .
M 2000( mqcl i ) # crt mqm t estPl ease w ai t w hi l e 64 G B fi le syst em i s ini ti al ized f or queue manager 't est '.I BM M Q Appl i ance queue manager creat ed.The queue manager i s associ at ed w i t h inst al l ati on 'M QAppl i ance'.Creat i ng or repl aci ng def aul t obj ect s f or queue manager 't est '.Def aul t obj ect s st at i st i cs : 83 created. 0 repl aced. 0 f ai led.Compl et i ng set up.Set up compl et ed.
M 2000( mqcl i ) # st rmqm t estI BM M Q Appl i ance queue manager 't est ' st art i ng.The queue manager i s associ at ed w i t h inst al l ati on 'M QAppl i ance'.5 l og records accessed on queue manager 't est ' dur i ng t he l og repl ay phase.Log repl ay f or queue manager 't est ' compl et e.Transact i on manager st at e recovered f or queue manager 't est '.I BM M Q Appl i ance queue manager 't est ' st art ed usi ng V8. 0. 0. 4.
M 2000( mqcl i ) # runmqsc t est5724- H72 ( C) Copyri ght I BM Corp. 1994, 2014.St art i ng M Q SC f or queue manager t est .
M 2000( mqcl i ) # crt mqm t estPl ease w ai t w hi l e 64 G B fi le syst em i s ini ti al ized f or queue manager 't est '.I BM M Q Appl i ance queue manager creat ed.The queue manager i s associ at ed w i t h inst al l ati on 'M QAppl i ance'.Creat i ng or repl aci ng def aul t obj ect s f or queue manager 't est '.Def aul t obj ect s st at i st i cs : 83 created. 0 repl aced. 0 f ai led.Compl et i ng set up.Set up compl et ed.
M 2000( mqcl i ) # st rmqm t estI BM M Q Appl i ance queue manager 't est ' st art i ng.The queue manager i s associ at ed w i t h inst al l ati on 'M QAppl i ance'.5 l og records accessed on queue manager 't est ' dur i ng t he l og repl ay phase.Log repl ay f or queue manager 't est ' compl et e.Transact i on manager st at e recovered f or queue manager 't est '.I BM M Q Appl i ance queue manager 't est ' st art ed usi ng V8. 0. 0. 4.
M 2000( mqcl i ) # runmqsc t est5724- H72 ( C) Copyri ght I BM Corp. 1994, 2014.St art i ng M Q SC f or queue manager t est .
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.
23 © 2015 IBM Corporation
Notes:Security– UsersandObjects
• AnapplianceadministratorcanbeauthorisedtoperformMQadministration– Applianceandmessagingadministratorsarecompletelyseparatefrom
messaging(applicationconnection)users
• Theappliancesupportsscalablesecurityadministration(assoftwareMQ8.0.0.2onwardsdoes)– Forasmallnumberofmessagingusers,youcandefinethemlocally– Forlargercommunities,youcanuseanoff-boardrepository.Expectthisto
becomeapopular/commonchoiceforsimplermanagement• UsingexternalLDAPrepository• AuthorizationcheckscanincludegroupmembershipsfromLDAP• Messaginguseridsdon’tneedtobedefinedineachserver/appliance
• IngeneralOAMfunctionalityisasforotherdistributedMQplatforms.• Notethatbydefaultontheappliance,authoritiesareappliedtotheUSER
andnottheGROUP.
24 © 2015 IBM Corporation
Security– Messagesandconnections
Traditional MQ (software) Queue Manager
Application
Application
M 2000( mqcl i ) # crt mqm t estPl ease w ai t w hi l e 64 G B fi le syst em i s ini ti al ized f or queue manager 't est '.I BM M Q Appl i ance queue manager creat ed.The queue manager i s associ at ed w i t h inst al l ati on 'M QAppl i ance'.Creat i ng or repl aci ng def aul t obj ect s f or queue manager 't est '.Def aul t obj ect s st at i st i cs : 83 created. 0 repl aced. 0 f ai led.Compl et i ng set up.Set up compl et ed.
M 2000( mqcl i ) # st rmqm t estI BM M Q Appl i ance queue manager 't est ' st art i ng.The queue manager i s associ at ed w i t h inst al l ati on 'M QAppl i ance'.5 l og records accessed on queue manager 't est ' dur i ng t he l og repl ay phase.Log repl ay f or queue manager 't est ' compl et e.Transact i on manager st at e recovered f or queue manager 't est '.I BM M Q Appl i ance queue manager 't est ' st art ed usi ng V8. 0. 0. 4.
M 2000( mqcl i ) # runmqsc t est5724- H72 ( C) Copyri ght I BM Corp. 1994, 2014.St art i ng M Q SC f or queue manager t est .
New certificate management commands
TLS (SSL) on channels
End to end and at-rest encryption using AMS built in and included as standard
25 © 2015 IBM Corporation
Notes:Security– Messagesandconnections
• TheappliancesupportssecureconnectivityoverTLS(/SSL)– Certificatescanbeimportedtotheappliance
– FullAMSentitlementisincludedinthepurchaseofeithertheM2000AorM2000Bappliance.– Thoughcurrentlylimitedtoclientsideencryption(noserverside
interceptor)
• “MQInternetPass-Thru”(MS81:MQIPT)maybeusedinfrontofappliancequeuemanagers(asforsoftwareMQ)toprovideDMZtunnellingorproxy– interestedincustomerfeedbackonintegratingthiskindoffunctionalityin
afutureversionoftheappliance
26 © 2015 IBM Corporation
Connectivity
• TheIBMMQAppliancesupportsanumberofprotocolsformessagetransmission
• Asyouwouldexpect,alltheusualconnectivitytoMQinfrastructure:
• MQclientprotocol– forconnectivityfromapplications
• Clientlibrariesavailableintheusualplaces,notshipped withtheappliance
• MQserverprotocol– forconnectivitywithotherqueuemanagers• Thiswillsupport sender-receiverchannelsandserver-requesterchannels
• MQClustering– forsimplifiedadministrationandworkloadmanagement• AppliancequeuemanagerscanjoinexistingclustersorhostFullRepositories
• Subjecttocustomerinterestwemayaddfurtherprotocolssuchas– MQTT– forinternetofthingsandmobile/webmessaging
27 © 2015 IBM Corporation
HighAvailability- Concept
QM1 QM2 QM3
QM1 QM2 QM3
Fully synchronousreplication
• No persistent data loss on failure• 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)
28 © 2015 IBM Corporation
HighAvailability– Failurescenario
QM1 QM2 QM3
QM1 QM2 QM3
Fully synchronousreplication
• Clients (and other Queue managers) reconnect to alternative IP
• Usually transparent to application
29 © 2015 IBM Corporation
HighAvailability– Physicallayout
Replication Connection(10 Gb Ethernet)Heartbeat Connections
(1 Gb Ethernet)
30 © 2015 IBM Corporation
HA- Notes
• Primaryinstanceofqueuemanagerrunsononeappliance• SecondaryinstanceontheotherforHAprotection
• Primaryandsecondaryworktogether• Operationsonprimaryautomaticallyreplicatedtosecondary• Allpersistentmessagesloggedatbothnodesbeforereturnto
application
• Appliancesmonitoroneanotherandperformlocalrestart/failover
• EasiertosetupthanotherHAsolutions(nosharedfilesystem/shareddisks)
• Supportsmanualfailover,e.g.forrollingupgrades
• ReplicationissynchronousoverEthernet,for100%fidelity• Routablebutnotintendedforlongdistances• Ensureallelementsofroutingredundantifnotusingdirectcables
31 © 2015 IBM Corporation
PerformanceandCapacity
l TheIBMMQApplianceisavailableintwomodels,tosuitarangeofperformanceandcapacityrequirements– They’renotsoldonaPVUbasis– butapproximately420&1400PVU– ’B’upgradecanbepurchasedto‘B+’(equivalenttoA)
• Applianceisdedicatedtorunningmessagingserverworkload– Nootherworkload(applicationsormiddleware)– Performanceshouldbepredictable– Capacityplanningshouldbeeasier
• Firmwarecomespre-tunedformaximummessagingperformance– Placementofworkload,resourceutilisation,etc.
• Performancereports– MPA1– generalperformance,modelA/Bcomparison– MPA2– highavailabilityandDR,includingscalingtohighlatencies
32 © 2015 IBM Corporation
Updatingandmaintaining
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
33 © 2015 IBM Corporation
What’sNew
34 © 2015 IBM Corporation
DisasterRecovery– 8.0.0.4
DR ReplicationAsynchronous(10 Gb Ethernet)
• 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.
35 © 2015 IBM Corporation
DisasterRecovery– Flexibletopologies
Productionappliance
Off-siteDRappliance
Asynchronousreplication
FlexibleConfig• AswithHA,configurationisperqueuemanager– thoughwithDRthereisno
conceptofa‘group’.• EachQMindependentlyconfiguresreplicationtoaparticularappliance.• E.g.couldconfiguresingle‘DR’sitecoveringliveappliancesatmultiplesites
MixedTest/DRappliance
Productionappliance
36 © 2015 IBM Corporation
FileManagement(UI)– newin8.0.0.4
36
37 © 2015 IBM Corporation
DisasterRecoveryforHAgroups– 8.0.0.5
DR ReplicationAsynchronous(10 Gb Ethernet)
8.0.0.4 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
The DR appliance is asynchronously updated from whichever HA node is active
HA Replication
Synchronous(10Gb Ethernet)
8.0.0.5 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
Note that this does still not (yet) allow symmetrical HA pair to HA pair replication
38 © 2015 IBM Corporation
ConnectMQLightapplicationsdirectlytoMQAppliance
• VerysimplemessagingAPI• Support invarietyof languagesandruntimes;
Node.js,Python, Java,etc…
• MQsupportthroughanewchanneltypeAMQPnow(8.0.0.5)alsoavailableontheAppliance.• SimilarinstyletoanMQTTchannel• Supports thesubsetoftheAMQP1.0Oasis
specificationrequired forMQLightapplications
• MQLightapplicationsinteroperablewithallotherMQapplications• Allsharethesametopicspace
C
JMS
MQTT.NET
COBOL
QMgr
QMgr
QMgr
38
Messaging that application developers will love to use, helping them make responsive applications that scale easily
8.0.0.5
39 © 2015 IBM Corporation
• 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
Minimum of two spare ports available for MQ/application use – which may also be aggregated for availability and bandwidth
• Current 1.2 TB HDDs replaced by 3.2 TB SSDs
• Same RAID 1 configuration
HardwareUpdate(‘M2001’)
Notes:1. A and B capacity (CPU) options will remain as today2. Customers with M2000 models – contact IBM sales representative
for migration options.
Initial results show up to around 3x performance improvement for some (heavily persistent) messaging workloads
40 © 2015 IBM Corporation
Hardwarerefresh- Notes
• TheM2001completelyreplacesM2000– whichwillnolongerbeavailabletomarketfromM2001release.
• M2001willshipwiththelatest(8.0.0.5)firmware,alsoavailabletodownloadforexistingM2000customers
• M2000ownersmaychoosetocontinuewithexistinghardware(whichwillremainsupportedwithfirmwareupdates),butupgrade/migrationoptionsareavailable
• Newperformancereportswillbeavailableshortlydemonstratingthepersistentmessagingprofileofthenewhardware.
41 © 2015 IBM Corporation
Onthehorizon
42 © 2015 IBM Corporation
ExternalStorage(statementofdirection)• Fromtheannounceletter:“InafutureversionoftheapplianceIBM
intendstosupportfibrechannelconnectiontoexternalstorage,enablingadditionalcapabilities…”
SAN
43 © 2015 IBM Corporation
ExternalStorage(statementofdirection)• Fromtheannounceletter:“InafutureversionoftheapplianceIBM
intendstosupportfibrechannelconnectiontoexternalstorage,enablingadditionalcapabilities…”
SAN
SAN
44 © 2015 IBM Corporation
Update/Lifecylequestions:
Lockeddownsecureupdatemodeland‘oneshot’upgradecommand,isoneofthemostattractivefeaturesoftheappliance.
Basicsoflifecycle:Applianceisonatraditional5:3supportcycleMajorhardwarerefreshesarelikelytofollowDataPowermodel
(traditionallyapproximately3year)Firmwareupdates(fixpacks)publishedthroughFixCentral.
SpecialfactorsTakinga‘continuousdelivery’modelatleastforearlyfixpacks,expect
regularupdatesincludingnewfunction(seestatementsofdirectionfollowing)
Supportonlyprovidedatlatestfixpack – aspartof‘standardization’ofappliance.Shouldbelesschallengingpropositiononappliancethanelsewhereasnolocalapplicationcode,exitsetc.
45 © 2015 IBM Corporation
§ PrebuiltforHubpattern– noAppsondevice§ Noadditionalsoftwareinstallation
§ NouserExitsinMQ§ Monitoringagentsmustberemote
§ HighAvailabilityout-of-the-box§ Pre-tuned§ SingleFirmwareupdateforwholeappliance
§ Firmwareupdateinc.applianceandMQFixpack
§ Canberolledbackasansingle unit
IBMMQAppliance IBMMQV8onCustomServer
Key Differences with Appliance Form-factor
45
§ DIYHubor Genericserver– Apps+Middleware§ Installanysoftware
§ Build&maintainyourowncustomextensions§ Addlocalmonitoringagents
§ NeedsHAClusterSWorNetworkStorageforHA§ Customtuningforeachlayer(OS/Middleware)§ Discretemaintenanceforeachlayer
§ MQFixpacks
§ OSmaintenance,securitypatchesetc.
App
Tuning
MQ / Middleware
OS
Hardware
46 © 2015 IBM Corporation
Notes:KeydifferencescomparedtoinstallableMQ• “Hub”pattern;noapplicationsdeployedtotheappliance– Applicationsmustconnectasremoteclients– Shouldnotusuallyneedapplicationcodechanges(build/configonly)– DoesrequireconsiderationofQOSthisprovides
• Nouserexitscanberunontheappliance– Manyexitsalreadymetwithbuiltinfunction– e.g.CHLAUTH,
CONNAUTH– Appliancespecificfeaturesaddressotherneeds– e.g.Subscriptionbased
activitytrace,monitoring– IfyoucurrentlycustomiseMQwithexitswe’dliketotalk…
• ApairofappliancescanbeusedforHighAvailability– Withnosharedfilesystemorshareddisk
• Command-lineinterfaceontheapplianceisnotageneral-purposeshell– Hasfamiliarcommandsforthingsyouneed– e.g.norunmqlsr,becauseMQlistenersrununderQMcontrol
47 © 2015 IBM Corporation
Summary/Moreinformation
• TheMQapplianceisavailablenow!
• Twomodels,tosuitdifferentusesandperformancerequirements
• ExistingMQfeatureswithsimpledeploymentandadministration– Includingbuilt-inHAsupport– Withoutcustomisationviaexits
• Particularlysuitedtoconsolidation(“Hub”),andmessaginggatewayscenarios– aswellasanyothersituationrequiringaneasytodeploy,lowtime-to-valueMQconfiguration
http://www-01.ibm.com/support/knowledgecenter/SS5K6E/welcome
https://github.com/ibm-messaging/mq-appliance
http://www.redbooks.ibm.com/Redbooks.nsf/RedpieceAbstracts/sg248283.html