{"id":22,"date":"2018-12-27T12:03:57","date_gmt":"2018-12-27T12:03:57","guid":{"rendered":"http:\/\/trindade.myphotos.cc\/lazysysadmin\/?p=22"},"modified":"2024-07-05T11:40:40","modified_gmt":"2024-07-05T10:40:40","slug":"ibm-mq-introduction","status":"publish","type":"post","link":"https:\/\/trindade.myphotos.cc\/lazysysadmin\/2018\/12\/27\/ibm-mq-introduction\/","title":{"rendered":"IBM<\/span> MQ<\/span>: Introduction"},"content":{"rendered":"\n
\"IBM<\/figure>\n\n\n\n

I\u2019ll start this blog with a piece of soft\u00adware I\u2019ve been learn\u00ading in the past few months: IBM<\/span> MQ<\/span>. <\/p>\n\n\n\n

Mes\u00adsage queu\u00ading is a dis\u00adtrib\u00aduted inter-process com\u00admu\u00adni\u00adca\u00adtion method based on mes\u00adsage pass\u00ading. Typ\u00adi\u00adcal mes\u00adsage queu\u00ading sys\u00adtems have mech\u00ada\u00adnisms to ensure mes\u00adsages are deliv\u00adered to their intend\u00aded des\u00adti\u00adna\u00adtion and that no mes\u00adsages are lost dur\u00ading trans\u00admis\u00adsion and reception.<\/p>\n\n\n\n

IBM<\/span> MQ<\/span> itself is a mar\u00adket-proven prod\u00aduct which has matured as the years went by. It\u2019s now almost an indus\u00adtry stan\u00addard and it is used in many indus\u00adtries, such as bank\u00ading, insur\u00adance and even the auto\u00admo\u00adtive industry.<\/p>\n\n\n\n

What is message queuing?<\/h2>\n\n\n\n

Sim\u00adply put, mes\u00adsage queu\u00ading is the mech\u00ada\u00adnism which is used by appli\u00adca\u00adtion to com\u00admu\u00adni\u00adcate with each oth\u00ader by using mes\u00adsages. The mes\u00adsages are usu\u00adal\u00adly sent to a \u201cmes\u00adsage bro\u00adker\u201d (not to be con\u00adfused with IBM<\/span> Infor\u00adma\u00adtion Bro\u00adker, for\u00admer\u00adly, IBM<\/span> Web\u00adSphere Mes\u00adsage Bro\u00adker, which is an Enter\u00adprise Ser\u00advice Bus).<\/p>\n\n\n\n

The mes\u00adsage bro\u00adker (in this case, IBM<\/span> MQ<\/span>) is respon\u00adsi\u00adble for stor\u00ading mes\u00adsages while in tran\u00adsit (option\u00adal\u00adly stor\u00ading them to per\u00adma\u00adnent stor\u00adage for data recov\u00ader\u00ading pur\u00adpos\u00ades) and guar\u00adanties deliv\u00adery. It also has fea\u00adtures which enables it to route mes\u00adsages to sev\u00ader\u00adal des\u00adti\u00adna\u00adtions at once (in IBM<\/span> MQ<\/span>, this is called pub\u00adlish and subscribe).<\/p>\n\n\n\n

History<\/h2>\n\n\n\n

IBM<\/span> MQ<\/span> is the nat\u00adur\u00adal evo\u00adlu\u00adtion of IBM\u2019s mes\u00adsag\u00ading prod\u00aducts. It all start\u00aded in the 1960s, when IBM<\/span> released the IBM<\/span> 7740 Com\u00admu\u00adni\u00adca\u00adtion Con\u00adtrol Sys\u00adtem and the IBM<\/span> 7750 Pro\u00adgrammed Trans\u00admis\u00adsion Con\u00adtrol. These were pro\u00adgram\u00adma\u00adble mes\u00adsage-switch\u00ading hard\u00adware prod\u00aducts, which enabled mes\u00adsage-ori\u00adent\u00aded com\u00admu\u00adni\u00adca\u00adtion between computers.<\/p>\n\n\n\n

After, in 1971, IBM<\/span> released TCAM<\/span> (Telecom\u00admu\u00adni\u00adca\u00adtions Access Method) for its S\/360 fam\u00adi\u00adly of com\u00adput\u00ader sys\u00adtems, and\u00adhav\u00ading adopt\u00aded CICS<\/span> for trans\u00adac\u00adtion man\u00adage\u00adment, users want\u00aded a way to inte\u00adgrate TCAM<\/span> with CICS<\/span>.<\/p>\n\n\n\n

These prod\u00aducts went through sev\u00ader\u00adal ver\u00adsions and in 1992, IBM<\/span> decid\u00aded to release IBM<\/span> MQSeries, which incor\u00adpo\u00adrat\u00aded an evo\u00adlu\u00adtion of the TCAM<\/span> mes\u00adsage-pass\u00ading engine. MQSeries was lat\u00ader (in 2002) renamed to Web\u00adSphere MQ<\/span> (because of its inte\u00adgra\u00adtion in the Web\u00adSphere prod\u00aduct family).<\/p>\n\n\n\n

The first MQSeries ver\u00adsion for dis\u00adtrib\u00aduted sys\u00adtems (the first six releas\u00ades were for the S\/360 and AS<\/span>\/400 com\u00adput\u00ader sys\u00adtems) was named MQSeries 2.0 and was avail\u00adable for OS<\/span>\/2 and AIX<\/span>. It was released in Feb\u00adru\u00adary 1995.<\/p>\n\n\n\n

With ver\u00adsion 8.0, IBM<\/span> dropped the word \u2018Web\u00adSphere\u2019 from the name and released IBM<\/span> MQ<\/span> 8.0 in May 23rd 2014.<\/p>\n\n\n\n

The cur\u00adrent ver\u00adsion is IBM<\/span> MQ<\/span> 9.1 and it was released on July 27th 2018. <\/p>\n\n\n\n

MQ<\/span> Releases<\/h2>\n\n\n\n

IBM<\/span> MQ<\/span> is avail\u00adable in two dif\u00adfer\u00adent forms: Con\u00adtin\u00adu\u00adous Release and a Long Term Support.<\/p>\n\n\n\n

Long Term Sup\u00adport releas\u00ades have the third ver\u00adsion num\u00adber equal to 0 (zero). Con\u00adtin\u00adu\u00adous Deliv\u00adery ver\u00adsion num\u00adbers and in non-zero num\u00adbers. For exam\u00adple, IBM<\/span> MQ<\/span> 9.0.0 is an LTS<\/span> ver\u00adsion; 9.0.1 is the first CD<\/span> ver\u00adsion for IBM<\/span> MQ<\/span> 9.0.<\/p>\n\n\n\n

Con\u00adtin\u00adu\u00adous Deliv\u00adery ver\u00adsions always con\u00adtain the lat\u00adest fea\u00adtures and bug fix\u00ades; LTS<\/span> releas\u00ades are only updat\u00aded via fix packs and indi\u00advid\u00adual bug fix\u00ades and include no new fea\u00adtures; the only way to update a CD<\/span> release is to install the new one over the installed version.<\/p>\n","protected":false},"excerpt":{"rendered":"

I\u2019ll start this blog with a piece of soft\u00adware I\u2019ve been learn\u00ading in the past few months: IBM<\/span> MQ<\/span>.  Mes\u00adsage queu\u00ading is a dis\u00adtrib\u00aduted inter-process com\u00admu\u00adni\u00adca\u00adtion method based on mes\u00adsage pass\u00ading. Typ\u00adi\u00adcal mes\u00adsage queu\u00ading sys\u00adtems have mech\u00ada\u00adnisms to ensure mes\u00adsages are \u2026 Con\u00adtin\u00adue read\u00ading \u2192<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"wp_typography_post_enhancements_disabled":false,"footnotes":""},"categories":[2,3],"tags":[5,10,12,9,4,8,13],"class_list":["post-22","post","type-post","status-publish","format-standard","hentry","category-middleware","category-mq","tag-ibm","tag-ibm-mq","tag-ibmmq","tag-middleware","tag-mq","tag-mqseries","tag-webspheremq"],"featured_image_src":null,"featured_image_src_square":null,"author_info":{"display_name":"Ant\u00f3nio Trindade","author_link":"https:\/\/trindade.myphotos.cc\/lazysysadmin\/author\/trindade\/"},"_links":{"self":[{"href":"https:\/\/trindade.myphotos.cc\/lazysysadmin\/wp-json\/wp\/v2\/posts\/22","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/trindade.myphotos.cc\/lazysysadmin\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/trindade.myphotos.cc\/lazysysadmin\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/trindade.myphotos.cc\/lazysysadmin\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/trindade.myphotos.cc\/lazysysadmin\/wp-json\/wp\/v2\/comments?post=22"}],"version-history":[{"count":2,"href":"https:\/\/trindade.myphotos.cc\/lazysysadmin\/wp-json\/wp\/v2\/posts\/22\/revisions"}],"predecessor-version":[{"id":25,"href":"https:\/\/trindade.myphotos.cc\/lazysysadmin\/wp-json\/wp\/v2\/posts\/22\/revisions\/25"}],"wp:attachment":[{"href":"https:\/\/trindade.myphotos.cc\/lazysysadmin\/wp-json\/wp\/v2\/media?parent=22"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/trindade.myphotos.cc\/lazysysadmin\/wp-json\/wp\/v2\/categories?post=22"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/trindade.myphotos.cc\/lazysysadmin\/wp-json\/wp\/v2\/tags?post=22"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}