|  | 
 
  
    | RSS Feed - WebSphere MQ Support | RSS Feed - Message Broker Support |  
 
  
	|    |  |  
  
	| Java vs ESQL in WMB | « View previous topic :: View next topic » |  
  	| 
		
		
		  | Author | Message |  
		  | gajanan_matre | 
			  
				|  Posted: Wed May 08, 2013 1:56 am    Post subject: Java vs ESQL in WMB |   |  |  
		  | Newbie
 
 
 Joined: 08 May 2013Posts: 1
 
 
 | 
			  
				| Can someone tell me the tasks which are specific to java and which are to ESQL? |  |  
		  | Back to top |  |  
		  |  |  
		  | anurag.munjal | 
			  
				|  Posted: Wed May 08, 2013 2:00 am    Post subject: |   |  |  
		  |  Voyager
 
 
 Joined: 08 Apr 2012Posts: 97
 
 
 | 
			  
				| It clearly depends on the need of your message flow! ESQL can carry out most of the common stuff which you want to carry out using WMB.
  |  |  
		  | Back to top |  |  
		  |  |  
		  | lancelotlinc | 
			  
				|  Posted: Wed May 08, 2013 3:04 am    Post subject: |   |  |  
		  |  Jedi Knight
 
 
 Joined: 22 Mar 2010Posts: 4941
 Location: Bloomington, IL USA
 
 | 
			  
				| ESQL Compute node strong point is being able to walk the message tree more easily than a JCN. So if your logic needs to aggressively query, read and manipulate the logical message tree, a Compute node is a good choice. You can of course access Java from an ESQL Compute node also. 
 A JCN strong point is native access to the JRE and third-party jars without too much hubub.
 
 There are many other Compute nodes also: .Net, PHP, and XSL Transform to name the favorites.
 
 None of the message flow compute nodes are mutually exclusive. If your boss is asking you to choose one to use exclusively, tell him or her that he or she is un-knowledgable about the product.
 _________________
 http://leanpub.com/IIB_Tips_and_Tricks
 Save $20: Coupon Code: MQSERIES_READER
 |  |  
		  | Back to top |  |  
		  |  |  
		  | kimbert | 
			  
				|  Posted: Wed May 08, 2013 3:11 am    Post subject: |   |  |  
		  |  Jedi Council
 
 
 Joined: 29 Jul 2003Posts: 5543
 Location: Southampton
 
 | 
			  
				| Thanks lancelotinc : that's nicely put. 
 
  You forgot(?) to mention the Mapping node. It is often a very good choice, especially for users on v8 or later. 
	| Quote: |  
	| There are many other Compute nodes also: .Net, PHP, and XSL Transform to name the favorites |  |  |  
		  | Back to top |  |  
		  |  |  
		  | lancelotlinc | 
			  
				|  Posted: Wed May 08, 2013 3:19 am    Post subject: |   |  |  
		  |  Jedi Knight
 
 
 Joined: 22 Mar 2010Posts: 4941
 Location: Bloomington, IL USA
 
 | 
			  
				| 
   
	| kimbert wrote: |  
	| Thanks lancelotinc : that's nicely put. 
 
  You forgot(?) to mention the Mapping node. It is often a very good choice, especially for users on v8 or later. 
	| Quote: |  
	| There are many other Compute nodes also: .Net, PHP, and XSL Transform to name the favorites |  |  
 Your welcome kimbert. Thanks for the complement.
 
 While there have been some marvelous work done on the mapping node in V8, I'm still a little stand-offish regarding it. For XML-to-XML transformations, I find the mapping node to be awesome, especially if the format of the data fields can map directly into the target structure. For other more complex logic which I often deal with in the SOAP Web Service realm, calling multiple downstream providers, I find the ability to change the flow of logic more applicable to ESQL rather than mapping node. Complex logic is more convenient for me to implement in ESQL than mapping node (or mapping node calling an ESQL subroutine).
 _________________
 http://leanpub.com/IIB_Tips_and_Tricks
 Save $20: Coupon Code: MQSERIES_READER
 |  |  
		  | Back to top |  |  
		  |  |  
		  | Vitor | 
			  
				|  Posted: Wed May 08, 2013 5:15 am    Post subject: |   |  |  
		  |  Grand High Poobah
 
 
 Joined: 11 Nov 2005Posts: 26093
 Location: Texas, USA
 
 | 
			  
				| 
   
	| lancelotlinc wrote: |  
	| I find the ability to change the flow of logic more applicable to ESQL rather than mapping node. Complex logic is more convenient for me to implement in ESQL than mapping node (or mapping node calling an ESQL subroutine). |  
 This is another important point over and above the very well made points above, as the resource base of the site is a consideration. If you're a shop with deep Java skills, you may be more inclined to use a JCN where a Compute node is perhaps more technically matched.
 
 Or you may not. You might equally feel that the technical superiority of the Compute node for your requirements is sufficient to get ESQL training.
 _________________
 Honesty is the best policy.
 Insanity is the best defence.
 |  |  
		  | 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
 
 |  |  |  |