JSRP Configuration to send events to a JMS queue (Doc ID 2391766.1)

Last updated on OCTOBER 01, 2022

Applies to:

Purpose

This article describes the JSRP parameters that need to be configured in ASAP 7.3.0.3.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 7.3.0.3.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 7.3.0.3.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.

Scope

 This applies to ASAP 7.3.0.3 and higher

Details

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.