JSRP Configuration to send events to a JMS queue
(Doc ID 2391766.1)
Last updated on DECEMBER 04, 2019
Applies to:Oracle Communications ASAP - Version 184.108.40.206.0 and later
Oracle Communications Order and Service Management - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
This article describes the JSRP parameters that need to be configured in ASAP 18.104.22.168.0+ to enable JSRP to send events to a JMS queue. This can help simplify the integration with upstream systems such as Oracle Communications Order and Service Management (OSM).
In earlier versions of ASAP, JSRP sends asynchronous events about order lifecycle updates to JMS Topics (XVTEventTopic and JVTEventTopic). A messaging bridge is used to forward these events from the Event Topic to a SAF imported queue. However, starting in ASAP 22.214.171.124.0, by having the new JSRP parameters configured as mentioned in this document, JSRP can also send events to a JMS queue.
The following article describes a common approach for integrating OSM and ASAP.
“Configuring WebLogic Resources for OSM Integration With ASAP And UIM On Different Domains” (Doc ID 1431235.1).
If you are upgrading to ASAP 126.96.36.199.0 and hence are switching from the “messaging bridge” approach to "event queue" approach, then it is important to delete the messaging bridge in your domain. Otherwise, OSM will receive each event twice.
The following diagram (from Doc ID 1431235.1) shows the messaging components for OSM-ASAP integration when using an event queue. The events are sent directly to the OSM Event Queue via SAF imported queue.
If no reply-to value is specified by the upstream system, then responses will also be sent to the event queue.
This applies to ASAP 188.8.131.52 and higher
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