My Oracle Support Banner

Priority Orders In ASAP [ MessageQueue / WebService Queue / Webservice End Point URL] (Doc ID 2998226.1)

Last updated on JANUARY 19, 2024

Applies to:

Oracle Communications ASAP - Version 7.4.0.0.0 and later
Information in this document applies to any platform.

Goal

On ASAP 7.4.0.0.0 version:

Priority Orders in ASAP [ MessageQueue / WebService Queue / Webservice endpoint URL]

There is a business scenario that is a blocker to the design, it is like while processing some Credit Control Orders (in bulk), it should not hamper any activation order requests from OSM via JMS Queue.

ASAP has order priority, but the JMS queue doesn't have it, it does process orders as FIFO.  That means, the Order Balancer doesn't propagate incoming 'JMSPriority' values when forwarding messages to ASAP

E.g. 6000 orders queued for Credit control in JMS (<ENV_ID>.MessageQueue) from OSM to ASAP, and later some 100 orders were received for Activation which has some financial impact on its order completion time. So, what should be the workaround that those Activation orders get processed ASAP first and then those credit control orders? Order priority can be given high to Activation orders, but that will work only once after the order reaches ASAP, but we are talking about prioritizing at a level up.

Should we use a separate out-of-the-box queue i.e '<ENV_ID>.WebServiceQueue' for having Credit Control Orders only, and normal Activation Orders via <ENV_ID>?MessageQueue.

Will that help in bypassing the issue of bulk processing priority?

Or sending Credit Control Orders at Web Service URL would work?

In such scenarios how the priority will be decided?
 

Solution

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
Goal
Solution
References


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