Professional Documents
Culture Documents
A cluster is a group of queue managers set up in such a way that the queue managers can communicate directly with one another over a single network, without the need for transmission queue, channel, and remote queue definitions. Advantages of Clustering: Reduced system administration Increased high availability Improved resource utilization Workload sharing
Components of a cluster
Cluster :- Network Of Queue Managers. Cluster Queue Manager:- Queue Manager which is Member of a Cluster. Cluster Queue:- Queue Part of Cluster Queue Manager & defined as Cluster queue Repository:- Holds Cluster Information Repository Queue Manager:- Queue Manager which holds the repository Full Repository:- Queue Manager which holds complete set of information Partial Repository:- Queue Manager which holds partial information. Cluster Receiver Channel:- Receiver channel used in Cluster Cluster Sender Channel:- Sender Channel used in Cluster Cluster Transmission Queue:- Transmission Queue Used in Cluster Binding:- Method to use single queue for all message in cluster environment
A queue manager that hosts a complete set of information about every queue manager in the cluster is referred to as having a full repository for the cluster. The other queue managers in the cluster inquire about the information in the full repositories and build up their own subsets of this information in partial repositories.
A partial repository contains information about only those queue managers with which the queue manager needs to exchange messages. The queue managers request updates to the information they need, so that if it changes, the full repository queue manager will send them the new information
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
Setting up cluster
Step-1 Determine which queue manager should hold full repositories A full repository contains a complete set of information about every queue manager and object in the cluster You will need at least one, preferably two Step-2 Alter the queue manager definitions to add repository definitions ALTER QMGR REPOS(cluster_name) Step-3 Define the CLUSRCVR channels Every queue manager in the cluster needs a CLUSRCVR with a conname pointing to itself. DEFINE CHANNEL(channel_name) CHLTYPE(CLUSRCVR) TRTYPE(TCP) CONNAME(my_ip_name_or_address(port)) CLUSTER(cluster_name) Step-4 Define the CLUSSDR channels Define one CLUSSDR to a full repository queue manager. The channel name must match that of the CLUSRCVR on the full repository DO NOT define a CLUSSDR to point to a partial repository. DEFINE CHANNEL(channel_name) CHLTYPE(CLUSSDR) TRPTYP(TCP) CONNAME(remote_ip_name_or_address(port)) CLUSTER(cluster_name) Step-5 Define a cluster queue DEFINE QLOCAL(qname) CLUSTER(cluster_name) Other queue managers in the cluster can send message to it without making remote-queue definitions for it. Only the local queue manager can read messages from an instance of the cluster queue You can use a sample program to test putting messages to clustered queues
Updates Subscribe to the blog for updates through email Also you can keep in touch using these social media Website: http://websphere.gizapge.com Facebook: http://facebook.com/MiddlewareLibrary Twitter: http://twitter.com/NodeAgent Youtube: http://youtube.com/NodeAgent Friendfeed: http://friendfeed.com/NodeAgent Delicious: http://delicious.com/NodeAgent
Thank You
http://websphere.gizapage.com