15 OLM - Provision Order and Update Fulfillment Order Business Flows: Implementation

This chapter provides an overview of the Provision Order and Update Fulfillment Order business flows and discusses industry Oracle Application Integration Architecture (Oracle AIA) components and integration services.

This chapter includes the following sections:

• Section 15.1, "Provision Order and Update Fulfillment Order Business Flows Overview"

• Section 15.2, "Oracle OSM Fulfillment to Oracle OSM Provisioning Integration Flow"

• Section 15.3, "Industry Oracle AIA Components"

• Section 15.4, "Integration Services"

15.1 Provision Order and Update Fulfillment Order Business Flows Overview

These business flows are enabled using the Oracle Communications Order to Cash Oracle Order and Service Management (Oracle OSM) pre-built integration option.

The following integration flow involves passing provision order requests to Oracle OSM Service Order Management (Oracle OSM Provisioning) and then providing the ability to update Oracle OSM Central Order Management (Oracle OSM COM) with Oracle OSM Provisioning milestones, status, and data.

• Oracle OSM Fulfillment to Oracle OSM Provisioning

15.2 Oracle OSM Fulfillment to Oracle OSM Provisioning Integration Flow

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 Oracle OSM Provisioning and receiving updates back:

Oracle OSM Fulfillment (COM) to Oracle OSM Provisioning sequence diagram

Figure 15-1 Oracle OSM Fulfillment (COM) to Oracle OSM Provisioning Sequence Diagram

When this process is initiated, the following events occur:

1. Whenever a new order is created in Provisioning, a ProcessProvisioningOrderEBM message is created by the Oracle OSM Central Fulfillment System (Oracle OSM CFS) (for OSM COM). The message is enqueued in the AIA_CRTFO_OUT_JMSQ using the store and forward (SAF) mechanism.

2. The ProcessProvisioningOrderOSMCFSCommsJMSConsumer 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.

3. The routing mentioned in the previous step produces the message into the AIA_FOPROV_IN_JMSQ. SAF puts the message into Oracle OSM. Oracle OSM Provisioning then picks up the message from the queue and processes it accordingly.

4. During provisioning, one or more update messages are enqueued by Oracle OSM Provisioning into Oracle OSM WebLogic and eventually moves to AIA_FOPROV_OUT_JMSQ using SAF. The ProcessFulfillmentOrderUpdateOSMPROVCommsJMSConsumer dequeues the ProcessFulfillmentOrderUpdateEBM message and routes the message to the ProcessFulfillmentOrderUpdateOSMCFSCommsJMSProducer.

5. The ProcessFulfillmentOrderUpdateOSMCFSCommsJMSProducer then enqueues the ProcessFufillmentOrderUpdateEBM to the AIA_FOCFS_IN_JMSQ using SAF. Oracle OSM picks up this message to update the status of the order.

For more information about the events that occur when this process initiates, see Chapter 7, "Understanding the Process Integration for Order Lifecycle Management."

15.2.1 Defining Transaction Boundaries and Recovery Details

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.

For more information about system errors and business errors, see Section 27.5.2, "Using Error Type to Control Response to Order Fallout."

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 Oracle 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 Oracle 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.

For more information about rollback procedures, see Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack, "Configuring Oracle AIA Processes for Error Handling and Trace Logging", Configuring Fault Policies to Not Issue Rollback Messages.

15.3 Industry Oracle AIA Components

The process integration uses these industry 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).

For more information about using the OER and configuring it to provide the AIA Reference Doc link, see Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack, "Configuring and Using Oracle Enterprise Repository as the Oracle SOA Repository."

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.

For more information, see Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack, "Working with AIA Design Patterns," AIA Assets Extensibility Patterns, Extending Existing Schemas in AIA.

15.4 Integration Services

These services are delivered with this integration:

• ProcessProvisioningOrderOSMCFSCommsJMSConsumer

• ProcessProvisioningOrderOSMPROVCommsJMSProducer

• ProcessFulfillmentOrderUpdateOSMPROVCommsJMSConsumer

• ProcessFulfillmentOrderUpdateOSMCFSCommsJMSProducer

15.4.1 ProcessProvisioningOrderOSMCFSCommsJMSConsumer

For interacting with Oracle OSM Provisioning, OSM COM pushes ProcessProvisioningOrderEBM message into AIA_CRTFO_OUT_JMSQ using SAF.

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.

15.4.2 ProcessProvisioningOrderOSMPROVCommsJMSProducer

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 SAF. Oracle OSM Provisioning then consumes this message and processes it further.

This service has one operation: Initiate.

15.4.3 ProcessFulfillmentOrderUpdateOSMPROVCommsJMSConsumer

For interacting with Oracle OSM COM, Oracle OSM Provisioning pushes ProcessFulfillmentOrderUpdateEBM message into AIA_FOPROV_OUT_JMSQ using SAF.

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.

15.4.4 ProcessFulfillmentOrderUpdateOSMCFSCommsJMSProducer

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 Oracle OSM queue.

This service has one operation: Initiate