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 » WebSphere Message Broker (ACE) Support » Java Compute node vs calling Java module in ESQL code

Post new topic  Reply to topic
 Java Compute node vs calling Java module in ESQL code « View previous topic :: View next topic » 
Author Message
geethgubi
PostPosted: Tue Feb 09, 2010 6:52 am    Post subject: Java Compute node vs calling Java module in ESQL code Reply with quote

Apprentice

Joined: 18 Dec 2008
Posts: 44

We are rewriting an application for performance improvements. For some of the reasons we need to write the code in java. I recommended calling the java module (only for the part which has to be in java (JDBC calls)) from the esql code. But I read in one of the google article that instead of calling the java module from the esql, we can go ahead and use java compute node. I am confused on what are the pros and cons that both of these are going to bring in. Can someone help me by listing out or directing me to some article which explains these?
Back to top
View user's profile Send private message
zpat
PostPosted: Tue Feb 09, 2010 7:14 am    Post subject: Reply with quote

Jedi Council

Joined: 19 May 2001
Posts: 5866
Location: UK

Don't use native Java in WMB, use only the Java compute nodes.

WMB has all the database access capability you need builtin.

Too many developers are seeing the word "Java" and assuming they have to code their own logic. WMB is not WAS.

The entire point of WMB is NOT to do that sort of coding. Use the greater productivity and reliability of using the WMB builtin features.

Using Java trained developers to work with WMB (presumably without being trained on WMB) is likely to lead to the wrong use of WMB.

The choice of ESQL or Java won't lead to performance improvements, the correct use of WMB features and general design principles matter, not the compute node language.
Back to top
View user's profile Send private message
ovasquez
PostPosted: Thu Feb 11, 2010 4:11 pm    Post subject: Reply with quote

Centurion

Joined: 09 Dec 2005
Posts: 141
Location: Lima, Peru

zpat wrote:
Don't use native Java in WMB, use only the Java compute nodes.
WMB has all the database access capability you need builtin.
.

WMB for z/OS, only access DB2 for z/OS..from ESQL...
For other database is necesary use JavaCompute node...
_________________
Oscar Vásquez Flores
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 » WebSphere Message Broker (ACE) Support » Java Compute node vs calling Java module in ESQL code
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.