ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » IBM MQ Java / JMS » Design Issue.

Post new topic  Reply to topic
 Design Issue. « View previous topic :: View next topic » 
Author Message
viki
PostPosted: Thu Mar 02, 2006 5:17 am    Post subject: Design Issue. Reply with quote

Acolyte

Joined: 07 Feb 2006
Posts: 50

Hi,

I'm facing a design issue. Here is the scenario. See block diagram here.

There are multiple clients machines which will connect to the machine running MQ via WAN. Let's say:

-- clients machines are CM1, CM2....CMn.
-- machine running MQ is MQM (i.e. MQ Machine).

Client machine (CMn) sometimes have to put message on MQM and sometimes they have to get message residing on MQM. Same message cannot belonged to two or more clients at the same time.

There is also another machine (say it: AM) which connects to MQM and put message on MQM for a particular client. AM also get message from MQM which is actually put by CMn.

Question:
1) After recieving (GETing) message from MQM, how AM will identify that which CMn has PUT this message. In other words, how AM will differentiate b/w messages which it will GET from MQM?

2) Suppose there are 1000 clients, i.e. CM1, CM2,...CM1000. Now:
a) Should MQM has seprate queue to PUT/GET message? Then there will be 1000 queues on MQM, one for each client.
b) Should MQM has seprate qeueu for PUT and GET? Then there will be total two queues, one for PUT and one for GET.
c) Is there any recommended approach of creating queue based upon number of clients? Like for 1000 clients, one must create at least 10 queue on MQM. That is 100 clients per queue?

Please see the block diagram for the above scenario here.

Any help in this regard would be highly appreciated!

Bye,
Viki.
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Thu Mar 02, 2006 6:52 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

What is the nature of the communication between the clients and the AM?

What is the nature of the communication between each client?

Is the client making a request of the AM and receiving a reply?

If so, this is a standard design pattern, and documented in the Application Programming Guide.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
viki
PostPosted: Fri Mar 03, 2006 11:29 am    Post subject: Reply with quote

Acolyte

Joined: 07 Feb 2006
Posts: 50

Quote:
What is the nature of the communication between the clients and the AM?

What is meant by nature of the communication . If it is LAN, WAN then:

Clients will put/get the message in MQM via WAN; And AM will put/get those messages from MQM via WAN.

Bottom line is that: there are some messages which have to be sent from AM to the Clients and vice versa. Remember, Each message will belonged to the specific client and not to two or more clients. Here, MQM will be used as a bridge b/w Client and AM.

Quote:
What is the nature of the communication between each client?

Client will not communicate with each other.
Quote:

Is the client making a request of the AM and receiving a reply?

Yes, communucation between client and AM will be bi-directional.
Quote:

If so, this is a standard design pattern, and documented in the Application Programming Guide.

Which design pattern is this? What is the name? It'll be great if you could provide the link.

Looking forward to you.

Bye,
Viki.
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Fri Mar 03, 2006 11:37 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

So the clients are not talking to each other. Each client is instead sending messages to the AM server and receiving messages from the AM server.

I mean "nature of communications" at an abstract level. What type of message is the client sending? Is the client asking a question? Or is it just sending data? Likewise, is the AM server returning an answer to a question, or merely sending different and unrelated data.

The design pattern I meant was "request/reply", and as I said, it's in the Application Programming Guide for WebSphere MQ.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
viki
PostPosted: Fri Mar 03, 2006 12:39 pm    Post subject: Reply with quote

Acolyte

Joined: 07 Feb 2006
Posts: 50

Quote:
So the clients are not talking to each other. Each client is instead sending messages to the AM server and receiving messages from the AM server.

Let me add more: So the clients are not talking to each other. Each client is instead sending messages to the AM server and receiving messages from the AM server. Where MQM will play the role of bridge b/w client and AM.

Quote:
I mean "nature of communications" at an abstract level. What type of message is the client sending? Is the client asking a question? Or is it just sending data? Likewise, is the AM server returning an answer to a question, or merely sending different and unrelated data.

Does it really effects the design pattern to be chosen? I mean, will design pattern which I am about to adopt will depend upon the nature of communication? Client and AM will be actually sending file (in fact file contents) to each other. At this stage, I'm not sure whether AM will reply an answer to the clients or not.

I've not seen request/reply yet. Is it, it's original name? Coz. in software engineering we have specific names of design patterns. Like Singleton, Facade etc.

Bye,
Viki.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Fri Mar 03, 2006 12:50 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

Viki you need to look under JMS patterns and you should find them there...

Enjoy
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
viki
PostPosted: Sat Mar 04, 2006 1:19 am    Post subject: Reply with quote

Acolyte

Joined: 07 Feb 2006
Posts: 50

Hi,
There is a chapter in WebSphere MQ Information Center i.e. "Part 1: Designing Applications that use WebSphere MQ". I have skimmed via it and found some useful info.

Quote:
Viki you need to look under JMS patterns and you should find them there...

JMS Patterns are in same chapter?

Also, being a J2EE/JMS guy, is it my job to look on MQ design issues? I mean, if there is a MQ Administrator available, then isn't it his job? Albiet, I love to get into desing issues and over all architecture, but still just want to categorize this task.

Bye,
Viki.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Sat Mar 04, 2006 4:50 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

Did you even google for JMS Patterns??
A wealth of information to be found there.

Enjoy
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » IBM MQ Java / JMS » Design Issue.
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.