| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Platform-dependent variable values |
« View previous topic :: View next topic » |
| Author |
Message
|
| edtguy |
 Posted: Thu Feb 10, 2005 12:14 pm Post subject: Platform-dependent variable values |
 |
|
Novice
Joined: 28 Oct 2004
Posts: 13
Location: Hoboken, NJ, USA
|
I have the following scenario:
I currently have two platforms for the message broker: development and qa. I also have a single instance of a faxing service that is to be brokered from both platforms. In order for the faxing service to know which platform to forward its status responses to, it expects a value to be set in the incoming fax message. This message is created in a compute node of the broker and the response target value is currently hard-coded for the development environment. I do not want to have to maintain two separate versions of the message flow, one for dev and one for qa, just to set the correct value of this parameter. I would like to possibly initialize a global variable from either the O/S environment or some configuration or property file.
Does WMQI have any built-in feature for setting platform-specific values from either the environment or some config file?
TIA,
Ed |
|
| Back to top |
|
 |
| JT |
| Posted: Thu Feb 10, 2005 12:37 pm Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
The IA06 Get all environment variables supportpac provides a node that will supply all of the broker's system environments variables, through a special ENV branch.
Or you could use a database in the role of a property/config file, and retrieve the values through a SQL Select call. |
|
| Back to top |
|
|
| JT |
| Posted: Thu Feb 10, 2005 1:59 pm Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
One more thought.
If it's available for your platfrom, the IA91 Broker domain data store supportpac has a 'CacheConfig' node that initalizes a memory cache from a database at the broker domain level. The cache is available to all message flows that are managed by the broker, and the cache exists for the life of the broker. This eliminates the need to perform a multitude of SQL Select calls from various message flows, in order to obtain the configuration values from the database. |
|
| 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
|
|
|
|
