Author |
Message
|
zpat |
Posted: Tue May 14, 2002 11:27 pm Post subject: |
|
|
 Jedi Council
Joined: 19 May 2001 Posts: 5866 Location: UK
|
What I would like is for IBM to stop removing the support pacs for MQSI 2.0.1 or MQSI 2.0.2 just because the function is provided in WMQI 2.1 or can be done better in Java.
Most sites are NOT in production with WMQI 2.1 - IBM needs to remember that the real world does not install new releases into critical production servers for up to a year after GA. |
|
Back to top |
|
 |
CodeCraft |
Posted: Fri May 17, 2002 4:41 am Post subject: Re: a Trash node. |
|
|
Disciple
Joined: 05 Sep 2001 Posts: 195
|
ernest-ter.kuile wrote: |
I know there are ways to have a message disappear, however I would like an explicit way to trash a message, have a node like a terminal MQOutput which send all messages to the Great MQ Queue in the sky, or makes a brave attempt to fill up /dev/null
If only to clarify a message flow.
|
To explicitly trash a message, route it to a compute node named EXPLICIT.TRASH which does nothing with the message! |
|
Back to top |
|
 |
artist |
Posted: Mon May 19, 2003 4:32 am Post subject: |
|
|
Newbie
Joined: 06 Aug 2001 Posts: 5
|
An http/https Input/output nodes. |
|
Back to top |
|
 |
CodeCraft |
Posted: Mon May 19, 2003 6:57 am Post subject: HTTP/HTTPS nodes |
|
|
Disciple
Joined: 05 Sep 2001 Posts: 195
|
I suspect this is already available. Check out the IBM WMQI Support Packs Web Page. |
|
Back to top |
|
 |
drajib |
Posted: Fri May 23, 2003 4:37 am Post subject: |
|
|
 Apprentice
Joined: 25 Mar 2003 Posts: 42 Location: India
|
A global place to write User Defined Functions from where all compute nodes even belonging to different flows could access them
Externalizing DB access specifiers so that they do not have to be hard coded seperately for each select/insert/update/delete handler node within a flow |
|
Back to top |
|
 |
zpat |
Posted: Fri May 23, 2003 5:25 am Post subject: |
|
|
 Jedi Council
Joined: 19 May 2001 Posts: 5866 Location: UK
|
Central storage of ESQL source is available in WMQI v5. |
|
Back to top |
|
 |
ernest-ter.kuile |
Posted: Fri May 23, 2003 6:15 am Post subject: |
|
|
 Apprentice
Joined: 13 May 2002 Posts: 49 Location: KLM Holland
|
zpat wrote: |
Central storage of ESQL source is available in WMQI v5. |
'is available' ?!?! when did version 5 comme out ?
And what happend to v3 and v4 ? |
|
Back to top |
|
 |
zpat |
Posted: Fri May 23, 2003 6:52 am Post subject: |
|
|
 Jedi Council
Joined: 19 May 2001 Posts: 5866 Location: UK
|
GA date is June 27, so I suppose "will be available" is more accurate. |
|
Back to top |
|
 |
jefflowrey |
Posted: Fri May 23, 2003 9:01 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
Quote: |
And what happend to v3 and v4 ? |
Marketing. |
|
Back to top |
|
 |
wmqiguy |
Posted: Fri May 23, 2003 11:55 am Post subject: |
|
|
 Centurion
Joined: 09 Oct 2002 Posts: 145 Location: Florida
|
Marketing is right, but at least it is consistent. MQSeries also made a jump from V2 to V5, so at least the related products like MQSI/WMQI are making the same jump. Also, Websphere App Server is at V5, so it will help to keep all the Websphere products at the same level. Much easier for manager types to understand.
Regards,
Todd |
|
Back to top |
|
 |
plewton |
Posted: Tue May 27, 2003 9:27 am Post subject: |
|
|
Novice
Joined: 20 May 2003 Posts: 14
|
As with almost everyone else, HTTP Post/Get and Socket Nodes would make my life a lot easier on the Java programming front.
These would also be extremely useful if they supported HTTPS through the Java Secure Sockets Extension.
Also Flat File adapter nodes would be great, with the capability say to generate a new message for each delimited/fixed length record in a file, and in reverse the capability to generate a new date/time stamped flat file for each record in a message. |
|
Back to top |
|
 |
jsware |
Posted: Tue May 27, 2003 10:13 am Post subject: |
|
|
 Chevalier
Joined: 17 May 2001 Posts: 455
|
An update to the MQGet plugin that allows browsing of messages on a queue to occur. We could then store flow configuration information in a queue and read it to determine what needs to happen. This allows us to configure a flow's processing dynamically.
Don't want to store this in a database for a number of reasons... |
|
Back to top |
|
 |
jefflowrey |
Posted: Tue May 27, 2003 1:17 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
Quote: |
Also Flat File adapter nodes would be great, with the capability say to generate a new message for each delimited/fixed length record in a file, and in reverse the capability to generate a new date/time stamped flat file for each record in a message. |
It's really straight forward to write a Java plugin to save pieces of a message to a flat file. At least, if you know Java and know how to write Java plug-ins, it's really straight forward.
You could possibly adapt/extend the 'Q' utility (MA01) to put files into queues - it already puts each record (up to a specific buffer length) into an individual message .
It's also really straight foward to write any sort of message->file and file->message adapter as a standalone MQSeries application. And there may possibly be real Adapters that do this. |
|
Back to top |
|
 |
zpat |
Posted: Wed May 28, 2003 12:30 am Post subject: |
|
|
 Jedi Council
Joined: 19 May 2001 Posts: 5866 Location: UK
|
The Redbook "WMQI 2.1 migration", contains a sample Java plugin INPUT NODE which monitors for files arriving in a directory and passes the data into a flow (which can obviously generate a message). |
|
Back to top |
|
 |
GYR |
Posted: Wed May 28, 2003 3:33 am Post subject: |
|
|
Acolyte
Joined: 23 Jan 2002 Posts: 72
|
The ability to use jdbc from witihin the java node allowing the use of connection to other platforms like AS400. Anybody got extreme experience in writing nodes would not mind a mind dump email address with profile....appreciated. |
|
Back to top |
|
 |
|