Browse Prior Art Database

Method and System for Grouping Messages in a Clustered Environment

IP.com Disclosure Number: IPCOM000202364D
Publication Date: 2010-Dec-14
Document File: 3 page(s) / 74K

Publishing Venue

The IP.com Prior Art Database

Abstract

A method and system for grouping messages in a clustered environment is disclosed.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 01 of 3

Method and System for Grouping Messages in a Clustered Environment

Disclosed is a method and system for grouping messages in a clustered environment.

Generally, there are four entities involved in transmission of messages in a clustered environment. These include producers, cluster managers, individual queue managers and consumers, When a producer sends multiple messages in the clustered environment, the messages are distributed across multiple destinations. In some instances, a producer may be required to send multiple messages which are to be received by a single consumer.

Accordingly, the method and system disclosed herein enables a producer to provide an indication to the cluster managers to facilitate consumption of multiple messages belonging to a group by a single consumer. The producer may provide the following attribute on each message of the multiple messages to provide the indication to the cluster manager.

MQPMO

_GROUP

                          . Each of the cluster managers has a dedicated Cluster Message Group Process (CMGP) that is responsible for maintaining the link. The link is maintained to ensure that the grouping of multiple messages from the producer is enforced. As each message belonging to the group is received by a corresponding cluster manager, the corresponding CMGP stores one or more attributes of the message. In an instance, a CMGP may store the attributes of a message as,

class{

String clusterQmgrName;

String clusterQName;

String groupName;

int messageSequenceNumber;

String messageID;

Object ConsumerReference;

_ENFORCE

The one or more attributes stored by the CMGPs are provided by the cluster managers. Further, the one or more attributes provide details regarding physical addresses of the destinations where the multiple messages have been delivered to. For example, if ten

1

ENFORCE = true

The cluster managers maintain a link for all the messages with the attribute MQPMO

_

_STRICT

_GROUP

_STRICT

}

.


Page 02 of 3

messages belonging to a group are received from a producer, the attributes corresponding to the ten messages is as follows:

ClstrQmgrName

ClstrQName

GroupName

MsgSeqNo

MsgID

ConsumerR eference

QM1

Q1

MY

_GROUP

1

11111

Null

QM1

Q1

MY

_GROUP

2

22222

Null

QM1

Q1

MY

_GROUP

3

33333

Null

QM2

Q1

MY

_GROUP

4

44444

Null

QM2

Q1

MY

_GROUP

5

55555

Null

QM2

Q1

MY

_GROUP

6

66666

Null

QM3

Q1

MY

_GROUP

7

77777

Null

QM3

Q1

MY

_GROUP

8

88888

Null

QM3

Q1

MY

_GROUP

9

99999

Null

QM3

Q1

MY

_GROUP

10

12345

Null

Accordingly, the CMGP tracks the number of messages belonging to a group and the physical addresses of the locations where the messages have been delivered to. This information is provided to one or more queue managers in the cluster environment. In the example illustrated earlier, the queue managers in the cluster environment are QM1, QM2, and QM3. Consumer references for each of the messages are retained as null and are updated when a consumer connects with the corresponding queue manager for receiving a message. The queue managers...