Transcription
IBM WebSphere Front coverWebSphere MQ PrimerAn Introduction to Messagingand WebSphere MQLearn the basic concepts of messagingDiscover the fundamentals ofWebSphere MQGet started quickly withWebSphere MQMark E. Tayloribm.com/redbooksRedpaper
International Technical Support OrganizationWebSphere MQ Primer: An Introduction to Messagingand WebSphere MQDecember 2012REDP-0021-01
Note: Before using this information and the product it supports, read the information in “Notices” on page v.Second Edition (December 2012)This edition applies to Version 7, Release 1, Modification 0 and Version 7, Release 5, Modification 0 ofWebSphere MQ for Multiplatform (product number 5724-H72) and to Version 7, Release 1, Modification 0 ofWebSphere MQ for z/OS (product number 5655-R36). Copyright International Business Machines Corporation 2012. All rights reserved.Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP ScheduleContract with IBM Corp.
ContentsNotices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vTrademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viPreface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiThe author of this paper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiNow you can become a published author, too! . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiiComments welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiiStay connected to IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiiChapter 1. Concepts of messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1.1 The business case for message-oriented middleware . . . . . . . . . . . . . . . . . . . . . . . . . .1.2 Application simplification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1.3 Example scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1.3.1 Retail kiosks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1.3.2 Faster bank payments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1.3.3 Airport information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1.4 A messaging-based solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1.4.1 Messaging in a service-oriented architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123444455Chapter 2. Introduction to WebSphere MQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72.1 Messaging with WebSphere MQ. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82.1.1 A history of WebSphere MQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92.2 Core concepts of WebSphere MQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102.2.1 Asynchronous messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.2.2 WebSphere MQ clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.2.3 WebSphere MQ Telemetry clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.2.4 Application programming interfaces (APIs). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.2.5 Reliability and integrity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.2.6 WebSphere MQ messaging styles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.2.7 WebSphere MQ topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162.2.8 Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202.2.9 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212.2.10 Management and monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212.3 Diverse platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222.4 Relationships with other products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232.4.1 WebSphere Message Broker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232.4.2 WebSphere Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Chapter 3. Getting started with WebSphere MQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3.1 Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3.1.1 Message descriptor (MQMD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3.1.2 Message properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3.2 WebSphere MQ objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3.2.1 Queue manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3.2.2 Queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3.2.3 Topic objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3.2.4 Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3.3 Configuring WebSphere MQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3.3.1 Creating a queue manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Copyright IBM Corp. 2012. All rights reserved.2526262728282830313232iii
iv3.3.2 Managing WebSphere MQ objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3.4 Writing applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3.4.1 A code fragment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3.5 Triggering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3.6 Configuring a WebSphere MQ client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3.6.1 How to define a client/server connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3.7 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3.8 Configuring communication between queue managers . . . . . . . . . . . . . . . . . . . . . . . .3.8.1 How to define a connection between two systems . . . . . . . . . . . . . . . . . . . . . . . .3.9 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33343739424345464750Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Online resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Help from IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51515151WebSphere MQ Primer: An Introduction to Messaging and WebSphere MQ
NoticesThis information was developed for products and services offered in the U.S.A.IBM may not offer the products, services, or features discussed in this document in other countries. Consultyour local IBM representative for information on the products and services currently available in your area. Anyreference to an IBM product, program, or service is not intended to state or imply that only that IBM product,program, or service may be used. Any functionally equivalent product, program, or service that does notinfringe any IBM intellectual property right may be used instead. However, it is the user's responsibility toevaluate and verify the operation of any non-IBM product, program, or service.IBM may have patents or pending patent applications covering subject matter described in this document. Thefurnishing of this document does not grant you any license to these patents. You can send license inquiries, inwriting, to:IBM Director of Licensing, IBM Corporation, North Castle Drive, Armonk, NY 10504-1785 U.S.A.The following paragraph does not apply to the United Kingdom or any other country where suchprovisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATIONPROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS ORIMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer ofexpress or implied warranties in certain transactions, therefore, this statement may not apply to you.This information could include technical inaccuracies or typographical errors. Changes are periodically madeto the information herein; these changes will be incorporated in new editions of the publication. IBM may makeimprovements and/or changes in the product(s) and/or the program(s) described in this publication at any timewithout notice.Any references in this information to non-IBM websites are provided for convenience only and do not in anymanner serve as an endorsement of those websites. The materials at those websites are not part of thematerials for this IBM product and use of those websites is at your own risk.IBM may use or distribute any of the information you supply in any way it believes appropriate without incurringany obligation to you.Any performance data contained herein was determined in a controlled environment. Therefore, the resultsobtained in other operating environments may vary significantly. Some measurements may have been madeon development-level systems and there is no guarantee that these measurements will be the same ongenerally available systems. Furthermore, some measurements may have been estimated throughextrapolation. Actual results may vary. Users of this document should verify the applicable data for theirspecific environment.Information concerning non-IBM products was obtained from the suppliers of those products, their publishedannouncements or other publicly available sources. IBM has not tested those products and cannot confirm theaccuracy of performance, compatibility or any other claims related to non-IBM products. Questions on thecapabilities of non-IBM products should be addressed to the suppliers of those products.This information contains examples of data and reports used in daily business operations. To illustrate themas completely as possible, the examples include the names of individuals, companies, brands, and products.All of these names are fictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.COPYRIGHT LICENSE:This information contains sample application programs in source language, which illustrate programmingtechniques on various operating platforms. You may copy, modify, and distribute these sample programs inany form without payment to IBM, for the purposes of developing, using, marketing or distributing applicationprograms conforming to the application programming interface for the operating platform for which the sampleprograms are written. These examples have not been thoroughly tested under all conditions. IBM, therefore,cannot guarantee or imply reliability, serviceability, or function of these programs. Copyright IBM Corp. 2012. All rights reserved.v
TrademarksIBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business MachinesCorporation in the United States, other countries, or both. These and other IBM trademarked terms aremarked on their first occurrence in this information with the appropriate symbol ( or ), indicating USregistered or common law trademarks owned by IBM at the time this information was published. Suchtrademarks may also be registered or common law trademarks in other countries. A current list of IBMtrademarks is available on the Web at http://www.ibm.com/legal/copytrade.shtmlThe following terms are trademarks of the International Business Machines Corporation in the United States,other countries, or both:AIX CICS DB2 IBM IMS MQSeries PowerHA RACF Redbooks Redpaper Redbooks (logo)Smarter Planet WebSphere z/OS The following terms are trademarks of other companies:Linux is a trademark of Linus Torvalds in the United States, other countries, or both.Microsoft, Windows, and the Windows logo are trademarks of Microsoft Corporation in the United States,other countries, or both.Java, and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or itsaffiliates.UNIX is a registered trademark of The Open Group in the United States and other countries.Other company, product, or service names may be trademarks or service marks of others.viWebSphere MQ Primer: An Introduction to Messaging and WebSphere MQ
PrefaceThe power of IBM WebSphere MQ is its flexibility combined with reliability, scalability, andsecurity. This flexibility provides a large number of design and implementation choices.Making informed decisions from this range of choices can simplify the development ofapplications and the administration of a WebSphere MQ messaging infrastructure.Applications that access a WebSphere MQ infrastructure can be developed using a widerange of programming paradigms and languages. These applications can run within asubstantial array of software and hardware environments. Customers can use WebSphereMQ to integrate and extend the capabilities of existing and varied infrastructures in theinformation technology (IT) system of a business.This IBM Redpaper publication provides an introduction to message-oriented middlewareto anyone who wants to understand messaging and WebSphere MQ. It covers the conceptsof messaging and how WebSphere MQ implements those concepts. It helps you understandthe business value of WebSphere MQ. It provides introductory information to help you getstarted with WebSphere MQ. No previous knowledge of the product and messagingtechnologies is assumed.The author of this paperThis paper was produced by a specialist working at the International Technical SupportOrganization, Raleigh Center.Mark E. Taylor is a member of the WebSphere MQ TechnicalStrategy organization at the IBM Hursley laboratory in England.Mark is responsible for defining the functions included in newreleases of WebSphere MQ. During his 25 year career with IBM,Mark worked in a variety of development and services roles. Hewrote code for the early versions of IBM MQSeries , porting it tonumerous UNIX operating systems.Thanks to the following people for their contributions to this project:Marcela AdanIBM Redbooks Project Leader, International Technical Support Organization, RaleighCenterDeana CobleTechnical Writer, International Technical Support Organization, Raleigh CenterThanks to the author of the previous edition of this paper: Dieter Wackerow, author of the first edition, MQSeries Primer, published in October 1999 Copyright IBM Corp. 2012. All rights reserved.vii
Now you can become a published author, too!Here’s an opportunity to spotlight your skills, grow your career, and become a publishedauthor—all at the same time! Join an ITSO residency project and help write a book in yourarea of expertise, while honing your experience using leading-edge technologies. Your effortswill help to increase product acceptance and customer satisfaction, as you expand yournetwork of technical contacts and relationships. Residencies run from two to six weeks inlength, and you can participate either in person or as a remote resident working from yourhome base.Find out more about the residency program, browse the residency index, and apply online at:ibm.com/redbooks/residencies.htmlComments welcomeYour comments are important to us!We want our papers to be as helpful as possible. Send us your comments about this paper orother IBM Redbooks publications in one of the following ways: Use the online Contact us review Redbooks form found at:ibm.com/redbooks Send your comments in an email to:red[email protected] Mail your comments to:IBM Corporation, International Technical Support OrganizationDept. HYTD Mail Station P0992455 South RoadPoughkeepsie, NY 12601-5400Stay connected to IBM Redbooks Find us on Facebook:http://www.facebook.com/IBMRedbooks Follow us on Twitter:http://twitter.com/ibmredbooks Look for us on LinkedIn:http://www.linkedin.com/groups?home &gid 2130806 Explore new Redbooks publications, residencies, and workshops with the IBM Redbooksweekly sf/subscribe?OpenForm Stay current on recent Redbooks publications with RSS phere MQ Primer: An Introduction to Messaging and WebSphere MQ
1Chapter 1.Concepts of messagingThis chapter discusses the reasons why a business might require a messaging solution anddifferent requirements for messaging. This chapter provides some examples of wheremessaging is used. This chapter contains the following sections: The business case for message-oriented middlewareApplication simplificationExample scenariosA messaging-based solution Copyright IBM Corp. 2012. All rights reserved.1
1.1 The business case for message-oriented middlewareBusiness environments are constantly changing. Applications that were written 20 years agoneed to exchange data with applications written last week. Examples of this changingenvironment can be one company that merges with another company, a new partner tocommunicate with, an application that is used internally in a company is now exposed tocustomers, or different departments within a company need to share programs.The growth of Internet banking required services, such as managing payments or queryingaccount information, to be made available through a range of channels. The core data can beheld in a database on a mainframe, but a user of a browser requires a front-end webapplication server to interact with that database. As new delivery channels are created, suchas smartphone applications, easy ways for that new mechanism to interact are needed. Thesmartphone application must communicate with the same applications and database withoutchanging the database.The evolutionary speed of IT systems makes essential the ability to integrate across manyenvironments with multiple applications reliably and quickly.Messaging is an effective way to connect these systems. It hides many of the details ofcommunication from the application developer and gives a simple interface. Simplifying allowsthe developer to concentrate on the business problem instead of worrying about matters suchas recovery, reliability, and operating system differences.A further feature of messaging solutions is the decoupling of one application from another.Many mechanisms for communicating between applications require that both applications areavailable at the same time. Messaging uses an asynchronous model, which means that anapplication that generates messages does not have to execute at the same time as anapplication that consumes those messages. Reducing the requirements for simultaneousavailability reduces complexity and can improve overall availability. Messages can be sent tospecific applications or distributed to many different applications at the same time.2WebSphere MQ Primer: An Introduction to Messaging and WebSphere MQ
Figure 1-1 shows basic patterns for connectivity.Application to application communicationApplication AApplication BEvent distribution on any scaleApplication BEventDistributorApplication AApplication CFigure 1-1 Using messaging to connect applications and distribute dataAsynchrony is used in various ways. It can queue large volumes of work, and that work is thensubmitted once a day by a batch process. Or, work can be submitted immediately and thenprocessed as soon as the receiving application finishes dealing with a previous request.Asynchronous processing does not imply long response times. Many applications were builtand successfully execute by using messaging for real-time interactive operations.1.2 Application simplificationOne of the key features of messaging is to remove complexity from application code.Worrying about reliability or recovery is the job of the middleware product or component, suchas the messaging provider. Developers can simply focus on writing the business logic.The following list covers some of the factors that need to be dealt with by middleware, andhidden from application developers, regardless of the business application:Once-only processingBusiness transactions normally happen exactly once. Middlewareneeds to ensure all the systems that are involved in that transactiondo their job, exactly once. There must be no loss or duplication.Applications must not write complex code for recovery or to reversepartially completed operations (compensation) code if individualsystems fail.UbiquityRun your applications on the platform where it makes the mostsense. Be able to integrate applications seamlessly on a widerange of operating systems and hardware environments.Chapter 1. Concepts of messaging3
Easy to changeUsing industry standards can help you become more responsive asskills can be maintained and reused across projects. Newapplications can be rapidly written and deployed.Easy to extendScale your applications rapidly to any volume without downtime.Add more processing without application change. Roll out newapplications and features quickly and safely without downtime.ComplianceMeet enterprise, industry, and regulatory requirements easily,especially as those requirements evolve. A middlewareimplementation needs to assist with auditing and other complianceobjectives, giving a consistent interface for all applications.Performance and availabilityMake the best use of the systems. Provide services for high andcontinuous availability.SecurityProvide a secure environment. Data is protected from loss,modification, and reading. Losing sensitive data, or failing tocomply with regulations, costs time, money, and reputation.1.3 Example scenariosThis section gives examples of where messaging solves a real-world problem.1.3.1 Retail kiosksA retailer wants to respond rapidly to online customer needs and have a consistent view ofdata that is shown at 25,000 self-service kiosks. Data is changing rapidly, and it needs to bedistributed rapidly to these kiosks.The kiosks in the network are connected by a messaging service to the central databasesand changes are pushed out rapidly. More than 14,000 transactions are processed eachsecond.1.3.2 Faster bank paymentsGovernment regulation that limits payment clearing times requires faster payment processesthrough near-instant money transfers between banks.A high-performance payment solution is developed that uses a messaging solution to routemessage traffic between systems. Many existing components of the older payment systemwere able to be adapted to work with the new messaging layer, preserving investment inthese programs. The government requirement was to be able to clear payments in under twohours. However, this solution is technically capable of completing its processing in seconds. Ithandles millions of transactions every day.1.3.3 Airport informationAt an airport, rapid changes in government regulations are coupled with increasingpassenger volumes. This airport needs a flexible IT infrastructure that is populated withseamlessly integrated systems. The airport currently supports daily business operations withan inflexible heterogeneous infrastructure.4WebSphere MQ Primer: An Introduction to Messaging and WebSphere MQ
1.4 A messaging-based solutionA messaging-based solution establishes a shared integration layer, enabling the seamlessflow of multiple types of data between the customer’s heterogeneous systems. For example,airport staff can now easily access important information, such as flight schedule changesfrom multiple systems. A messaging-based solution can also flexibly integrate new systems toaccommodate evolving government regulations.1.4.1 Messaging in a service-oriented architectureService-oriented architecture (SOA) is a business-centric IT architectural approach. Thisapproach supports business integration as linked, repeatable business tasks or services.SOA helps users build composite applications. Composite applications draw uponfunctionality from multiple sources within and beyond the enterprise to support horizontalbusiness processes. SOA is an architectural style that makes this possible. For moreinformation about SOA, see the following link:http://www.ibm.com/soaThe most important characteristic of SOA is the flexibility to treat elements of businessprocesses and the underlying information technology infrastructure as secure, standardizedcomponents (services). These components can be reused and combined to addresschanging business priorities. SOA requires that applications can interact with each other.This book is not intended to discuss SOA in detail, but a critical aspect of implementing thearchitecture is to have connectivity. The seven main attributes of the connectivityinfrastructure are: ReliableSecureTime flexible and resilientTransactionalIncrementalUbiquitousBasis for enterprise service bus (ESB)Any messaging component fitting in the connectivity infrastructure must satisfy and supportall these capabilities. A flexible and robust messaging backbone is a key component of SOAand provides the transport foundation for an ESB.Chapter 1. Concepts of messaging5
6WebSphere MQ Primer: An Introduction to Messaging and WebSphere MQ
2Chapter 2.Introduction to WebSphere MQThis chapter introduces IBM WebSphere MQ and how it implements messaging. Coreconcepts are described, and major features are discussed.This chapter contains the following sections: Messaging with WebSphere MQCore concepts of WebSphere MQDiverse platformsRelationships with other products Copyright IBM Corp. 2012. All rights reserved.7
2.1 Messaging with WebSphere MQWebSphere MQ is the market-leading messaging integration middleware product. Originallyintroduced in 1993 (under the MQSeries name), it always focused on providing an available,reliable, scalable, secure, and high-performance transport mechanism to address therequirements that we discussed in the previous chapter.WebSphere MQ always connected systems and applications, regardless of the platform orenvironment. It is essential to be able to communicate between a GUI desktop applicationthat is running on Microsoft Windows and an IBM CICS transaction that is running on IBMz/OS . That value of universality is core to the product, and this value has not changed in allthe time that it has been available. What has changed is the range of environments in whichWebSphere MQ can or must live.There are newer platforms, environments, requirements for qualities of service (QoS), andnewer messaging patterns. Security has become more important as systems are madeaccessible to more users across an enterprise and beyond it. Performance and scalabilityrequirements have increased. Regulators and auditors have imposed more controls on whatcan or must be done. Systems, which need access to enterprise data, have become bothmore powerful (faster, more processors, and so on) and much less powerful (sensors, tablets,and mobile phones).Therefore, WebSphere MQ has evolved.There are now more ways for applications to reach a WebSphere MQ queue manager and toaccess any existing applications that were already WebSphere MQ enabled. Newapplications can be written that use alternative interfaces and still maximize the reliability andperformance of WebSphere MQ. Those new applications do not need a completereplacement of existing infrastructure. The applications work with what you already have andwhat you know how to manage.At the same time as adding new interfaces, protocols, and environments, a large amount ofthe WebSphere MQ workload continues to be executed in mainframe-based data centers.The efficient use of, and integration with, the capabilities of the IBM z hardware and operatingsystems is critical. As this book shows, WebSphere MQ V7.1 for z/OS significantly improvesthe performance, capacity, and availability that can be achieved when running in a sysplex.8WebSphere MQ Primer: An Introduction to Messaging and WebSphere MQ
2.1.1 A history of WebSphere MQFigure 2-1 shows a time line of WebSphere MQ versions and some highlights of the featuresand products that have been made available.History of WebSphere MQMQAdvance dSe curityMQ Telem etryMQ FileTra ns ferMQ E xpressEx tendedSe curityMQ LowLa tencyMQE verypla ceV7V6WebSphere MQV5.3V1.1MQIassureddelivery1990sV2V2.1multip
viii WebSphere MQ Primer: An Introduction to Messaging and WebSphere MQ Now you can become a published author, too! Here’s an opportunity to spotlight your skills, grow your career, and become a published author—all at the same time! Join an ITSO residency project and help write a book in yourFile Size: 1MBPage Count: 64Explore furtherIBM MQ Tutorial IBM WebSphere MQ Tutorial for Beginners .mindmajix.comWebsphere MQ Basics Tutorial. Websphere MQ Basics Tutorial .medium.comibm mq tutorial mq tutorial for beginners - YouTubewww.youtube.comIBM MQ Tutorialswww.ibm.comIBM MQ Tutorial WebSphere MQ Training Videos SVR .svrtechnologies.comRecommended to you b
