| Author | 
		  Message
		 | 
		
		  | chittari | 
		  
		    
			  
				 Posted: Thu May 09, 2002 1:24 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Newbie
 
 Joined: 22 Apr 2002 Posts: 9 Location: India/Bangalore 
  | 
		  
		    
			  
				Can some body suggest me some documentation(/Expalin me) which will expalin me the comparision of socket programming with MQSeries.
 
Thanx in Advance .. Giri | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | mrlinux | 
		  
		    
			  
				 Posted: Thu May 09, 2002 3:31 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Grand Master
 
 Joined: 14 Feb 2002 Posts: 1261 Location: Detroit,MI USA 
  | 
		  
		    
			  
				There is no socket programming with MQSeries 
 
 _________________ Jeff 
 
 
IBM Certified Developer MQSeries
 
IBM Certified Specialist MQSeries
 
IBM Certified Solutions Expert MQSeries | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | chittari | 
		  
		    
			  
				 Posted: Thu May 09, 2002 3:46 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Newbie
 
 Joined: 22 Apr 2002 Posts: 9 Location: India/Bangalore 
  | 
		  
		    
			  
				No, I will put my questino again !!!
 
You can send msgs across systems by Socket programming also..so, what are advantages of using MQSeries for this purpose..
 
 
Hope it is clear !!!
 
Thanx in advance .. Giri | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | mrlinux | 
		  
		    
			  
				 Posted: Thu May 09, 2002 4:09 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Grand Master
 
 Joined: 14 Feb 2002 Posts: 1261 Location: Detroit,MI USA 
  | 
		  
		    
			  
				Well there are several.
 
  1) The Destination Application doesnt have to running in order for the source 
 
     application to send data.
 
  2) Less burden on application developers to adding code for retries,timeouts 
 
     and other network type issues
 
  3) By using qmgr-qmgr communicatons it allows you to have a loosely coupled 
 
     applications, IE the src/Dest applications are not coded to know where the 
 
     other one is, this would allow you to move one app to a bigger box without 
 
     changing the applications 
 
 _________________ Jeff 
 
 
IBM Certified Developer MQSeries
 
IBM Certified Specialist MQSeries
 
IBM Certified Solutions Expert MQSeries | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | chittari | 
		  
		    
			  
				 Posted: Thu May 09, 2002 4:24 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Newbie
 
 Joined: 22 Apr 2002 Posts: 9 Location: India/Bangalore 
  | 
		  
		    
			  
				Thanx for the answer. 
 
Actually some guy asked me about this comparion & I will tell him to refer this discussion.
 
Thanx... Giri | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | zpat | 
		  
		    
			  
				 Posted: Thu May 09, 2002 11:22 pm    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Jedi Council
 
 Joined: 19 May 2001 Posts: 5867 Location: UK 
  | 
		  
		    
			  
				Persistency, messages are logged (if required) and assured one-time delivery.
 
 
Automatic conversion of code pages at the local system if required.
 
 
Triggering of applications possible on message arrival.
 
 
General flexibility - with lots of options available when needed.
 
 
Interplatform connectivity, including to SNA based mainframes.
 
 
Ability to route via a message broker, or use pub/sub design.
 
 
Ability to manage the message infrastructure with system management tools
 
 
facilities for transactionality - this is very important to be able to commit/backout messages as part of a unit of work, and coordinate with DB updates as well.
 
 
Etc etc.
 
 
 
 
 
 | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | 
		    
		   |