Presented in Feb 2015 at Interconnect
This presentation is aimed at helping application developers understand how to best use MQ features for higher performance.
This document discusses IBM MQ clustering and how it provides availability, scalability, and workload balancing. It describes how to set up a basic two node cluster with full repository queue managers and cluster receiver and sender channels. It then discusses more advanced clustering capabilities like supporting multiple applications and global deployments spanning different regions.
IBM Integration Bus & WebSphere MQ - High Availability & Disaster Recovery
This covers the various aspects of configuration IBM Integration Bus when looking to implement a highly available system and comprehensive disaster recovery plan.
IBM MQ provides capabilities to keep data safe and businesses running in the event of failures. This includes solutions for high availability (HA) and disaster recovery (DR) whether running on-premises or in hybrid cloud environments. HA aims to keep systems running through failures while DR focuses on recovering after an HA failure. Key HA technologies in IBM MQ include queue manager clusters, queue sharing groups, multi-instance queue managers, and HA clusters. These solutions provide redundancy to prevent single points of failure and enable fast failover. DR requires replicating data to separate sites which IBM MQ supports through various backup and replication features.
IBM MQ (formerly known as MQSeries) is a middleware messaging product that allows applications on different platforms to communicate asynchronously by sending and receiving messages. It guarantees message delivery and supports advanced features like triggering actions on message receipt. MQ provides a common API for applications to connect to message queues, publish/consume messages, and ensures delivery across heterogeneous systems. It is widely used to integrate legacy mainframe systems with modern platforms.
Compares REST APIs and MQ. Then describes the capabilities of MQ's new built in REST messaging API. Finally covers MQ's support for z/OS Connect EE which is an alternative way of accessing MQ using REST.
IBM MQ certified containers allow MQ to be deployed in containerized environments like Kubernetes. The containers leverage features of IBM Cloud Private like centralized logging, monitoring, and metering. The certified containers also provide high availability and non-root user options to help secure MQ in container deployments.
I presented at the IBM MQ French User Group in Paris on the topic of What's new in MQ. I covered both what was new in IBM MQ 9.3 LTS and what was new in the latest IBM MQ 9.3.1 CD release.
An overview of IBM MQ's high availability capabilities, plus a deeper dive in to the new Replicated Data Queue Manager (RDQM) feature that is available in IBM MQ V9.0.4 on Linux.
Basics of Kafka and IBM Cloud Event Streams. Includes all the major topics of Kafka, like Brokers, Clusters, Topics, Partitions, Producers, Consumers, Streams, and Connectors. What Event Stream offers more than just Kafka. Some difference between Kafka and IBM MQ.
Kafka with IBM Event Streams - Technical Presentation
IBM Event Streams is a fully supported Apache Kafka distribution with additional capabilities. It provides powerful operations tooling, an award-winning user experience, and support that can be trusted. Deployment options include Event Streams on IBM Cloud, Red Hat OpenShift, and Cloud Pak for Integration. Key features include high availability, easy scaling of the Kafka cluster, rolling upgrades, disaster recovery with geo-replication, and connectors to integrate with various data sources.
MQ Series is a middleware product from IBM that enables applications on different platforms to communicate asynchronously through message queues. It provides reliable message delivery and supports various programming languages. MQ Series handles message storage, delivery, and translation between platforms. It is commonly used for distributed inter-system communication, data propagation between mainframe and client systems, and asynchronous event-driven processing.
The document provides an overview of the fundamentals of Websphere MQ including:
- The key MQ objects like messages, queues, channels and how they work
- Basic MQ administration tasks like defining, displaying, altering and deleting MQ objects using MQSC commands
- Hands-on exercises are included to demonstrate programming with MQ and administering MQ objects
A presentation from internal meeting on Message Broker System and RabbitMQ. RabbitMQ is open source message broker software that implements the Advanced Message Queuing Protocol (AMQP).
This document provides an overview of WebSphere MQ Administration training notes. It discusses key concepts in message-oriented middleware including messaging, queuing, MQSeries, and the Message Queue Interface. It also describes common MQ objects like queue managers, queues, channels, and messages. The document outlines how applications use MQ calls to connect to queue managers and put and get messages from queues.
1) The document provides tips for optimizing performance on WebSphere DataPower devices by adjusting caching, enabling persistent connections, using processing rules efficiently, optimizing MQ and XSLT configurations, and leveraging synchronous and asynchronous actions appropriately.
2) It recommends creating a "facade service" to monitor and shape requests to external services like logging servers to prevent slow responses from impacting core transactions. This facade service would use monitors and service level management policies to control latencies.
3) Using separate delegate services with monitoring is suggested to avoid direct connections to external services that could become slow and bottleneck transactions if they degrade in performance.
3450 - Writing and optimising applications for performance in a hybrid messag...
Messaging architectures in any environment, from local standalone deployments through to public clouds, must provide the highest reliability yet maximize their performance. This session gives you an insight into IBM MQ and how applications can be made to perform to their absolute best while maintaining the data integrity that IBM MQ is renowned for. We'll see how this can be achieved through a combination of good application design, system tuning and architectural patterns.
IBM IMPACT 2014 - AMC-1882 Building a Scalable & Continuously Available IBM M...
This document provides an overview of designing a scalable and highly available IBM MQ infrastructure. Key points include:
- Using a client/server architecture with MQ deployed separately from applications provides flexibility and allows MQ to be treated as critical infrastructure similar to a database.
- Each sender should connect to two queue managers and each receiver should have two listeners concurrently attached to provide redundancy and no single point of failure.
- Other topics covered include synchronous request/response, publish/subscribe messaging, limitations for ordered messages, and integrating with IBM Integration Bus.
The document emphasizes an active/active design philosophy with minimum two queue managers and discusses workload management strategies for sending and receiving messages across multiple queue managers.
Hhm 3474 mq messaging technologies and support for high availability and acti...
The document discusses concepts of business continuity including high availability, continuous serviceability, and continuous availability across sites. It then discusses how messaging technologies like IBM MQ can provide various levels of business continuity. Specifically, it provides examples of how MQ can enable active-active configurations across multiple sites for continuous availability through data synchronization and workload distribution. This allows no downtime even during planned or unplanned events.
Enable business continuity and high availability through active active techno...
IBM provides an overview of an active-active solution implemented by China Everbright Bank for their credit card system. The solution uses WebSphere MQ for real-time data synchronization between active sites in Beijing and Shanghai. This allows workload and data to be distributed across both sites for continuous availability in case of an outage. Key components discussed include the messaging architecture, application design considerations for performance, and procedures for planned and unplanned site switches. The implementation provides business continuity for Everbright Bank's credit card processing.
Topic: Speedtest: Benchmark Your Apache Kafka®️
Abstract: In this session, Mark will talk about running benchmarking utilities for Apache Kafka; to determine how much MB/sec a cluster can handle; how to set up automated benchmark runs (including the repo), and using this to find and optimize client-side producer configuration properties
Expanding your options with the IBM MQ Appliance - IBM InterConnect 2016
The document discusses the IBM MQ Appliance, which provides IBM MQ V8 in an appliance form factor for scalable and secure messaging. Key capabilities of the MQ Appliance include:
1) Rapid deployment of queue managers on the appliance with built-in high availability and disaster recovery capabilities that do not require external dependencies.
2) Simplified maintenance through firmware updates that bundle appliance, operating system, and MQ fixpack updates together.
3) Secure administration through local and web-based interfaces, and encryption of messaging using built-in MQ Advanced Message Security.
IBM MQ High Availabillity and Disaster Recovery (2017 version)
This document discusses high availability and disaster recovery strategies for IBM MQ. It describes technologies like queue manager clusters, multi-instance queue managers, and HA clusters that can be used to provide high availability when failures occur across datacenters and clouds. Multi-instance queue managers provide basic failover of a queue manager between two systems without an HA cluster. HA clusters coordinate failover of resources like the queue manager, shared storage, and IP address across multiple machines for increased reliability. The IBM MQ Appliance also supports high availability between two appliances.
Hands on guide to the nuts and bolts of administering an MQ Appliance and key differences from working with a software MQ installation. (Live presentation was accompanied by demonstration of the MQ Console WebUI capabilities - some screenshots included give a flavor).
AME-1934 : Enable Active-Active Messaging Technology to Extend Workload Balan...
Session Type : Breakout Session
Date/Time : Thu, 26-Feb, 10:30 AM-11:30 AM
Venue : Mandalay Bay
Room : Surf Ballroom E
Descriptions:
Active-Active is the target model of modern data center, its successfully adoption includes not only the mainframe, but also the heterogeneous and periphery distributed platforms which makes it much complex to implement. Data synchronization is the heart in the various technologies of active-active, which messaging technology been chose in its implementation.
This session gives an overview of active-active technologies on both z and distributed platforms; highlight how does the Active-Active gives the benefits of both high availability and workload balancing, we also discuss China customer cases to implement messaging based active-active.
Semantic Validation: Enforcing Kafka Data Quality Through Schema-Driven Verif...
"Incorrect data produced into Kafka can be a poison pill that has the potential to disrupt businesses built upon Kafka. The “Semantic Validation” feature is designed to address the challenges posed by incorrect or unexpected data in Kafka’s data processing pipelines, with the goal of mitigating such disruptions. By allowing users to define robust field constraints directly within schemas, such as Avro, we aim to enhance data quality and minimize the downstream impacts of inaccurate data in Kafka.
Furthermore, this feature can be expanded to include offline data processing, in addition to Kafka and Flink real-time processing. By combining real-time processing, batch analytics, and AI data pipelines, a global semantic validation system can be built.
In our upcoming talk, we will delve into the use cases of this feature, discuss its architecture, provide examples of defining rules, and explain how we enforce these rules. Ultimately, we will demonstrate how this feature can significantly enhance reliability and trustworthiness in Uber’s data processing pipelines."
Architecting and Tuning IIB/eXtreme Scale for Maximum Performance and Reliabi...
Abstract: Recent projects have stressed the "need for speed" while handling large amounts of data, with near zero downtime. An analysis of multiple environments has identified optimizations and architectures that improve both performance and reliability. The session covers data gathering and analysis, discussing everything from the network (multiple NICs, nearby catalogs, high speed Ethernet), to the latest features of extreme scale. Performance analysis helps pinpoint where time is spent (bottlenecks) and we discuss optimization techniques (MQ tuning, IIB performance best practices) as well as helpful IBM support pacs. Log Analysis pinpoints system stress points (e.g. CPU starvation) and steps on the path to near zero downtime.
IBM WebSphere MQ: Managing Workloads, Scaling and Availability with MQ ClustersDavid Ware
IBM WebSphere MQ Clustering can be used to solve many problems, from simplified administration and workload management in an MQ network, to horizontal scalability and continuous availability of messaging applications. This session will show the full range of uses of MQ Clusters to solve real problems, highlighting the underlying technology being used.
This has been superseded by http://www.slideshare.net/DavidWare1/ame-2273-mq-clustering-pdf
IBM MQ: An Introduction to Using and Developing with MQ Publish/SubscribeDavid Ware
IBM MQ allows application programmers to use the publish/subscribe application model with ease. This session takes you through the fundamental publish/subscribe concepts and how they relate to IBM MQ. Covering aspects of system design, configuration and application programming, this session is essential for all users looking to adopt publish/subscribe with IBM MQ.
This document discusses IBM MQ clustering and how it provides availability, scalability, and workload balancing. It describes how to set up a basic two node cluster with full repository queue managers and cluster receiver and sender channels. It then discusses more advanced clustering capabilities like supporting multiple applications and global deployments spanning different regions.
IBM Integration Bus & WebSphere MQ - High Availability & Disaster RecoveryRob Convery
This covers the various aspects of configuration IBM Integration Bus when looking to implement a highly available system and comprehensive disaster recovery plan.
IBM MQ - High Availability and Disaster RecoveryMarkTaylorIBM
IBM MQ provides capabilities to keep data safe and businesses running in the event of failures. This includes solutions for high availability (HA) and disaster recovery (DR) whether running on-premises or in hybrid cloud environments. HA aims to keep systems running through failures while DR focuses on recovering after an HA failure. Key HA technologies in IBM MQ include queue manager clusters, queue sharing groups, multi-instance queue managers, and HA clusters. These solutions provide redundancy to prevent single points of failure and enable fast failover. DR requires replicating data to separate sites which IBM MQ supports through various backup and replication features.
IBM MQ (formerly known as MQSeries) is a middleware messaging product that allows applications on different platforms to communicate asynchronously by sending and receiving messages. It guarantees message delivery and supports advanced features like triggering actions on message receipt. MQ provides a common API for applications to connect to message queues, publish/consume messages, and ensures delivery across heterogeneous systems. It is widely used to integrate legacy mainframe systems with modern platforms.
Compares REST APIs and MQ. Then describes the capabilities of MQ's new built in REST messaging API. Finally covers MQ's support for z/OS Connect EE which is an alternative way of accessing MQ using REST.
MQ Guide France - IBM MQ and ContainersRobert Parker
IBM MQ certified containers allow MQ to be deployed in containerized environments like Kubernetes. The containers leverage features of IBM Cloud Private like centralized logging, monitoring, and metering. The certified containers also provide high availability and non-root user options to help secure MQ in container deployments.
IBM MQ Whats new - including 9.3 and 9.3.1Robert Parker
I presented at the IBM MQ French User Group in Paris on the topic of What's new in MQ. I covered both what was new in IBM MQ 9.3 LTS and what was new in the latest IBM MQ 9.3.1 CD release.
IBM Think 2018: IBM MQ High AvailabilityJamie Squibb
An overview of IBM MQ's high availability capabilities, plus a deeper dive in to the new Replicated Data Queue Manager (RDQM) feature that is available in IBM MQ V9.0.4 on Linux.
Basics of Kafka and IBM Cloud Event Streams. Includes all the major topics of Kafka, like Brokers, Clusters, Topics, Partitions, Producers, Consumers, Streams, and Connectors. What Event Stream offers more than just Kafka. Some difference between Kafka and IBM MQ.
Kafka with IBM Event Streams - Technical PresentationWinton Winton
IBM Event Streams is a fully supported Apache Kafka distribution with additional capabilities. It provides powerful operations tooling, an award-winning user experience, and support that can be trusted. Deployment options include Event Streams on IBM Cloud, Red Hat OpenShift, and Cloud Pak for Integration. Key features include high availability, easy scaling of the Kafka cluster, rolling upgrades, disaster recovery with geo-replication, and connectors to integrate with various data sources.
MQ Series is a middleware product from IBM that enables applications on different platforms to communicate asynchronously through message queues. It provides reliable message delivery and supports various programming languages. MQ Series handles message storage, delivery, and translation between platforms. It is commonly used for distributed inter-system communication, data propagation between mainframe and client systems, and asynchronous event-driven processing.
The document provides an overview of the fundamentals of Websphere MQ including:
- The key MQ objects like messages, queues, channels and how they work
- Basic MQ administration tasks like defining, displaying, altering and deleting MQ objects using MQSC commands
- Hands-on exercises are included to demonstrate programming with MQ and administering MQ objects
A presentation from internal meeting on Message Broker System and RabbitMQ. RabbitMQ is open source message broker software that implements the Advanced Message Queuing Protocol (AMQP).
This document provides an overview of WebSphere MQ Administration training notes. It discusses key concepts in message-oriented middleware including messaging, queuing, MQSeries, and the Message Queue Interface. It also describes common MQ objects like queue managers, queues, channels, and messages. The document outlines how applications use MQ calls to connect to queue managers and put and get messages from queues.
1) The document provides tips for optimizing performance on WebSphere DataPower devices by adjusting caching, enabling persistent connections, using processing rules efficiently, optimizing MQ and XSLT configurations, and leveraging synchronous and asynchronous actions appropriately.
2) It recommends creating a "facade service" to monitor and shape requests to external services like logging servers to prevent slow responses from impacting core transactions. This facade service would use monitors and service level management policies to control latencies.
3) Using separate delegate services with monitoring is suggested to avoid direct connections to external services that could become slow and bottleneck transactions if they degrade in performance.
3450 - Writing and optimising applications for performance in a hybrid messag...Timothy McCormick
Messaging architectures in any environment, from local standalone deployments through to public clouds, must provide the highest reliability yet maximize their performance. This session gives you an insight into IBM MQ and how applications can be made to perform to their absolute best while maintaining the data integrity that IBM MQ is renowned for. We'll see how this can be achieved through a combination of good application design, system tuning and architectural patterns.
IBM IMPACT 2014 - AMC-1882 Building a Scalable & Continuously Available IBM M...Peter Broadhurst
This document provides an overview of designing a scalable and highly available IBM MQ infrastructure. Key points include:
- Using a client/server architecture with MQ deployed separately from applications provides flexibility and allows MQ to be treated as critical infrastructure similar to a database.
- Each sender should connect to two queue managers and each receiver should have two listeners concurrently attached to provide redundancy and no single point of failure.
- Other topics covered include synchronous request/response, publish/subscribe messaging, limitations for ordered messages, and integrating with IBM Integration Bus.
The document emphasizes an active/active design philosophy with minimum two queue managers and discusses workload management strategies for sending and receiving messages across multiple queue managers.
Hhm 3474 mq messaging technologies and support for high availability and acti...Pete Siddall
The document discusses concepts of business continuity including high availability, continuous serviceability, and continuous availability across sites. It then discusses how messaging technologies like IBM MQ can provide various levels of business continuity. Specifically, it provides examples of how MQ can enable active-active configurations across multiple sites for continuous availability through data synchronization and workload distribution. This allows no downtime even during planned or unplanned events.
Enable business continuity and high availability through active active techno...Qian Li Jin
IBM provides an overview of an active-active solution implemented by China Everbright Bank for their credit card system. The solution uses WebSphere MQ for real-time data synchronization between active sites in Beijing and Shanghai. This allows workload and data to be distributed across both sites for continuous availability in case of an outage. Key components discussed include the messaging architecture, application design considerations for performance, and procedures for planned and unplanned site switches. The implementation provides business continuity for Everbright Bank's credit card processing.
Topic: Speedtest: Benchmark Your Apache Kafka®️
Abstract: In this session, Mark will talk about running benchmarking utilities for Apache Kafka; to determine how much MB/sec a cluster can handle; how to set up automated benchmark runs (including the repo), and using this to find and optimize client-side producer configuration properties
Expanding your options with the IBM MQ Appliance - IBM InterConnect 2016Leif Davidsen
The document discusses the IBM MQ Appliance, which provides IBM MQ V8 in an appliance form factor for scalable and secure messaging. Key capabilities of the MQ Appliance include:
1) Rapid deployment of queue managers on the appliance with built-in high availability and disaster recovery capabilities that do not require external dependencies.
2) Simplified maintenance through firmware updates that bundle appliance, operating system, and MQ fixpack updates together.
3) Secure administration through local and web-based interfaces, and encryption of messaging using built-in MQ Advanced Message Security.
IBM MQ High Availabillity and Disaster Recovery (2017 version)MarkTaylorIBM
This document discusses high availability and disaster recovery strategies for IBM MQ. It describes technologies like queue manager clusters, multi-instance queue managers, and HA clusters that can be used to provide high availability when failures occur across datacenters and clouds. Multi-instance queue managers provide basic failover of a queue manager between two systems without an HA cluster. HA clusters coordinate failover of resources like the queue manager, shared storage, and IP address across multiple machines for increased reliability. The IBM MQ Appliance also supports high availability between two appliances.
Hands on guide to the nuts and bolts of administering an MQ Appliance and key differences from working with a software MQ installation. (Live presentation was accompanied by demonstration of the MQ Console WebUI capabilities - some screenshots included give a flavor).
AME-1934 : Enable Active-Active Messaging Technology to Extend Workload Balan...wangbo626
Session Type : Breakout Session
Date/Time : Thu, 26-Feb, 10:30 AM-11:30 AM
Venue : Mandalay Bay
Room : Surf Ballroom E
Descriptions:
Active-Active is the target model of modern data center, its successfully adoption includes not only the mainframe, but also the heterogeneous and periphery distributed platforms which makes it much complex to implement. Data synchronization is the heart in the various technologies of active-active, which messaging technology been chose in its implementation.
This session gives an overview of active-active technologies on both z and distributed platforms; highlight how does the Active-Active gives the benefits of both high availability and workload balancing, we also discuss China customer cases to implement messaging based active-active.
Semantic Validation: Enforcing Kafka Data Quality Through Schema-Driven Verif...HostedbyConfluent
"Incorrect data produced into Kafka can be a poison pill that has the potential to disrupt businesses built upon Kafka. The “Semantic Validation” feature is designed to address the challenges posed by incorrect or unexpected data in Kafka’s data processing pipelines, with the goal of mitigating such disruptions. By allowing users to define robust field constraints directly within schemas, such as Avro, we aim to enhance data quality and minimize the downstream impacts of inaccurate data in Kafka.
Furthermore, this feature can be expanded to include offline data processing, in addition to Kafka and Flink real-time processing. By combining real-time processing, batch analytics, and AI data pipelines, a global semantic validation system can be built.
In our upcoming talk, we will delve into the use cases of this feature, discuss its architecture, provide examples of defining rules, and explain how we enforce these rules. Ultimately, we will demonstrate how this feature can significantly enhance reliability and trustworthiness in Uber’s data processing pipelines."
Architecting and Tuning IIB/eXtreme Scale for Maximum Performance and Reliabi...Prolifics
Abstract: Recent projects have stressed the "need for speed" while handling large amounts of data, with near zero downtime. An analysis of multiple environments has identified optimizations and architectures that improve both performance and reliability. The session covers data gathering and analysis, discussing everything from the network (multiple NICs, nearby catalogs, high speed Ethernet), to the latest features of extreme scale. Performance analysis helps pinpoint where time is spent (bottlenecks) and we discuss optimization techniques (MQ tuning, IIB performance best practices) as well as helpful IBM support pacs. Log Analysis pinpoints system stress points (e.g. CPU starvation) and steps on the path to near zero downtime.
IBM IMPACT 2014 AMC-1866 Introduction to IBM Messaging CapabilitiesPeter Broadhurst
IBM Messaging provides market-leading capabilities for anywhere-to-anywhere integration across mobile, cloud, and enterprise platforms - from the simplest pair of applications requiring basic connectivity and data exchange, to the most complex business process management environments. Come to this session to understand the value and rationale of message/queuing and the IBM Messaging family of products; its key features and functions; and how it can be used to build a secure, flexible, and scalable messaging backbone for a business.
Hpe service virtualization 3.8 what's new chicago admJeffrey Nunn
Service Virtualization is an HPE branded solution that helps simulate and emulate the behavior of specific components in heterogeneous component-based applications such as API-driven apps, ERP apps, cloud-based apps, and web services/service-oriented architectures (SOA).
Value Proposition
Empowers developers and testers to easily automate, predict, accelerate and scale their application testing and delivery through virtualization and simulation of dependent components and services that are either off limits, unavailable, inaccessible, or with costly fees to access.
The document introduces the IBM MQ Appliance, which provides IBM MQ messaging capabilities in an appliance form factor for simplified deployment and administration. Key features include built-in high availability without external dependencies, scalable security administration using LDAP, and connectivity via MQ client and server protocols. The appliance is available in two models to suit different performance and capacity needs.
The document provides an overview of Confluent Control Center and how it can be used to monitor Apache Kafka deployments. It discusses how Control Center provides visibility into key metrics for brokers, topics, consumers and connectors. It also describes how Control Center helps answer important business questions about whether applications are receiving all data, showing the latest data, if the applications or cluster need to scale, and ensures data is not lost. Control Center provides dashboards, alerts and visibility to help operators effectively manage Kafka clusters and identify and address issues.
This document provides guidelines for capturing and formatting test content for popular applications to be used on the Mu Dynamics test platform. It describes how to capture packet capture (PCAP) files using Wireshark for non-HTTP applications, and HTTP Archive (HAR) files using Firebug for HTTP-based applications. The steps include installing the necessary software, capturing representative application traffic, filtering the captures, generating scenarios in the Mu platform, and validating the scenarios. Standards are also defined for naming, formatting and describing the scenario files, JSON metadata files and PCAP/HAR captures to ensure consistency.
Using Kubernetes to make cellular data plans cheaper for 50M usersMirantis
Use case of Kubernetes based NFV infrastructure used in production to run an open source evolved packet core. Presented by Facebook Connectivity and Mirantis at KubeCon + CloudNativeCon Europe 2020.
Similar to IBM MQ - better application performance (20)
IBM MQ V9 provides a new optional delivery model with two streams: a long-term support stream for stability and a rapid function delivery stream. It includes features like central provisioning of client configuration, a new quality of service for Advanced Message Security called Confidentiality, and LDAP authorization support for Windows clients. Activity trace information can now be subscribed to via publish/subscribe without additional configuration.
IBM MQ - Monitoring and Managing Hybrid Messaging EnvironmentsMarkTaylorIBM
This presentation was given at Interconnect 2016. It starts by showing the interfaces within MQ for management and monitoring, and then shows how these are used within a cloud environment to control the delivery of a service-based messaging system.
IBM MQ Version 8.0.0.4 includes new features such as message expiry caps, event formatting samples, command and configuration events for security changes, and integration of MQLight. It also improves SSL/TLS configuration verification and provides a relocatable MQ client. Future plans include more frequent delivery of incremental changes.
The document discusses the benefits of meditation for reducing stress and anxiety. Regular meditation practice can help calm the mind and body by lowering heart rate and blood pressure. Studies have shown that meditating for just 10-20 minutes per day can have significant positive impacts on both mental and physical health over time.
A review of new features in IBM's premier messaging product.
After a short look at 2013 updates, it gives an overview of all features of the V8 release. Other presentations go into deeper details on some of these features, but this gives the essential flavour for it all.
Efficient hot work permit software for safe, streamlined work permit management and compliance. Enhance safety today. Contact us on +353 214536034.
https://sheqnetwork.com/work-permit/
COMPSAC 2024 D&I Panel: Charting a Course for Equity: Strategies for Overcomi...Hironori Washizaki
Hironori Washizaki, "Charting a Course for Equity: Strategies for Overcoming Challenges and Promoting Inclusion in the Metaverse", IEEE COMPSAC 2024 D&I Panel, 2024.
What is OCR Technology and How to Extract Text from Any Image for FreeTwisterTools
Discover the fascinating world of Optical Character Recognition (OCR) technology with our comprehensive presentation. Learn how OCR converts various types of documents, such as scanned paper documents, PDFs, or images captured by a digital camera, into editable and searchable data. Dive into the history, modern applications, and future trends of OCR technology. Get step-by-step instructions on how to extract text from any image online for free using a simple tool, along with best practices for OCR image preparation. Ideal for professionals, students, and tech enthusiasts looking to harness the power of OCR.
Ansys Mechanical enables you to solve complex structural engineering problems and make better, faster design decisions. With the finite element analysis (FEA) solvers available in the suite, you can customize and automate solutions for your structural mechanics problems and parameterize them to analyze multiple design scenarios. Ansys Mechanical is a dynamic tool that has a complete range of analysis tools.
An MVP (Minimum Viable Product) mobile application is a streamlined version of a mobile app that includes only the core features necessary to address the primary needs of its users. The purpose of an MVP is to validate the app concept with minimal resources, gather user feedback, and identify any areas for improvement before investing in a full-scale development. This approach allows businesses to quickly launch their app, test its market viability, and make data-driven decisions for future enhancements, ensuring a higher likelihood of success and user satisfaction.
Are you wondering how to migrate to the Cloud? At the ITB session, we addressed the challenge of managing multiple ColdFusion licenses and AWS EC2 instances. Discover how you can consolidate with just one EC2 instance capable of running over 50 apps using CommandBox ColdFusion. This solution supports both ColdFusion flavors and includes cb-websites, a GoLang binary for managing CommandBox websites.
IN Dubai [WHATSAPP:Only (+971588192166**)] Abortion Pills For Sale In Dubai** UAE** Mifepristone and Misoprostol Tablets Available In Dubai** UAE
CONTACT DR. SINDY Whatsapp +971588192166* We Have Abortion Pills / Cytotec Tablets /Mifegest Kit Available in Dubai** Sharjah** Abudhabi** Ajman** Alain** Fujairah** Ras Al Khaimah** Umm Al Quwain** UAE** Buy cytotec in Dubai +971588192166* '''Abortion Pills near me DUBAI | ABU DHABI|UAE. Price of Misoprostol** Cytotec” +971588192166* ' Dr.SINDY ''BUY ABORTION PILLS MIFEGEST KIT** MISOPROSTOL** CYTOTEC PILLS IN DUBAI** ABU DHABI**UAE'' Contact me now via What's App… abortion pills in dubai Mtp-Kit Prices
abortion pills available in dubai/abortion pills for sale in dubai/abortion pills in uae/cytotec dubai/abortion pills in abu dhabi/abortion pills available in abu dhabi/abortion tablets in uae
… abortion Pills Cytotec also available Oman Qatar Doha Saudi Arabia Bahrain Above all** Cytotec Abortion Pills are Available In Dubai / UAE** you will be very happy to do abortion in Dubai we are providing cytotec 200mg abortion pills in Dubai** UAE. Medication abortion offers an alternative to Surgical Abortion for women in the early weeks of pregnancy. We only offer abortion pills from 1 week-6 Months. We then advise you to use surgery if it's beyond 6 months. Our Abu Dhabi** Ajman** Al Ain** Dubai** Fujairah** Ras Al Khaimah (RAK)** Sharjah** Umm Al Quwain (UAQ) United Arab Emirates Abortion Clinic provides the safest and most advanced techniques for providing non-surgical** medical and surgical abortion methods for early through late second trimester** including the Abortion By Pill Procedure (RU 486** Mifeprex** Mifepristone** early options French Abortion Pill)** Tamoxifen** Methotrexate and Cytotec (Misoprostol). The Abu Dhabi** United Arab Emirates Abortion Clinic performs Same Day Abortion Procedure using medications that are taken on the first day of the office visit and will cause the abortion to occur generally within 4 to 6 hours (as early as 30 minutes) for patients who are 3 to 12 weeks pregnant. When Mifepristone and Misoprostol are used** 50% of patients complete in 4 to 6 hours; 75% to 80% in 12 hours; and 90% in 24 hours. We use a regimen that allows for completion without the need for surgery 99% of the time. All advanced second trimester and late term pregnancies at our Tampa clinic (17 to 24 weeks or greater) can be completed within 24 hours or less 99% of the time without the need for surgery. The procedure is completed with minimal to no complications. Our Women's Health Center located in Abu Dhabi** United Arab Emirates** uses the latest medications for medical abortions (RU-486** Mifeprex** Mifegyne** Mifepristone** early options French abortion pill)** Methotrexate and Cytotec (Misoprostol). The safety standards of our Abu Dhabi** United Arab Emirates Abortion Doctors remain unparalleled. They consistently maintain the lowest complication rates throughout the nation. Our
A captivating AI chatbot PowerPoint presentation is made with a striking backdrop in order to attract a wider audience. Select this template featuring several AI chatbot visuals to boost audience engagement and spontaneity. With the aid of this multi-colored template, you may make a compelling presentation and get extra bonuses. To easily elucidate your ideas, choose a typeface with vibrant colors. You can include your data regarding utilizing the chatbot methodology to the remaining half of the template.
2. Please Note
IBM’s statements regarding its plans, directions, and intent are subject to change
or withdrawal without notice at IBM’s sole discretion.
Information regarding potential future products is intended to outline our general
product direction and it should not be relied on in making a purchasing decision.
The information mentioned regarding potential future products is not a
commitment, promise, or legal obligation to deliver any material, code or
functionality. Information about potential future products may not be incorporated
into any contract. The development, release, and timing of any future features or
functionality described for our products remains at our sole discretion.
Performance is based on measurements and projections using standard IBM
benchmarks in a controlled environment. The actual throughput or performance
that any user will experience will vary depending upon many factors, including
considerations such as the amount of multiprogramming in the user’s job stream,
the I/O configuration, the storage configuration, and the workload processed.
Therefore, no assurance can be given that an individual user will achieve results
similar to those stated here.
3. Agenda
• Some performance numbers
• Structure of the Queue Manager
• Function Walkthroughs
• Client Channels
• Logging and Recovery
4. Agenda
• Some performance numbers
• Structure of the Queue Manager
• Function Walkthroughs
• Client Channels
• Logging and Recovery
5. Performance Bottlenecks
• Business Systems are complex
‒ Often no single bottleneck limiting performance
‒ Performance can mean different things to different people
‒ Throughput
Scalability
Low resource usage
• Not only limited by physical resources
‒ Application design, such as parallelism can have major effect
• Performance Reports (from SupportPac site) show range of
scenarios
RAM CPU NetworkI/O
Bottlenecks
9. Distributed Performance in V8
• Improvements to distributed queue manager scaling
‒ Improve efficiency
‒ Better exploitation of wider SMP machines
‒ Looking at customer-provided application patterns not just benchmarks
Always happy to have more customer examples
• Multiplexed client performance
‒ Increase the performance of multiplexed client channels (SHRCONV > 0)
‒ Especially for SHRCONV=1
• Other areas that helped:
‒ Cache alignment for internal structures
‒ Extended 64-bit exploitation for locking primitives
‒ RFH2 handling, particularly for waiting-getter
Fewer copies of data are needed
‒ Better compiler optimisations including feedback-directed optimisation
‒ Faster data conversion (especially for 1208)
Many messages are in 1208 codepage
Optimised handling when the queue manager needs to convert them
10. Agenda
• What is distributed WebSphere MQ?
• Structure of the Queue Manager
• Function Walkthroughs
• Client Channels
• Logging and Recovery
13. Agenda
• What is distributed WebSphere MQ?
• Structure of the Queue Manager
• Function Walkthroughs
• Client Channels
• Logging and Recovery
14. MQI Stub
Application
IPCC
Execution
Controller
IPCC
IPCC
DAP
Kernel
Agent
IPCC
Application (MQI Stub)
Verify parameters and handles
Construct a Connect message
Call API crossing exit
Send a message to the EC
Application (MQI Stub)
Receive the reply
Construct an IPCC message
Send the message to the agent
Application (MQI Stub)
Receive reply and call API crossing exit
Return HCONN
Execution Controller
Choose an agent or start a new one
Construct a reply IPCC message
Return reply to application
Agent
Check App's permission to connect
Allocate and assign agent resources
Send IPCC reply back to application
MQCONN
15. Performance Implications: Connection Binding
• Fastpath binding removes inter-process communications
‒ Implies that the application is 'trusted'
‒ MQCONNX option MQCNO_FASTPATH_BINDING
‒ Application failure can corrupt queue manager
• Primary benefit is for non-persistent message processing
‒ Use for MCAs, Broker
- 30% CPU saving
MQ
Appl
Agent
Memory
Log
IPC
Standard
Binding
MQ
Appl
Agent
Memory
Log
FASTPATH
Binding
17. Application (MQI Stub)
Verify hConn
Call API crossing exit
Verify parameter addressability
Place parameters in an Open message
Send an IPCC message to the agent
MQI Stub
Application
IPCC
DAP
Kernel
Agent
IPCC
Agent
Application interface
Verify open parameters
Kernel
Verify operation validity
Resolve target – including cluster lookup
Check permissions on the queue
DAP
Load the queue ready for gets and puts if required
ƒThis is the part that can use system resources
Kernel
Generate handle to object for application
Generate responses and event messages
IPCC
Send reply back to application
Application (MQI Stub)
Receive reply
Call API crossing exit
Return HOBJ
MQOPEN of a queue
18. MQOPEN internal changes for V8
• The object catalog is the list of objects and a map to the real files
‒ Shows that queue 'X.Y' is stored in "/var/mqm/qmgrs/<qm>/queues/X!Y"
‒ dspmqfls command shows the map
‒ Updated whenever an object is created or deleted
• In MQ V7 there were just two locks associated with the object catalog
‒ A significant implication of this scheme was that an MQOPEN could not
overlap with the creation/deletion of a queue (or any other object)
‒ Ghost queues introduced in MQ V5.2 went some way to reducing the impact,
particularly for TDQ’s, but very significant serialization implications remained.
• MQ V8 uses finer grained locks
‒ The master mutex need not be owned while waiting for the object mutex.
• The most significant impact of this serialization change is that dynamic
queues can now be created and destroyed concurrently with MQOPEN
activity
27
19. Performance Implications: Heavyweight MQI Calls
• MQCONN is a “heavy” operation
‒ Don’t let your application do lots of them
‒ Wrappers and OO interfaces can sometimes hide what’s really happening
‒ Lots of MQCONNs can drop throughput from 1000s Msgs/Sec to 10s
Msgs/Sec
• MQOPEN is also ‘heavy’ compared to MQPUT/MQGET
‒ Depends on the type of queue and whether first use
Loading pre-existing queue; creating dynamic queue
‒ It’s where we do the security check
Try to cache queue handles if more than one message
‒ If you’re only putting one message consider using MQPUT1
Particularly client bindings
• Try to avoid exclusive access to the Queue
‒ Makes it harder to scale the solution
For example adding more instances of application
‒ Implies that reliance on message order is not required
Partition the data to allow parallel processing?
21. Tuning Queue Buffers
• Increasing buffers can improve performance
‒ More information can be kept in memory, without flushing to disk
‒ Costs more memory per modified queue
• But no documented external mechanism to do it
‒ Performance supportpacs indicate how to do it
‒ DefaultQBufferSize / DefaultPQBufferSize
‒ SupportPac MS0P (Cat2 – ie “as-is”) includes “QTune” program
c:> java -jar qtune.jar -d c:mqmqmgrsQMAqueuesSYSTEM!DEFAULT!LOCAL!QUEUE
File c:mqmqmgrsQMAqueuesSYSTEM!DEFAULT!LOCAL!QUEUEq
Stored npBuff = 64 kB
Stored pBuff = QMgr default
Stored maxQSize = 2,097,151 MB
22. Performance Implications: Persistence
• Log bandwidth is going to restrict throughput
‒ Put the log files on the fastest disks you have, separate from queue file
‒ Persistent messages are the main things requiring recovery after an outage
‒ Can significantly affect restart times
• Why use persistence?
‒ False assumption that persistence is for "important" data and nonpersistent for
when you don't care
‒ The real reason for persistent messages is to reduce application complexity
‒ With persistent, apps do not need logic to detect and deal with lost messages
‒ If your app (or operational procedures) can detect and deal with lost
messages, then you do not need to use persistent messages
• Understand which apps use persistence
MQPUT Queue File
Log
23. Kernel
Verify operation validity
(Resolve cluster queue destination)
DAP
Reserve space for the message data
If (persistent message)
Write log records for the update
(Wait for log records to reach the disk if outside syncpoint)
Write the message to the queue file
Else (non-persistent)
If (space available in queue buffer)
Copy the message data into the buffer
Else
Write the message to the queue file without logging
Maintain queue statistics such as queue depth
Kernel
Generate responses and events, wakeup getters/drive async consumers
Serialised
MQPUT Walkthrough
Also check for "if waiting getter"
Tip!
Use persistent messages with
syncpoint
24. Put to a waiting getter
• MQPUT most efficient if there is getting application waiting
‒ Having multiple applications processing queue increases percentage
‒ May not appear ‘balanced’ – May keep one ‘hot’
• Only for out of syncpoint messages
‒ Both persistent and non-persistent
‒ If Persistent outside of syncpoint, think carefully about why using persistence
Got message could be lost if crash before returning to the application!
• No queuing required
‒ Removes a lot of processing of placing the message onto the queue
• Significantly reduces CPU cost and improves throughput
‒ Lots of improvements on this area in newest releases (7.1, 7.5)
MQPUT MQGET
MQGET
MQGET
25. Kernel
Verify operation validity
Check message expiry
Wait for message if not available
DAP
Locate a message meeting the requested criteria including
current browse cursor position
priority
message id, correlation id, segment or group conditions
Copy data into the message buffer
If (persistent)
Write log record
(Wait for log record to reach the disk if outside syncpoint)
Move the browse cursor if required
Maintain queue statistics such as queue depth
Kernel
Generate responses and events
Serialised
MQGET Walkthrough
Tip!
In request reply model, get by correlid
more efficient than get by msgid
26. Kernel
Verify operation validity
DAP
Write log record to end transaction
Wait for this log record to reach the disk
Lock all queues touched in this transaction
For each queue
Make any changes to messages in the transaction visible
Unlock queue
Kernel
Generate responses and events
Wakeup Getters/Drive Async Consumers
MQCMIT Walkthrough
Deal with 2PC protocol if in an
XA transaction
27. Performance Implications: Syncpoint
• Do you need it?
‒ Yes, when a set of work needs to either all be performed, or all not performed
• Maximum Size of UOW can be limited
‒ QMGR MAXUMSGS parm
‒ Set to sensible value to avoid runaway applications
• Make sure you keep the size of your UOWs small
‒ Don’t forget to end the UOW
• Cheaper to process in syncpoint for persistent messages
‒ Up to a point, not huge UOWs
‒ Log not forced after every MQPUT/MQGET
• Useful even when only a single message inside syncpoint
‒ And running multiple parallel applications
28. Good Application Design - Summary
• Long-running connection
• Opens queues up-front
• Uses syncpoint for persistent operations
• No message affinities so multiple instances can run in parallel
29. Publish/Subscribe Implementation from V7
• MQOPEN, MQPUT, MQGET very similar to point-to-point
‒ Includes cluster resolution
‒ Need to find closest admin topic node
‒ Internal subscribers may forward publication to another queue manager
• Durable Subscriptions held on SYSTEM.DURABLE.SUBSCRIBER.QUEUE
‒ Multiple subscriptions consolidated into single message
‒ Why is there no non-durable subscriber queue?
‒ Retained publications also stored on a queue
• Handling application abend
‒ V6 cleanup for non-durable subs was “automatic” for JMS, manual otherwise
‒ Automatic for V7+
• Managed destinations
‒ Agent creates queue in MQSUB - trace shows internal MQOPEN (kqiOpenModel)
• Parallel match-space access via shared memory set
‒ Several applications can publish simultaneously on the same topic
‒ Lock held during subscribe/unsubscribe processing
30. Message Processing
• Persistent pubs switch to non-persistent-ish for non-durable
subscriptions
‒ Does not change the reliability level
‒ Messages are not logged, but they keep the “persistent” flag
‒ Improves performance
• Properties stored as part of the message
‒ Logged for persistence, rcdmqimg etc
‒ Written to disk in either RFH2 or an “internal” format
‒ Converted to application-required format during MQGET
• Selectors on queues can cause all messages to be browsed
‒ Queue lock may be held during selection
31. Agenda
• What is distributed WebSphere MQ?
• Structure of the Queue Manager
• Function Walkthroughs
• Client Channels
• Logging and Recovery
• Multiple Installation Support
32. Clients from V7
• Many changes to the client protocols in V7
‒ All can improve performance
• Multiplexing or Shared Conversations
‒ For multi-threaded applications
‒ Several connections use the same socket
• Asynchronous Put
‒ For sending applications
• Read-ahead
‒ For receiving applications
• New threads inside application for full-duplex comms
‒ Sharecnv(0) – May be fast but no full-duplex so miss good functionality
‒ Sharecnv(1) – One socket per hconn, optimised in V8 - recommended value
‒ Sharecvn(10) – Shared socket for multiple conversations (default value)
35. Client Connection Performance.
• Lots of internal changes at V8
‒ Channel status table restructure
‒ Reduce cost of health checking (MQIBindType=FASTPATH)
‒ Keep a hash table of processes, each with a sub-list of threads.
‒ Reduce cost of creating/deleting TDQ’s
‒ Channel process pooling pre-start
• Net effect of all of these changes is significant improvement to the queue
manager’s ability to accept a large number of inbound connections in a
relatively short time.
• In one test the time taken to attach 50,000 clients, with each client
owning a TDQ, reduced from over an hour at 7.0.1.6 to under 4 minutes
at MQ V8.
59
36. Agenda
• What is distributed WebSphere MQ?
• Structure of the Queue Manager
• Function Walkthroughs
• Channels
• Logging and Recovery
• Multiple Installation Support
37. What's the point of logging?
• A log record is written for each persistent update
‒ The log record describes the update
• Optimisations to minimise serialisation points
• Write-Ahead Logging
‒ The log is always more up-to-date than the actual data
• Log is a sequential file
‒ Sequential I/O is much quicker than random
‒ Single point of writing rather than to individual object files
• Log and actual data are reconciled during strmqm
‒ Progress information displayed
• Point of consistency – Checkpoint
‒ Log control file: amqhlctl.lfh – in log directory
‒ Checkpoint amqalchk.fil – qmgr directory
‒ Backup queue managers from MQ V6
Myth!
Triple write integrity does not mean
we write all data 3 times!
38. Looking at logger performance
• Can extract internal information from a service tool
‒ Lots of MQ performance PMRs turn out to be disk-related. So recording was
added to the internal state
amqldmpa –c H –m <qmgr> -d 8 –n <count> -s <interval> -f <file>
‒ The amqldmpa program can dump lots of other internal information too
• Includes logger I/O activity
‒ WriteTimeMax shows maximum time (microseconds) to complete I/O
‒ WriteSizeMax shows largest (bytes) I/O
‒ Since qmgr started
• Maintains averages
‒ WriteSizeShort is short-term (64-sample) weighted average of recent writes
‒ WriteSizeLong is longer-term (1024-sample) weighted average
‒ Similarly for WriteTimeShort/Long
• From one PMR:
‒ WriteTimeMax = 59102377, WriteSizeMax=2097152
‒ So it has taken nearly 60 seconds to write 2MB
‒ Implies they need to talk to disk support team!
39. Summary – understand the applications
• Understand the application pattern
‒ Exclusivity, affinity
• Understand the individual application
‒ Many times have heard "it's using persistence" when it's not. Or vice versa.
• If you don't have access to application source, tools exist to help
‒ Application Activity Reports
‒ MQ Trace
41. Notices and Disclaimers (con’t)
Information concerning non-IBM products was obtained from the suppliers of those products, their published
announcements or other publicly available sources. IBM has not tested those products in connection with this
publication and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM
products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.
IBM does not warrant the quality of any third-party products, or the ability of any such third-party products to
interoperate with IBM’s products. IBM EXPRESSLY DISCLAIMS ALL WARRANTIES, EXPRESSED OR IMPLIED,
INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE.
The provision of the information contained herein is not intended to, and does not, grant any right or license under any
IBM patents, copyrights, trademarks or other intellectual property right.
• IBM, the IBM logo, ibm.com, Bluemix, Blueworks Live, CICS, Clearcase, DOORS®, Enterprise Document
Management System™, Global Business Services ®, Global Technology Services ®, Information on Demand,
ILOG, Maximo®, MQIntegrator®, MQSeries®, Netcool®, OMEGAMON, OpenPower, PureAnalytics™,
PureApplication®, pureCluster™, PureCoverage®, PureData®, PureExperience®, PureFlex®, pureQuery®,
pureScale®, PureSystems®, QRadar®, Rational®, Rhapsody®, SoDA, SPSS, StoredIQ, Tivoli®, Trusteer®,
urban{code}®, Watson, WebSphere®, Worklight®, X-Force® and System z® Z/OS, are trademarks of
International Business Machines Corporation, registered in many jurisdictions worldwide. Other product and
service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on
the Web at "Copyright and trademark information" at: www.ibm.com/legal/copytrade.shtml.
42. Thank You
Your Feedback is
Important!
Access the InterConnect 2015
Conference CONNECT Attendee
Portal to complete your session
surveys from your smartphone,
laptop or conference kiosk.