|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Clarification required abt UPES |
« View previous topic :: View next topic » |
Author |
Message
|
Muthukumar |
Posted: Thu Nov 28, 2002 10:12 pm Post subject: Clarification required abt UPES |
|
|
Newbie
Joined: 28 Nov 2002 Posts: 1 Location: India
|
Hi
I have modeled a message flow in MQSI to implement a UPES. To which queue i have to reply back the output xml from MQSI to MQWF. I got this doubt becuase while defining the UPES in MQWF, we have provision to spepcify the queue where the MQWF put XML. There is no option to specify from which queue, the MQWF will read the reply message from the MQSI.
Can any one pls clear my doubt.
regards _________________ Muthukumar N
Consultant
G4 Software Technologies India Ltd |
|
Back to top |
|
 |
jmac |
Posted: Fri Nov 29, 2002 5:58 am Post subject: |
|
|
 Jedi Knight
Joined: 27 Jun 2001 Posts: 3081 Location: EmeriCon, LLC
|
UPES replies always go to EXEXMLINPUTQ. _________________ John McDonald
RETIRED |
|
Back to top |
|
 |
Vladimir |
Posted: Mon Dec 02, 2002 6:35 pm Post subject: |
|
|
 Acolyte
Joined: 14 Nov 2002 Posts: 73 Location: USA, CA, Bay Area
|
jmac wrote: |
UPES replies always go to EXEXMLINPUTQ. |
John,
Looking into application extensibility, I think it is better to reply into FMC.FMCGRP.EXE.XML (this name has with default queue prefix FMC and system group FMCGRP in it). Although it is an alias to the local EXEXMLINPUTQ queue, it is not shared in the cluster and when you start using MQ cluster and load balancing - you will have to change the name of the queue you are using too. It is not a big deal and you should put this queue name in the application configuration anyway, but it is better to avoid it, I think.
Actually, IBM suggested us to use aliases always and not to rely on the local queue names. They may be changed in future as part of some implementation changes.  |
|
Back to top |
|
 |
Ratan |
Posted: Mon Dec 02, 2002 9:46 pm Post subject: |
|
|
 Grand Master
Joined: 18 Jul 2002 Posts: 1245
|
Vladimir wrote: |
jmac wrote: |
UPES replies always go to EXEXMLINPUTQ. |
John,
Looking into application extensibility, I think it is better to reply into FMC.FMCGRP.EXE.XML (this name has with default queue prefix FMC and system group FMCGRP in it). Although it is an alias to the local EXEXMLINPUTQ queue, it is not shared in the cluster and when you start using MQ cluster and load balancing - you will have to change the name of the queue you are using too.
|
What do you mean by FMC.FMCGRP.EXE.XML queue is not clustered? It most certainly is clustered.
And why do you want to change the name of the queue when using MQCluster and load balancing?
-Laze |
|
Back to top |
|
 |
Vladimir |
Posted: Tue Dec 03, 2002 12:59 pm Post subject: |
|
|
 Acolyte
Joined: 14 Nov 2002 Posts: 73 Location: USA, CA, Bay Area
|
lazeknight wrote: |
What do you mean by FMC.FMCGRP.EXE.XML queue is not clustered? |
Gosh... I wrote it not really clear, sorry.
I meant that EXEXMLINPUTQ is not clustered and you should avoid using it because of that fact.
FMC.FMCGRP.EXE.XML and FMC.FMCGRP.FMCSYS.EXE.XML are aliases and they are shared in the cluster. It is better to use them in your application.
 |
|
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
|
|
|
|