| Oracle® Application Integration Architecture Oracle Communications Order to Cash Integration Pack Implementation Guide for Siebel CRM, Oracle Communications Order and Service Management, and Oracle Communications Billing and Revenue Management Release 11.3 Part Number E50337-01 |
|
|
PDF · Mobi · ePub |
This chapter describes the Provision Order and Update Fulfillment Order business flows and explains how the Oracle Communications Order to Cash Integration Pack for Siebel customer relationship management (Siebel CRM), Oracle Communications Order and Service Management (OSM), and Oracle Communications Billing and Revenue Management (BRM) (the integration) implements the business flow using communications industry-specific Oracle Application Integration Architecture (Oracle AIA) components and integration services.
The following Pre-Built Integration options enable the Provision Order and Update Fulfillment Order business flows:
Oracle Communications Order to Cash for Siebel CRM and OSM Pre-Built Integration option
Oracle Communications Order to Cash for Siebel CRM, OSM, and BRM Pre-Built Integration option
The Provision Order and Update Fulfillment Business Order business flows support the following integration flow:
OSM Fulfillment to OSM Provisioning integration flow: passes provision order requests to OSM in the service order management role (OSM SOM) and updates OSM in the central order management role (OSM COM) with OSM SOM milestones, status, and data.
This integration flow uses the following interfaces:
ProcessProvisioningOrderOSMCFSCommsJMSConsumer
ProcessProvisioningOrderOSMPROVCommsJMSProducer
ProcessFulfillmentOrderUpdateOSMCFSCommsJMSProducer
ProcessFulfillmentOrderUpdateOSMPROVCommsJMSConsumer
Figure 15-1 illustrates the sequence of events for requesting provisioning of an order to OSM Provisioning and receiving updates back:
When this process is initiated, the following events occur:
Whenever a new order is created in Provisioning, a ProcessProvisioningOrderEBM message is created by OSM COM. The message is enqueued in the AIA_CRTFO_OUT_JMSQ queue using the store-and-forward mechanism.
The ProcessProvisioningOrderOSMCFSCommsJMSConsumer service monitors the AIA_CRTFO_OUT_JMSQ queue and dequeues the message from the Oracle AIA queue using a JMS adapter service whenever a message exists. The message is then routed to the ProcessProvisioningOrderOSMPROVJMSProducer service.
The routing mentioned in the previous step produces the message into the AIA_FOPROV_IN_JMSQ queue. The store-and-forward mechanism puts the message into OSM. OSM SOM then picks up the message from the queue and processes it accordingly.
During provisioning, one or more update messages are enqueued by OSM SOM into OSM WebLogic and eventually moves to the AIA_FOPROV_OUT_JMSQ queue using store-and-forward. The ProcessFulfillmentOrderUpdateOSMPROVCommsJMSConsumer service dequeues the ProcessFulfillmentOrderUpdateEBM message and routes it to the ProcessFulfillmentOrderUpdateOSMCFSCommsJMSProducer service.
The ProcessFulfillmentOrderUpdateOSMCFSCommsJMSProducer service enqueues the ProcessFufillmentOrderUpdateEBM message in the AIA_FOCFS_IN_JMSQ queue using store-and-forward. OSM picks up this message to update the status of the order.
See "Understanding the Process Integration for Order Lifecycle Management" for more information about the events that occur when this process initiates.
For this flow there are two transaction boundaries. Table 15-1 describes the transactions involved, the database operations, and what actions to take in case of an error.
See "Using Error Type to Control Response to Order Fallout" for more information about system and business errors.
The following services are involved:
ProcessProvisioningOrderOSMCFSCommsJMSConsumer
ProcessProvisioningOrderOSMPROVCommsJMSProducer
ProcessFulfillmentOrderUpdateOSMPROVCommsJMSConsumer
ProcessFulfillmentOrderUpdateOSMCFSCommsJMSProducer
Table 15-1 Transaction Boundaries and Recovery Details
| Transaction | DB Operations | In Case of Error | Recovery |
|---|---|---|---|
|
ProcessProvisioningOrderOSMCFSCommsJMSConsumer routes the message to ProcessProvisioningOrderOSMPROVCommsJMSProducer, which produces message into AIA_FOPROV_IN_JMSQ. SAF puts message in OSM. |
None. |
Rollback JMS message to originating queue AIA_CRTFO_OUT_JMSQ_ErrorQ |
Resubmit the message from AIA_CRTFO_OUT_JMSQ_ErrorQ. |
|
During provisioning, update messages are dequeued by OSM and eventually moves to AIA_FOPROV_OUT_JMSQ. ProcessFulfillmentOrderUpdateOSMPROVCommsJMSConsumer routes the message to ProcessFulfillmentOrderUpdateOSMCFSCommsJMSProducer, which produces the message to AIA_FOCFS_IN_JMSQ. |
None. |
Rollback JMS message to the originating queue AIA_FOPROV_OUT_JMSQ_ErrorQ. |
Resubmit the order from AIA_FOPROV_OUT_JMSQ_ErrorQ. |
See "Configuring Oracle AIA Processes for Error Handling and Trace Logging", Configuring Fault Policies to Not Issue Rollback Messages in Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack for more information about rollback procedures.
The Provision Order and Update Fulfillment Order business flows use the following communications industry-specific Oracle AIA components:
ProvisioningOrderEBO
ProcessProvisioningOrderEBM
FulfillmentOrderEBO
ProcessFulfillmentOrderUpdateEBM
The industry enterprise business object (EBO) and enterprise business message XML schema (EBM XSD) files are located here: $AIA_HOME/AIAMetaData/AIAComponents/EnterpriseObjectLibrary/Industry/Communications/EBO/
The industry enterprise business service (EBS) WSDL files are located here: $AIA_HOME/AIAMetaData/AIAComponents/EnterpriseBusinessServiceLibrary/Industry/Communications/EBO/
For detailed documentation of individual EBOs and EBMs, click the AIA Reference Doc link on EBO and EBM detail pages in the Oracle Enterprise Repository (OER).
EBOs can be extended, for instance, to add new data elements. These extensions are protected and remain intact after a patch or an upgrade, so long as the extensibility guidelines are followed.
See Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack for more information about:
Configuring and using OER as the Oracle SOA Repository to provide the AIA Reference doc link
Extending existing schemas and EBOs
The following services are delivered with the Provision Order and Update Fulfillment Order business flows:
ProcessProvisioningOrderOSMCFSCommsJMSConsumer
ProcessProvisioningOrderOSMPROVCommsJMSProducer
ProcessFulfillmentOrderUpdateOSMPROVCommsJMSConsumer
ProcessFulfillmentOrderUpdateOSMCFSCommsJMSProducer
For interacting with OSM Provisioning, OSM Fulfillment pushes ProcessProvisioningOrderEBM message into AIA_CRTFO_OUT_JMSQ using store-and-forward.
The ProcessProvisioningOrderOSMCFSCommsJMSConsumer is a Mediator process that has a JMS Adapter Service. This Mediator service continuously polls the AIA_CRTFO_OUT_JMSQ. The ProcessProvisioningOrderOSMCFSCommsJMSConsumer dequeues the ProcessProvisioningOrderEBM and routes it to the ProcessProvisioningOrderOSMPROVCommsJMSProducer.
This service has one operation: Consume_Message.
The ProcessProvisioningOrderOSMPROVCommsJMSProducer is a BPEL process that has a JMS Adapter Service. This BPEL process is responsible for pushing the ProcessProvisioningOrderEBM message into the AIA_FOPROV_IN_JMSQ using store-and-forward. OSM Provisioning then consumes this message and processes it further.
This service has one operation: Initiate.
For interacting with OSM COM, OSM SOM pushes ProcessFulfillmentOrderUpdateEBM message into AIA_FOPROV_OUT_JMSQ using store-and-forward.
The ProcessFulfillmentOrderUpdateOSMPROVCommsJMSConsumer is a Mediator process with a JMS Adapter Service. The ProcessFulfillmentOrderUpdateOSMPROVCommsJMSConsumer dequeues the ProcessFulfillmentOrderUpdateEBM from AIA_FOPROV_OUT_JMSQ and routes it to ProcessFulfillmentOrderUpdateOSMCFSCommsJMSProducer.
This service has one operation: Consume_Message.
The ProcessFulfillmentOrderUpdateOSMCFSCommsJMSProducer is a BPEL process that has a JMS Adapter Service. This BPEL process is responsible for pushing the ProcessFulfillmentOrderUpdateEBM Message into the AIA_FOCFS_IN_JMSQ. Using the SAF mechanism, it gets into the appropriate OSM queue.
This service has one operation: Initiate
|
 Copyright © 2011, 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
