| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| User-defined Promotable Property... Can I? |
« View previous topic :: View next topic » |
| Author |
Message
|
| whbrownnc |
 Posted: Tue Aug 30, 2005 4:13 pm Post subject: User-defined Promotable Property... Can I? |
 |
|
Novice
Joined: 07 May 2003
Posts: 20
Location: Charlotte, NC
|
I would like to define a "promotable" property within my message flow. I would like to be able to set that property in the configuration tab of the bar file editor, and then refer to it within the ESQL of a Compute node within the message flow.
1) Can this be done?
2) If so... how?
3) If not, can you make a recommendation on how to pass a value into the message flow from the bar file so that it can be accessed wihtin the ESQL.
Essentially, I am attempting to provide a value that will vary between the test and production environment without "touching" the code.
_________________
Thanks,
Bill Brown
Integration Hosting and Services
IBM Certified - WMQ 6.0, 2008
IBM Certified - WMB 6.0, 2008 |
|
| Back to top |
|
 |
| JT |
| Posted: Tue Aug 30, 2005 5:17 pm Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
1. No
2. See #1
3. A few thoughts:- In the past we would set a system environment variable on the broker server that identified the environment that the broker supported (dev, int, uat, prod). Then within the message flows we used the IA06 Get All Environment Variables plug-in to retrieve that value and make it available for interrogation further down the line, by setting the value to a variable in the environment tree.
- We have since replaced that mechanism with a custom node that examines the name of the broker and sets an environment variable that identifies the environment.
- For those brokers that don't conform to our standard naming convention, we use the Initialization feature (Chapter 7) in the IA91 Broker Domain Data Store supportpac. The feature provides the ability to load a database table into the broker memory. The memory cache is then available to all instances of your messageflows, via a CacheGet node, throughout the messageflows' lifecycle.
|
|
| Back to top |
|
|
| whbrownnc |
| Posted: Tue Aug 30, 2005 5:50 pm Post subject: |
|
|
Novice
Joined: 07 May 2003
Posts: 20
Location: Charlotte, NC
|
Thanks...
I like the IA91 memory cache idea...
I think I found a fairly simple workaround.... I set the Topic property on the MQInput node... a bit of a kludge, granted, but it appears to work... I set the value into the Body of the message in the first compute node in the flow and then null out the property (just so I don't produce some obscure downstream behavior....)
If you see anything hazardous with this approach (other than the high offense of using of a data element for a purpose other than that for which it was designed...) please let me know.
Interestingly, the online help did not make reference to Topic as an MQInput node property.... (I am working with CSD04)
_________________
Thanks,
Bill Brown
Integration Hosting and Services
IBM Certified - WMQ 6.0, 2008
IBM Certified - WMB 6.0, 2008 |
|
| 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
|
|
|
|
