MQSeries.net :: View topic - Non-trivial intertransaction cooperation (trigger?)

SoZoneOfSky

Hello everybody,

I have application under WAS which sends a lot of messages (~500.000) to queue every night. On MQ Series with dispatch workflow those messages are parsed and dispersed to several out queues (as many as target systems interested in messages from our application). Sending of messages split into several transactions, because of maximum messages count limitation and reliability reasons.
In simplest case target system gets as many messages as our application produce, in that case there is no problem, simple format conversion is implmented.
But some systems expect all messages in, I would say, 'packed' view.

Example.
1 in case of total N messages for simple target system:
Msg1, Msg2 ... Msgn --> MESSAGE1, MESSAGE2 ... MESSAGEN
2 in case of total N messages for problem target system:
Msg1, Msg2 ... Msgn --> STARTMESSAGE, MESSAGE1, MESSAGE2 ... MESSAGEN, METAMESSAGE

The root of all evil here is METAMESSAGE, which should contain information about count of messages. This requirement forces me to use some special synchronization after application finished all messages sending.
For now I have no idea how to provide mentioned synchronization better. Should it be a message to separate (special) queue? Also I have no idea how to access messages which are already in known queue on Mq Series for that moment.
If anybody have any thoughts how it can/should be implemented, please give me know!

Thanks in advance,
Pavel