| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Triggering |
« View previous topic :: View next topic » |
| Author |
Message
|
| MichaelBulla |
 Posted: Wed Nov 29, 2006 12:19 am Post subject: |
 |
|
Apprentice
Joined: 27 Sep 2006
Posts: 31
Location: Hamburg/Germany
|
| jefflowrey wrote: |
| so "queuename" is not the name of the transmit queue, and "managername" is the name of the remote queue manager, and also the name of the XMITQ that you have configured against the sender channel that goes to the remote queue manager? |
Queuename is the targetqueue on a the remote-manager. Thats the way I did.
So, does it make any difference, if I use this "direct-routing" or if I use remotequeues?
Bye Michael |
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed Nov 29, 2006 12:49 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| MichaelBulla wrote: |
So, does it make any difference, if I use this "direct-routing" or if I use remotequeues?
|
Disclaimer - my Java sucks.
Given that you're having problems & it's not best practice I'd set up a remote queue. In theory, your putting program should not need to know where it's target is but be insulated from it by the remote queue. For instance, the receiving application might be moved to a different queue manager, for scaling or network reasons. With your method, all the applications would need to be changed & recompiled. Using a remote queue allows the administrator to seamlessly change the destination.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Nov 29, 2006 2:41 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| MichaelBulla wrote: |
| So, does it make any difference, if I use this "direct-routing" or if I use remotequeues? |
No, it doesn't make a difference.
Again, is the "managername" the name of a transmit queue on the local queue manager? Otherwise, direct addressing doesn't work.
And if the transmit queue is used by a sender channel that doesn't go to a queue manager named 'managername', then your messages will go to DLQ or get discarded at the remote end (depending on persistence).
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| dutilleul |
| Posted: Thu Nov 30, 2006 4:57 am Post subject: |
|
|
Newbie
Joined: 23 Feb 2006
Posts: 7
Location: Bruxelles
|
| MichaelBulla wrote: |
| dutilleul wrote: |
Hi Michael,
I try to apply the same tips on a windows machine unsuccesfully.
I've updated the file [installation_dir]\EclipseSDK30\eclipse\configuration\config.ini with the same value you gived, but the MQExplorer language stay unchanged.
Do you know the tips on windows ? Is it a registry value ?
Thanks in advance for help. |
Im sorry, I had a typo in my post. The correct term should be
org.osgi.framework.language=en
osgi.nl=en_US
Maybe thats the problem. In other case you should look in an eclipse-Forum for help. Afaik Langugage settings are done by the the underlaying eclipse-framework.
Bye Michael[/b] |
osgi.nl=en_US works well 
In the mean time, I've found another solution :
I've just made a copy of the file +MQ_INSTALL_PATH+/bin/runmqcfg.cmd and adding the following line :
set AMQ_EXPLORER=%AMQ_EXPLORER% -nl en_US
now, I start MQExplorer with command runmqcfg (with a shortcut indeed).
This can let other user choosing their language. 
Thanks for your help Michael
bye |
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
