Author |
Message
|
broker_new |
Posted: Sun Mar 07, 2010 10:47 am Post subject: WMBv7.0->FileBrowse node |
|
|
 Yatiri
Joined: 30 Nov 2006 Posts: 614 Location: Washington DC
|
Hi Guys,
We have MQInput, MQGet nodes which can browse for the messages in queue. Why not a file browse node in WMBv7 future releases? _________________ IBM ->Let's build a smarter planet |
|
Back to top |
|
 |
smdavies99 |
Posted: Sun Mar 07, 2010 11:01 am Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
Have you submitted an enhancement Request? _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
Back to top |
|
 |
broker_new |
Posted: Tue Mar 09, 2010 8:01 am Post subject: |
|
|
 Yatiri
Joined: 30 Nov 2006 Posts: 614 Location: Washington DC
|
Any information or link for the enhancement request? _________________ IBM ->Let's build a smarter planet |
|
Back to top |
|
 |
fjb_saper |
Posted: Tue Mar 09, 2010 1:48 pm Post subject: Re: WMBv7.0->FileBrowse node |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
broker_new wrote: |
Hi Guys,
We have MQInput, MQGet nodes which can browse for the messages in queue. Why not a file browse node in WMBv7 future releases? |
Is this a hidden way of loading a property file?
Could you please state your case for a file browse node:
a) Why do you need to browse a file in your flow?
b) Why is a DB not suitable
Thanks  _________________ MQ & Broker admin |
|
Back to top |
|
 |
smdavies99 |
Posted: Tue Mar 09, 2010 11:58 pm Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
My guess is for that old favourite,
Reading a properties file as if Broker was a Java app server. _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
Back to top |
|
 |
broker_new |
Posted: Wed Mar 10, 2010 12:22 am Post subject: |
|
|
 Yatiri
Joined: 30 Nov 2006 Posts: 614 Location: Washington DC
|
It is definitely for reading a properties file.
Do you really think reading a file proves that the product is as if an app server, in that case Broker is definitely another application server. _________________ IBM ->Let's build a smarter planet |
|
Back to top |
|
 |
smdavies99 |
Posted: Wed Mar 10, 2010 3:00 am Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
Broker probably is an 'appserver' in a (IMHO) loose definition.
What I was trying to say was that Java App Servers such as WAS, JBOSS etc, i.e. those that use Java as their only environment, use properties files and in some cases far, far to many of them.
Broker (IMHO) uses a different paradyme and you run into problems (As is evident on this forum) if you try to write Broker Flows/apps as if they were running on WAS.
The common argument I get for people wanting to use properties files with broker is that "These values might change".
Fine, why not have a Table in a DB that is read by the flow in a read only, no lock way once every 10 seconds (using a timer node) and storing the results in a set of shared ESQL variables.
IMHO, and hey, I've only been using fron since 2.0.1 days, this is far more efficient than reading a properties file with every message being processed.
If you are processing 100+ messages per second using multiple instances of the flow then you are going to hit locking problems with the file read whereas in my scenario, there are none.
Just my 2p worth.(Not that 2p will buy you much these days) _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
Back to top |
|
 |
|