| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Environmental Variable within a Broker |
« View previous topic :: View next topic » |
| Author |
Message
|
| puvvada |
 Posted: Wed Mar 12, 2003 11:48 am Post subject: Environmental Variable within a Broker |
 |
|
Apprentice
Joined: 01 Apr 2002
Posts: 27
|
Hi,
We developed a custom node to log some information. Since we don't need to log all the time, we planned to use an environmental variable.
Once the Broker is started and if we tried to set the env variable to a different value, the broker doesn't seems to take it, rather it is using the old value. Only if we recycle the broker the new value is effective.
My question is, Is there a way to change an env variable to be effective within a broker without recycling it.
We are using WMQI 2.1 on AIX 4.3
Thanks for your help,
-Deven |
|
| Back to top |
|
 |
| lillo |
| Posted: Wed Mar 12, 2003 11:22 pm Post subject: |
|
|
Master
Joined: 11 Sep 2001
Posts: 224
|
Hi,
We are doing something similar in one of our java plugin and it is working fine. You should know that each execution group is a different java machines, so they don´t share anything.
If you write your own java plugin, as you did, and put a variable in the JVM then when you ask for it in the same execution group you will get its value back. Then the first time the message flow execute should add the variable to the JVM and the next time getting the value back just asking for it.
Cheers,
_________________
Lillo
IBM Certified Specialist - WebSphere MQ |
|
| Back to top |
|
|
| puvvada |
| Posted: Thu Mar 13, 2003 6:37 am Post subject: Environmental Variable within a Broker |
|
|
Apprentice
Joined: 01 Apr 2002
Posts: 27
|
Hi,
The plugin that was developed is in C/C++. It is not developed in JAVA.
-Deven |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Mar 13, 2003 7:09 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
The environment for any program is copied into the program space once when the program starts up. In the case of your plug-in, it is set (as you've seen) when the broker starts up.
You may be able to code your plug-in to refresh the environment. Or you can code your plug-in to use something other than the environment (like a properties file or a registry or an ldap entry or a database or anything) to determine if you want to log or not.
You may also be able to use the existing logging and tracing facilities in WMQI within your plugin, and thus use mqsichangetrace to enable or disable your own logging. I don't know how to do this, but I believe it's possible. |
|
| 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
|
|
|
|
