| Author |
Message
|
| jeevan |
 Posted: Wed Oct 25, 2006 6:11 am Post subject: Is ESQL redundant in Websphere Message Broker v6.0? |
 |
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
I am new to MB application development. I am planning to learn it now. My understanding is that until WBIMB v5.0 ESLQ was programming language although java could be used. But in new version, a new node ->java node has been introduced, which replaces the use of ESLQ. Still we can program in ESQL, but it is not necessary. Am I correct? Can one avoid ESQL totally while developing message broker application in MB v6.0?
At the same time, who else uses ESQL besides MQSI/WBIMB? It is good idea to avoid ESQL or useful to learn it?
Sharing your ideas /opinion would be appreciated, |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Wed Oct 25, 2006 6:19 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Yes, one can totally avoid ESQL in version 6 of Broker.
Java, however, in no way replaces ESQL.
Neither does the Mapping node replace ESQL.
There are three ways to code transformations in Broker (well, four if you count C plugin nodes) - Java, ESQL, and Mapping.
In all three cases, you still have to know how to develop message broker transformations - and ESQL can be simpler to learn that with than Java.
And in all cases, MB is a complicated product, and you should get training.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Oct 25, 2006 6:32 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
My lack of Java may be producing a biased view here, but I still prefer to use ESQL rather than Java.
Also from a training standpoint, there is a significant chance that you will be called upon to amend or maintain a V6 broker (possibly one of mine!) where ESQL has been used extensively, or where the broker is an upgrade & the flows have been imported in ESQL from an earlier version. In both of these cases your effectiveness will be greatly reduced without a proper knowledge of ESQL.
My 2 cents. Differing opinions welcomed.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| jeevan |
| Posted: Wed Oct 25, 2006 7:17 am Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
Thank you both Vitor and Jeff for your opinion. Sorry for that but I have touched two points. ESQL and MB 6. In this case, I agree with you that one has to have ESLQ as Vitor said. One can only use java, but if he has to work with previously developed messaing application which uses a lot fo ESLQ, no choice.
But the other point I am trying ot bring here is about ESLQ technology itself. I think ( i am not APP guru though) Java will remain in scene at least another 6-7 years and is heavily used in app dev and EAI. How about ESQL? It is used in any other hardware plftform or software ?
Thanks |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Oct 25, 2006 7:24 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
ESQL has never been used anywhere other than in MQSI/WMQI/WBIMB/WMB.
But then again, VisualBasic has never been used anywhere other than on Microsoft machines.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Oct 25, 2006 7:27 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
AFAIK ESQL is only used on the message broker platform, but as the name suggests it's a superset of the ANSI SQL standard. So it's not wasted time learning it.
Touching on your other point, Java is likely to be around much longer than 6-7 years. As you say it's heavily used in app development so the developed code base will keep it in use for a while to come.
I remember once being told by a bright young thing that C & COBOL would disappear from the computing scene within 5 years, drowned in a wave of development in this new "Java" language. All the legacy apps would be rewritten, mainframes would be replaced by mid-range Unix and a golden age of web-based applications would begin.
That was a lot more than 5 years ago & he wasn't wrong about the web-based apps, but there's still a lot of C & COBOL sloshing round. I expect the same will be true for Java when the Next Big Thing is developed. It's won't be taken up simultaniously by every code shop, the tried and trusted Java (!) will be left running.
That's probably 4 cents now, but differing opinions still welcomed.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Oct 25, 2006 7:31 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
ESQL is not really a superset or a subset of the ANSI SQL Standard.
ESQL Select supports only a subset of the features of ANSI SQL Select. And I'd be surprised if ANSI SQL Select had MOVE.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| mqmatt |
| Posted: Wed Nov 01, 2006 6:49 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
| jefflowrey wrote: |
| There are three ways to code transformations in Broker (well, four if you count C plugin nodes) - Java, ESQL, and Mapping. |
Five if you count XSLT  |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Nov 01, 2006 6:51 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I consider XSLT to be mostly "outside" broker... 
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
