ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Design a synchronous message Flow

Post new topic  Reply to topic
 Design a synchronous message Flow « View previous topic :: View next topic » 
Author Message
anshuman861
PostPosted: Wed Jun 07, 2023 10:37 pm    Post subject: Design a synchronous message Flow Reply with quote

Newbie

Joined: 19 Oct 2022
Posts: 1

I have a requirement where I will be getting a File as an input, and a message in a Queue as a 2nd input.
The requirement is to wait for both the messages to arrive and then start the processing. If the File arrives 1st, then I need to wait until the message arrives in the Queue, and then start the processing for both the inputs and vice-versa as well, if the message arrives in the Queue first, then I need to wait until the file arrives, and then start the processing.
There is no restriction on weather to do it in two different applications or in the same application.

Is there a way to achieve this. I tried reading some IBM documents but couldn't find anything useful.
Back to top
View user's profile Send private message
gbaddeley
PostPosted: Mon Jun 12, 2023 4:18 pm    Post subject: Reply with quote

Jedi

Joined: 25 Mar 2003
Posts: 2495
Location: Melbourne, Australia

What are the consequences if a file or a message never arrives? Or there is a significant delay between them? Or files and messages arrive out of order?

A possible approach is to put the files (or references to them) and the messages into a DB, using two separate flows. One of these flows, or a third flow, does a matching operation, and starts processing when it finds both pieces are present. There will also need to be some form of reconciliation, to flag files or messages that are missing the other piece after a period of time.

As you can see, this is quite messy, and makes a case for not having this requirement in the first place.

If the file and message is from the same source (or near to it), they should be combined into one message or one file. This removes the wait / reconciliation problem.
_________________
Glenn
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Design a synchronous message Flow
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.