| Author |
Message
|
| mgk |
 Posted: Tue Sep 06, 2005 7:57 am Post subject: ESQL Enhancements in WebSphere Message Broker V6 |
 |
|
Padawan
Joined: 31 Jul 2003
Posts: 1642
|
As Ian mentioned here:
http://www.mqseries.net/phpBB2/viewtopic.php?t=24163
WebSphere Message Broker v6 was announced today. There are lots of enhancements in Message Broker v6, but I thought that readers of this forum may be interested in some of the key enhancements to ESQL as these seem to address quite a few of the questions raised recently. From the release announcement these are:
* In-memory cache to avoid access to databases for read only routing or validation data
* Improved support for creating DATETIME variables
* Access to multiple databases from the same compute node
* Dynamic database schemas
* New user-defined properties that can pass parameters to ESQL to modify standard behavior
* Access to environment information such as flow name and broker name, and so forth
* Improved support for result sets returned by database stored procedures
* Improved error recovery by the use of SQL handlers
* Multiple out terminals to combine the function of compute and filter nodes
Regards,
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue Sep 06, 2005 8:12 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
There's a lot of really nice stuff in this new release. The ability to deploy jar files through the standard broker deployment facilities, for instance.
But this is a little disheartening
| Quote: |
| Migration considerations: Tools and utilities will be available to assist migration from the previous release. |
So it sounds like migration will be a little more complicated than exporting projects from v5 and importing into v6...
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| JLRowe |
| Posted: Tue Sep 06, 2005 8:13 am Post subject: |
|
|
Yatiri
Joined: 25 May 2002
Posts: 664
Location: South East London
|
Excellent stuff, a nice feature set.
Can you get/set the namespace of an MbElement in the java API yet?
This has caused me great problems in the past. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Sep 06, 2005 8:15 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I'd think you would set the namespace by setting the name of the MBElement to include the namespace qualifier...
But I've not tried, and the announcement doesn't mention.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| mqmatt |
| Posted: Tue Sep 06, 2005 8:23 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
| jefflowrey wrote: |
There's a lot of really nice stuff in this new release. The ability to deploy jar files through the standard broker deployment facilities, for instance.
But this is a little disheartening
| Quote: |
| Migration considerations: Tools and utilities will be available to assist migration from the previous release. |
So it sounds like migration will be a little more complicated than exporting projects from v5 and importing into v6... |
I certainly hope not 
This refers (in the most part) to migration of the runtime components. Migrating a ConfigMgr/broker is now a case of issuing "mqsimigratecomponents <componentname(s)>" and the command does the migration for you. This works because different versions of the product can now coexist.
For the v5 -> v6 toolkit, you simply connect to your v5 workspace from the v6 toolkit and rebuild. The only file format that will require explicit migration are message maps.
-Matt |
|
| Back to top |
|
|
| mgk |
| Posted: Tue Sep 06, 2005 8:41 am Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1642
|
JLRowe wrote:
| Quote: |
| Can you get/set the namespace of an MbElement in the java API yet? |
Yes you can do both of these.
Regards,
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Sep 06, 2005 8:55 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| mqmatt wrote: |
I certainly hope not
This refers (in the most part) to migration of the runtime components. Migrating a ConfigMgr/broker is now a case of issuing "mqsimigratecomponents <componentname(s)>" and the command does the migration for you. This works because different versions of the product can now coexist.
For the v5 -> v6 toolkit, you simply connect to your v5 workspace from the v6 toolkit and rebuild. The only file format that will require explicit migration are message maps. |
Applause, Applause!
That's what I was hoping for.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Tue Sep 06, 2005 11:08 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
Is it just me or did the BI part drop out of the name with V6?
The announcement consistently mentions:
WebSphere Message Broker V6.0 and
WebSphere Event Broker V6.0
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| markt |
| Posted: Tue Sep 06, 2005 11:09 am Post subject: |
|
|
Knight
Joined: 14 May 2002
Posts: 508
|
Not just you.
You don't think a new release of the broker could be made without changing the name do you? |
|
| Back to top |
|
|
|
|
