I Using the Oracle Mediator Resequencer Feature

The Oracle Mediator Resequencer feature is used by various integration flows to ensure that messages are processed in a particular sequence.

See the discussion of resequencing in Oracle Mediator in Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite for more information about resequencer.

Queues and Flows Enabled for Sequencing

Table I-1 lists the queues and flows that are enabled for sequencing.

Note:

OSM manages scenarios where multiple revisions for the same order are sent out of sequence. If you are using a different order management system it must have similar support.

Table I-1 Queues and Flows Enabled for Sequencing

Oracle AIA Queue	Flow	JMS Priority	Sequencing Criteria	Comments
AIA_UPDSO_OUT_JMSQ	Update order flow from OSM to Oracle AIA for Siebel CRM.	Not set	Group By: Account ID mentioned in the ObjectCrossReference section of the update message(/UpdateSalesOrderEBM/EBMHeader/Sender/ObjectCrossReference/SenderObjectIdentification/AlternateObjectKey/ID[@schemeID = 'CUSTOMERPARTY_ACCOUNTID' and @schemeAgencyID = 'COMMON']) Order of Processing: FIFO (First in First Out). Composite Name: UpdateSalesOrderOSMCFSCommsJMSConsumer.	Note: The consumer in the Create Trouble Ticket for Order Fallout business flow is only a sample. The resequencer in this flow ensures that multiple updates for the same order are processed in the right sequence.
AIA_CRTCUST_OUT_JMSQ	Order flow from OSM to Oracle AIA for customer data creation in billing.	Set by OSM	Group By: Account ID on the message (this is either the Billing account or the Service account on the order line that must be created in billing) and the target system identifier. concat($in.SyncCustomerPartyListEBM/ns0:SyncCustomerPartyListEBM/ns0:DataArea/ns0:SyncCustomerPartyList/ns0:CustomerPartyAccount/corecom:Identification/corecom:ApplicationObjectKey/corecom:ID[@schemeID='AccountId'], $in.SyncCustomerPartyListEBM/ns0:SyncCustomerPartyListEBM/corecom:EBMHeader/corecom:Target/corecom:ID) Order of Processing: FIFO (First in First Out). Composite Name: CommunicationsCustomerPartyEBSV2Resequencer.	The resequencer in this flow ensures that the solution can successfully handle processing of concurrent orders for the same customer.
--	Sync customer flow from Siebel CRM system to Oracle Customer Hub.	Not Set	Group By: AccountID. Order of Processing: FIFO (First in First Out). Composite Name: SyncAcctSiebelAggrEventConsumer SyncContSiebelAggrEventConsumer.	Also available in the Agent Assisted Billing Care pre-built integration. The resequencer in this flow ensures that multiple updates for the same customer are processed in the right sequence.
AIA_CRTFO_IN_JMSQ	Order flow from Oracle AIA to OSM	Set by ProcessSalesOrderFulfillmentOSMCFSCommsJMSProducer	None. (Onus is on OSM.)	NA
AIA_CRTBO_OUT_JMSQ	Order flow from OSM to AIA for billing.	Set by OSM	None as delivered. Customers can use ProcessFulfillmentOrderBillingOSMCFSCommsJMSConsumer to implement custom sequencing.	NA
AIA_UPDBO_IN_JMSQ	Order flow from AIA (from billing) to OSM	Set by ProcessFulfillmentOrderBillingResponseOSMCFSCommsJMSProducer	None. (Onus is on OSM.)	NA
AIA_UPDCUST_IN_JMSQ	Response of the customer creation in billing from AIA to OSM	Set by ProcessFOBillingAccountListRespOSMCFSCommsJMSProducer	None. (Onus is on OSM)	NA
AIA_CRTFO_OUT_JMSQ	Create Fulfillment Order flow from OSM to Oracle AIA for the provisioning system	Set by OSM.	None as delivered. Customer can use ProcessProvisioningOrderOSMCFSCommsJMSConsumer to implement custom sequencing.	NA
AIA_FOCFS_IN_JMSQ	Update Fulfillment Order flow from Oracle AIA (from the provisioning system) to OSM)	Set by ProcessFulfillmentOrderUpdateOSMCFSCommsJMSProducer	None. (Onus is on OSM)	NA
AIA_FOPROV_OUT_JMSQ	Update Fulfillment Order flow from the provisioning system to Oracle AIA (for OSM)	Set by provisioning system	None as delivered. Customer can use ProcessFulfillmentOrderUpdateOSMPROVCommsJMSConsumer to implement custom sequencing.	NA
AIA_FOPROV_IN_JMSQ	Create Fulfillment Order from Oracle AIA (from OSM) to the provisioning system.	Set by ProcessProvisioningOrderOSMPROVCommsJMSProducer	None. (Onus is on OSM)	NA

Resolving Errors in Flows with Resequencer

If an error occurs in the Oracle Communications Billing and Revenue Management (BRM) Customer provider, the message may be blocked in the CommunicationsCustomerPartyEBSV2Resequencer service and the error message may not propagate back to CommsProcessFulfillmentOrderBillingAccountListEBF. In these situations, fallout specialists must take corrective action on the resequencer to move the flow. If the message fails due to a system error (for example, if the target system is unavailable), then fallout specialists must retry the message from resequencer. If the message fails because of a business error, then the fallout specialist must unblock the resequencer.

An error may occur in the Siebel CRM provider after it is consumed by UpdateSalesOrderOSMCFSCommsJMSConsumer and sent for processing. In this situation the messages are rolled back to the resequencer for this consumer and any subsequent order updates for that particular order are not processed. If this occurs, the fallout specialist must take corrective action on this resequencer to move the flow like the ones described above. If the message fails due to a system error (for example, if the target system is unavailable), then fallout specialists must retry the message from resequencer. If the message fails because of a business error, then the fallout specialist must unblock the resequencer.

See the discussion of monitoring resequenced messages in Oracle Fusion Middleware Administrator's Guide for Oracle SOA Suite and Oracle Business Process Management Suite for more information on unblocking and retrying.