-
1. Re: How executeBatchGroup and jmsReplyTo should work?
I think there's a gap. As far as I know jmsReplyTo will not return the batch group status automatically. That's the reason getBatchGroupStatus request is in place. But it's a feature the product can surely add (my view). You can create a support case requesting this enhancement request.
-
2. Re: How executeBatchGroup and jmsReplyTo should work?
Hi,
GetBatchGroupStatus returns the status of a batch group; polls for status after executing asynchronously
You can read more about it here
Rahul
-
3. Re: How executeBatchGroup and jmsReplyTo should work?
Subbu is correct here, After calling ExecuteBatchGroup, wait and then use GetBatchGroupStatus to see if the batch group executed successfully.
When making an asynchronous call, the runStatus of 0 (success) means that GetBatchGroupStatus was successfully placed in the async queue. To see the actual runStatus of the batch group, you can also specify a value in the jmsReplyTo field when making the call. The SIF response message containing the run status of the batch group will be returned on this queue
-
4. Re: How executeBatchGroup and jmsReplyTo should work?
Yes, however how it is using that "replyTo" parameter is bit strange. I raised question to support, because I see errors on the log
JMSDestination: queue://SiperianQueue?busName=SiperianBus
JMSReplyTo: queue://MDMAsyncSIF?busName=MDMBus
..
javax.jms.InvalidDestinationException: CWSIA0062E: Failed to create a MessageProducer for queue://MDMAsyncSIF?busName=MDMBus
..
Caused by: com.ibm.ws.sib.processor.exceptions.SIMPNotPossibleInCurrentConfigurationException: CWSIK0038E: The foreign bus with name MDMBus was not found on messaging engine MDMCluster01.000-SiperianBus on bus SiperianBus.
..
as far as I know SiperianBus is standard input queue, but this seems to use it for outbound. Bit odd behaviour.
-
5. Re: How executeBatchGroup and jmsReplyTo should work?
I assume this is for the GetBatchGroupStatus jmsReplyTo. Can you share the full request XML after removing username/password and any host name details? You can get the XML from the cmxserver.log in DEBUG mode.
Also, can you share the defintion of this outbound queue "MDMAsyncSIF"? If JBoss, you can pull it from the standalone-full.xml file.