| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| configurable behavior in WMB6 (setting UDP values) |
View previous topic :: View next topic |
| Author |
Message
|
| osmanm |
 Posted: Tue Nov 04, 2008 2:31 am Post subject: configurable behavior in WMB6 (setting UDP values) |
 |
|
Newbie
Joined: 04 Nov 2008
Posts: 3
|
Any idea about this.
I need to have switchable (configurable) behavior in a WMB flow. Something like trace level does. Some time we need extra (meta) information in response message. This extra information is default off. When extra info is needed we want only to change (by administrator) some parameter without need for new deployment.
Maybe this can be done with User Defined Property. I have defined flow level UDP named INFO_ENABLED (with default value is false), and a filter node which use this value to decide about extra info. We want to enable administrators to only change value of UDP and extra functionality is enabled.
But I can’t find a way “how to change a value of UDP without changing the .bar file and without new deployment?”
Do you know how can I change a flow UDP value without new deployment of bar file in WMB 6 (not WMB 6.1)? If you don’t, is there any other way to get this done (have functionality which can be controlled outside a flow). |
|
| Back to top |
|
 |
| elvis_gn |
| Posted: Tue Nov 04, 2008 3:30 am Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi osmanm,
Bar files you need to redeploy.
Use Database, maintain a table with Flow specific parameters in Key Value Pairs.
Read the table when the flow is deployed and update the flow when the table is updated...you could use the Broker Cache Nodes for memory.
Regards. |
|
| Back to top |
|
|
| osmanm |
| Posted: Tue Nov 04, 2008 4:06 am Post subject: |
|
|
Newbie
Joined: 04 Nov 2008
Posts: 3
|
1. I thought about database table, but database it to expensive for performance. Switch using database table brings overhead. If I cache value, then I need refresh mechanism (using one of TimerNode, another InputNode, or special admin message on current InputNode).
2. What do you mean with update the flow when the table is updated ? stop / start ?
This can be solution. In my case it is not best because I want to apply solution as pattern in many flows. Addition of database table of Input queue per flow is to expensive.
Any way thanks.
Someone, another suggestion? |
|
| Back to top |
|
|
| elvis_gn |
| Posted: Tue Nov 04, 2008 4:21 am Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi osmanm,
| osmanm wrote: |
| 2. What do you mean with update the flow when the table is updated ? stop / start ? |
Use table trigger(on data change) to generate an XML which will run your cache updation flow.
| osmanm wrote: |
| This can be solution. In my case it is not best because I want to apply solution as pattern in many flows. Addition of database table of Input queue per flow is to expensive. |
Create a sub-flow which starts with the MQInput etc, next immediately load the cache for the particular flow from memory...You will not have to hit the database at all...if cache is empty request loading of cache from Db, which will be a rare occurrence.
Regards. |
|
| Back to top |
|
|
| osmanm |
| Posted: Tue Nov 04, 2008 5:42 am Post subject: |
|
|
Newbie
Joined: 04 Nov 2008
Posts: 3
|
|
| Back to top |
|
|
|
|
|
|
|
Page 1 of 1 |
|
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
|
|
|
|
