BRM Advanced Queues Different Type than PIN_EVENT_TY
(Doc ID 2517448.1)
Last updated on FEBRUARY 16, 2021
Applies to:Oracle Communications Billing and Revenue Management - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
With the implementation of Advanced Queues(AQ) integration between Billing and Revenue Management(BRM) and Oracle Service Broker(OSB), the following problem has been encountered.
The type of USER_DATA BRM produces is PIN_EVENT_TY while OSB can only accomodate sys.aq$_jms_text_message and sys.aq$_jms_bytes_message.
Question: Is there a way to set a different type than PIN_EVENT_TY on BRM side?
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