UpdateSalesOrderSiebelCommsJMSConsumer is Slow During Flow Execution (Doc ID 2636527.1)

Last updated on MARCH 29, 2023

Applies to:

Goal

Scenario:

• After upgrade to AIA (Oracle Application Integration Architecture) 12.2, one is observing some slowness in the UpdateSalesOrderSiebelCommsJMSConsumer Mediator Composite before it calls the UpdateSalesOrderSiebelCommsProvABCSImpl composite.
• This is identified in some medium level of testing during SIT (System integration testing).
• There is about 1 minute delay in this mediator.
• This can be a significant issue when testing with larger volume.
• What can be done to improve the performance of this composite?

Following analysis can be considered in above context:

• Siebel status update should happen in the same order that OSM (Order and Service Management) updates it. Let us say that OSM published status “In-progress” and “completed”, Siebel should be updating the status in the same order “in-progress” and “completed”.
• System is using re-sequencer in AIA to achieve this functionality.
• Regarding the re-sequencer fine tuning, AIA does not have any special requirement, rather it depends on SOA (service-oriented architecture) fine tuning.
• As a general understanding, re-sequencer performance depends upon several factors such as database tuning, thread tuning for re-sequencer and groups; so one can refer the SOA recommendations for further guidelines. Below are couple of SOA 12c performance tuning related to re-sequencer.
  https://docs.oracle.com/middleware/1213/soasuite/administer/GUID-DAC86612-2ED4-4AA6-BF3F-CAFE3DA38C4C.htm#SOAAG37220
  https://docs.oracle.com/middleware/1213/core/ASPER/mediator.htm#ASPER424
  https://docs.oracle.com/middleware/12212/soasuite/administer/GUID-DAC86612-2ED4-4AA6-BF3F-CAFE3DA38C4C.htm#SOAAG37220
  https://docs.oracle.com/middleware/12212/lcm/ASPER/GUID-0F0D2370-55FA-47E4-8AC8-C879FFF4A7EF.htm#ASPER99246

Based on some configuration changes from above documentation it still does not hep and on further analysis below could be a possible cause of this time taken:

• Even after some relevant changes, there is a complete 1 minute gap between the UpdateSalesOrderSiebelCommsJMSConsumer and the UpdateSalesOrderSiebelCommsProvABCSImpl call
• On analyzing further, there are a couple of properties in the UpdateSalesOrderSiebelCommsJMSConsumer_RS.mplan file as mentioned below.
  
  

Question:

The question is whether one can make this value as 0 and also can one make maxRowsRetrieved as 5 (mentioned as a default value) to tune this flow execution.

Solution

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