| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Using Queue other than EXEXMLINPUTQ..... |
« View previous topic :: View next topic » |
| Author |
Message
|
| Hari |
 Posted: Thu Apr 22, 2004 9:53 am Post subject: Using Queue other than EXEXMLINPUTQ..... |
 |
|
Centurion
Joined: 21 Nov 2002
Posts: 117
Location: USA
|
Hi all,
Normally Workflow picks up messages, say the XML messages to start of a process instance....from the queue "EXEXMLINPUTQ".
Is it possible for us to set a user-defined queue say "MYQueue", so that WF picks up the messages from this queue.
If this possible how do we go about it?
Regards,
Hari |
|
| Back to top |
|
 |
| CHF |
| Posted: Thu Apr 22, 2004 10:02 am Post subject: |
|
|
Master
Joined: 16 Dec 2003
Posts: 297
|
Create an Alias Queue "MYQueue" -- Target Queue "EXEXMLINPUTQ".
CHF  |
|
| Back to top |
|
|
| Hari |
| Posted: Thu Apr 22, 2004 10:39 am Post subject: |
|
|
Centurion
Joined: 21 Nov 2002
Posts: 117
Location: USA
|
I have done that....but is it possible to have an altogether different local queue other than "EXEXMLINPUTQ".
Regards,
Hari |
|
| Back to top |
|
|
| Ratan |
| Posted: Thu Apr 22, 2004 10:54 am Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
EXEXMLINPUTQ is where Workflow listens for XML input messages. Theoritically you might be able to have a different Queue where fmcemain listens on. I am not sure if it can be done. Even if it is done, I think IBM would not support it.
_________________
-Ratan |
|
| Back to top |
|
|
| CHF |
| Posted: Thu Apr 22, 2004 12:21 pm Post subject: |
|
|
Master
Joined: 16 Dec 2003
Posts: 297
|
| Quote: |
| user-defined queue say "MYQueue", so that WF picks up the messages from this queue |
Just of curious, Why you want to achieve this? Is this something you are planning to implement?
CHF |
|
| Back to top |
|
|
| praveenchhangani |
| Posted: Thu Apr 22, 2004 12:23 pm Post subject: |
|
|
Disciple
Joined: 20 Sep 2002
Posts: 192
Location: Chicago, IL
|
Hari,
Here's my 2 cents worth:
Conventionally the EXEXMLINPUTQ is the queue where one must put the XML messages for workflow transaction processing to begin and I agree with Ratan that sometimes crossing those boundaries can certainly cause a bit of email/phone tag with IBM, however if I think I know what you may be trying to achieve here, I believe it is more than possible.
The most common reason as to why Workflow developers/architects avoid taking the route directly putting something on the EXEXMLINPUTQ has to do with the robustness of their error handling. In other words, if by accident a message is put on the EXEXMLINPUTQ which is not valid or has a missing parameter somewhere or is non workflow xml compliant, then instead of having workflow send an error to the administration queue and/or put the message(es) on hold, the developers can avoid that by creating another local queue, putting the messages on that queue for example PREXMLINPUTQ and run their custom developed code to parse through all incoming messages prior to loading on the EXEXMLINPUTQ, and then move the messages to the EXEXMLINPUTQ. (This way you are essentially adding another layer of error control)
Another reason for this is sometimes(again goes back to your architecture), there is a need to gain statistics on EXACTLY what is coming in, what has gone through and what has been processed. (You can build a java parser that performs some algorithm and gives you just that - however obviously you wouldn't want to do that directly from the EXEXMLINPUTQ as per performance considerations, hence the use of another queue.
The thing to be careful about here, has to do with OTHER applications that might want to talk to the EXEXMLINPUTQ rather than a local queue that you defined, so keep that in mind when going the unconventional route. A lot of times there are Workflow plug and play applications that tend to have the EXEXMLINPUTQ hardcoded in them and although in this case, that would not be an issue as the messages eventually DO arrive on the EXEXMLINPUTQ and DO go through any error handling capabilities provided by the workflow product itself, however it's just something to keep at the back of your mind.
Good luck!
Thanks,
_________________
Praveen K. Chhangani,
IBM Certified Solutions Designer -
MQ Workflow 3.4. |
|
| Back to top |
|
|
| Ratan |
| Posted: Thu Apr 22, 2004 1:00 pm Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
| Quote: |
| Is it possible for us to set a user-defined queue say "MYQueue", so that WF picks up the messages from this queue. |
Praveen, I believe Hari is asking something else.
_________________
-Ratan |
|
| 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
|
|
|
|
