DOCSLIB.ORG

Protecting Message Data by Implementing MQ AMS End to End Message Security

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Protecting Message Data by Implementing MQ AMS End to End Message Security Protecting Message Data by Implementing MQ AMS End to End Message Security Introduction: Key Concepts MQ AMS augments IBM MQ security by providing data protection of messages. Three “Qualities of Protection” (QOP) are provided: Integrity (signed) IBM MQ messages are signed when put on a queue and the signature embedded into the message is verified when the message is retrieved. The signature identifies the sender of the message and ensures that the content of the message has not been changed. MQ AMS uses PKCS #7 data-envelope to envelop a message in a digital signature. Privacy (sealed) IBM MQ messages are signed as above but the content of the message is also encrypted. The key used to encrypt messages is itself encrypted for each potential recipient so that the messages can be retrieved by one or more recipients. MQ AMS uses PKCS #7 data-envelope to envelop a message in a digital signature. Confidentiality (encrypted only) IBM MQ messages are encrypted end-to-end using a symmetric key and are not digitally signed. This reduces the amount of asymmetric key operations by half and improves performance. Optionally the encryption keys can be reused for multiple messages going to the same recipient. The second and subsequent messages incur no asymmetric key operations which keeps performance similar to plaintext/unprotected message throughput. Data protection is provided by various interceptors relying on configuration files, PKI keystores and certificates. This is in addition to the standard protection available for IBM MQ objects using the IBM MQ Object Authority Manager (OAM) or SAF (via a product such as IBM’s RACF) on z/OS. The diagram below depicts the overall architecture: Interceptors MQ AMS implements security by intercepting IBM MQ API calls. The following APIs are supported: • Message Queue Interface (MQI) • Java Message Service (JMS) • IBM MQ Java Service (JMS) • IBM MQ Java Classes Three interceptors are provided: • IBM MQ server interceptor To protect messages put or get by applications using the mqm library and using the interprocess communication (IPC), also called bindings mode. This interceptor will also protect messages for Java applications (either using the MQ Java API or JMS) connecting in MQ bindings mode. • IBM MQ C client interceptor To protect messages put or get by applications using the mqm client library and therefore connecting using a (non-Java) MQ client connection. • IBM MQ Java interceptor (JMS and MQ Java) To protect messages put or get by Java applications (MQ Java API or JMS) using either client connections or bindings mode. Note that if you use this interceptor for applications using Java bindings mode, you should consider disabling the server interceptor to avoid signing/encrypting messages twice. Public Key Infrastructure (PKI) and Certificates MQ AMS uses Public Key Infrastructure (PKI) identities to represent users or applications. The identities are used to sign and encrypt messages. An identity is represented by the distinguished name (DN) of a personal X.509 (v2/v3) certificate associated with the signed and/or encrypted message. To authenticate this authority, the user or application must have access to a keystore containing a public certificate and an associated private key. A mechanism is provided to map the OS identity of the user or application to the specific keystore file. Object Authority Manager (OAM) MQ AMS provides message security. It does not provide authorization services for IBM MQ objects. The task to authorize access to IBM MQ resources (queue manager, queues and other objects) remains the responsibility of the IBM MQ Object Authority Manager (OAM) or RACF (or other SAF) on z/OS. When an interceptor intercepts the MQ API calls from an application, it delegates the authorization request to the IBM MQ authority service. Error Handling MQ AMS defines an error handling queue (SYSTEM.PROTECTION.ERROR.QUEUE) to manage messages that contain errors or messages that cannot be decrypted. If a received message does not meet the security requirements for the queue it is on, then the message is moved to the error handling queue. The following is a non-exclusive list of possible reasons why a message might be sent to the error handling queue: • Quality of protection mismatch • Decryption error • PDMQ header error • Size mismatch • Encryption algorithm strength mismatch • Unknown error The system error handling queue can optionally be defined as an alias queue pointing to another queue. The Objective of this lab is to demonstrate the simultaneous implementation of IBM® MQ Security features like OAM, SSL, AMS & CHLAUTH in an Integrated Test Case Scenario which can be taken as a template for Large Scale Implementation at Enterprise Level. The specific configuration of Advanced Message Security (AMS) feature is required to meet the regulatory requirement of PCI DSS (Payment Card Industry Data Security Standard) which mandates business critial information like Credit / Debit Cards & other important Bank transactions to be secured & encrypted. The above diagram depicts our Test Case Scenario at High Level As per the above diagram, Application user Alice puts a messages through SSL/TLS enabled Client Connection Channel into an AMS enabled Cluster Queue Alias (AMS_A) defined under TEST1 Qmgr. This Q Alias points to AMS enabled Cluster Local Queue (AMS_E) defined under TEST2 Qmgr through a secure Cluster Channel. Once the business critical message(s) reaches Q Local (AMS_E), it will be encrypted using pre- defined AMS rules set at the Queue Level. Only authorized Application user Bob should be able to retrieve the the data from the Queue (AMS_E). Going by this configuration, even ‘mqm’ or ‘root’ user does Not have the default authority to read / browse the message from Queue (AMS_E) without setting explicit AMS security rules! Hence, highly sensitive Customer data like Credit / Debit Card information is secured from the point it originates from Application user Alice till it is consumed by Application user Bob from the other end of the secure MQ network. From Implementation Perspective, we have created & configured the following components: 1. Created a MQ Cluster called ‘POC’ having 3 Qmgrs TEST(1,2,3) where TEST(1,2) are Full Repository (FR) Qmgrs & TEST3 is the Partial Repository(PR) Qmgr. 2. Created an Internal Certificate Authority (CA) for signing Certificate Requests for MQ Clients & Cluster Qmgrs. 3. Configured SSL/TLS at Cluster Channels using in-house Certificate Authority (CA) 4. Created a dedicated Queue Manager CCDT for Administration & Maintenance of Client Connection Channel file (CCDT) called AMQCLCHL.TAB. 5. Configured MQ Clients (Alice & Bob) connectivity with Qmgrs using CCDT. 6. Configured Channel Authentication (CHLAUTH) rules to Allow / Block incoming requests from MQ Client users Alice & Bob. 7. Created & Configured have 2 AMS enabled Cluster Queues AMS_A (QA) defined under TEST1 & AMS_E (QL) define under TEST2 Qmgrs respectively. 8. AMS Keystores are created using Self-Signed Certificates of Alice & Bob. With these Security Configurations in place, this Test Case demonstrate a comprehensive security solution by making use of most of the built-in IBM MQ Security features like OAM, SSL/TLS, CHLAUTH & AMS to achieve End to End Message Security Solution which includes Authentication, Authorization, Encryption & Digital Signature. Thus, MQ messages are secured while in transit through SSL/TLS enabled MQ Channels as well as while sitting in the AMS enabled Local Queue before being processed by receiving Application. Step-by-step 1. MQ Configuration Items This entire article on IBM MQ Security Solution can be broken down into 4 Major parts: 1. Creation & Configuration of MQ Cluster with SSL/TLS Enabled Channels. 2. Configuration of SSL/TLS enabled MQ Client Connectivity with Cluster Queue Managers using CCDT file AMQCLCHL.TAB. 3. Setting up the CHLAUTH rules at Channel Level for enhanced Security. 4. Implementation of AMS Security Rules at Queue Level. #################################### Internal Certificate Authority (CA): /home/mqm/CA TEST1 Qmgr’s SSL Keystore: /var/mqm/qmgrs/TEST1/ssl TEST2 Qmgr’s SSL Keystore: /var/mqm/qmgrs/TEST2/ssl TEST3 Qmgr’s SSL Keystore: /var/mqm/qmgrs/TEST3/ssl Alice’s home directory: /home/alice/ Alice’s SSL Keystore: /home/alice/keystore Bob’s home directory: /home/bob Bob’s SSL Keystore: /home/bob/keystore CCDT File: /home/CCDT/AMQCLCHL.TAB ==> Centralized Location to be used by both Alice & Bob CCDT File Administration: /var/mqm/qmgrs/CCDT/@ipcc/AMQCLCHL.TAB ##################################################### 2. Define Queue Managers This is the first part of the exercise wherein we are going to create 3 Qmgrs & define the Listener Process for each. Create TEST1 Qmgr ################# crtmqm TEST1 Strmqm TEST1 Runmqsc TEST1 DEFINE LISTENER(TEST1.LISTENER) TRPTYPE(TCP) PORT(1417) CONTROL(QMGR) end Create TEST2 Qmgr ################# crtmqm TEST2 DEFINE LISTENER(TEST2.LISTENER) TRPTYPE(TCP) PORT(1415) CONTROL(QMGR) Create TEST3 Qmgr ################# crtmqm TEST3 DEFINE LISTENER(TEST3.LISTENER) TRPTYPE(TCP) PORT(1416) CONTROL(QMGR) Checkpoint Test: You can Stop / Start the Queue Managers and listeners via the commands or through the MQ Explorer; verify if the Listener Programs are running using the command: ps -ef | grep runmqlsr Observation: 3. Create a MQ Cluster In this Section, we are going to create a Cluster called POC & make 3 Qmgrs part of the Cluster. Configured TEST1 & TEST2 as the Full Repository (FR) & TEST3 as the Partial
Load more

Recommended publications
  • MQ Jan 2005.P65
    67 January 2005 In this issue 3 Generating and executing commands in batch for MQ on z/OS 10 Integrating COBOL applications with Microsoft BizTalk Server 2004 – part 2 19 Display tool for WebSphere MQ objects on Unix 31 Introduction to, and usage of, the WebSphere MQ JMS Admin tool 39 How to migrate Plug-In node from WMQI to WBIMB 50 MQ news © Xephon Inc 2005 MQ Update Published by Subscriptions and back-issues Xephon Inc A year’s subscription to MQ Update, PO Box 550547 comprising twelve monthly issues, costs Dallas, Texas 75355 $380.00 in the USA and Canada; £255.00 in the USA UK; £261.00 in Europe; £267.00 in Australasia and Japan; and £265.50 elsewhere. In all cases Phone: 214-340-5690 the price includes postage. Individual issues, Fax: 214-341-7081 starting with the July 2000 issue, are available Editor separately to subscribers for $33.75 (£22.50) Trevor Eddolls each including postage. E-mail: [email protected] Contributions Publisher When Xephon is given copyright, articles Colin Smith published in MQ Update are paid for at the rate E-mail: [email protected] of $160 (£100 outside North America) per 1000 words and $80 (£50) per 100 lines of code Disclaimer for the first 200 lines of original material. The Readers are cautioned that, although the remaining code is paid for at the rate of $32 (£20) information in this journal is presented in good per 100 lines. To find out more about faith, neither Xephon nor the organizations or contributing an article, without any obligation, individuals that supplied information in this please download a copy of our Notes for journal give any warranty or make any Contributors from www.xephon.com/nfc.
    [Show full text]
  • Universal Messaging with IBM MQ V8 IBM Redbooks Solution Guide
    ® Universal Messaging with IBM MQ V8 IBM Redbooks Solution Guide By implementing messaging technologies, businesses can use a consistent approach to connectivity, decoupling the business application from the complex tasks of handling failures, error recovery, transaction integrity, security, and scalability. IBM® MQ® provides the universal messaging backbone for service-oriented architecture (SOA) connectivity (Figure 1). It connects virtually any commercial IT system, with support for more than 80 platforms. Figure 1. Overview of the IBM MQ solution IBM MQ includes a choice of APIs and supports the Java™ Message Service (JMS) API. IBM MQ is the market-leading messaging integration middleware product. Originally introduced in 1993 (under the IBM MQSeries® name), IBM MQ provides an available, reliable, scalable, secure, and high-performance transport mechanism to address businesses connectivity requirements. Universal Messaging with IBM MQ V8 1 Did you know? IBM MQ has the following credentials and industry recognition: It is the most widely deployed messaging backbone, with over 10,000 customers using the IBM messaging backbone: o Over 90% of Fortune 50 companies and of Fortune 10 companies use the IBM messaging backbone. o Over 80% of Global 25 companies and 70% of Global 10 companies use the IBM messaging backbone. It is entrusted with tens of billions of messages each day: o A government client sends 675 million messages per day. o A banking client handles over 213 million messages per day on IBM z/OS® alone. It is relied upon as the mission-critical backbone: o A financial markets client handles USD 1 trillion worth of traffic per day on one IBM MQ network.
    [Show full text]
  • MQ for Administrators
    MQ for Administrators Arthur Rodriguez [email protected] TxMQ Inc. Capitalware's MQ Technical Conference v2.0.1.5 MQ for Administrators The session builds on the basic introduction to MQ, with a focus on Administrative best practices, system architecture considerations, naming conventions, basic and advanced tools (command line & the explorer, scripting and automation, backup and recovery and basic troubleshooting techniques). • Agenda • Scope of MQ Administration • Assumptions • Architecture • Target Audience • Installation & Maintenance • Role of the MQ Administrator • Availability, Recovery and • What MQ Admins do Restart • Quick Review of MQ ? • Administrative Tasks • What is MQ ? • Tools • MQ System Components • Troubleshooting Techniques • Conclusion Capitalware's MQ Technical Conference v2.0.1.5 MQ for Administrators Assumptions Basic understanding of MQ and Message Queueing in an enterprise computing environment Background in Linux, Unix or Windows systems administration Target Audience Anyone responsible for or interested in MQ systems administration MQ Admins may come from various backgrounds, network engineers, Linux, Unix, and Windows admins, or MQ developers. Goal Provide a high level overview of the roles and responsibilities of the MQ Administrator. Tips of preforming some regular MQ Administrator activities and overall scope of the MQ Administrator role in an enterprise computing environment. Provide some best practices Capitalware's MQ Technical Conference v2.0.1.5 Role of the MQ Administrator Capitalware's MQ Technical Conference v2.0.1.5 Role of the MQ Administrator To support business functions, IT operations and application development by assuring the availability, reliability, accessibility, and performance of MQ systems and services. MQ Administrators are responsible to ensure not only that MQ systems and services are fully operational, but that they are being utilized effectively and efficiently.
    [Show full text]
  • 17059: Are Z/OS & Distributed MQ Platforms Like Oil and Water?
    17059: Are z/OS & distributed MQ platforms like oil and water? Mark Taylor Lyn Elkins [email protected] [email protected] IBM Hursley IBM ATS Insert Custom Session QR if Desired. Introduction • One objective of MQ is isolating apps from needing to understand platforms ‒ There is a common API that can be expressed in many languages • Another objective is to have (reasonably) common operational model ‒ Much of admin is the same on all platforms • But it’s not all the same ‒ One dichotomy has always been whether to be natural to MQ-ness or behave like other things on the platform ‒ Some features don’t make sense on some platforms For example, .Net interface is only on Windows ‒ Some features have not been implemented everywhere for other reasons • So there are differences, and that is what this presentation will cover • Will base this on V8 Code Streams • There are essentially two implementations of MQ from Hursley lab ‒ z/OS ‒ Distributed (Windows, Unix, Linux, i) ‒ There are some further subspecies variants like VSE or NSS • Within Distributed implementation, there are some platform unique features ‒ But we won’t discuss those here ‒ Most platform-unique code abstracts OS facilities like locking or NLS or threads • In the early days, some code was written for one and then “ported” ‒ In particular, the channel code ‒ Meant double-fixing, and re-porting for each release • Internal architecture (eg tasks, threads) very different ‒ But we won't discuss much of that. Understanding externals is more important • Since V7.0, some code is
    [Show full text]
  • MP1K: IBM MQ for Z/OS Version 9 Performance Report
    MP1K: IBM MQ for z/OS version 9.0 Performance Report June 2016 IBM MQ Performance IBM UK Laboratories Hursley Park Winchester Hampshire SO21 2JN Take Note! Before using this report, please be sure to read the paragraphs on “disclaimers”, “warranty and liability exclusion”, “errors and omissions” and other general information paragraphs in the “Notices” section below. First edition, June 2016. This edition applies to IBM MQ for z/OS version 9.0 (and to all subsequent releases and modifications until otherwise indicated in new editions). © Copyright International Business Machines Corporation 2016. All rights reserved. Note to U.S. Government Users Documentation related to restricted rights. Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule contract with IBM Corp. Notices DISCLAIMERS The performance data contained in this report were measured in a controlled environment. Results obtained in other environments may vary significantly. You should not assume that the information contained in this report has been submitted to any formal testing by IBM. Any use of this information and implementation of any of the techniques are the responsibility of the licensed user. Much depends on the ability of the licensed user to evaluate the data and to project the results into their own operational environment. WARRANTY AND LIABILITY EXCLUSION The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUD- ING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
    [Show full text]
  • Product Documentation for Integrating with Appdynamics APM Fix Pack 9 November 2020
    IBM Z Application Performance Management Connect 6.1 Product Documentation for integrating with AppDynamics APM Fix pack 9 November 2020 IBM Contents Integrating with AppDynamics APM.......................................................................5 Introducing components........................................................................................7 Z APM Connect Base....................................................................................................................................7 Z APM Connect Distributed Gateway.......................................................................................................... 8 Z APM Connect CICS TS Data Producer...................................................................................................... 8 Z APM Connect IMS Data Producer............................................................................................................. 9 Z APM Connect Interceptor......................................................................................................................... 9 Z APM Connect request monitoring exits..................................................................................................10 IBM MQ Monitoring Subsystem component............................................................................................. 11 Installing and configuring.................................................................................... 13 Prerequisites and system preparation.....................................................................................................
    [Show full text]
  • Running and Supporting MQ Light Applications
    Running and Supporting MQ Light Applications Matthew Whitehead IBM MQ Development [email protected] Copyright © IBM 2016 Capitalware's MQ Technical Conference v2.0.1.6 Agenda • What is MQ Light? • The MQ Light API • Running MQ Light apps in Bluemix • IBM MQ support for MQ Light • Demos Copyright © IBM 2016 Capitalware's MQ Technical Conference v2.0.1.6 IBM Messaging Deliver Messaging Enable Developers to Backbone for Enterprise build more scalable, responsive applications Focus on traditional MQ values, rock-solid Focus on app use cases, enterprise-class service, breadth of languages, ease-of-operation, breadth ease-of-deployment, micro of platform coverage, services, integration with availability, z/OS developer frameworks exploitation Copyright © IBM 2016 Capitalware's MQ Technical Conference v2.0.1.6 What is MQ Light? 1. A new messaging API 2. A messaging runtime for on-premise development 3. A PaaS messaging runtime for admin-free cloud deployment (the MessageHub Service in Bluemix) More on all of these throughout the slides... Copyright © IBM 2016 Capitalware's MQ Technical Conference v2.0.1.6 MQ Light : Software and Cloud Messaging that application developers will love to use, helping them make responsive applications that scale easily 3 ways to run an MQ Light application: Bluemix Message Hub service (MQ Light service now deprecated) MQ Light software download IBM MQ 8.0.0.4 Open APIs crafted to feel natural in a growing range of popular languages Tooling that makes modular app development easy Copyright © IBM 2016 Capitalware's
    [Show full text]
  • Introduction to MQ
    Introduction to MQ Sam Goulden IBM MQ L3 Service MQ Technical Conference v2.0.1.8 Agenda ¡ Messaging What is messaging and why use it? What does MQ give you? ¡ Fundamentals of IBM MQ Messaging models Key components Messaging applications MQ Environments Security Reliability and availability Administration MQ Advanced MQ Technical Conference v2.0.1.8 What is messaging? ¡ It connects your applications! From the simplest pairs of applications… ...to the most complex ¡ and breaks the tight coupling… business processes. MQ Technical Conference v2.0.1.8 Why use it? ¡ Extended reach ¡ Reliability ¡ Scalability ¡ Flexibility ¡ Provides for simplification of application development Ubiquity Easy to change and scale Focus on the business logic ¡ Important regardless of the initial scale of deployment MQ Technical Conference v2.0.1.8 Direct communication between applications Request an action App B App A Wait for a response ¡ Issues with this ‘synchronous’ approach Both applications A and B must always be available for A to continue A cannot do anything whilst B is processing A’s request What is B fails whilst A is waiting for it to complete? What is B needs to handle a high workload of different priority requests? MQ Technical Conference v2.0.1.8 As systems become more Maximum number of Fragility of tight coupling tightly coupled, their connections goes up with reliance on each other the square of increases the number of systems The cost of a failure of a Scaling systems process increases independently to respond to requirements becomes
    [Show full text]
  • Interview Questions Answers . ORG Interviewer and Interviewee Guide
    3/25/2015 MQ Series Interview Questions and Answers Interview Questions Answers . ORG Interviewer And Interviewee Guide Home About Us Contact Us Directory Forum SEARCH MQ Series Questions And Answers All Categories >> Mainframes >> MQ Series >> MQ series job test questions and answers guide. The one who provides the best answers with a perfect presentation is the one who wins the job hunting race. Learn MQ Series and get preparation for the new job ► Question and Answers ► Download eBook Google Cloud Hadoop ► Download Software Rabbit MessageQ CATEGORIES Problems? Linux OS Mainframes Anytime Anywhere Access CICS CLIST (Command List) IBM ADABAS IBM AS400 Honor 4X Dual Sim Phone IBM Assembler IBM COBOL400 hihonor.in/products/mobile/honor4x IBM COOLPLEX Only Rs.10499 with great features High review IBM DB400 score. Order now! IBM MainFrame IBM MVS IBM Natural MQ Series guide updated at 12 Jan 15 in Category Mainframes and visited 571 Times IBM OS 2 IBM OS390 ► MQ Series ► PDF ► Queue ► To PDF Java IBM QMF IBM QSAM IBM REXX Download PDF IBM RPG400 DOWNL OA D MQ S E RIE S QUE S TIONS E B OOK IBM Sysplex IDMS IMS DB Submit Your Question MQ Series Questions and Answers: JCL MQ Series 1 :: What is Dead Letter Queue? VSAM Management ­ When a queue is not delivered to their correct destinations, then it is called as Dead Letter queue Marketing ­ When the destination queue is full, the dead­letter queue occurs. It is identified by Medical SYSTEM.DEAD.LETTER.QUEUE. ­ A dead­letter queue is defined for distributed queuing, on each queue manager Microsoft
    [Show full text]
  • Application Programming with MQ Verbs (Z/OS and Distributed) 17903
    Application Programming with MQ Verbs (z/OS & Distributed) 17903, Dolphin, Oceanic 3, Tues Aug 11th 2015, 3:15 - 4:15pm Mayur Raja IBM Hursley Park, Winchester, UK [email protected] Legal Disclaimer The information contained in this publication is provided for informational purposes only. While efforts were made to verify the completeness and accuracy of the information contained in this publication, it is provided AS IS without warranty of any kind, express or implied. In addition, this information is based on IBM’s current product plans and strategy, which are subject to change by IBM without notice. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, this publication or any other materials. Nothing contained in this publication is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software. References in this presentation to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and/or capabilities referenced in this presentation may change at any time at IBM’s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or feature availability in any way. Nothing contained in these materials is intended to, nor shall have the effect of, stating or implying that any activities undertaken by you will result in any specific sales, revenue growth or other results.
    [Show full text]
  • CICS TS for Z/OS: Using CICS Service Flow Runtime Chapter 1
    CICS Transaction Server for z/OS 5.5 Using CICS Service Flow Runtime IBM Note Before using this information and the product it supports, read the information in “Notices” on page 187. This edition applies to the IBM® CICS® Transaction Server for z/OS® Version 5 Release 5 (product number 5655-Y04) and to all subsequent releases and modifications until otherwise indicated in new editions. © Copyright International Business Machines Corporation 1974, 2020. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents About this PDF.....................................................................................................vii Chapter 1. Product overview..................................................................................1 The runtime environment and BTS..............................................................................................................2 The service flow project tools......................................................................................................................4 Benefits of CICS Service Flow Runtime and service flow project tools..................................................... 5 Server adapters............................................................................................................................................5 Front End Programming Interface (FEPI) server adapter..................................................................... 6 Link3270 server adapter.......................................................................................................................
    [Show full text]
  • Websphere MQ V6 Fundamentals
    Front cover WebSphere MQ V6 Fundamentals Overview of message queuing and WebSphere MQ V6.0 Broad technical introduction to the Websphere MQ product Hands-on guide to the first steps of building a WebSphere MQ infrastructure Saida Davies Peter Broadhurst ibm.com/redbooks International Technical Support Organization WebSphere MQ V6 Fundamentals November 2005 SG24-7128-00 Note: Before using this information and the product it supports, read the information in “Notices” on page xv. First Edition (November 2005) This IBM Redbook edition is an update to the Redpaper MQSeries Primer, REDP-0021. This edition applies to Version 6, Release 0, Modification 0, of IBM WebSphere MQ (product number 5724-H72). © Copyright International Business Machines Corporation 2005. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Notices . xv Trademarks . xvi Preface . xvii The team that wrote this redbook. xvii Become a published author . xix Comments welcome. xx Summary of changes . xxi November 2005 . xxi Chapter 1. Overview . 1 Chapter 2. Concepts of message queuing . 5 2.1 Core concepts . 6 2.1.1 Middleware . 6 2.1.2 Messages . 7 2.1.3 Queues . 7 2.1.4 Point-to-point messaging . 9 2.1.5 Publish/subscribe messaging . 10 2.2 Simplification . 12 2.2.1 Development focuses on business logic . 12 2.2.2 Application maintenance and portability . 13 2.3 Scalability and performance . 14 2.4 Reliability and data integrity . 16 2.4.1 Exactly once delivery . 16 2.4.2 Units of work .
    [Show full text]