Businesses are transforming their enterprise IT infrastructure so that application teams can provision resources in an automated, self-service or "as-a-Service" fashion, often from a self-service portal or as part of an on-premise Platform-as-a-Service (PaaS). In this session, we explain the tools and techniques that are available to integrate MQ into such an environment. This changes an MQ deployment from a high-touch activity with significant interaction between humans on the application and middleware teams to an automated, efficient process.
IBM MQ provides reliable, secure messaging capabilities. It ensures exactly once delivery of transactional messages and has been proven reliable over 25 years. MQ supports various APIs, protocols, and languages to connect diverse applications simply and at scale. It can integrate with systems like Salesforce, blockchain, and Kafka through bridges and connectors. Management of MQ is evolving to support consistent configuration, automated deployment, configuration as code, self-service, and integration of diagnostic data for improved operations.
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.
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.
Building an Active-Active IBM MQ Systemmatthew1001
Shows how message availability and service availability can be configured to reduce downtime and improve overall availability of your MQ network. Demonstrates how Uniform Clusters can be used to help keep your service availability high.
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.
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.
This presentation gives an overview of the many updates to the IBM MQ family of messaging products leading up to the release on MQ V9.1 LTS in July 2018. Learn how MQ has been continuously delivering new features and capabilities, enabling enterprise level messaging in ever more cloud and on-prem solutions, whether you're building your own MQ environment, using the MQ Appliance or looking to consume MQ as a service. This presentation introduces the main updates made to MQ during the 9.0.x continuous delivery releases that culminated in MQ 9.1 long term support release.
IBM MQ provides reliable, secure messaging capabilities. It ensures exactly once delivery of transactional messages and has been proven reliable over 25 years. MQ supports various APIs, protocols, and languages to connect diverse applications simply and at scale. It can integrate with systems like Salesforce, blockchain, and Kafka through bridges and connectors. Management of MQ is evolving to support consistent configuration, automated deployment, configuration as code, self-service, and integration of diagnostic data for improved operations.
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.
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.
Building an Active-Active IBM MQ Systemmatthew1001
Shows how message availability and service availability can be configured to reduce downtime and improve overall availability of your MQ network. Demonstrates how Uniform Clusters can be used to help keep your service availability high.
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.
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.
This presentation gives an overview of the many updates to the IBM MQ family of messaging products leading up to the release on MQ V9.1 LTS in July 2018. Learn how MQ has been continuously delivering new features and capabilities, enabling enterprise level messaging in ever more cloud and on-prem solutions, whether you're building your own MQ environment, using the MQ Appliance or looking to consume MQ as a service. This presentation introduces the main updates made to MQ during the 9.0.x continuous delivery releases that culminated in MQ 9.1 long term support release.
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.
Interconnect 2017: 6885 Deploying IBM MQ in the cloudRobert Parker
Presentation delivered at Interconnect 2017 Session ID 6885.
Most businesses are either already using cloud technologies, or are planning to do so in the near future. Whether it's moving to a public or private cloud environment, or simply adopting cloud-like practices in deploying and managing your on-premise systems, many of you are doing this with IBM MQ. There are an almost endless number of cloud technologies available: IBM Bluemix, Microsoft Azure, Amazon Web Services, OpenStack, Docker, Kubernetes, Chef, Google Cloud Platform... This session will give an overview of many of these technologies and platforms, and describe how IBM MQ should be deployed, configured and managed when using them.
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.
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.
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
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.
These slides were presented at the Cloud Technical University 2017 in Madrid.
Businesses are transforming their enterprise IT infrastructure to run in the Cloud. This doesn't have to be a simple lift and shift, it
promotes selfservice practices and new automated deployment and management techniques. This session will explain the many
possibilities and techniques that are available to run MQ in such environments, whether you're looking to move to a public or private
cloud, such as Bluemix, Azure, AWS, OpenStack or Docker environments.
Deploying and managing IBM MQ in the CloudRobert Parker
When moving to the cloud you want to ensure that the deployment and management of your cloud queue managers is as easy and streamlined as possible. In this session we will look at a few tools you can use to deploy and manage your queue managers, as well as where you can find examples of these tools in action.
This presentation was given at the WebSphere User Group in Hursley, June 2017.
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
New Tools and Interfaces for Managing IBM MQMatt Leming
The document provides an overview of new tools and interfaces for managing IBM MQ, including the mqweb server, MQ REST API, and MQ Console. The mqweb server runs the MQ Console and REST API applications using WebSphere Liberty Profile. The MQ REST API allows administering MQ via REST and JSON, providing alternatives to PCF. The MQ Console is a browser-based graphical tool for administering and managing MQ queues, queue managers, and other objects.
Enterprise messaging and IBM MQ is a critical part of any system, this session shows you how MQ is rapidly evolving to meet your needs. Irrespective of your platform or environment, this session introduces many of the updates to MQ in 2019 and 2020, whether that's in administration, building fault tolerant, scalable messaging solutions, or securing your systems.
IBM WebSphere MQ: Using Publish/Subscribe in an MQ NetworkDavid Ware
The publish/subscribe model can be used across a network of IBM WebSphere MQ queue managers, whether in a manually configured topology or in an MQ cluster. This session looks in depth at designing such systems, covering a wide range of requirements from availability to scalability and how they can be solved. A basic understanding of publish/subscribe in MQ would be beneficial, such as in "IBM WebSphere MQ: Using the Publish/Subscribe messaging paradigm"
This has been superseded by http://www.slideshare.net/DavidWare1/ame-2272-mq-publish-subscribe-network-pdf
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.
CTU 2017 I173 - how to transform your messaging environment to a secure messa...Robert Parker
This document summarizes an IBM Cloud Technical University session on transforming a messaging environment to be secure. The session covered various security features in IBM MQ including connection authentication, authorization, channel authentication using address maps and SSL peer maps, transport layer security (TLS), and security exits. It provided examples of how to configure each feature step-by-step, such as defining authentication information, setting channel authentication rules to blacklist addresses, and setting up a queue manager and channel to use TLS with certificates. The goal was to take an unsecured queue manager and secure it using these IBM MQ security features.
HHM-3481: IBM MQ for z/OS: Enhancing Application and Messaging Connectivity ...Matt Leming
Today's business environment is driving re-engineering of business systems using new techniques and architectures. This session will elaborate on the new environments MQ for z/OS is enabling for Java JMS applications, and enhanced interconnectivity capabilities that put MQ for z/OS at the vital heart of a hybrid messaging world.
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.
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).
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.
Introducing IBM Message Hub: Cloud-scale messaging based on Apache KafkaAndrew Schofield
IBM Message Hub is a new Bluemix service for messaging in the cloud. It's ideal for linking together microservices to build a scalable, flexible application in the cloud. It's great for feeding data at speed into other services such as analytics. You can also use it to bridge securely from your enterprise MQ systems into the cloud.
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.
The document discusses IBM's MQ infrastructure including MQ 7.1, MQ AMS, and MQ FTE. It provides an agenda covering universal connectivity with MQ, MQ File Transfer Edition, MQ security with MQ AMS, and features of MQ 7.1 including security policies. The document is presented by AJ Aronoff from Prolifics and focuses on MQ infrastructure for security and high availability.
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
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.
Interconnect 2017: 6885 Deploying IBM MQ in the cloudRobert Parker
Presentation delivered at Interconnect 2017 Session ID 6885.
Most businesses are either already using cloud technologies, or are planning to do so in the near future. Whether it's moving to a public or private cloud environment, or simply adopting cloud-like practices in deploying and managing your on-premise systems, many of you are doing this with IBM MQ. There are an almost endless number of cloud technologies available: IBM Bluemix, Microsoft Azure, Amazon Web Services, OpenStack, Docker, Kubernetes, Chef, Google Cloud Platform... This session will give an overview of many of these technologies and platforms, and describe how IBM MQ should be deployed, configured and managed when using them.
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.
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.
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
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.
These slides were presented at the Cloud Technical University 2017 in Madrid.
Businesses are transforming their enterprise IT infrastructure to run in the Cloud. This doesn't have to be a simple lift and shift, it
promotes selfservice practices and new automated deployment and management techniques. This session will explain the many
possibilities and techniques that are available to run MQ in such environments, whether you're looking to move to a public or private
cloud, such as Bluemix, Azure, AWS, OpenStack or Docker environments.
Deploying and managing IBM MQ in the CloudRobert Parker
When moving to the cloud you want to ensure that the deployment and management of your cloud queue managers is as easy and streamlined as possible. In this session we will look at a few tools you can use to deploy and manage your queue managers, as well as where you can find examples of these tools in action.
This presentation was given at the WebSphere User Group in Hursley, June 2017.
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
New Tools and Interfaces for Managing IBM MQMatt Leming
The document provides an overview of new tools and interfaces for managing IBM MQ, including the mqweb server, MQ REST API, and MQ Console. The mqweb server runs the MQ Console and REST API applications using WebSphere Liberty Profile. The MQ REST API allows administering MQ via REST and JSON, providing alternatives to PCF. The MQ Console is a browser-based graphical tool for administering and managing MQ queues, queue managers, and other objects.
Enterprise messaging and IBM MQ is a critical part of any system, this session shows you how MQ is rapidly evolving to meet your needs. Irrespective of your platform or environment, this session introduces many of the updates to MQ in 2019 and 2020, whether that's in administration, building fault tolerant, scalable messaging solutions, or securing your systems.
IBM WebSphere MQ: Using Publish/Subscribe in an MQ NetworkDavid Ware
The publish/subscribe model can be used across a network of IBM WebSphere MQ queue managers, whether in a manually configured topology or in an MQ cluster. This session looks in depth at designing such systems, covering a wide range of requirements from availability to scalability and how they can be solved. A basic understanding of publish/subscribe in MQ would be beneficial, such as in "IBM WebSphere MQ: Using the Publish/Subscribe messaging paradigm"
This has been superseded by http://www.slideshare.net/DavidWare1/ame-2272-mq-publish-subscribe-network-pdf
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.
CTU 2017 I173 - how to transform your messaging environment to a secure messa...Robert Parker
This document summarizes an IBM Cloud Technical University session on transforming a messaging environment to be secure. The session covered various security features in IBM MQ including connection authentication, authorization, channel authentication using address maps and SSL peer maps, transport layer security (TLS), and security exits. It provided examples of how to configure each feature step-by-step, such as defining authentication information, setting channel authentication rules to blacklist addresses, and setting up a queue manager and channel to use TLS with certificates. The goal was to take an unsecured queue manager and secure it using these IBM MQ security features.
HHM-3481: IBM MQ for z/OS: Enhancing Application and Messaging Connectivity ...Matt Leming
Today's business environment is driving re-engineering of business systems using new techniques and architectures. This session will elaborate on the new environments MQ for z/OS is enabling for Java JMS applications, and enhanced interconnectivity capabilities that put MQ for z/OS at the vital heart of a hybrid messaging world.
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.
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).
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.
Introducing IBM Message Hub: Cloud-scale messaging based on Apache KafkaAndrew Schofield
IBM Message Hub is a new Bluemix service for messaging in the cloud. It's ideal for linking together microservices to build a scalable, flexible application in the cloud. It's great for feeding data at speed into other services such as analytics. You can also use it to bridge securely from your enterprise MQ systems into the cloud.
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.
The document discusses IBM's MQ infrastructure including MQ 7.1, MQ AMS, and MQ FTE. It provides an agenda covering universal connectivity with MQ, MQ File Transfer Edition, MQ security with MQ AMS, and features of MQ 7.1 including security policies. The document is presented by AJ Aronoff from Prolifics and focuses on MQ infrastructure for security and high availability.
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
IBM Messaging Security - Why securing your environment is important : IBM Int...Leif Davidsen
Presentation from IBM InterConnect 2016 . With growth in the number of business applications and exponential growth in connectivity between applications and systems, it is important to understand not just how to implement security, but why it is important to ensure all parts of the business can appreciate it and apply the right levels of security to their messaging system use. - jointly presented by Leif Davidsen and Rob Parker
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.
This document provides an agenda for a training on WebSphere Message Broker concepts, technical walkthroughs, and application development. The agenda covers prerequisites, introductions to application integration challenges, enterprise application integration, service oriented architecture, the enterprise service bus, WebSphere Message Broker, ESQL, developing applications using ESQL, Java, and mappings. It also covers installing and configuring WebSphere Message Broker, examples, and troubleshooting. The training will provide concepts and hands-on labs related to integrating applications and developing integration solutions using WebSphere Message Broker.
IBM presentation at Digital Media Barcelona- Twitter For Business Microbloggi...the bureau, digital agency
IBM presentation: Twitter for business - Microblogging goes to work by Delphine Remy-Boutant, WW Social Media Marketing Manager IBM SWG - Digital Media Barcelona event 16th September
The document discusses interactive displays and kiosks in libraries. It provides examples of different types of kiosks and displays seen in various libraries, including touchscreen displays showing maps, availability of computers, and digital signage. Guidelines and best practices are presented for designing accessible and usable kiosks, including testing interfaces with users. Various software options and tools for creating digital signage and interactive displays are also listed.
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.
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.
The bits bytes and business benefits of securing your mq environment and mess...Leif Davidsen
The document discusses securing IBM MQ environments and messages. It outlines the business need for connectivity and how an increasingly connected environment also increases security risks. It then discusses various methods for securing MQ, including authentication, authorization, auditing, and encryption. It emphasizes that securing systems is important but proving security through auditing and documentation is also critical. Finally, it recommends that readers review their MQ security policies and practices to ensure they are up to date on the latest versions and security features.
Whats new in IBM MQ; V9 LTS, V9.0.1 CD and V9.0.2 CDDavid Ware
This has now been superseded by https://www.slideshare.net/DavidWare1/whats-new-in-ibm-mq-march-2018
Messaging is the secret ingredient for linking your applications together, whether they're in the cloud, your datacenters, or across all these environments. IBM MQ is ideally placed to perform that task. This session will take you through all the updates to the IBM MQ portfolio from June 2016 to March 2017, from the most recent continuous delivery releases to the new cloud environments where IBM MQ runs.
This document introduces IBM Message Hub, which is Apache Kafka as a service on Bluemix. Message Hub provides Kafka with additions like multi-tenancy, security features, REST APIs, administration interfaces, and monitoring. It discusses how Message Hub is based on Kafka 0.9 but with IBM contributions back to the community. The document also outlines the key features of Message Hub around multi-tenancy, security, flexibility, management, and performance. Other related Bluemix services like Message Connect and the Message Hub Incubator are also briefly mentioned.
WMQ Toolbox: 20 Scripts, One-liners, & Utilities for UNIX & Windows T.Rob Wyatt
This document provides summaries of 20 tools, scripts, and utilities for working with WebSphere MQ on UNIX and Windows systems. It begins with some equivalents between UNIX and Windows commands, then describes each tool in 1-2 sentences, including parsing trigger messages from the command line, checking if a queue manager is running, finding queues with message depths above a threshold, stopping all channels on a queue manager, and enhancing MQSC scripts and FTE XML files.
Design - Integration Scenarios for Hybrid CloudLaurenWendler
This document discusses hybrid cloud integration and is presented by Dave Beeler, an IBM Federal Hybrid Cloud Architect. It makes three key points:
1. There is an increasing need to integrate across hybrid environments as businesses adopt both on-premise and cloud-based systems.
2. Three trends are changing the integration market: the rise of "two-speed IT", systems of insight and engagement, and the API economy.
3. IBM offers a hybrid integration platform that provides a cohesive set of modular services to address any integration need across on-premise and cloud environments. These include integration tools, API management, and hybrid cloud services.
IBM Interconnect 2016. This session outlines the offerings and initiatives that IBM provides around cloud and "as-a-service" messaging. We explain their roles and how they work together to deliver agility to business, while retaining the mission-critical reliability that enterprises have come to expect of IBM messaging. Topics include the work we are doing in IBM MQ Enterprise messaging to facilitate its deployment in public and private IaaS clouds, the use of MQ in Docker and how we are making it easier to build self-service deployments on-premise, the new MQ Light API and how it can be exploited from IBM Bluemix and "fast-speed of IT" systems of engagement, the MQ Light Service for IBM Bluemix and the work we are doing with the Apache Kafka project.
DevOps & Continuous Test for IIB and IBM MQStuart Feasey
This document discusses the benefits of continuous testing and service virtualization. It notes that continuous testing helps enable agile practices across the development lifecycle by allowing teams to test earlier with greater coverage at lower cost. It also discusses how service virtualization can help test integration points without requiring real services, thus speeding up testing. The document provides an example of how IBM products like Rational Integration Tester and Rational Test Virtualization Server can be used to continuously test applications and their interactions with virtualized services as part of the development and deployment process.
IBM MQ: Using Publish/Subscribe in an MQ NetworkDavid Ware
The publish/subscribe model can be used across a network of MQ queue managers, whether in a manually configured topology or in an MQ cluster. This session looks in-depth at designing such systems, covering a wide range of requirements from availability to scalability, and explaining how they can be addressed. A basic understanding of publish/subscribe in MQ would be beneficial for attendees.
For an introduction to MQ publish/subscribe, first see this presentation: http://www.slideshare.net/DavidWare1/ame-2271-mq-publish-subscribe-pdf
Apache Kafka Reliability Guarantees StrataHadoop NYC 2015 Jeff Holoman
Kafka provides reliability guarantees through replication and configuration settings. It replicates data across multiple brokers to protect against failures. Producers can ensure data reaches the brokers through configuration of request.required.acks. Consumers can commit offsets to prevent data loss. Monitoring is also important to detect any potential data loss between producers and consumers.
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.
IBM Smart Cloud Orchestrator is a cloud management platform that allows businesses to leverage IBM as a business partner. It provides an overview of Smart Cloud Orchestrator and the IBM Cloud Marketplace. It discusses how business partners can engage with IBM and benefit from opportunities to reach new customers by providing integration content and solutions on the marketplace. It also covers how partners can get technical enablement, certification for their content, early access to betas, and exposure at IBM conferences. The document provides information for business partners on how to develop and deliver content for Smart Cloud Orchestrator and the IBM Cloud Marketplace.
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.
HHM 6887 Managing Your Scalable Applications in an MQ Hybrid Cloud Worldmatthew1001
This document provides an overview of IBM MQ sessions at the InterConnect 2017 conference, including:
- A schedule of MQ sessions occurring each day of the conference across topics like the MQ Appliance, hybrid cloud, and security.
- A brief description of each session including titles and speakers.
- A notice that the information provided is subject to change and limitations on warranties and liability.
The document discusses the benefits of automating various IT projects and processes using the MidVision extension for IBM Rational Automation Framework. It provides examples of projects that can be accelerated through automation, such as middleware upgrades, platform migrations, and core application upgrades. The MidVision extension allows centralized management of WebSphere MQ configurations and deployment of changes similarly to code. It helps reduce errors and ensures consistency across environments.
IBM's SmartCloud Orchestrator provides end-to-end automation of cloud service delivery through workload orchestration, resource orchestration, and service orchestration. It integrates with existing data center tools and processes using open standards. The Orchestrator includes content types like software bundles, virtual images, and patterns to automate multi-tier application deployments. It also allows custom orchestration operations through actions, user interfaces, and service offerings.
The Microservices approach is a new way of building composable, cloud-native applications. This session is designed for developers who are transforming existing applications to Microservices, or creating new Microservices style applications. The session will cover best practices, patterns including Service Registration and Discovery, and key development tools required for building distributed Microservices style applications. The session will also cover best practices for automating the operations of these applications, using container orchestration services.
IaaS provides on-demand, self-service access to computing resources like servers and storage. PaaS automates the deployment of applications on top of IaaS and handles scaling. SaaS delivers applications to users through a thin client like a web browser. iPaaS facilitates integration between SaaS, PaaS, IaaS, and on-premise systems through a cloud-based platform. Popular IaaS include OpenStack and VMware vSphere, PaaS include Cloud Foundry and OpenShift, while Salesforce and Office 365 are examples of SaaS.
This document provides an overview of enterprise cloud transformation best practices. It discusses key aspects of cloud maturity models, alignment of IT and business strategy, agile cloud development practices, and software defined networking (SDN). Specific topics covered include virtualization maturity, cloud brokerage, application lifecycles, and network functions virtualization. Examples from AT&T and Virtela are given to illustrate real-world SDN implementations.
Automating the Cloud: A Deep Dive into Virtual Machine ProvisioningHitesh Mohapatra
Virtual machine provisioning allows users to quickly provision new virtual machines through a self-service interface in minutes, rather than the days it previously took to provision physical servers. Virtual machine migration also allows live migration of virtual machines between physical hosts in milliseconds for maintenance or upgrades. Standards like OVF and OCCI help ensure interoperability and portability of virtual machines across platforms. The virtual machine lifecycle includes provisioning, serving requests, and deprovisioning resources when the service is ended.
GWC : MQ Light - from monolith to Microservices for speed and scaleachatt83
The presentation I used in the Global WebSphere Community's webcast covering how MQ Light is being used to connect together components of a microservice architecture
Virtual machine provisioning automates the process of deploying new virtual machines on physical servers in minutes rather than the days it previously took. It allocates computing resources to support the virtual machine. Virtual machine migration allows maintenance tasks to be completed in milliseconds rather than hours by live migrating virtual machines between physical servers. Together, provisioning and migration improve efficiency and flexibility while maintaining service availability and meeting service level agreements.
Virtual machine provisioning automates the process of deploying new virtual machines on physical servers in minutes rather than the days it previously took. It allocates computing resources to support the virtual machine. Virtual machine migration allows maintenance tasks to be completed in milliseconds rather than the lengthy downtime previously required. Together, provisioning and migration improve efficiency and flexibility while maintaining service availability and meeting service level agreements.
The document provides an overview of new features in Version 9 of IBM Integration Bus. Key highlights include:
- Graphical tools that make integration development more simple and productive, such as an enhanced graphical mapper.
- Universal connectivity that supports diverse platforms and systems, including .NET, databases, and message queues.
- Industry-specific functionality like enhancements for healthcare integration.
- Dynamic capabilities like integrated policies for managing integration workload and system performance.
- Visualization and monitoring of integrations in real-time through a web console.
The Overview of Microservices ArchitectureParia Heidari
This document discusses monolithic architecture and microservices architecture. It begins by defining monolithic architecture as having a single code base with multiple components/modules. It then lists advantages like being simple to develop, test, deploy and scale, as well as drawbacks like flexibility, maintenance, reliability, and scaling challenges.
Microservices architecture is presented as a solution to problems with monolithic architecture. Each microservice has a specific focus and functionality. Benefits include improved testability, loose coupling, and ability to develop, deploy and scale services independently. Challenges include increased complexity of developing, testing and operating distributed systems.
The document provides examples and discusses strategies for migrating a monolithic system to microservices, technologies
A rules based incident ticketing and tracking platform ideally suited for all customer facing enterprises, who want to record, track and resolve any and every customer issue or complaint within a time bound framework.
Features vertical movement (escalation) as well as horizontal (propagation) of all tickets, thereby enabling to record the complete lifecycle of a ticket.
Join Marc Trouard-Riolle from Citrix Cloud Product Marketing for the latest presentation in the Citrix Cloud Master Class series.
In this session you will hear about building private enterprise clouds with Citrix CloudPlatform:
Learn about hypervisor, storage and networking considerations within private cloud use cases
Build a tailored availability zone for traditional workloads
See a step-by-step demonstration of building an enterprise private cloud
Francisco Javier Ramirez Urea - Hopla - OSL19marketingsyone
Title: Building Modern Applications with Docker 3.0
Docker Enterprise provides an enterprise grade solution to allow your team to modernize your applications. In this talk we will see how Docker will help us to build, ship and run applications faster. Integrating Docker Enterprise Solutions in our development pipelines.
We will review all new features that came with release 3.0 to improve our application building workflow.
Similar to InterConnect 2016: IBM MQ self-service and as-a-service (20)
Mobile app Development Services | Drona InfotechDrona Infotech
Drona Infotech is one of the Best Mobile App Development Company In Noida Maintenance and ongoing support. mobile app development Services can help you maintain and support your app after it has been launched. This includes fixing bugs, adding new features, and keeping your app up-to-date with the latest
Visit Us For :
Everything You Need to Know About X-Sign: The eSign Functionality of XfilesPr...XfilesPro
Wondering how X-Sign gained popularity in a quick time span? This eSign functionality of XfilesPro DocuPrime has many advancements to offer for Salesforce users. Explore them now!
WWDC 2024 Keynote Review: For CocoaCoders AustinPatrick Weigel
Overview of WWDC 2024 Keynote Address.
Covers: Apple Intelligence, iOS18, macOS Sequoia, iPadOS, watchOS, visionOS, and Apple TV+.
Understandable dialogue on Apple TV+
On-device app controlling AI.
Access to ChatGPT with a guest appearance by Chief Data Thief Sam Altman!
App Locking! iPhone Mirroring! And a Calculator!!
Flutter is a popular open source, cross-platform framework developed by Google. In this webinar we'll explore Flutter and its architecture, delve into the Flutter Embedder and Flutter’s Dart language, discover how to leverage Flutter for embedded device development, learn about Automotive Grade Linux (AGL) and its consortium and understand the rationale behind AGL's choice of Flutter for next-gen IVI systems. Don’t miss this opportunity to discover whether Flutter is right for your project.
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.
UI5con 2024 - Keynote: Latest News about UI5 and it’s EcosystemPeter Muessig
Learn about the latest innovations in and around OpenUI5/SAPUI5: UI5 Tooling, UI5 linter, UI5 Web Components, Web Components Integration, UI5 2.x, UI5 GenAI.
Recording:
https://www.youtube.com/live/MSdGLG2zLy8?si=INxBHTqkwHhxV5Ta&t=0
Malibou Pitch Deck For Its €3M Seed Roundsjcobrien
French start-up Malibou raised a €3 million Seed Round to develop its payroll and human resources
management platform for VSEs and SMEs. The financing round was led by investors Breega, Y Combinator, and FCVC.
SOCRadar's Aviation Industry Q1 Incident Report is out now!
The aviation industry has always been a prime target for cybercriminals due to its critical infrastructure and high stakes. In the first quarter of 2024, the sector faced an alarming surge in cybersecurity threats, revealing its vulnerabilities and the relentless sophistication of cyber attackers.
SOCRadar’s Aviation Industry, Quarterly Incident Report, provides an in-depth analysis of these threats, detected and examined through our extensive monitoring of hacker forums, Telegram channels, and dark web platforms.
How Can Hiring A Mobile App Development Company Help Your Business Grow?ToXSL Technologies
ToXSL Technologies is an award-winning Mobile App Development Company in Dubai that helps businesses reshape their digital possibilities with custom app services. As a top app development company in Dubai, we offer highly engaging iOS & Android app solutions. https://rb.gy/necdnt
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.
Using Query Store in Azure PostgreSQL to Understand Query Performance
InterConnect 2016: IBM MQ self-service and as-a-service
1. HHM-3613 Deploying MQ resources in a self-service
or as-a-service infrastructure
David Ware
IBM MQ Architect
2. Please Note:
2
• 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.
4. Why?
Enterprises need increased agility with improved administration efficiency
“Applications deployed in minutes or hours, not months”
“Same size middleware team, more and more applications”
“The system must be able to respond to change”
• Business pressures on the infrastructure teams to do more with less
• Low MQ skills with application owners
• MQ must fit into a cloud deployment
5. How?
• MQ infrastructure teams must increase the speed of delivery to
their customers
• MQ complexities need hiding from the application teams
• Confidence in the MQ infrastructure must be maintained
• But how do you get that from MQ?
– Self service
• Providing a portal for self-service provisioning of MQ resources
– As a service
• Adopt a service style messaging architecture
http://ibm.biz/mqaas_red
6. Benefits
• Running a self service/as a service infrastructure will provide many benefits
– Increased agility
• Empowers lines of businesses
– Improved usability
• Concentrate on the meaning to the users, not MQ
– Improved efficiency
• Streamline the development, test and production roll outs
– Improved consistency
• Provides a framework for enforcing company standards and designs
8. The MQ Light Service in IBM Bluemix
• IBM runs a fully managed messaging
service for users in Bluemix
• Providing applications access to
asynchronous messaging using the
MQ Light API
• This is underpinned by a highly available,
fully automated MQ environment…
12. But behind the scenes
Bluemix Network Bridge
MQ Light Operations Tools
MQ Light Service Runtime
BlueMix Fabric
MQ Light
Service Broker
(Provisioning Interface)Cloud
Controller DEAs
Chef
server
MQ Light
Lookup App
(Directory Service)
Agent Pairs
[Multi-instance MQ Queue Managers]
(User apps)
Operations and Monitoring
Browser
Logstash
Servers
[Log Collation]
Conductor
[Operations
Functions]
Component
Store
Build
server
Retrieve
Connecton
Details
Connections from Applications
DevOps
Single Instance 2 Instances
https://mqlightprod-lookup.ng.bluemix.nethttps://mqlight-broker.ng.bluemix.net
Highly Available GPFS Storage Cluster [QM Data] ZooKeeper Cluster [Service State]
Grafana / Seyren
[Statistics and
Monitoring]
Omnibus Gateway
[Alarm Relay]
KeyBox
[Audited SSH
Access]
Operations
Portal
Quorum NSD
VM
Templates Omnibus Dashboard
[Alarm Dashboard]
VMRAID NSD RAID NSD VM VM VM VM VM
VM
BMBM
VM VM VM VM VM VMVM
Authenticated HTTP Proxy [Blink]
Port Forwarder
[BoschCli]
VM VM VM VM
MQ Light Delivery pipeline
Firewall rule allowing access for
Omnibus dashboard port 10002
Key Authenticated
SSH Proxy [BoschCli]
15. Self service
• Who is this ‘self’?
– Typically the application owning teams
– But could be the administration team
• Scope of self service?
– Development environments
– Test systems
– Production environments
• Extent of what to self serve?
– Simple provisioning of queues?
– Provisioning of whole queue managers and architectures?
16. Self service tooling
• From one point of view MQ’s “self service portal” is
simply its traditional administrative tooling
– I.e. MQ Explorer, runmqsc
– This provides remote access to MQ configuration, with per-
user/group authorisation for visibility and modification.
• Some expose all this to their development users
• However…
– You can’t expect your users to know all there is to know about
MQ configuration
– You probably only want to expose a subset of capabilities
– MQ is not the centre of the universe! You’ll need to coordinate
MQ resources with the other components in the solution
anyway
17. Self service tooling
• So from that point of view, MQ doesn’t have self service tooling
• And as no off the shelf solution will 100% match your corporation’s
requirements you’ll need to build/customise your own
– And many have built such tooling over the years
• Options for coordinated self service provisioning
• UrbanCode Deploy
• Pure Application Systems
• Chef, Puppet, …
• Third party tooling
• Hand rolled
• Instead, MQ provides the interfaces to make using these possible…
19. IBM UrbanCode Deploy
• UrbanCode orchestrates and automates the
deployment of applications and middleware
configurations into development, test and
production environments.
• Coordinates deployments across multiple
machines.
• MQ plugin for UrbanCode provides automations
for off the peg or customised deployments of
UrbanCode artefacts
• Queue manager creation
• Queues, channels, topics, etc.
• Custom mqsc scripts
• …
See the MQ as-a-service redpaper for details
20. IBM MQ Chef Cookbook
• Experimental IBM MQ cookbook
• Demonstrates idempotent installation on
MQ installation on Linux
• Includes queue manager creation and
start
• More to be added
• Feedback very welcome
https://github.com/ibm-messaging/mq-chef
21. Self-service portal considerations
• Limit the MQ options available to
users as much as possible
– This will depend on the expected MQ
skill level of users
– Minimise MQ resources and attributes
exposed to the users
– Ideally abstract the underlying MQ
resources from the users
– We’ll discuss this area more later
• Use a portal to act as an
intermediary
– Do not grant your users MQ
administrator rights, the portal is the MQ
administrator
• Log all changes
– Either using the portal
– Or (and) with MQ configuration events
• Integrate resources direct into the
monitoring system
– When provisioning systems, enable
background monitoring as standard
23. As a service MQ
• MQ has near infinite variations in architectures and
configurations
– Excellent for allowing customisation to your companies exact requirements
– Bad to expose to the end users through self-service
• To support self-service, limit those variations and
customisations to a minimal set of patterns
– Once the patterns have been determined, the self-service tooling should
map any requests onto the appropriate pattern
– This reduces the level of end user knowledge required to make changes
– It also simplifies the job of the operations teams in supporting such systems
• You may need to compromise on some of your customisations and
optimisations
24. MQ as a service best practices
• There is no single MQ pattern but there are
good practices that can make such
deployments more successful
– Naming conventions
– Separate the applications from the queue managers
– Application isolation
– MQ Clustering
– Messaging hubs
25. Naming conventions
• Pick a naming convention and
enforce it
– Use your self service portal to generate
the names, don’t leave it to the user
– Helps the operations teams to
understand the system even if it has
been created by the application teams
– Be mindful of the MQ 48 character,
special character, restrictions
– Map names of MQ resources into a directory
to record additional information
• For example, for each resource:
– Who is responsible for this resource?
– What applications are dependant of this
resource?
– What role is this resource playing?
– Unique within the application
• E.g. “ORGA.APPZ.REQUEST.Q1”
26. Detach applications from queue managers
• Binding an application to a specific queue manager can restrict future
changes
– Changes to architecture
– Changes to scale of messaging or application runtimes
– Changes to software versions
– Maintenance windows
• Run applications remote from the queue managers
– Connect as clients to queue managers
• Hide specific queue manager names from the applications
– An application should definitely not need to hard code a queue manager’s name
• Use Client Channel Definition Tables (CCDTs)
– These provide encapsulation of connection information
– Centrally administered and distributed to applications
– Enable security, high availability and workload balancing of clients
QMgr
Application ApplicationApplication
27. Client channel definition table (aka CCDT)
• Applications simply connect to a “queue
manager” name
• MQ architecture detail hidden from the
application
• CCDT defines which real queue managers
the application will connect to
– Can be a single queue manager
– Or a group, defined in the CCDT
• Selection can be ordered or randomised
and weighted
QM1
QM3
QM2
CCDT
QMGRP1: QM1
QMGRP2: QM2
QMGRP2: QM3
Application 1
connect: *QMGRP1
Application 2
connect: *QMGRP2
Application 2
connect: *QMGRP2
Use ‘*’ names to decouple the application from the real queue manager name
28. • CCDTs can represent connection details to
multiple queue managers
• CLNTCONN channels are defined to identify the
SVRCONN channels
• Define multiple CLNTCONNs in a central place to
generate the CCDT
– It doesn’t have to be any of the queue managers owning the
SVRCONNs
– Pre-MQ V8: Use a dedicated queue manager for this
purpose
– MQ V8: Use runmqsc –n to remove the need for a queue
manager
• Distribute CCDTs to the application locations
– Should be integrated into the orchestration of
MQ resources and applications.
Client channel definition table (aka CCDT)
Create the QMgrs and define
their SVRCONNs
Centrally define all the
CLNTCONNs that represent
all the QMgrs
Take the CCDT and make
available to the connecting
applications
• A single CCDT for your MQ estate or one per
application?
– A single CCDT can be easier to create but updates can be
expensive
– Separate CCDTs make it easier to update when an
application’s needs change
29. AppApp
Queue manager tenancy
• Multiple applications need isolation from each other
– Security and impact
• Do you share queue managers or provide dedicated ones for your users?
• Multi tenant
– Lower machine overheads
– More care needed in configuring to achieve isolation
• Isolation of machine resources not possible
– Harder/simpler to monitor
• Depends on your view of more queue managers
– Fine grain security required
• Single tenant
– Simple to configure, maintain and monitor
– Very good isolation
– A proliferation of queue managers
– Harder when integration is required
QMgr
App
QMgr
App
QMgr
App
QMgr
App
App
App
QMgr
App
App
App
QMgr
App
30. Queue manager architectures
• Standardize your queue managers
– Minimise bespoke configurations
– Groups of queue managers have roles, providing
equivalent capabilities
– Consider a layered architecture
• For example:
– Connectors: Queue managers that inbound
applications connect to
– Service providers: Queue managers that
host the resources being serviced
31. MQ Clustering for integration
• MQ clusters is the right way to connect queue
managers together for as-a-service
• Fits the model of easily adding and removing
queue managers
• Dynamically handles end-to-end routing
• Provides workload balancing for horizontal
scaling and dynamic routing for continuous
availability
• Drastically reduces the amount of
configuration required when new resources
are defined, simplifying any self service
solution
QMgr
QMgr
QMgr
QMgr
QMgr
32. An MQ Hub topology
• Pulling all this together into the MQ “Hub” topology
– The hub decouples the applications from the
underlying MQ infrastructure
MQ
App
App
App
App
App
App
App
App
Service requestor or
event emitters
Service provider or
long running consumer
33. An MQ Hub topology
App
App
App
App
App
App
App
App
QM1
QM2
QM2
QM1
Make each queue manager highly
available
Have multiple equivalent queue managers
• Pulling all this together into the MQ “Hub” topology
– High availability of the MQ runtime should be baked into the
hub design
34. An MQ Hub topology
App
App
App
App
App
App
App
App
QM1
QM2
QM2
QM1
Use CCDTs and design
applications to be able to
connect to one of many
queue managers
Connect instances of your
service applications to
more than one queue
manager
• Pulling all this together into the MQ “Hub” topology
– The applications must be configured to exploit the
availability of the MQ runtime
35. An MQ Hub topology
App
App
App
App
App
App
App
App
QM1
QM2
QM2
QM1
• Pulling all this together into the MQ “Hub” topology
– Separating out the MQ infrastructure into
front facing and service facing tiers can be
used to improve workload balancing.
QM1
QM2
QM4
QM3
Separate out the requestor/emitter queue managers from the
service provider queue managers
Use an MQ cluster to workload balance and dynamically route
work to the service providers
36. An MQ Hub topology
App
App
App
App
App
App
App
App
QM1
QM2
QM2
QM1
• Pulling all this together into the MQ “Hub” topology
QM1
QM2
QM4
QM3
QM5
QM5
App
App
App App
Applications and MQ
infrastructure can now be
independently scaled
38. MQ environments
• As a service architectures apply to every type of runtime
– Physical Hardware
– Virtual machines
– Containers
• Management and provisioning layers provide the real benefits
– PureApplication
– Docker with Kubernetes/Swarm/…
– Many, many others…
39. Physical hardware
• IBM MQ Appliance
• A dedicated environment to easily and
quickly provision and configure queue
managers
• No external dependencies
– Simplifies provisioning
– Normalises behaviour
App
App
App
App
App
App
App
App
QM1
QM2
QM1
QM2
QM1
App
App
App App
40. Virtual machines
• IBM supports MQ running in virtual machines
– Simply build your VM based on a supported MQ O/S
– Install MQ plus any required software and configuration
– Use and reuse, from development through to production
• Many benefits
– Simple replication of environments
• Using pre-canned, tried and tested, software stacks
– Isolation from host and other VMs
• Reduce risks from multi-tenancy
– Separation from physical servers
• More efficient utilisation of hardware
Virtual machine
Virtual machine
Virtual machine
Virtual machine
Virtual machine
Virtual machine
41. Operating system
Hypervisor
Virtual machine
Operating
system
Bins / libs
App App
Containers
• Containers provide a similar
environment to a VM but lighter in
weight
– A virtual machine provides an abstraction of the
physical hardware
– A container abstracts the OS level, typically at the
user level
• Linux containers
– Containers all share the same OS kernel
– Images are constructed from layered filesystems
– Containers isolate applications from each other and
the underlying infrastructure
Virtual machines
Operating system
Container
Bins / libs
App App
Container
App App
Bins / libs
Container
App App
Containers
Container
App App
Virtual machine
Operating
system
Bins / libs
App App
42. MQ in Docker
• Docker automates the deployment of applications inside
software containers
• MQ 8.0.0.4+ supported to run inside a Docker image.
Details: https://ibm.biz/mqdocker
• Brings the benefits of Docker to MQ
– Lightweight containers for running MQ
– Predictable and standardized units for deploying MQ
– Process, resource and dependency isolation
• IBM samples for customizing and building your own Docker images
– Best practice guidance
– Runs an MQ queue manager inside a container, isolated from the rest of your system
42
43. Persistent storage for containers and VMs
• Where VM or container storage is
ephemeral, alternative storage is
required
– Unless you are willing to create a fresh,
empty, queue manager every time the
container re-starts!
– Our example Docker files show the use
of Docker volumes for hosting the
queue manager data
• Storage options
– Local storage
• Simple but limits containers to a single system
– Networked block storage
• Relies on the container management to
reattach storage as required
– Networked filesystem
• Access across containers enables use of multi
instance queue managers and removes
requirement on container management
• MQ is sensitive to filesystem characteristics
The storage layer is critical to a queue manager’s performance, reliability,
availability and even identity
44. MQ ecosystem – what should we do next?
Architect
DevelopDeploy
Operate
44
45. Summary
• Self service will increase your agility and efficiency
• Define your best practices up front
• Design your MQ architecture to be deployed as-a-service
• Apply it to the runtime and orchestration framework of your choice
More sessions related to this topic this week:
Wednesday 2:30pm 6332 MQ Flow Automation & Self-service at Bloomberg
Thursday 8:30am 2931 Business agility through self service messaging
Thursday 11:30am 3537 Monitoring and managing hybrid messaging environments
46. IBM MQ early access programs
Interested in hearing about the future direction of MQ?
Want to influence the shape of features while they’re still on the drawing board?
Want access to early drivers?
Join any of the IBM MQ early programs
IBM MQ v.Next early program
IBM MQ Appliance early program
IBM MQ on HP Non Stop Server early program
Talk to your IBM contact, alternatively email pete_murphy@uk.ibm.com for further details
46
47. Where do I get more information?
IBM Messaging developerWorks
developer.ibm.com/messaging
IBM Messaging Youtube
https://www.youtube.com/IBMmessagingMedia
LinkedIn
Ibm.biz/ibmmessaging
Twitter
@IBMMessaging
IBM MQ Facebook
Facebook.com/IBM-MQ-8304628654/
48. Monday
10:30-11:30 3592 New MQ features
3452 Managing applications
12:00-13:00 2835 MQ on z/OS and Distributed
15:00-16:00 3470 Latest MQ z/OS features
2833 Where is my message?
3544 MQ Light in an MQ infrastructure
16:30-17:30 3573 Hybrid cloud messaging
2941 MQ Advanced
Tuesday
08:30-09:30 3540 The MQ Light API
12:00-13:00 3456 The IBM MQ Appliance
13:15-14:15 3499 Introducing Message Hub
3458 MQ Appliance administration
14:30-15:30 6432 MQ updates and futures (InnerCircle)
2849 Messaging feedback roundtable
16:00-17:00 3544 MQ Light in an MQ infrastructure
3513 MQ hands on lab
Wednesday
08:30-09:30 3602 Managing your MQ environment
12:00-13:00 3613 Designing MQ self service
6408 Hybrid messaging roadmap (InnerCircle)
13:15-14:00 3416 HA and DR with MQ
3433 Why secure your messaging?
15:45-16:30 3429 Securing MQ
2847 Meet the messaging experts
16:00-17:00 3508 MQ Light hands on lab
16:45-17:30 2275 Migrating to the IBM MQ Appliance
Thursday
08:30-09:15 3420 MQ Clustering
2931 Business agility with self service MQ
09:30-10:15 3479 MQ z/OS clusters and shared queue
3450 Optimising MQ applications
2849 Messaging feedback roundtable
10:30-11:15 3465 MQ Appliance high availability
3481 MQ z/OS messaging connectivity
11:30-12:15 3474 Active-active messaging
3537 Monitoring and managing MQ
3425 MQ publish/subscribe
Find us at the EXPO:
Hybrid Integration peds 65-68
Check out the Hybrid Messaging sub topic under the
Hybrid Integration topic for further customer and business
partner sessions
Hybrid Messaging from the IBM experts at InterConnect 2016
Sunday
14:30-15:30 6408 Hybrid messaging roadmap (InnerCircle)
50. Notices and Disclaimers Con’t.
50
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 h erein 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, Aspera®, Bluemix, Blueworks Live, CICS, Clearcase, Cognos®, DOORS®, Emptoris®, Enterprise Document Management System™, FASP®,
FileNet®, Global Business Services ®, Global Technology Services ®, IBM ExperienceOne™, IBM SmartCloud®, IBM Social Business®, Information on Demand, ILOG,
Maximo®, MQIntegrator®, MQSeries®, Netcool®, OMEGAMON, OpenPower, PureAnalytics™, PureApplication®, pureCluster™, PureCoverage®, PureData®,
PureExperience®, PureFlex®, pureQuery®, pureScale®, PureSystems®, QRadar®, Rational®, Rhapsody®, Smarter Commerce®, SoDA, SPSS, Sterling Commerce®,
StoredIQ, Tealeaf®, Tivoli®, Trusteer®, Unica®, 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.
51. Thank You
Your Feedback is Important!
Access the InterConnect 2016 Conference Attendee Portal to complete
your session surveys from your smartphone,
laptop or conference kiosk.