| Author |
Message
|
| biswagourab |
 Posted: Fri Jun 09, 2006 8:16 am Post subject: Typical issue with WBIMB 6.0 |
 |
|
Apprentice
Joined: 31 May 2005
Posts: 47
Location: London
|
Hi All
One thing that I noticed about the WBIMB 6.0 .... once we deploy a flow with the settings in the nodes, it does not changes its settings even when we put new values.
Like in this case the compute node kept looking for the local DB even after I specified a remote DB ODBC name.
Did anyone else face this problem?
Biswa |
|
| Back to top |
|
 |
| Bill.Matthews |
| Posted: Fri Jun 09, 2006 9:19 am Post subject: Re: Typical issue with WBIMB 6.0 |
|
|
Master
Joined: 23 Sep 2003
Posts: 232
Location: IBM (Retired)
|
| biswagourab wrote: |
Hi All
One thing that I noticed about the WBIMB 6.0 .... once we deploy a flow with the settings in the nodes, it does not changes its settings even when we put new values.
Like in this case the compute node kept looking for the local DB even after I specified a remote DB ODBC name.
Did anyone else face this problem?
Biswa |
I've seen something similar - changed settings in a node property not being picked up when the flow is already in the bar file and you simply re-add it. The work-around is to either use a new bar file or delete the flow from the bar, save the bar and then add it. I opened a pmr and its due to be fixed in fixpack 2 for the tooling.
_________________
Bill Matthews |
|
| Back to top |
|
|
| biswagourab |
| Posted: Fri Jun 09, 2006 10:55 am Post subject: |
|
|
Apprentice
Joined: 31 May 2005
Posts: 47
Location: London
|
Thanks for the temporary fix. Really wonder how many bugs this product has !!!!
Will work around creating a new bar file till then.
Thanks
Biswa |
|
| Back to top |
|
|
| elvis_gn |
| Posted: Fri Jun 09, 2006 8:01 pm Post subject: Re: Typical issue with WBIMB 6.0 |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi,
| Bill.Matthews wrote: |
I've seen something similar - changed settings in a node property not being picked up when the flow is already in the bar file and you simply re-add it. The work-around is to either use a new bar file or delete the flow from the bar, save the bar and then add it. I opened a pmr and its due to be fixed in fixpack 2 for the tooling. |
Isn't this the way the Bar is supposed to work ?  What changes u make at the bar level will only be lost if u remove and add the flow again....That is how u can use a flow across many brokers without having to change the node properties everytime....
Or is there more to this than what i'm getting from ur post
Regards. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Sat Jun 10, 2006 5:34 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I guess it sounds like the broker.xml file has the values for node properties of the flow in it, and when the properties are changed in the flow then the broker.xml is not getting updated when the flow is added. Only if the flow is deleted first are they getting updated. That makes sense - when re-adding the flow, the default properties should get updated but not any overrides.
But I never "re-add" a flow. I always delete it and then add it. It's just safer - I know for sure what I've got in the bar.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| madi |
| Posted: Mon Jun 12, 2006 9:30 am Post subject: |
|
|
Chevalier
Joined: 17 Jan 2006
Posts: 475
|
i think this is the way it is supposed to work and this is how it works in 5.0
is you configure a flow in the bar file for example change the data source name ..... then if you add the same flow again to the bar file .... the data source name is preserved ... which is actually a good thing ......
we have a different data source name for prod ... so i change it in the bar file configuration and i dont have to worry abt changing it again everytime i deploy changes to the same flow again and again 
--madi |
|
| Back to top |
|
|
|
|
