|  | 
 
  
    | RSS Feed - WebSphere MQ Support | RSS Feed - Message Broker Support |  
 
  
	|    |  |  
  
	| what is the best design practice | « View previous topic :: View next topic » |  
  	| 
		
		
		  | Author | Message |  
		  | Ajju. | 
			  
				|  Posted: Tue Oct 29, 2002 2:35 pm    Post subject: what is the best design practice |   |  |  
		  |  Voyager
 
 
 Joined: 26 Jul 2002Posts: 77
 
 
 | 
			  
				| Well folks i have one web application talking to multiple legacy db's. 
 that is my web appication can put 5 different types (Types means different data content in XML format) of messages in a queue.
 
 so what is the best practice in industry for this type of appication :
 
 i.e, shud i create 5 different queues for each message or shud i create just one queue for all message... keping in mind that all the queues are connected to only one QM from where the message is then processed according to data in it.
 
 
 pl. advice,
 Ajit
 |  |  
		  | Back to top |  |  
		  |  |  
		  | kirani | 
			  
				|  Posted: Tue Oct 29, 2002 10:12 pm    Post subject: |   |  |  
		  | Jedi Knight
 
 
 Joined: 05 Sep 2001Posts: 3779
 Location: Torrance, CA, USA
 
 | 
			  
				| I would use only one queue for all these message types. I would use some field in MQMD header, like MsgType or ApplIdentityData to indicate what is the format of the XML message. _________________
 Kiran
 
 
 IBM Cert. Solution Designer & System Administrator - WBIMB V5
 IBM Cert. Solutions Expert - WMQI
 IBM Cert. Specialist - WMQI, MQSeries
 IBM Cert. Developer - MQSeries
 
 
 |  |  
		  | Back to top |  |  
		  |  |  
		  | Ajju. | 
			  
				|  Posted: Wed Oct 30, 2002 6:00 am    Post subject: |   |  |  
		  |  Voyager
 
 
 Joined: 26 Jul 2002Posts: 77
 
 
 | 
			  
				| thanks kiran, Even i am in favour of using only one queue, but let me put my question in this way.
 
 I have one web application talking to multiple legacy db's(to be specific 5 db's).
 
 that is my web appication can put 5 different types XML message (Types means different data XML format) in a queue.
 
 and the remote QM has 5 different applications which picks up the message using triggering functionality and CICS transactions.
 
 so what is the best practice in industry for this type of appication :
 
 i.e, shud i create 5 different queues for each message for 5 different applications
 
 what if the remote queue becomes full because the destination queue specific application which picks of the message does not work or is down for maintanance. so what i want is the remaining  4 applications shud work independent of each other.
 
 
 thanks,
 Ajit
 |  |  
		  | Back to top |  |  
		  |  |  
		  | RogerLacroix | 
			  
				|  Posted: Wed Oct 30, 2002 8:42 pm    Post subject: |   |  |  
		  |  Jedi Knight
 
 
 Joined: 15 May 2001Posts: 3265
 Location: London, ON  Canada
 
 | 
			  
				| Hi, 
 If each message type invokes a different "business function or business process" then I strongly suggest that you use separate queues.
 
 This allows for a simple design (plus scalable) and the receiving application does not have to search the queue for its message type (because with separate queues you know that only a specific message type will be in a given queue).
 
 later
 Roger...
 _________________
 Capitalware: Transforming tomorrow into today.
 Connected to MQ!
 Twitter
 |  |  
		  | Back to top |  |  
		  |  |  
		  | Ajju. | 
			  
				|  Posted: Thu Oct 31, 2002 5:34 am    Post subject: |   |  |  
		  |  Voyager
 
 
 Joined: 26 Jul 2002Posts: 77
 
 
 |  |  
		  | Back to top |  |  
		  |  |  
		  |  |  |  
  
	|    |  | Page 1 of 1 |  
 
 
  
  	| 
		
		  | 
 
 | 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
 
 |  |  |  |