How Can JMSTopic Event Messages Be Restricted To Avoid Overload?
(Doc ID 1116183.1)
Last updated on DECEMBER 04, 2019
Applies to:Oracle Communications ASAP - Version 4.7.1 and later
Information in this document applies to any platform.
***Checked for relevance on 22/FEB/2013***
***Checked for relevance on July-5-2018***
There are four types of XML Event Messages generated in JMS Topic for every WO, which adds overload to the topic.
Can the unused xml event messages generated in topic be restricted at ASAP level itself not to get generated to avoid overload in system and allow only the required xml event messages to be generated in topic for the upstream to consume?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document