The document provides steps to set up a cluster between two queue managers, LONDON and NEWYORK, named INVENTORY. Key steps include defining the cluster name, designating queue managers as repositories, defining cluster receiver and sender channels, advertising the INVENTQ queue, and testing messaging between the queue managers.
This document contains 7 multiple choice questions about WebSphere MQ v7. The questions cover topics like what is required to support publish-subscribe messaging, commands for starting and stopping MQ tracing, security checks when connecting to a local queue manager from a distributed platform, the MQI API call that is not required when writing a message to a queue, where to look to determine access rights to an MQ object on distributed systems, the prefix for MQ error messages, and the operation that must be done first before writing messages to a queue.
WebSphere MQ is messaging and queuing middleware from IBM that allows applications to communicate asynchronously by sending messages to queues. It provides guaranteed message delivery, decoupling of sending and receiving applications, and publish/subscribe capabilities. Programs using the MQ API can connect to queue managers to put and get messages from queues without having direct connections to each other. Messages have properties and data, and can be persistent or non-persistent. Queues store messages and allow parallel access by multiple applications.
MQ Cluster cover by Murali Krishna Nookella
Murali Krishna Nookella covers MQ Cluster for the beginners in MQ
Murali Krishna Nookella case by concept covers Message Queue
Containers provide security through mechanisms like kernel namespaces, control groups (cgroups), and SELinux labels. The Docker daemon manages these mechanisms to isolate containers and apply resource limits. While containers enable application density and portability, administrators must still practice secure configuration by limiting container privileges, updating containers regularly, and monitoring logs. When used properly, containers can improve security by isolating applications and minimizing the risk of compromise.
This presentation covers how app deployment model evolved from bare metal servers to Kubernetes World.
In addition to theoretical information, you will find free KATACODA workshops url to perform practices to understand the details of the each topics.
Container Orchestration with Docker Swarm and KubernetesWill Hall
This presentation covers the basics of what container orchestration is providing pros and cons of Docker Swarm, Kubernetes and Amazon ECS and outlining the terms and tools you will need to successfully use them.
Windows Server 2003 supports two types of clusters: server clusters and network load balancing (NLB) clusters. Server clusters provide high availability for applications like databases and messaging servers, connecting each node to shared storage. NLB clusters balance load for applications like web servers, assigning each node a cloned data set. Designing an effective cluster involves considering availability needs, scaling options, and using tools like the Network Load Balancing Manager and Cluster Administrator.
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.
This document contains 7 multiple choice questions about WebSphere MQ v7. The questions cover topics like what is required to support publish-subscribe messaging, commands for starting and stopping MQ tracing, security checks when connecting to a local queue manager from a distributed platform, the MQI API call that is not required when writing a message to a queue, where to look to determine access rights to an MQ object on distributed systems, the prefix for MQ error messages, and the operation that must be done first before writing messages to a queue.
WebSphere MQ is messaging and queuing middleware from IBM that allows applications to communicate asynchronously by sending messages to queues. It provides guaranteed message delivery, decoupling of sending and receiving applications, and publish/subscribe capabilities. Programs using the MQ API can connect to queue managers to put and get messages from queues without having direct connections to each other. Messages have properties and data, and can be persistent or non-persistent. Queues store messages and allow parallel access by multiple applications.
MQ Cluster cover by Murali Krishna Nookella
Murali Krishna Nookella covers MQ Cluster for the beginners in MQ
Murali Krishna Nookella case by concept covers Message Queue
Containers provide security through mechanisms like kernel namespaces, control groups (cgroups), and SELinux labels. The Docker daemon manages these mechanisms to isolate containers and apply resource limits. While containers enable application density and portability, administrators must still practice secure configuration by limiting container privileges, updating containers regularly, and monitoring logs. When used properly, containers can improve security by isolating applications and minimizing the risk of compromise.
This presentation covers how app deployment model evolved from bare metal servers to Kubernetes World.
In addition to theoretical information, you will find free KATACODA workshops url to perform practices to understand the details of the each topics.
Container Orchestration with Docker Swarm and KubernetesWill Hall
This presentation covers the basics of what container orchestration is providing pros and cons of Docker Swarm, Kubernetes and Amazon ECS and outlining the terms and tools you will need to successfully use them.
Windows Server 2003 supports two types of clusters: server clusters and network load balancing (NLB) clusters. Server clusters provide high availability for applications like databases and messaging servers, connecting each node to shared storage. NLB clusters balance load for applications like web servers, assigning each node a cloned data set. Designing an effective cluster involves considering availability needs, scaling options, and using tools like the Network Load Balancing Manager and Cluster Administrator.
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.
A brief study on Kubernetes and its componentsRamit Surana
Kubernetes is an open source orchestration system for Docker containers. It handles scheduling onto nodes in a compute cluster and actively manages workloads to ensure that their state matches the users declared intentions. Using the concepts of "labels" and "pods", it groups the containers which make up an application into logical units for easy management and discovery.
Open Cluster Management (OCM) PresentationKnoldus Inc.
The Open Cluster Management project consists of several multi cluster components, which are used to access and manage your clusters. It was started to bring together the various aspects of managing Kubernetes clusters into an integrated solution comprised of loosely coupled building blocks
Kubernetes: An Introduction to the Open Source Container Orchestration PlatformMichael O'Sullivan
Originally designed by Google, Kubernetes is now an open-source platform that is used for managing applications deployed as containers across multiple hosts - now hosted under the Cloud Native Computing Foundation. It provides features for automating deployment, scaling, and maintaining these applications. Hosts are organised into clusters, and applications are deployed into these clusters as containers. Kubernetes is compatible with several container engines, notably Docker. The popularity of Kubernetes continues to increase as a result of the feature-rich tooling when compared to use of a container-engine alone, and a number of Cloud-based hosted solutions are now available, such as Google Kubernetes Engine, Amazon Elastic Container Service for Kubernetes, and IBM Cloud Container Service.
This talk will provide an introduction to the Kubernetes platform, and a detailed view of the platform architecture from both the Control Plane and Worker-node perspectives. A walk-through demonstration will also be provided. Furthermore, two additional tools that support Kubernetes will be presented and demonstrated - Helm: a package manager solution which enables easy deployment of pre-built Kubernetes software using Helm Charts, and Istio: a platform in development that aims to simplify the management of micro-services deployed on the Kubernetes platform.
Speaker Bio:
Dr. Michael J. O'Sullivan is a Software Engineer working as part of the Cloud Foundation Services team for IBM Cloud Dedicated, in the IBM Cloud division in Cork. Michael has worked on both Delivery Pipeline/Deployment Automation and Performance Testing teams, which has resulted in daily exposure to customer deployments of IBM Cloud services such as the IBM Cloud Containers Service, and the IBM Cloud Logging and Metrics Services. Michael has also worked on deployment of these services to OpenStack and VMware platforms. Michael holds a PhD in Computer Science from University College Cork (2012 - 2015), where, under the supervision of Dr. Dan Grigoras, engaged in research of Mobile Cloud Computing (MCC) - specifically, studying and implementing solutions for delivering seamless user experiences of MCC applications and services. Prior to this, Michael graduated with a 1st Class Honours Degree in Computer Science from University College Cork in 2012.
CloudStack is open source cloud computing software that manages infrastructure for cloud services. It supports various hypervisors like KVM, vSphere, and XenServer for virtualization. CloudStack manages the network, storage, and compute nodes that make up a cloud infrastructure. It allows service providers to offer self-service virtual machines, storage, and networking to customers and enterprises to offer private clouds to employees without involving IT departments. CloudStack provides features like automatic configuration, graphical user interface, APIs, high availability, and supports multiple hypervisors. It divides infrastructure into zones, pods, clusters, and regions for isolation, redundancy and management.
Openstack is an open source cloud operating system that manages large pools of compute, storage, and networking resources. It consists of several components including Nova (compute), Neutron (networking), Glance (images), Keystone (identity), and Cinder (block storage). The major hypervisor options supported by Openstack are KVM, XenServer, and vSphere. Common deployment models include a basic 3 node architecture with separate controller and compute nodes, or a scaled compute-only environment.
Kubernetes is an open-source tool for managing containerized applications across clusters of nodes. It provides capabilities for deployment, maintenance, and scaling of applications. The document discusses Kubernetes concepts like pods, deployments, services, namespaces and components like the API server, scheduler and kubelet. It also covers Kubernetes commands and configuration using objects like config maps, secrets, volumes and labels.
WebSphere MQ is a middleware tool that facilitates reliable application-to-application communication by sending and receiving messages via messaging queues. It provides a secure transport layer that moves data unchanged in the form of messages between applications across platforms. WebSphere MQ uses APIs to support programming languages like Java, C, COBOL. It differentiates between persistent and non-persistent messages to ensure reliable delivery. The queue manager maintains objects like queues, channels, and listens to ensure message flow.
Recent momentum around the evolution of Containers are gradually increase in last two years.Containers virtualize an OS and applications running in each container believe that they have full access to their very own copy of that OS. This is analogous to what VMs do when they virtualize at a lower level, the hardware. In the case of containers, it’s the OS that does the virtualization and maintains the illusion.
Recent past many software companies have quickly adopted container technologies, including Docker Containers, aware of the threat and advantage of the approach. For example, Linux companies have also jumped into the ground, seeing as this as an opportunity to grow the Linux market. Also Microsoft is going to add features to support containers and VMware have made efforts in integrating support for Docker into virtual machine technology.
Recent momentum around the evolution of Containers are gradually increase in last two years.Containers virtualize an OS and applications running in each container believe that they have full access to their very own copy of that OS. This is analogous to what VMs do when they virtualize at a lower level, the hardware. In the case of containers, it’s the OS that does the virtualization and maintains the illusion.
Recent past many software companies have quickly adopted container technologies, including Docker Containers, aware of the threat and advantage of the approach. For example, Linux companies have also jumped into the ground, seeing as this as an opportunity to grow the Linux market. Also Microsoft is going to add features to support containers and VMware have made efforts in integrating support for Docker into virtual machine technology.
This document outlines the topics that will be covered in a Linux high availability clustering training course. It will provide hands-on experience with configuring and managing a HA cluster using Pacemaker on Red Hat Enterprise Linux/CentOS. Key concepts that will be covered include cluster types, advantages of clustering, HA concepts like failover and fencing, cluster architecture, installing a basic cluster, managing cluster nodes and resources, troubleshooting, and using shared storage technologies like GFS2 and LVM in a clustered environment. Students will gain skills in deploying, configuring, and managing a production-ready HA infrastructure.
Kubernetes is an open-source system for automating deployment, scaling, and management of containerized applications. It groups containers that make up an application into logical units for easy management and discovery. Kubernetes masters manage worker nodes, and pods which are the basic building blocks, containing one or more containers. It provides self-healing, horizontal pod autoscaling, service discovery, load balancing, configuration management.
Kubernetes basics information along with stateful session infoKapildev292285
This document contains:
1. A set of Kubernetes icons that can be used to create diagrams about Kubernetes concepts and components.
2. Descriptions of common Kubernetes computing, storage, network, RBAC, and configuration resources.
3. Examples of how the icons can be used to depict Kubernetes architectures, applications, and relationships between components.
Recent momentum around the evolution of Containers are gradually increase in last two years.Containers virtualize an OS and applications running in each container believe that they have full access to their very own copy of that OS. This is analogous to what VMs do when they virtualize at a lower level, the hardware. In the case of containers, it’s the OS that does the virtualization and maintains the illusion.
Deploying oracle rac 10g with asm on rhel and sles with svcwikiwei
This document provides guidance on configuring Oracle RAC 10g with ASM on Red Hat Linux and SUSE Linux using the IBM SAN Volume Controller (SVC). The SVC simplifies storage management by pooling storage from various systems into a single resource and enables nondisruptive data migration. It also improves availability through replication services. The document outlines configuring the SVC, device mapper multipath, and identifying storage on cluster nodes for ASM. It aims to demonstrate an easy configuration using these guidelines.
ARCHITECTING TENANT BASED QOS IN MULTI-TENANT CLOUD PLATFORMSArun prasath
Achieving QOS in a multi-tenant cloud platforms is still a difficult task and many companies follow different approaches to solve this problem. Here in this document I tried architecting a simple solution for achieving different QOS for different tenants in a Multi-tenant cloud environment based on my experiments with containers , docker and cgroup on Openstack.
This plugin monitors the Microsoft Exchange Server 2007/2010 servers using a series of system commad and the software already installed on the system. For more information visit the following webpage: http://pandorafms.com/index.php?sec=Library&sec2=repository&lng=en&action=view_PUI&id_PUI=274
The document provides information about installing and configuring OpenStack including:
1) It describes the hardware, software and networking requirements for the control and compute nodes when installing OpenStack.
2) It explains the different deployment options for OpenStack including all-in-one, multiple control and compute nodes, and different options for separating services.
3) It provides steps for installing OpenStack using Packstack, including generating SSH keys, editing the answer file and starting the deployment.
4) It gives an overview of the message broker services used by OpenStack and describes how to configure RabbitMQ or Qpid as the message broker.
Practical Container Security by Mrunal Patel and Thomas Cameron, Red HatDocker, Inc.
You can secure your containerized microservices without slowing down development. Through a combination of Linux kernel features and open source tools, you can isolate the host from the container and the containers from each other, as well as finding vulnerabilities and securing data. Two of Red Hat's Docker contributors will discuss the state of container security today, covering Linux namespaces, SElinux, cgroups, capabilities, scan, seccomp, and other tools you can use right now.
This document provides step-by-step instructions for creating a high availability SQL Server 2008 R2 cluster with two nodes using Microsoft Cluster Service on Windows Server 2008 R2. It discusses SQL clustering requirements, changes in Windows 2008/R2 related to clustering, and considerations for installing and configuring a two-node SQL cluster. The document also references additional technologies like Network Load Balancing that can provide further redundancy and scalability beyond normal clustering constraints.
Docker moves very fast, with an edge channel released every month and a stable release every 3 months. Patrick will talk about how Docker introduced Docker EE and a certification program for containers and plugins with Docker CE and EE 17.03 (from March), the announcements from DockerCon (April), and the many new features planned for Docker CE 17.05 in May.
This talk will be about what's new in Docker and what's next on the roadmap
A brief study on Kubernetes and its componentsRamit Surana
Kubernetes is an open source orchestration system for Docker containers. It handles scheduling onto nodes in a compute cluster and actively manages workloads to ensure that their state matches the users declared intentions. Using the concepts of "labels" and "pods", it groups the containers which make up an application into logical units for easy management and discovery.
Open Cluster Management (OCM) PresentationKnoldus Inc.
The Open Cluster Management project consists of several multi cluster components, which are used to access and manage your clusters. It was started to bring together the various aspects of managing Kubernetes clusters into an integrated solution comprised of loosely coupled building blocks
Kubernetes: An Introduction to the Open Source Container Orchestration PlatformMichael O'Sullivan
Originally designed by Google, Kubernetes is now an open-source platform that is used for managing applications deployed as containers across multiple hosts - now hosted under the Cloud Native Computing Foundation. It provides features for automating deployment, scaling, and maintaining these applications. Hosts are organised into clusters, and applications are deployed into these clusters as containers. Kubernetes is compatible with several container engines, notably Docker. The popularity of Kubernetes continues to increase as a result of the feature-rich tooling when compared to use of a container-engine alone, and a number of Cloud-based hosted solutions are now available, such as Google Kubernetes Engine, Amazon Elastic Container Service for Kubernetes, and IBM Cloud Container Service.
This talk will provide an introduction to the Kubernetes platform, and a detailed view of the platform architecture from both the Control Plane and Worker-node perspectives. A walk-through demonstration will also be provided. Furthermore, two additional tools that support Kubernetes will be presented and demonstrated - Helm: a package manager solution which enables easy deployment of pre-built Kubernetes software using Helm Charts, and Istio: a platform in development that aims to simplify the management of micro-services deployed on the Kubernetes platform.
Speaker Bio:
Dr. Michael J. O'Sullivan is a Software Engineer working as part of the Cloud Foundation Services team for IBM Cloud Dedicated, in the IBM Cloud division in Cork. Michael has worked on both Delivery Pipeline/Deployment Automation and Performance Testing teams, which has resulted in daily exposure to customer deployments of IBM Cloud services such as the IBM Cloud Containers Service, and the IBM Cloud Logging and Metrics Services. Michael has also worked on deployment of these services to OpenStack and VMware platforms. Michael holds a PhD in Computer Science from University College Cork (2012 - 2015), where, under the supervision of Dr. Dan Grigoras, engaged in research of Mobile Cloud Computing (MCC) - specifically, studying and implementing solutions for delivering seamless user experiences of MCC applications and services. Prior to this, Michael graduated with a 1st Class Honours Degree in Computer Science from University College Cork in 2012.
CloudStack is open source cloud computing software that manages infrastructure for cloud services. It supports various hypervisors like KVM, vSphere, and XenServer for virtualization. CloudStack manages the network, storage, and compute nodes that make up a cloud infrastructure. It allows service providers to offer self-service virtual machines, storage, and networking to customers and enterprises to offer private clouds to employees without involving IT departments. CloudStack provides features like automatic configuration, graphical user interface, APIs, high availability, and supports multiple hypervisors. It divides infrastructure into zones, pods, clusters, and regions for isolation, redundancy and management.
Openstack is an open source cloud operating system that manages large pools of compute, storage, and networking resources. It consists of several components including Nova (compute), Neutron (networking), Glance (images), Keystone (identity), and Cinder (block storage). The major hypervisor options supported by Openstack are KVM, XenServer, and vSphere. Common deployment models include a basic 3 node architecture with separate controller and compute nodes, or a scaled compute-only environment.
Kubernetes is an open-source tool for managing containerized applications across clusters of nodes. It provides capabilities for deployment, maintenance, and scaling of applications. The document discusses Kubernetes concepts like pods, deployments, services, namespaces and components like the API server, scheduler and kubelet. It also covers Kubernetes commands and configuration using objects like config maps, secrets, volumes and labels.
WebSphere MQ is a middleware tool that facilitates reliable application-to-application communication by sending and receiving messages via messaging queues. It provides a secure transport layer that moves data unchanged in the form of messages between applications across platforms. WebSphere MQ uses APIs to support programming languages like Java, C, COBOL. It differentiates between persistent and non-persistent messages to ensure reliable delivery. The queue manager maintains objects like queues, channels, and listens to ensure message flow.
Recent momentum around the evolution of Containers are gradually increase in last two years.Containers virtualize an OS and applications running in each container believe that they have full access to their very own copy of that OS. This is analogous to what VMs do when they virtualize at a lower level, the hardware. In the case of containers, it’s the OS that does the virtualization and maintains the illusion.
Recent past many software companies have quickly adopted container technologies, including Docker Containers, aware of the threat and advantage of the approach. For example, Linux companies have also jumped into the ground, seeing as this as an opportunity to grow the Linux market. Also Microsoft is going to add features to support containers and VMware have made efforts in integrating support for Docker into virtual machine technology.
Recent momentum around the evolution of Containers are gradually increase in last two years.Containers virtualize an OS and applications running in each container believe that they have full access to their very own copy of that OS. This is analogous to what VMs do when they virtualize at a lower level, the hardware. In the case of containers, it’s the OS that does the virtualization and maintains the illusion.
Recent past many software companies have quickly adopted container technologies, including Docker Containers, aware of the threat and advantage of the approach. For example, Linux companies have also jumped into the ground, seeing as this as an opportunity to grow the Linux market. Also Microsoft is going to add features to support containers and VMware have made efforts in integrating support for Docker into virtual machine technology.
This document outlines the topics that will be covered in a Linux high availability clustering training course. It will provide hands-on experience with configuring and managing a HA cluster using Pacemaker on Red Hat Enterprise Linux/CentOS. Key concepts that will be covered include cluster types, advantages of clustering, HA concepts like failover and fencing, cluster architecture, installing a basic cluster, managing cluster nodes and resources, troubleshooting, and using shared storage technologies like GFS2 and LVM in a clustered environment. Students will gain skills in deploying, configuring, and managing a production-ready HA infrastructure.
Kubernetes is an open-source system for automating deployment, scaling, and management of containerized applications. It groups containers that make up an application into logical units for easy management and discovery. Kubernetes masters manage worker nodes, and pods which are the basic building blocks, containing one or more containers. It provides self-healing, horizontal pod autoscaling, service discovery, load balancing, configuration management.
Kubernetes basics information along with stateful session infoKapildev292285
This document contains:
1. A set of Kubernetes icons that can be used to create diagrams about Kubernetes concepts and components.
2. Descriptions of common Kubernetes computing, storage, network, RBAC, and configuration resources.
3. Examples of how the icons can be used to depict Kubernetes architectures, applications, and relationships between components.
Recent momentum around the evolution of Containers are gradually increase in last two years.Containers virtualize an OS and applications running in each container believe that they have full access to their very own copy of that OS. This is analogous to what VMs do when they virtualize at a lower level, the hardware. In the case of containers, it’s the OS that does the virtualization and maintains the illusion.
Deploying oracle rac 10g with asm on rhel and sles with svcwikiwei
This document provides guidance on configuring Oracle RAC 10g with ASM on Red Hat Linux and SUSE Linux using the IBM SAN Volume Controller (SVC). The SVC simplifies storage management by pooling storage from various systems into a single resource and enables nondisruptive data migration. It also improves availability through replication services. The document outlines configuring the SVC, device mapper multipath, and identifying storage on cluster nodes for ASM. It aims to demonstrate an easy configuration using these guidelines.
ARCHITECTING TENANT BASED QOS IN MULTI-TENANT CLOUD PLATFORMSArun prasath
Achieving QOS in a multi-tenant cloud platforms is still a difficult task and many companies follow different approaches to solve this problem. Here in this document I tried architecting a simple solution for achieving different QOS for different tenants in a Multi-tenant cloud environment based on my experiments with containers , docker and cgroup on Openstack.
This plugin monitors the Microsoft Exchange Server 2007/2010 servers using a series of system commad and the software already installed on the system. For more information visit the following webpage: http://pandorafms.com/index.php?sec=Library&sec2=repository&lng=en&action=view_PUI&id_PUI=274
The document provides information about installing and configuring OpenStack including:
1) It describes the hardware, software and networking requirements for the control and compute nodes when installing OpenStack.
2) It explains the different deployment options for OpenStack including all-in-one, multiple control and compute nodes, and different options for separating services.
3) It provides steps for installing OpenStack using Packstack, including generating SSH keys, editing the answer file and starting the deployment.
4) It gives an overview of the message broker services used by OpenStack and describes how to configure RabbitMQ or Qpid as the message broker.
Practical Container Security by Mrunal Patel and Thomas Cameron, Red HatDocker, Inc.
You can secure your containerized microservices without slowing down development. Through a combination of Linux kernel features and open source tools, you can isolate the host from the container and the containers from each other, as well as finding vulnerabilities and securing data. Two of Red Hat's Docker contributors will discuss the state of container security today, covering Linux namespaces, SElinux, cgroups, capabilities, scan, seccomp, and other tools you can use right now.
This document provides step-by-step instructions for creating a high availability SQL Server 2008 R2 cluster with two nodes using Microsoft Cluster Service on Windows Server 2008 R2. It discusses SQL clustering requirements, changes in Windows 2008/R2 related to clustering, and considerations for installing and configuring a two-node SQL cluster. The document also references additional technologies like Network Load Balancing that can provide further redundancy and scalability beyond normal clustering constraints.
Docker moves very fast, with an edge channel released every month and a stable release every 3 months. Patrick will talk about how Docker introduced Docker EE and a certification program for containers and plugins with Docker CE and EE 17.03 (from March), the announcements from DockerCon (April), and the many new features planned for Docker CE 17.05 in May.
This talk will be about what's new in Docker and what's next on the roadmap
1. TABLE OF CONTENTS
Definitions of different terms..................................................................................................... 2
Cluster ................................................................................................................................................................. 2
Cluster queue manager ..................................................................................................................................... 2
Cluster queue ..................................................................................................................................................... 3
Repository ......................................................................................................................................................... 3
Comparison with distributed queuing ........................................................................................................ 3
Setting up a new cluster ............................................................................................................. 5
Steps Summary................................................................................................................................................... 6
Detail of steps..................................................................................................................................................... 7
Decide on the organization of the cluster and its name............................................................................. 7
Determine which queue managers should hold full repositories .............................................................. 7
Alter the queue-manager definitions to add repository definitions.......................................................... 7
Define the CLUSRCVR channels .................................................................................................................... 8
Define the CLUSSDR channels....................................................................................................................... 9
Define the cluster queue INVENTQ .............................................................................................................. 9
Start the listener on both Queue Managers .............................................................................................. 10
Verify and test the cluster ........................................................................................................................... 10
Using the sample program:......................................................................................................................... 10
References ............................................................................................................................... 11
2. CREATING MQ CLUSTER
Microsoft Windows
Definitions of different terms
Prior to going into details of cluster making, we will discuss brief definitions of different terms
which need to be known and clarified before creating a cluster.
Cluster
A cluster is a network of queue managers that are logically associated in some way. The queue
managers in a cluster may be physically remote. For example, they might represent the
branches of an international chain store and be physically located in different countries. Each
cluster within an enterprise should have a unique name
Cluster queue manager
A cluster queue manager is a queue manager that is a member of a cluster. A queue manager
may be a member of more than one cluster. Each cluster queue manager must have a name
that is unique throughout all the clusters of which it is a member. A cluster queue manager can
host queues, which it advertises to the other queue managers in the cluster. A cluster queue
manager does not have to host or advertise any queues. It can just feed messages into the
cluster and receive only responses that are directed explicitly to it, and not to advertised
queues.
Page 2 of 11
3. CREATING MQ CLUSTER
Microsoft Windows
Cluster queue
A cluster queue is a queue that is hosted by a cluster queue manager and made available to
other queue managers in the cluster. The cluster queue manager makes a local queue
definition for the queue, specifying the name of the cluster where the queue is to be found.
This definition has the effect of showing the other queue managers in the cluster that the
queue is there. The other queue managers in the cluster can put messages to a cluster queue
without needing a corresponding remote-queue definition. A cluster queue can be advertised in
more than one cluster.
Repository
A repository is a collection of information about the queue managers that are members of a
cluster. This information includes queue manager names, their locations, their channels, which
queues they host, and so on. The information is stored in the form of messages on a queue
called SYSTEM.CLUSTER.REPOSITORY.QUEUE. (This queue is one of the default objects created
when you start a WebSphere MQ queue manager, except on WebSphere MQ for z/OS where it is
defined as part of queue manager customization.) Typically, two queue managers in a cluster
hold a full repository.
Comparison with distributed queuing
If you do not use clusters, your queue managers are independent and communicate using
distributed queuing. If one queue manager needs to send messages to another it must have
defined:
o A transmission queue
o A channel to the remote queue manager
Page 3 of 11
4. CREATING MQ CLUSTER
Microsoft Windows
If you group queue managers in a cluster, the queue managers can make the queues that they
host available to every other queue manager in the cluster. Any queue manager can send a
message to any other queue manager in the same cluster without explicit channel definitions,
remote-queue definitions, or transmission queues for each destination. Every queue manager in
a cluster has a single transmission queue from which it can transmit messages to any other
queue manager in the cluster. Each queue manager in a cluster needs to define only:
o One cluster-receiver channel on which to receive messages
o One cluster-sender channel with which it introduces itself and learns about the cluster
Page 4 of 11
5. CREATING MQ CLUSTER
Microsoft Windows
Setting up a new cluster
Suppose you are setting up a new WebSphere MQ network for a chain store. The store has two
branches, one in London and one in New York. The data and applications for each store are
hosted by systems running separate queue managers. The two queue managers are called
LONDON and NEWYORK. The inventory application runs on the system in New York, connected
to queue manager NEWYORK. The application is driven by the arrival of messages on the
INVENTQ queue, hosted by NEWYORK. The two queue managers, LONDON and NEWYORK, are
to be linked in a cluster called INVENTORY so that they can both put messages to the INVENTQ.
Examples shows what this cluster looks like.
Note: On WebSphere MQ for Windows you can use one of the wizards supplied with WebSphere
MQ Explorer to create a new cluster similar to the one created by this task.
Page 5 of 11
6. CREATING MQ CLUSTER
Microsoft Windows
Steps Summary
Following are the summary of the steps you have to follow to successfully create a cluster.
1. Decide on the organization of the cluster and its name
2. Determine which queue managers should hold full repositories
3. Alter the queue-manager definitions to add repository definitions
4. Define the CLUSRCVR channels
5. Define the CLUSSDR channels
6. Define the cluster queue INVENTQ
7. Starting listeners
8. Verify and test the cluster
Page 6 of 11
7. CREATING MQ CLUSTER
Microsoft Windows
Detail of steps
Decide on the organization of the cluster and its name
You have decided to link the two queue managers, LONDON and NEWYORK, into a cluster. A
cluster with only two queue managers offers only marginal benefit over a network that is to use
distributed queuing, but that is extendable. When you open new branches of your store, you
will be able to add the new queue managers to the cluster easily and without any disruption to
the existing network. Here, the cluster name we will use is INVENTORY.
Determine which queue managers should hold full repositories
In any cluster, you need to nominate at least one queue manager, or preferably two, to hold
full repositories. In this example there are only two queue managers, LONDON and NEWYORK,
both of which hold full repositories.
Alter the queue-manager definitions to add repository definitions
On each queue manager that is to hold a full repository, you need to alter the queue-manager
definition, using the ALTER QMGR command and specifying the REPOS attribute:
C:> runmqsc LONDON
ALTER QMGR REPOS(INVENTORY)
AMQ8005: Websphere MQ queue manager changed.
C:> runmqsc NEWYORK
ALTER QMGR REPOS(INVENTORY)
AMQ8005: Websphere MQ queue manager changed.
Queue managers LONDON and NEWYORK will be changed to a full repository.
Note: If you just runmqsc and enter the ALTER QMGR command, the default queue manager
will be changed.
Page 7 of 11
8. CREATING MQ CLUSTER
Microsoft Windows
Define the CLUSRCVR channels
On every queue manager in a cluster you need to define a cluster-receiver channel on which
the queue manager can receive messages.
This definition defines the queue manager’s connection name and the CLUSTER keyword shows
the queue manager’s availability to receive messages from other queue managers in the
cluster. The queue manager’s connection name is stored in the repositories, where other queue
managers can refer to it. Examples of the responses to the commands are shown below.
Setting up a cluster (Using transport protocol TCP/IP)
On the LONDON queue manager, define:
DEFINE CHANNEL(TO.LONDON) CHLTYPE(CLUSRCVR) TRPTYPE(TCP)
CONNAME(LONDON.CHSTORE.COM) CLUSTER(INVENTORY)
DESCR(’TCP Cluster-receiver channel for queue manager LONDON’)
In this example the channel name is TO.LONDON, and the connection name (CONNAME) is the
network address of the machine the queue manager resides on, which is
LONDON.CHSTORE.COM.
(The network address can be entered either as an alphanumeric DNS hostname, or as a dotted-
decimal IP address.)
Eg. CONNAME(10.1.234.112(1414))
Where 1414 is the port on which queue manager is listening.
Do not allow the CONNAME to specify a generic name.
On the NEWYORK queue manager, define:
DEFINE CHANNEL(TO.NEWYORK) CHLTYPE(CLUSRCVR) TRPTYPE(TCP)
CONNAME(NEWYORK.CHSTORE.COM) CLUSTER(INVENTORY)
DESCR(’TCP Cluster-receiver channel for queue manager NEWYORK’)
Page 8 of 11
9. CREATING MQ CLUSTER
Microsoft Windows
Define the CLUSSDR channels
On every queue manager in a cluster you need to define one cluster-sender channel on which
the queue manager can send messages to one of the full repository queue managers. In this
case there are only two queue managers, both of which hold full repositories. They must each
have a CLUSSDR definition that points to the CLUSRCVR channel defined at the other queue
manager.
Note that the channel names given on the CLUSSDR definitions must
match those on the corresponding CLUSRCVR definitions.
On the LONDON queue manager, define:
DEFINE CHANNEL(TO.NEWYORK) CHLTYPE(CLUSSDR) TRPTYPE(TCP)
CONNAME(NEWYORK.CHSTORE.COM) CLUSTER(INVENTORY)
DESCR(’TCP Cluster-sender channel from LONDON to repository at NEWYORK’)
On the NEWYORK queue manager, define:
DEFINE CHANNEL(TO.LONDON) CHLTYPE(CLUSSDR) TRPTYPE(TCP)
CONNAME(LONDON.CHSTORE.COM) CLUSTER(INVENTORY)
DESCR(’TCP Cluster-sender channel from NEWYORK to repository at LONDON’)
Once a queue manager has definitions for both a cluster-receiver channel and a cluster-sender
channel in the same cluster, the cluster-sender channel is started.
Define the cluster queue INVENTQ
Define the INVENTQ queue on the NEWYORK queue manager, specifying the CLUSTER keyword.
DEFINE QLOCAL(INVENTQ) CLUSTER(INVENTORY)
The CLUSTER keyword causes the queue to be advertised to the cluster. As soon as the queue is
defined it becomes available to the other queue managers in the cluster. They can send
messages to it without having to make a remote-queue definition for it.
Page 9 of 11
10. CREATING MQ CLUSTER
Microsoft Windows
Start the listener on both Queue Managers
Now that you have completed all the definitions, start a listener program on each queue
manager. The listener program listens for incoming network requests and starts the cluster-
receiver channel when it is needed.
The cluster set up by this task looks like this:
DEFINE QLOCAL(INVENTQ) CLUSTER(INVENTORY)
AMQ8006: Websphere MQ queue created.
Clearly, this is a very small cluster. However, it is useful as a proof of concept. The important
thing to understand about this cluster is the scope it offers for future enhancement.
Verify and test the cluster
Issue some DISPLAY commands to verify the cluster that you have set up. The responses you see
should be similar to those shown below.
From the NEWYORK queue manager, issue the command:
dis clusqmgr(*)
Now issue the corresponding DISPLAY CHANNEL STATUS command:
dis chstatus(*)
Because the INVENTQ queue has been advertised to the cluster, applications running on
NEWYORK and applications running on LONDON both can put messages to the INVENTQ queue.
They can receive responses to their messages by providing a reply-to queue and specifying its
name when they put messages.
Using the sample program:
Test your setup by sending some messages between the two queue managers, using amqsput. In
the following example LONDON puts a message to the INVENTQ at NEWYORK:
Page 10 of 11
11. CREATING MQ CLUSTER
Microsoft Windows
1. On LONDON issue the command:
amqsput INVENTQ LONDON
2. Type some messages
3. On NEW YORK issue the command:
amqsget INVENTQ NEWYORK
4. You should now see the messages you entered on LONDON
References
o IBM Document
Websphere MQ Queue Manager Clusters
SC34-6589-00
URL : http://www-01.ibm.com/support/docview.wss?uid=pub1sc34658900
Page 11 of 11