This document discusses various clustering scenarios for WebSphere MQ, beginning with a simple initial setup and expanding in complexity. It addresses scenarios like workload balancing, high availability during failures, and location dependencies when applications and services are distributed across data centers separated by large distances. Key points covered include using queue aliases, cluster workload priorities, and the AMQSCLM monitoring tool to help direct messages to available instances of services and ensure responses can be routed properly even if client or queue manager failures occur.
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.
Building a Highly available messaging hub using the IBM MQ ApplianceAnthony Beardsmore
The MQ Appliance includes two key facilities for maintaining the availability of your messaging infrastructure across expected and unexpected outages. This session looks in depth at the HA and DR capabilities of the MQ Appliance and application considerations when using them.
IBM IMPACT 2014 - AMC-1883 - Where's My Message - Analyze IBM WebSphere MQ Re...Peter Broadhurst
Every MQ infrastructure team member has been asked the question, and most developers who have worked with MQ have asked it: "Where is my message?". In this session we look into the tools that MQ provides to find your messages. We demonstrate how to analyze the MQ recovery log on distributed platforms to find out what happened to your persistent messages, with the assistance of a new tool. We also look at how to trace the route messages take through your MQ infrastructure, and how to generate and analyze activity reports showing the behavior of MQ applications.
This document discusses high availability and disaster recovery strategies for IBM MQ. It introduces concepts like multi-instance queue managers, HA clusters, and MQ appliance HA groups that provide redundancy and failover capabilities. Automatic client reconnection is also covered, which allows MQ clients to seamlessly reconnect after a queue manager failure.
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 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.
Hhm 3479 mq clustering and shared queues for high availabilityPete Siddall
we review clustering and shared queue technologies, their differences and synergies, as a foundation for building a highly available messaging service with resilience during both planned and unplanned outages of z Systems components.
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.
Building a Highly available messaging hub using the IBM MQ ApplianceAnthony Beardsmore
The MQ Appliance includes two key facilities for maintaining the availability of your messaging infrastructure across expected and unexpected outages. This session looks in depth at the HA and DR capabilities of the MQ Appliance and application considerations when using them.
IBM IMPACT 2014 - AMC-1883 - Where's My Message - Analyze IBM WebSphere MQ Re...Peter Broadhurst
Every MQ infrastructure team member has been asked the question, and most developers who have worked with MQ have asked it: "Where is my message?". In this session we look into the tools that MQ provides to find your messages. We demonstrate how to analyze the MQ recovery log on distributed platforms to find out what happened to your persistent messages, with the assistance of a new tool. We also look at how to trace the route messages take through your MQ infrastructure, and how to generate and analyze activity reports showing the behavior of MQ applications.
This document discusses high availability and disaster recovery strategies for IBM MQ. It introduces concepts like multi-instance queue managers, HA clusters, and MQ appliance HA groups that provide redundancy and failover capabilities. Automatic client reconnection is also covered, which allows MQ clients to seamlessly reconnect after a queue manager failure.
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 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.
Hhm 3479 mq clustering and shared queues for high availabilityPete Siddall
we review clustering and shared queue technologies, their differences and synergies, as a foundation for building a highly available messaging service with resilience during both planned and unplanned outages of z Systems components.
Building highly available architectures with WAS and MQMatthew White
Abstract:
'This talk will look at architectures in which IBM MQ can be configured with the IBM WebSphere Application Server (and Liberty profiles) to give a highly-available scenario.
The basis be some of the scenarios that are documented in the developerWorks series "A flexible and scalable WebSphere MQ topology pattern". '
Aims:
Outline some of the technologies and features that can be used for High Availability
Consider some of the implications of technology choices
Provide references for further study
Find out what scenarios and concerns are of most interest
i.e. what should be developing next!
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.
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 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
Integrating cloud applications with your existing systems of record is essential to create truly engaging applications, and messaging is the secret ingredient when linking these worlds together. This session will cover what's new in IBM MQ version 8, and more recent enhancements, which can be used to create an efficient and reliable messaging infrastructure whether on-premise or in the cloud. Featured cloud integration points will include: how you combine MQ 8 with MQ Light to enable developers to join their newly created applications into your existing infrastructure, how to extend your on-premise MQ infrastructure into the cloud taking advantage of cloud deployment technologies such as Docker, and IBM's Message Hub.
IBM MQ - better application performanceMarkTaylorIBM
Presented in Feb 2015 at Interconnect
This presentation is aimed at helping application developers understand how to best use MQ features for higher performance.
These charts provide a high-level overview of IIB HA topologies:
• Comparison of active/active and active/passive HA
• Solutions for active/passive HA failover with IBM Integration Bus
• Solutions for active/active processing with IBM Integration Bus
• Adding Global Cache to active/active processing
• Combining all of the above
Only HTTP and JMS (MQ) workloads are shown
The document provides an introduction to the IBM MQ Appliance, including its key capabilities and differences from a traditional MQ software deployment. It highlights that the appliance provides the scalability and security of IBM MQ V8 in an optimized appliance form factor. The appliance allows for familiar administration through the MQ command line interface and MQ Explorer, while also providing a new browser-based web UI for management. It also includes built-in high availability without external dependencies.
The document introduces the IBM MQ Appliance, a new physical appliance that runs IBM MQ version 8 to simplify enterprise messaging networks. The appliance offers the scalability, security and administration of IBM MQ in a pre-configured hardware device to provide ease of deployment and management. It is intended to serve as a messaging hub, outpost, gateway or for partner connectivity in a standardized, low-cost and high availability configuration.
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).
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: Managing Workloads, Scaling and Availability with MQ ClustersDavid Ware
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. A basic understanding of IBM MQ clustering would be beneficial.
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.
HHM-3540: The IBM MQ Light API: From Developer Laptop to Enterprise Data Cen...Matt Leming
The IBM MQ Light API makes it simple for developers to create responsive applications that are easy to scale without having to become messaging experts. Increasingly, development teams choose from a wide variety of languages, so the MQ Light API is available in a range of popular languages such as Ruby and Python, with the syntax tailored to fit naturally in each. The same API can be used with MQ Light installed on a laptop, with enterprise MQ queue managers, or in the cloud with the Message Hub service, so you can move seamlessly between these environments. Come and see how this API can make your developers more productive.
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.
IBM MQ Advanced - IBM InterConnect 2016Leif Davidsen
Presentation from IBM InterConnect 2016 explaining the contents and benefits of IBM MQ Advanced, and positioning it compared to other Messaging offerings, and outlining different deployment options on-premise, or in the cloud, or as a hybrid messaging deployment
This presentation was delivered at the MQTC 2017 conference in Ohio. It covers different concepts and features of MQ you need to consider when moving your IBM MQ infrastructure into the cloud.
Designing IBM MQ deployments for the cloud generationDavid Ware
Businesses are transforming their enterprise IT infrastructure so that application teams can efficiently provision resources in an automated, self-service fashion, to be deployed as a service. In this session, we look at what that means with IBM MQ, and where previous design and deployment practices may not suit a more agile approach. We'll share what's possible with IBM MQ today, including the current best practices to achieve a low-touch, scalable solution whether deploying to the cloud or to on-premise systems.
Building highly available architectures with WAS and MQMatthew White
Abstract:
'This talk will look at architectures in which IBM MQ can be configured with the IBM WebSphere Application Server (and Liberty profiles) to give a highly-available scenario.
The basis be some of the scenarios that are documented in the developerWorks series "A flexible and scalable WebSphere MQ topology pattern". '
Aims:
Outline some of the technologies and features that can be used for High Availability
Consider some of the implications of technology choices
Provide references for further study
Find out what scenarios and concerns are of most interest
i.e. what should be developing next!
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.
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 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
Integrating cloud applications with your existing systems of record is essential to create truly engaging applications, and messaging is the secret ingredient when linking these worlds together. This session will cover what's new in IBM MQ version 8, and more recent enhancements, which can be used to create an efficient and reliable messaging infrastructure whether on-premise or in the cloud. Featured cloud integration points will include: how you combine MQ 8 with MQ Light to enable developers to join their newly created applications into your existing infrastructure, how to extend your on-premise MQ infrastructure into the cloud taking advantage of cloud deployment technologies such as Docker, and IBM's Message Hub.
IBM MQ - better application performanceMarkTaylorIBM
Presented in Feb 2015 at Interconnect
This presentation is aimed at helping application developers understand how to best use MQ features for higher performance.
These charts provide a high-level overview of IIB HA topologies:
• Comparison of active/active and active/passive HA
• Solutions for active/passive HA failover with IBM Integration Bus
• Solutions for active/active processing with IBM Integration Bus
• Adding Global Cache to active/active processing
• Combining all of the above
Only HTTP and JMS (MQ) workloads are shown
The document provides an introduction to the IBM MQ Appliance, including its key capabilities and differences from a traditional MQ software deployment. It highlights that the appliance provides the scalability and security of IBM MQ V8 in an optimized appliance form factor. The appliance allows for familiar administration through the MQ command line interface and MQ Explorer, while also providing a new browser-based web UI for management. It also includes built-in high availability without external dependencies.
The document introduces the IBM MQ Appliance, a new physical appliance that runs IBM MQ version 8 to simplify enterprise messaging networks. The appliance offers the scalability, security and administration of IBM MQ in a pre-configured hardware device to provide ease of deployment and management. It is intended to serve as a messaging hub, outpost, gateway or for partner connectivity in a standardized, low-cost and high availability configuration.
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).
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: Managing Workloads, Scaling and Availability with MQ ClustersDavid Ware
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. A basic understanding of IBM MQ clustering would be beneficial.
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.
HHM-3540: The IBM MQ Light API: From Developer Laptop to Enterprise Data Cen...Matt Leming
The IBM MQ Light API makes it simple for developers to create responsive applications that are easy to scale without having to become messaging experts. Increasingly, development teams choose from a wide variety of languages, so the MQ Light API is available in a range of popular languages such as Ruby and Python, with the syntax tailored to fit naturally in each. The same API can be used with MQ Light installed on a laptop, with enterprise MQ queue managers, or in the cloud with the Message Hub service, so you can move seamlessly between these environments. Come and see how this API can make your developers more productive.
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.
IBM MQ Advanced - IBM InterConnect 2016Leif Davidsen
Presentation from IBM InterConnect 2016 explaining the contents and benefits of IBM MQ Advanced, and positioning it compared to other Messaging offerings, and outlining different deployment options on-premise, or in the cloud, or as a hybrid messaging deployment
This presentation was delivered at the MQTC 2017 conference in Ohio. It covers different concepts and features of MQ you need to consider when moving your IBM MQ infrastructure into the cloud.
Designing IBM MQ deployments for the cloud generationDavid Ware
Businesses are transforming their enterprise IT infrastructure so that application teams can efficiently provision resources in an automated, self-service fashion, to be deployed as a service. In this session, we look at what that means with IBM MQ, and where previous design and deployment practices may not suit a more agile approach. We'll share what's possible with IBM MQ today, including the current best practices to achieve a low-touch, scalable solution whether deploying to the cloud or to on-premise systems.
Deep Dive on Microservices and Amazon ECS by Raul Frias, Solutions Architect,...Amazon Web Services
This document discusses running microservices on Amazon ECS. It begins with an overview of microservices and their characteristics. It then covers some of the key challenges in running microservices at scale, including resource and state management, data management, monitoring, service discovery, and deployment. The remainder of the document discusses how Amazon ECS addresses these challenges through features like container orchestration, load balancing, auto-scaling, service discovery integration, and support for continuous integration/delivery workflows. It includes examples of monitoring microservices with CloudWatch and third-party tools, as well as service discovery options.
Running Microservices on Amazon ECS - AWS April 2016 Webinar SeriesAmazon Web Services
This document provides an overview of running microservices on Amazon ECS. It begins by defining microservices and describing the challenges of managing them at scale. It then introduces Amazon ECS as a way to easily manage containers across a fleet of servers. Key features of ECS discussed include scalable and flexible container placement, integration with other AWS services for tasks like load balancing, and clustering containers together for management. The document also covers how to address microservices challenges with ECS, such as using services for discovery and deployment, CloudWatch for monitoring, and third party tools for additional functions. Continuous delivery options with Jenkins and Shippable are presented as well.
Modern Cloud-Native Streaming Platforms: Event Streaming Microservices with K...confluent
Microservices, events, containers, and orchestrators are dominating our vernacular today. As operations teams adapt to support these technologies in production, cloud-native platforms like Cloud Foundry and Kubernetes have quickly risen to serve as force multipliers of automation, productivity and value. Kafka is providing developers a critically important component as they build and modernize applications to cloud-native architecture. This talk will explore:
• Why cloud-native platforms and why run Kafka on Kubernetes?
• What kind of workloads are best suited for this combination?
• Tips to determine the path forward for legacy monoliths in your application portfolio
• Running Kafka as a Streaming Platform on Container Orchestration
Intro video here - https://youtu.be/MWsoXPFHY5Q
Can you afford an outage? What happens if one occurs? IBM MQ brings you the capabilities to build active-active solutions for continuous availability and to scale out a system horizontally. This presentation shows you how to use MQ to its fullest, stepping away from single queue managers and utilising MQ clusters and the new Uniform Cluster pattern which automatically keeps your applications balanced, no matter what happens.
Impact 2009 1783 Achieving Availability With W A Sz User ExperienceElena Nanos
The document discusses achieving high availability for WebSphere Application Server on z/OS. It describes the clustered architecture with control/servant regions that allows for automatic failover. It provides recommendations for minimizing the effects of timeouts, including setting timeout values and delaying servant termination. It also discusses health check procedures, alerts, avoiding memory leaks with ThreadLocals, and tools for monitoring and debugging the environment.
All the content of this website is informative and non-commercial, does not imply a commitment to develop, launch or schedule delivery of any feature or functionality, should not rely on it in making decisions, incorporate or take it as a reference in a contract or academic matters. Likewise, the use, distribution and reproduction by any means, in whole or in part, without the authorization of the author and / or third-party copyright holders, as applicable, is prohibited.
Arsitektur Aplikasi Modern - Faisal Henry SusantoDicodingEvent
Baparekraf Developer Day adalah kegiatan yang diadakan oleh Kementerian Pariwisata dan Ekonomi Kreatif/Badan Pariwisata dan Ekonomi Kreatif (Kemenparekraf/Baparekraf) dengan tujuan mengasah kemampuan teknis pengembang aplikasi di Indonesia. Kegiatan ini memungkinkan transfer pengetahuan dan standar industri secara langsung dari para praktisi yang telah sukses, khususnya pada bidang pengembangan aplikasi.
Back-End Session
Tema: Arsitektur Aplikasi Modern
Speaker: Faisal Henry Susanto (Praktisi IT)
Modern Cloud-Native Streaming Platforms: Event Streaming Microservices with A...confluent
Microservices, events, containers, and orchestrators are dominating our vernacular today. As operations teams adapt to support these technologies in production, cloud-native platforms like Pivotal Cloud Foundry and Kubernetes have quickly risen to serve as force multipliers of automation, productivity and value.
Apache Kafka® is providing developers a critically important component as they build and modernize applications to cloud-native architecture.
This talk will explore:
• Why cloud-native platforms and why run Apache Kafka on Kubernetes?
• What kind of workloads are best suited for this combination?
• Tips to determine the path forward for legacy monoliths in your application portfolio
• Demo: Running Apache Kafka as a Streaming Platform on Kubernetes
Fundamental and Practice.
Explain about microservices characters and pattern. And also how to be good build microservices. And also additional the scale cube and CAP theory.
Kubecon 2023 EU - KServe - The State and Future of Cloud-Native Model ServingTheofilos Papapanagiotou
KServe is a cloud-native open source project for serving production ML models built on CNCF projects like Knative and Istio. In this talk, we’ll update you on KServe’s progress towards 1.0, the latest developments, such as ModelMesh and InferenceGraph, and its future roadmap. We’ll discuss the Kubernetes design patterns used in KServe to achieve the core ML inference capability, as well as the design philosophy behind KServe and how it integrates the CNCF ecosystem so you can walk up and down the stack to use features to meet your production model deployment requirements. The well-designed InferenceService interface encapsulates the complexity of networking, lifecycle, server configurations and allows you to easily add serverless capabilities to model servers like TensorFlow Serving, TorchServe, and Triton on CPU/GPU. You can also turn on full service mesh mode to secure your InferenceServices. We’ll walk through different scenarios to show how you can quickly start with KServe and evolve to a production-ready setup with scalability, security, observability, and auto-scaling acceleration using CNCF projects like Knative, Istio, SPIFFE/SPIRE, OpenTelemetry, and Fluid.
Distributed Services Scheduling and Cloud ProvisioningAr Agarwal
This is the presentation for my final year project at NIT Allahabad (2013-14). The purpose of the project is to design a scheduling algorithm for cloud environment with proper resource management.
Microservices is a software architectural method where you decompose complex applications into smaller, independent services. Containers are great for running small decoupled services, but how do you coordinate running microservices in production at scale and what AWS services do you use? In this session, we will explore the reasoning and concepts behind microservices and how containers simplify building microservices based applications. We will also demonstrate how you can easily launch microservices on Amazon EC2 Container Service and how you can use ELB and Route 53 to easily do service discovery between microservices.
Presented at MQ Technical Conference 2018
More businesses are discovering the benefit of the cloud and moving parts or the whole of their infrastructure onto cloud platforms. In this session we will be looking at how you can utilize IBM MQ in the cloud including considerations you must make before moving your MQ infrastructure into the cloud. We will also look at what resources are available for you to use as a starting point for moving IBM MQ in the cloud.
CloudStack DC Meetup - Apache CloudStack Overview and 4.1/4.2 PreviewChip Childers
Chip Childers is the VP of Apache CloudStack and Principal Engineer at SunGard Availability Services.
Apache CloudStack is open source software that can deploy and manage large networks of virtual machines as a scalable IaaS cloud platform. It is a top-level project at the Apache Software Foundation.
CloudStack enables cloud operators to design, install, support, upgrade and scale diverse cloud environments. It also allows application owners to easily consume infrastructure services so that infrastructure does not get in the way of delivering applications to end users.
High-Speed Reactive Microservices - trials and tribulationsRick Hightower
Covers how we built a set of high-speed reactive microservices and maximized cloud/hardware costs while meeting objectives in resilience and scalability. This has more notes attached as it is based on the ppt not the PDF.
High availability of a messaging system is essential. This is especially true for IBM MQ systems which are absolutely critical to the smooth running of many enterprises. IBM MQ Advanced made achieving high availability even easier with Replicated Data Queue Managers. Learn how this and other HA capabilities fits into a system that provides both high availability of the messaging system as a whole and every last piece of critical messaging data that you care about.
Similar to IBM Managing Workload Scalability with MQ Clusters (20)
Savio Rodrigues - Cloud Enable Your Ent App - 11th SeptemberIBM Systems UKI
This document discusses IBM's PureApplication product which allows customers to easily enable their enterprise applications for cloud deployment. Some key points:
- PureApplication uses application patterns and an automated hybrid cloud platform to simplify deploying and managing applications across on-premises and off-premises cloud environments.
- Over 200 application patterns have been developed by IBM and partners across various domains to accelerate cloud deployment of existing applications.
- The automated hybrid cloud platform handles complex tasks like provisioning, monitoring, maintenance, and scaling to reduce the manual effort required for cloud application management.
- Customers can purchase the PureApplication Service on SoftLayer to deploy applications in IBM's public cloud infrastructure starting at a monthly price
Andrew Darley Presentation - Pure Future is Hybrid Cloud (London 11th September)IBM Systems UKI
- The document is an agenda for the "PureApplication" event discussing hybrid cloud.
- The keynote speaker is Andrew Darley, Head of Pure Systems at IBM Europe, who will discuss the future of hybrid cloud.
- There are several sessions on accelerating applications to hybrid cloud environments and case studies of organizations using IBM's hybrid cloud solutions.
Icon solutions presentation - Pure Hybrid Cloud Event, 11th September LondonIBM Systems UKI
This document discusses a webMethods pattern for IBM's PureApplication system. It describes how Icon Solutions created a pattern for a large UK retailer that included webMethods Broker and Integration Server to run their point-of-sale system. The pattern allowed the system to automatically scale on PureApplication based on workload, providing a scalable and flexible platform for the retailer. The document also discusses how patterns in general can provide benefits like repeatable deployments, reduced manual intervention, and self-service capabilities.
The document provides an overview of the IBM MQ Light Service for Bluemix. It introduces MQ Light and the MQ Light Service, which allows developers to easily incorporate messaging into their applications. The MQ Light Service supports the MQ Light API and JMS, provides auto-defined JMS queues, and handles connection details. Applications can be developed locally and seamlessly deployed to Bluemix. The document also demonstrates how to use MQ Light with Node.js and Java applications and provides an example demo scenario of a Twitter sentiment analysis application.
This document provides a summary of an IBM presentation on MQ Light (beta), a new messaging API and runtime designed for application developers. MQ Light includes a simple API based on AMQP 1.0, runtimes for on-premise deployment and on IBM Bluemix, and tooling for developer platforms like Node.js. The presentation demonstrates MQ Light's messaging model and deployment options, and encourages attendees to try the beta release.
MQ version 8 introduces two new major features: 64-bit buffer pools and 8-byte log RBAs. 64-bit buffer pools allow buffer pools to utilize up to 16 exabytes of storage above the bar, increasing maximum buffer pool size and number. 8-byte log RBAs increase the log RBA range from 6 bytes to 8 bytes, expanding the maximum log size before recycling.
The Log Manager statistics provide valuable information about logging performance in WebSphere MQ. They show the rate at which control intervals (CIs) are written to the log, which is important because all persistent data changes and object modifications must be logged. High logging volumes can indicate potential I/O issues or that the persistent workload is too great. The statistics help identify if checkpoints are occurring too frequently, logging is inefficient due to small transactions, or if applications are backing out transactions too often. Understanding logging performance is crucial as it usually impacts the performance of persistent messaging.
The document provides an introduction to using WebSphere MQ with WebSphere Application Server and the Liberty Profile. It discusses the WebSphere MQ JMS resource adapter which provides MQ messaging to WAS by harnessing the Java Connector Architecture. The resource adapter allows for easier maintenance and upgrading compared to directly using the JMS API or native bindings. It also covers configuring high availability with multi-instance queue managers.
This document discusses publish/subscribe capabilities in WebSphere MQ. It provides an overview of distributed publish/subscribe using hierarchies and clusters. Key points include:
- Hierarchies propagate subscriptions across connected queue managers, while clusters share subscription knowledge by clustering topic definitions.
- Direct routing sends publications directly between all cluster members, while topic host routing routes via queue managers hosting the clustered topic.
- Proxy subscriptions represent remote subscriptions on a queue manager and are used to propagate publications in hierarchies and clusters.
- The optimal topology depends on factors like scale, traffic patterns, and configuration flexibility needed. Direct clusters optimize publication routing but may not scale as well as hierarchies or topic host clusters.
The document summarizes the key changes in JMS 2.0 compared to JMS 1.1, including a simplified API with JMSContext, JMSProducer, and JMSConsumer interfaces. It discusses the new messaging features like delivery delay and asynchronous send. It also covers updates to the Java EE specification and how JMS 2.0 leverages features in Java 7 like try-with-resources for auto-closing resources. The document is intended to provide an introduction to the new features and gauge adoption of JMS 2.0.
Channel authentication records allow setting rules to control inbound connections to a queue manager. Rules can allow, block, or assign user IDs to connections. Attributes like IP address, hostname, SSL certificate, and user ID can be used to define rules. Obtaining hostnames requires reverse DNS lookup, which can be disabled. Rules can be restricted based on IP/hostname and certificate subject and issuer can be checked.
IBM WebSphere MQ V8 introduces new security features including changes to how channels use SSL/TLS certificates. Channels can now specify their own certificate label instead of using the queue manager's default. This allows a single queue manager to use multiple certificates to communicate with different business partners that require different certificate authorities. Server Name Indication is used to select the certificate during the TLS handshake based on the channel name.
IBM MQ V8 delivers enhancements for platform consistency, security, performance and standards compliance. Key updates include 64-bit support on all platforms, integration of additional capabilities into z/OS and IBM i, support for the JMS 2.0 standard, and improvements to .NET and WCF integration. The release also provides stronger encryption algorithms, expanded authentication options including LDAP, and usability enhancements to the runmqsc administration tool.
What is Augmented Reality Image Trackingpavan998932
Augmented Reality (AR) Image Tracking is a technology that enables AR applications to recognize and track images in the real world, overlaying digital content onto them. This enhances the user's interaction with their environment by providing additional information and interactive elements directly tied to physical images.
Introducing Crescat - Event Management Software for Venues, Festivals and Eve...Crescat
Crescat is industry-trusted event management software, built by event professionals for event professionals. Founded in 2017, we have three key products tailored for the live event industry.
Crescat Event for concert promoters and event agencies. Crescat Venue for music venues, conference centers, wedding venues, concert halls and more. And Crescat Festival for festivals, conferences and complex events.
With a wide range of popular features such as event scheduling, shift management, volunteer and crew coordination, artist booking and much more, Crescat is designed for customisation and ease-of-use.
Over 125,000 events have been planned in Crescat and with hundreds of customers of all shapes and sizes, from boutique event agencies through to international concert promoters, Crescat is rigged for success. What's more, we highly value feedback from our users and we are constantly improving our software with updates, new features and improvements.
If you plan events, run a venue or produce festivals and you're looking for ways to make your life easier, then we have a solution for you. Try our software for free or schedule a no-obligation demo with one of our product specialists today at crescat.io
E-commerce Application Development Company.pdfHornet Dynamics
Your business can reach new heights with our assistance as we design solutions that are specifically appropriate for your goals and vision. Our eCommerce application solutions can digitally coordinate all retail operations processes to meet the demands of the marketplace while maintaining business continuity.
OpenMetadata Community Meeting - 5th June 2024OpenMetadata
The OpenMetadata Community Meeting was held on June 5th, 2024. In this meeting, we discussed about the data quality capabilities that are integrated with the Incident Manager, providing a complete solution to handle your data observability needs. Watch the end-to-end demo of the data quality features.
* How to run your own data quality framework
* What is the performance impact of running data quality frameworks
* How to run the test cases in your own ETL pipelines
* How the Incident Manager is integrated
* Get notified with alerts when test cases fail
Watch the meeting recording here - https://www.youtube.com/watch?v=UbNOje0kf6E
Zoom is a comprehensive platform designed to connect individuals and teams efficiently. With its user-friendly interface and powerful features, Zoom has become a go-to solution for virtual communication and collaboration. It offers a range of tools, including virtual meetings, team chat, VoIP phone systems, online whiteboards, and AI companions, to streamline workflows and enhance productivity.
Odoo ERP software
Odoo ERP software, a leading open-source software for Enterprise Resource Planning (ERP) and business management, has recently launched its latest version, Odoo 17 Community Edition. This update introduces a range of new features and enhancements designed to streamline business operations and support growth.
The Odoo Community serves as a cost-free edition within the Odoo suite of ERP systems. Tailored to accommodate the standard needs of business operations, it provides a robust platform suitable for organisations of different sizes and business sectors. Within the Odoo Community Edition, users can access a variety of essential features and services essential for managing day-to-day tasks efficiently.
This blog presents a detailed overview of the features available within the Odoo 17 Community edition, and the differences between Odoo 17 community and enterprise editions, aiming to equip you with the necessary information to make an informed decision about its suitability for your business.
Takashi Kobayashi and Hironori Washizaki, "SWEBOK Guide and Future of SE Education," First International Symposium on the Future of Software Engineering (FUSE), June 3-6, 2024, Okinawa, Japan
Transform Your Communication with Cloud-Based IVR SolutionsTheSMSPoint
Discover the power of Cloud-Based IVR Solutions to streamline communication processes. Embrace scalability and cost-efficiency while enhancing customer experiences with features like automated call routing and voice recognition. Accessible from anywhere, these solutions integrate seamlessly with existing systems, providing real-time analytics for continuous improvement. Revolutionize your communication strategy today with Cloud-Based IVR Solutions. Learn more at: https://thesmspoint.com/channel/cloud-telephony
WhatsApp offers simple, reliable, and private messaging and calling services for free worldwide. With end-to-end encryption, your personal messages and calls are secure, ensuring only you and the recipient can access them. Enjoy voice and video calls to stay connected with loved ones or colleagues. Express yourself using stickers, GIFs, or by sharing moments on Status. WhatsApp Business enables global customer outreach, facilitating sales growth and relationship building through showcasing products and services. Stay connected effortlessly with group chats for planning outings with friends or staying updated on family conversations.
SMS API Integration in Saudi Arabia| Best SMS API ServiceYara Milbes
Discover the benefits and implementation of SMS API integration in the UAE and Middle East. This comprehensive guide covers the importance of SMS messaging APIs, the advantages of bulk SMS APIs, and real-world case studies. Learn how CEQUENS, a leader in communication solutions, can help your business enhance customer engagement and streamline operations with innovative CPaaS, reliable SMS APIs, and omnichannel solutions, including WhatsApp Business. Perfect for businesses seeking to optimize their communication strategies in the digital age.
Unveiling the Advantages of Agile Software Development.pdfbrainerhub1
Learn about Agile Software Development's advantages. Simplify your workflow to spur quicker innovation. Jump right in! We have also discussed the advantages.
Most important New features of Oracle 23c for DBAs and Developers. You can get more idea from my youtube channel video from https://youtu.be/XvL5WtaC20A
Software Engineering, Software Consulting, Tech Lead, Spring Boot, Spring Cloud, Spring Core, Spring JDBC, Spring Transaction, Spring MVC, OpenShift Cloud Platform, Kafka, REST, SOAP, LLD & HLD.
Using Query Store in Azure PostgreSQL to Understand Query PerformanceGrant Fritchey
Microsoft has added an excellent new extension in PostgreSQL on their Azure Platform. This session, presented at Posette 2024, covers what Query Store is and the types of information you can get out of it.
UI5con 2024 - Boost Your Development Experience with UI5 Tooling ExtensionsPeter Muessig
The UI5 tooling is the development and build tooling of UI5. It is built in a modular and extensible way so that it can be easily extended by your needs. This session will showcase various tooling extensions which can boost your development experience by far so that you can really work offline, transpile your code in your project to use even newer versions of EcmaScript (than 2022 which is supported right now by the UI5 tooling), consume any npm package of your choice in your project, using different kind of proxies, and even stitching UI5 projects during development together to mimic your target environment.
Do you want Software for your Business? Visit Deuglo
Deuglo has top Software Developers in India. They are experts in software development and help design and create custom Software solutions.
Deuglo follows seven steps methods for delivering their services to their customers. They called it the Software development life cycle process (SDLC).
Requirement — Collecting the Requirements is the first Phase in the SSLC process.
Feasibility Study — after completing the requirement process they move to the design phase.
Design — in this phase, they start designing the software.
Coding — when designing is completed, the developers start coding for the software.
Testing — in this phase when the coding of the software is done the testing team will start testing.
Installation — after completion of testing, the application opens to the live server and launches!
Maintenance — after completing the software development, customers start using the software.
2. 2
WebSphere MQ
IBM Software Group | WebSphere software
Agenda
Scenario 1 My first cluster
Starting to scale
Scenario 2 Service availability
Routing around failures
Scenario 3 Location dependency
Active active scenarios with ties to home
Scenario 4 Avoiding interference
What are we sharing?
Scenario 5 When things go wrong
Levels of DR and clustering implications
3. 3
WebSphere MQ
IBM Software Group | WebSphere software
Introduction
This session approaches the topic from a point of view of a set of common clustering
scenarios or ‘use cases’.
We will build up from a fairly simple and common initial clustering setup to tackle some of
the more complicated issues which often come up in evolving clustered environments.
Although not looking at the topic from a list of features or “how do I use widget x”
approach, as we work through the examples we will see where some of the recent
additions to WebSphere MQ’s clustering capabilities are relevant to these everyday
problems.
4. 4
WebSphere MQ
IBM Software Group | WebSphere software
Terminology / Key
Lots of different terminology floats around when you get into application
infrastructure discussions… Clients, applications, servers, services, requesters,
responders… For the purposes of this session:
Client – a ‘client’ in the general sense (whether connected
locally or remotely), uses WebSphere MQ to send one off
datagrams or initiates requests to services and waits for
replies.
Service – a process which consumes messages and takes
some action, often needing to reply to the requesting Client.
Queue Manager
Note that there may be more than one Instance of a client or service, either
connected to a given queue manager or the infrastructure as a whole.
A set of clients and services working together to achieve some useful end goal make
up an ‘application’.
Service
Client
QMgr
Full repository
Queue Manager
QMgr
8. 8
WebSphere MQ
IBM Software Group | WebSphere software
Client 1
Over time…
Service 1
Client 2
Client 2
Client 3
Service 3
Service 2 Service 1
QMgrQMgr QMgrQMgr
Client 1Client 1
9. 9
WebSphere MQ
IBM Software Group | WebSphere software
Over time...
App 1
Service 1
Client 2
Client 2
Client 3
Service 2
App 1Client 1
Service 1
QMgr
QMgr
QMgr
QMgr
Client 3
Client 1
Client 4
App 4App 4Client 4
Service 4
Service 3
Service 1Service 1
Service 3
10. 10
WebSphere MQ
IBM Software Group | WebSphere software
Until...
App 1
Service 1
Client 2
Client 2
Client 3
Service 2
App 1Client 1
Service 1
QMgr
QMgr
QMgr
QMgr
Client 3
Client 1
Client 4
App 4App 4Client 4
Service 4
Service 3
Service 1Service 1
Service 3
QMgr QMgr
11. 11
WebSphere MQ
IBM Software Group | WebSphere software
Basic Cluster
This illustrates the first reason we may move to a WebSphere MQ cluster –
simplified administration. Channel definitions - and, if we choose, the
addressing of individual queues within the cluster - are tasks which no longer
have to be manually carried out by the administrator.
At this point we still only have single instances of ‘service’ queues.
A degree of vertical scaling can be achieved by adding instances of the Service
processes connecting to the single queue manager hosting a particular queue, if
the application can cope with ‘interleaved’ processing.
12. 12
WebSphere MQ
IBM Software Group | WebSphere software
Service 1
Client 2
Client 2
Client 3
Service 2
App 1App 1Client 1
Service 1
QMgr
QMgr
QMgr
QMgr
Client 3
Client 1
Client 4
App 4App 4Client 4
Service 4
Service 3
Service 1Service 1
Service 3
QMgr QMgr
Zooming in on an application…
13. 13
WebSphere MQ
IBM Software Group | WebSphere software
Starting to scale horizontally…
• Workload Balancing
• Service Availability
• Location Transparency (of a kind)
Service 1
App 1App 1Client 1
Service 1
QMgr
QMgr
QMgr
14. 14
WebSphere MQ
IBM Software Group | WebSphere software
Starting to scale Horizontally
By adding instances of ‘service’ queues, we can start to scale applications
across multiple hosts and beyond the ‘vertical’ scaling on a single (albeit maybe
multi-CPU) system.
Using WebSphere MQ Clustering allows instances to be added and removed
without modifying the client or server applications
But may require some thinking ahead to design with this in mind – e.g. avoiding hard coded
queue manager names
As soon as we have multiple instances, questions arise about ‘choosing’ an
instance for a request, so as a natural consequence workload balancing
becomes available
Location transparency for ‘the service’ has been achieved at this point, but there
is still a strong coupling between ‘an instance’ and a particular queue manager –
for example for reply routing (see next section)
16. 16
WebSphere MQ
IBM Software Group | WebSphere software
• Target queues
• Transmission queues
Service 1
App 1App 1Client 1
Service 1
QMgr
QMgr
QMgr
Where can messages get stuck?
Target queue
Transmission queue
17. 17
WebSphere MQ
IBM Software Group | WebSphere software
Service 1
App 1App 1Client 1
Service 1
QMgr
QMgr
QMgr
The service queue manager/host fails
Message reallocation
Unbound messages on the
transmission queue can be
diverted
QMgr
Locked messages
Messages on the failed queue manager are
locked until it is restarted
Restart the queue
manager
Use multi-instance queue
managers or HA clusters to
automatically restart a queue
manager
Reconnect the service
Make sure the service is
restarted/reconnects to the
restarted queue manager
When a queue manager fails:
• Ensure inbound messages are not locked to it
• Restart it to release queued messages
18. 18
WebSphere MQ
IBM Software Group | WebSphere software
Failed Service Queue Manager
When a ‘service’ queue manager fails, request messages which have reached
that queue manager or responses on transmission queues are inevitably lost
until that queue manager can be restarted.
However – service availability can be maintained by making sure that there is
sufficient capacity in other hosts to cope with all requests being loaded onto
them.
This will be smoother and give higher availability if client applications can be
designed to avoid server affinity and strict message ordering requirements –
BIND_NOT_FIXED. Reallocation will then mean that even in-flight requests can
be re-routed.
To avoid the trapped request problem, consider HA clustering technology or
multi-instance queue managers.
20. 20
WebSphere MQ
IBM Software Group | WebSphere software
QMgr
QMgr
QMgr
• Cluster workload balancing does take into account the availability of
receiving applications.
• Or a build up of messages.
Service 1
App 1App 1Client 1
Service 1
The service application fails
Blissful ignorance
This queue manager is unaware of
the failure to one of the service
instances
Unserviced messages
Half the messages will quickly start
to build up on the service queue
21. 21
WebSphere MQ
IBM Software Group | WebSphere software
Service 1
App 1App 1Client 1
Service 1
QMgr
QMgr
QMgr
Monitoring for
service failures
22. 22
WebSphere MQ
IBM Software Group | WebSphere software
• WebSphere MQ provides a sample monitoring service
• Regularly checks for attached consuming applications
• Suitable for steady state service applications
Service 1
App 1App 1Client 1
Service 1
QMgr
QMgr
QMgr
Monitoring for
service failures
QMgr
QMgr
Moving messages
Any messages that slipped
through will be transferred to an
active instance of the queue
Detecting a change
When a change to the open
handles is detected the cluster
workload balancing state is
modified
Sending queue managers
Newly sent messages will be sent to
active instances of the queue
23. 23
WebSphere MQ
IBM Software Group | WebSphere software
Cluster Queue Monitoring Sample
A relatively new tool, amqsclm, is provided since 7.0.1.8 to ensure messages are directed
towards the instances of clustered queues that have consuming applications currently attached.
This allows all messages to be processed effectively even when a system is asymmetrical (i.e.
consumers not attached everywhere).
In addition it will move already queued messages from instances of the queue where no
consumers are attached to instances of the queue with consumers. This removes the chance of
long term marooned messages when consuming applications disconnect.
The above allows for more versatility in the use of clustered queue topologies where
applications are not under the direct control of the queue managers. It also gives a greater
degree of high availability in the processing of messages.
The tool provides a monitoring executable to run against each queue manager in the cluster
hosting queues, monitoring the queues and reacting accordingly.
The tool is provided as source (amqsclm.c sample) to allow the user to understand the mechanics of the
tool and customise where needed.
24. 24
WebSphere MQ
IBM Software Group | WebSphere software
AMQSCLM Logic
Based on the existing MQ cluster workload balancing mechanics:
Uses cluster priority of individual queues – all else being equal, preferring to send messages to
instances of queues with the highest cluster priority (CLWLPRTY).
Using CLWLPRTY always allows messages to be put to a queue instance, even when no consumers
are attached to any instance.
Changes to a queue’s cluster configuration are automatically propagated to all queue managers in the
cluster that are workload balancing messages to that queue.
Single executable, set to run against each queue manager with one or
more cluster queues to be monitored.
The monitoring process polls the state of the queues on a defined
interval:
If no consumers are attached:
CLWLPRTY of the queue is set to zero (if not already set).
The cluster is queried for any active (positive cluster priority) queues.
If they exist, any queued messages on this queue are got/put to the same queue.
Cluster workload balancing will re-route the messages to the active instance(s) of
the queue in the cluster.
If consumers are attached:
CLWLPRTY of the queue is set to one (if not already set).
Defining the tool as a queue manager service will ensure it is started
with each queue manager
26. 26
WebSphere MQ
IBM Software Group | WebSphere software
• Multiple locations for a client to connect to
•Allows new requests when one queue manager is unavailable.
• What happens to replies after a failure?
Service 1
App 1App 1Client 1
Service 1
Client availability
QMgr
QMgr
QMgrQMgr
27. 27
WebSphere MQ
IBM Software Group | WebSphere software
Service 1
App 1App 1Client 1
Service 1
Client host failure with an in flight request/response
QMgr
QMgr
QMgr
QMgr
• Reply messages are bound to the originating queue manager, with no ability to
redirect.
Reply message bound
The reply message will be locked to that
outbound queue manager
Request message
Typically a request message will fill in
the reply ReplyToQmgr based on the
outbound queue manager
28. 28
WebSphere MQ
IBM Software Group | WebSphere software
Service 1
App 1App 1Client 1
Service 1
Client host failure with an in flight request/response
QMgr
QMgr
QMgr
QMgr
• Reply-to queue aliases and reply-to queue manager aliases can be used to blank out
the outbound resolution of the ReplyToQMgr field.
• Typically, under normal running, you require the originating queue manager to receive the
replies, cluster workload balancing configuration can provide this.
DEF QLOCAL(REPLYQ)
CLUSTER(CLUSTER1)
DEF QREMOTE(REPLYQALIAS)
RNAME(REPLYQ)
RQMNAME(DUMMY)
Name resolution
Outgoing request resolves the ReplyToQ
to be ‘REPLYQ’ and ReplyToQMgr to be
‘DUMMY’
DEF QREMOTE(DUMMY)
RNAME(‘ ’)
RQMNAME(‘ ’)
Replying application
Application replies to ‘REPLYQ’ on
queue manager ‘DUMMY’
Name resolution
Target queue manager ‘DUMMY’ is
resolved to ‘ ’, allowing cluster
resolution to occur
DEF QLOCAL(REPLYQ)
CLUSTER(CLUSTER1)
DEF QREMOTE(REPLYQALIAS)
RNAME(REPLYQ)
RQMNAME(DUMMY)
Requesting application
Request message sets ReplyToQ
to be ‘REPLYQALIAS’ and
ReplyToQMgr to ‘ ’
29. 29
WebSphere MQ
IBM Software Group | WebSphere software
Failed ‘client’ queue manager Traditional applications will use ReplyToQMgr which has been set on outgoing request.
So may need to consider ReplyToQueueAlias to route response through workload
balancing.
Managing reconnection beyond scope of this session, and in ideal world will reconnect to
same queue manager (may involve HA clusters, multi instance queue managers),
however…
Clustered reply queues give various possibilities. Simplest case is ‘shared responses’
but not really worth discussing further… lets assume need to get back to particular client
‘instance’.
1) Can use priority to prefer ‘usual’ location. Using some form of polling perhaps, ensure
client connects / reconnects to particular queue manager whenever it is up. If down,
client and replies fail over to backup.
2) OR: can use AMQSCLM again to get replies to follow connection
31. 31
WebSphere MQ
IBM Software Group | WebSphere software
Global applications QMgr QMgr
QMgr QMgr
Service Service
Service Service
QMgr
QMgr
App 1App 1Client
QMgr
QMgr
App 1App 1Client
New York
London
but separated by an ocean and 3500 miles
• Prefer traffic to stay geographically local
• Except when you have to look further afield
• Clusters can be used to span geographies
32. 32
WebSphere MQ
IBM Software Group | WebSphere software
One cluster
A single cluster is often the simplest and best approach even when large
distances are involved – for example, cluster certainly doesn’t have to be
limited to a particular datacenter.
However, often for obvious reasons we would rather keep as much traffic as
possible ‘local’, and we would like to know that if we lose our connection to the
outside world for a period of time, things can keep running.
Conversely though, if a particular service is down locally, we’d like to make use
of the remote instance (even if it may be a bit slower than usual).
Finally, we’d like our applications to ‘look the same’ wherever we connect – the
deploying administrator might know this instance is running in London, but
does the application really have to be coded to cope with that?
34. 34
WebSphere MQ
IBM Software Group | WebSphere software
One cluster QMgr
Service
QMgr
App 1App 1Client
New York
London
• Clients always open AppQ
• Local alias determines the preferred region
• Cluster workload priority is used to target geographically local cluster aliases
• Use of CLWLPRTY enables automatic failover
•CLWLRANK can be used for manual failover
Service
App 1App 1Client
DEF QALIAS(AppQ)
TARGET(NYQ)
DEF QALIAS(NYQ)
TARGET(ReqQ)
CLUSTER(Global)
CLWLPRTY(9)
AppQ
NYQ
ReqQ
A
A
QMgr
AppQ
A
LonQ
A
QMgr
NYQ
ReqQ
A
LonQ
A
DEF QALIAS(AppQ)
TARGET(LonQ)
DEF QALIAS(LonQ)
TARGET(ReqQ)
CLUSTER(Global)
CLWLPRTY(4)
DEF QALIAS(LonQ)
TARGET(ReqQ)
CLUSTER(Global)
CLWLPRTY(9)
DEF QALIAS(NYQ)
TARGET(ReqQ)
CLUSTER(Global)
CLWLPRTY(4)
35. 35
WebSphere MQ
IBM Software Group | WebSphere software
QMgr QMgr
QMgr QMgr
Service Service
Service Service
QMgr
QMgr
App 1App 1Client
QMgr
QMgr
App 1App 1Client
New York
London
• The service queue managers join both geographical clusters
•Each with separate cluster receivers for each cluster, at different cluster priorities.
•Queues are clustered in both clusters.
• The client queue managers are in their local cluster only.
USA
EUROPE
QMgr
QMgr
QMgr
QMgr
The two cluster alternative
36. 36
WebSphere MQ
IBM Software Group | WebSphere software
Two cluster approach
Define two clusters.
USA and EUROPE
For service queue managers, define separate cluster receiver channels, one for each
cluster. Set the CLWLPRTY high on the one for the local cluster and low for the
remote one.
For service queue managers in New York:
DEFINE CHANNEL(USA.NYxx) CHLTYPE(CLUSRCVR) …. CLUSTER(USA) CLWLPRTY(9)
DEFINE CHANNEL(EUROPE.NYxx) CHLTYPE(CLUSRCVR) …. CLUSTER(EUROPE) CLWLPRTY(4)
For service queue managers in London:
DEFINE CHANNEL(EUROPE.LONxx) CHLTYPE(CLUSRCVR) …. CLUSTER(EUROPE) CLWLPRTY(9)
DEFINE CHANNEL(USA.LONxx) CHLTYPE(CLUSRCVR) …. CLUSTER(USA) CLWLPRTY(4)
Define a namelist of each service queue manager that contains both clusters and use
this when clustering queues.
DEFINE NAMELIST(GLOBAL) NAMES(USA,EUROPE)
DEFINE QLOCAL(QUEUE1) CLUSNL(GLOBAL)
Client queue managers only join the cluster that is local to them.
The client queue managers will choose the instances of queues that are on queue
managers with the highest CLWLPRTY on the channel.
For example, a queue manager in the EUROPE cluster will only see the EUROPE.* channels. So London
queue managers will have a CLWLPRTY of 9 and New York queue managers only 4, so preferring
London whilst it is available.
38. 38
WebSphere MQ
IBM Software Group | WebSphere software
App 1App 1Client
ServiceService
App 1App 1Client
ServiceService
App 1App 1Client
ServiceService
App 1App 1Client
App 1App 1Client
ServiceService
Real time queries
Big data transfer
Audit events
The cluster as a pipe
• Often a WebSphere MQ backbone will be used for multiple types of traffic
39. 39
WebSphere MQ
IBM Software Group | WebSphere software
App 1App 1Client
ServiceService
App 1App 1Client
ServiceService
App 1App 1Client
ServiceService
App 1App 1Client
App 1App 1Client
ServiceService
The cluster as a pipe
QMgr
QMgr
QMgr
QMgr
QMgr
QMgr
Channels
• Often a WebSphere MQ backbone will be used for multiple types of traffic
• When using a single cluster and the same queue managers, messages all
share the same channels
• Even multiple cluster receiver channels in the same cluster will not separate out
the different traffic types
40. 40
WebSphere MQ
IBM Software Group | WebSphere software
Mice and Elephants
Large non real time data is contending for resources with small ‘live’ request response
transactions.
with due attribution to T-Rob:
http://www.ibm.com/developerworks/websphere/techjournal/0804_mismes/0804_mismes.html
All Workload Balancing at the messaging / channel level
No distinction between a request that needs a week of CPU at the other end, and one which
needs 1 ms.
Pub Sub requires high ‘meshing’ – all queue managers aware of whole cluster
Potentially lots of channel work for hosts not interested in pub sub activity when superimposed
on existing cluster
Denial of Service potential
One application out of control = full cluster Transmit queue until someone can manually
intervene
The cluster as a pipe - Problems
41. 41
WebSphere MQ
IBM Software Group | WebSphere software
App 1App 1Client
ServiceService
App 1App 1Client
ServiceService
App 1App 1Client
ServiceService
App 1App 1Client
App 1App 1Client
ServiceService
The cluster as a pipe
QMgr
QMgr
QMgr
QMgr
QMgr
QMgr
Cluster
Cluster
Cluster
Channels
Channels
Channels
• Often a WebSphere MQ backbone will be used for multiple types of traffic
• When using a single cluster and the same queue managers, messages
all share the same channels
• Even multiple cluster receiver channels in the same cluster will not separate out
the different traffic types
• Multiple overlaid clusters with different channels enable separation
42. 42
WebSphere MQ
IBM Software Group | WebSphere software
Putting application in a separate cluster gives option of also giving it its own channel
Applications with a need for a strictly controlled WLM ratio can be given their own
clusters for this reason. However, bear in mind cost of too many overlapping clusters
RFE 23391
In general, try and group applications with similar requirements rather than ending up
with channel for every application
Real time / Batch / Pub sub
Applications don’t need to know which cluster their resources are in as long as
configuration is managed correctly on their behalf
New in WebSphere MQ 7.1: Pub sub can be limited to specialised clusters / queue
managers using PSCLUS attribute
New in WebSphere MQ 7.5: Channels for different clusters can also be separated at
transmission queue level
The cluster as a pipe
43. 43
WebSphere MQ
IBM Software Group | WebSphere software
QMgr
QMgrQMgr
Workload balancing level interference
Service 1
Client 1
Service 1
QMgr
Service 2
Client 2
Cluster workload balancing is at the channel level.
Messages sharing the same channels, but to different target queues will be counted together.
The two channels here have an even 50/50 split of messages…
…but the two instances of Service 1 do not!
Split Service 1 and Service 2 queues out into separate clusters, queue managers or
customise workload balancing logic.
x75
x100
x50
x75
x25
x50
Multiple applications sharing the same
queue managers and the same
cluster channels.
x75
44. 44
WebSphere MQ
IBM Software Group | WebSphere software QMgr
A much requested feature…
Multiple cluster transmission queues
Separation of Message Traffic
With a single transmission queue there is
potential for pending messages for cluster ChannelA to interfere
with messages pending for cluster ChannelB
Management of messages
Use of queue concepts such as MAXDEPTH not useful when using a single transmission queue for
more than one channel.
Monitoring
Tracking the number of messages processed by a cluster channel currently difficult/impossible using
queue.
Often requested, but not necessarily for, performance
In reality a shared transmission queue is not always the bottleneck, often other solutions to improving
channel throughput (e.g. multiple cluster receiver channels) are really what’s needed.
Multiple cluster transmit queues
QMgr
QMgr
QMgr
QMgr
V7.5 V8
Distributed z/OS
45. 45
WebSphere MQ
IBM Software Group | WebSphere software
Configured on the sending queue manager, not the owners of the cluster receiver channel
definitions.
Queue Manager switch to automatically create a dynamic transmission queue per cluster
sender channel.
ALTER QMGR DEFCLXQ( SCTQ | CHANNEL )
Dynamic queues based upon model queue. SYSTEM.CLUSTER.TRANSMIT.MODEL
Well known queue names.
SYSTEM.CLUSTER.TRANSMIT.<CHANNEL-NAME>
Multiple cluster transmit queues - Automatic
QMgr QMgr
QMgr
ChlA
ChlB
SYSTEM.CLUSTER.TRANSMIT.ChlA
SYSTEM.CLUSTER.TRANSMIT.ChlC
SYSTEM.CLUSTER.TRANSMIT.ChlB
ChlA
ChlC
ChlC
ChlB
46. 46
WebSphere MQ
IBM Software Group | WebSphere software
QMgr QMgr
QMgr
Still configured on the sending queue manager, not the owners of the cluster receiver
channel definitions.
Administratively define a transmission queue and configure which cluster sender
channels will use this transmission queue.
DEFINE QLOCAL(CLUSTER1.XMITQ) CLCHNAME(GREEN.*) USAGE(XMITQ)
Set a channel name pattern in CLCHNAME
Single/multiple channels (wildcard)
E.g. all channels for a specific cluster
(assuming a suitable channel naming convention!)
Any cluster sender channel not
covered by a manual transmission
queue defaults to the DEFCLXQ
behaviour
Multiple cluster transmit queues - Manual
Green.A
Pink.B
Pink.A
GREEN.XMITQ Green.A
Pink.A
Pink.B
PINK.XMITQ
48. 48
WebSphere MQ
IBM Software Group | WebSphere software
Everything
Applications must be able to connect and target the exact same MQ resources.
Every existing, in-flight, message must be processed whilst in DR mode.
New messages must be processed whilst in DR mode.
What do we need to recover?
WebSphere MQ resources
Applications must be able to connect and target the exact same MQ resources.
New messages must be processed whilst in DR mode.
Application availability
Applications must be able to connect and target equivalent MQ resources.
New messages must be processed whilst in DR mode.
49. 49
WebSphere MQ
IBM Software Group | WebSphere software
What to recover
Before discussing Disaster recovery in a clustered environment, we need to think about
what we mean by disaster recovery even on a single queue manager basis.
Many people will think of synchronous replication (using underlying host, disk replication
etc.) as the ‘gold standard’
The only way we can really achieve guaranteed identical configuration OR data.
Significant performance cost
Impractical in many scenarios (e.g. distance between data centres)
When moving beyond synchronous we have to consider whether it is only ‘configuration’
(queue, channel definitions, etc) or also data which we are trying to restore.
Restoring data implies WebSphere MQ may be being questionably used as ‘system of record’ – possibly
revisit architecture?
Application must be designed to deal with duplicate and/or lost messages
In a cluster, the line between data and config is further blurred
Cluster knowledge exists as state data on repository queue for example.
50. 50
WebSphere MQ
IBM Software Group | WebSphere software
Synchronous Replication
Datacenter 1
1
QMgr
2
QMgr
DB
DB
Datacenter 2
QMgr QMgrQMgr
DB
DB
QMgr
QMgr
QMgr
QMgr
Little need to replicate each full
repository, just keep the two apart
Outside the datacenter, queue
managers must be locatable in either
site
IP switching layer or comma separated channel names
QMgr
1 2
Recovering everything
Datacenter Replication
synchronous
51. 51
WebSphere MQ
IBM Software Group | WebSphere software
Synchronous disk replication
In either of these scenarios life is simple from a clustering perspective
As long as all queue managers see the fail over instance as ‘in the same place’,
or understand 7.0.1 style connection names, no other consideration is required
Some administrators will prefer to include full repositories in DR failover unit – no
strong requirement for this unless other factors apply
As long as good availability expectation between the pair, can add a new one at leisure to
pick up the strain in event of real loss of one.
May add significantly to performance cost of replication
52. 52
WebSphere MQ
IBM Software Group | WebSphere software
Asynchronous Replication
Datacenter 1
1
QMgr
2
QMgr
Datacenter 2
QMgr QMgr
QMgr
QMgr
QMgr
QMgr
Backup queue managers contain
historic messages (if any).
Cluster state will also be historic.
Refreshing cluster state on failover
and failback is essential.
1 2
QMgr
REFRESH
REFRESH
Recovering MQ resources
Datacenter Replication
asynchronous
53. 53
WebSphere MQ
IBM Software Group | WebSphere software
Asynchronous replication
Remember that cluster state will be persisted as ‘data’
REFRESH mandatory on restore from backup, failover, or ‘fail back’ to live.
Either a cloned queue manager or a backup can be made to work
Our experience is that when things go wrong, a ‘true’ backup is easier to work with
Same process then whether preserving some application data or not
Most common problem – missed refresh when reverting to ‘Live’ – things may appear to work
for a while…
IP address / conname can:
Change and be ok once re-advertised (after a REFRESH)
For a manually cloned queue manager this is probably the default
Blank connames also make this easy
Change but not actually need to re-advertise
E.g. Comma separated list – still need the REFRESH step though
Remain the same
Assuming have capability to modify routing, or DNS conname used
A new queue manager appearing with same name as an existing (possibly failed)
queue manager will be allowed in to take its place.
Message AMQ9468 / CSQX468I added to warn when this occurs
54. 54
WebSphere MQ
IBM Software Group | WebSphere software Datacenter 1
Datacenter 2
QMgr
QMgr
QMgr
QMgr
Backup queue managers are always
running.
Cluster workload balancing used to
direct traffic to live queue managers.
Messages will be trapped on live queue
managers in the event of a failure.
Applications must be designed to accommodate this configuration.
QMgr
QMgr
1
QMgr
2
QMgr
3
QMgr
4
QMgr
3
QMgr
4
Application availability
No Replication
warm standby
55. 55
WebSphere MQ
IBM Software Group | WebSphere software
Warm standby
This is the other ‘easy’ scenario, and the recommendation wherever possible
Applications must be designed to have loose affinities to any particular queue
manager
Put messages to clustered queues rather than Queue X @ QMgr Y
CLWLPRTY or for manual control CLWLRANK allow smooth switching between
primary and secondary instances as required
Data on failed queue managers will be trapped unless and until restarted
Implies applications must be able to replay
If this means duplication possible, restart procedures may need to clear out
This is the same as the earlier ‘One cluster’ scenario
56. 56
WebSphere MQ
IBM Software Group | WebSphere software
Everything
Live, cross center,
WebSphere MQ clustering
Duplicated queue manager
configuration
Restore from stale
backup
Restore nearly live
backup
Live disk replication
Asynchronous
replication
synchronous
replication
active/active
COST
How much do we need to recover?
WebSphere MQ resources
Application availability
REFRESH