Skip Headers
Oracle® Application Integration Architecture Oracle Communications Order to Cash Integration Pack Implementation Guide for Siebel CRM, Oracle Order and Service Management, and Oracle Billing and Revenue Management
Release 11.1

Part Number E22651-03
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

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

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

This chapter includes the following sections:

15.1 Provision Order and Update Fulfillment 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.

15.2 Oracle OSM Fulfillment to Oracle OSM Provisioning Integration Flow

This integration flow uses the following interfaces:

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

This image is described in surrounding text.

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 CommunicationsProvisioningOrderEBSV1 by calling the ProcessProvisioningOrder operation.

  3. The CommunicationsProvisioningOrderEBSV1 then routes the message to the ProcessProvisioningOrderOSMPROVJMSProducer.

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

  5. 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 passes it on to the CommunicationsFulfillmentOrderEBSV1 with the operation ProcessFulfillmentOrderUpdate.

  6. CommunicationsFulfillmentOrderEBSV1 routes the message to the ProcessFulfillmentOrderUpdateOSMCFSCommsJMSProducer. The producer 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.3 Industry Oracle AIA Components

The process integration uses these industry components:

The industry enterprise business object (EBO) and EBM XSD files are located here: $AIA_HOME/apps/AIAMetaData/AIAComponents/EnterpriseObjectLibrary/Industry/Communications/EBO/

The industry EBS WSDL files are located here: $AIA_HOME/apps/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 Application Integration Architecture - Foundation Pack: Integration Developer's Guide, "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.

For more information, see Oracle Application Integration Architecture - Foundation Pack: Integration Developer's Guide, "Extensibility for Oracle AIA Artifacts," Extending EBOs.

15.4 Integration Services

These services are delivered with this integration:

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 CommunicationsProvisioningOrderEBSV1 by calling the ProcessProvisioningOrder operation.

This service has one operation: Consume_Message.

15.4.2 CommunicationsProvisioningOrderEBSV1

The CommunicationsProvisioningOrderEBSV1 is a Mediator service and performs this routing operation:

ProcessProvisioningOrder: Routes the ProcessProvisioningOrderEBM to the ProcessProvisioningOrderOSMPROVJMSProducer.

For more information about this EBS, see Oracle Application Integration Architecture - Foundation Pack: Integration Developer's Guide, "Designing and Developing Enterprise Business Services" and Oracle Fusion Middleware Concepts and Technologies Guide for Oracle Application Integration Architecture Foundation Pack, "Understanding Enterprise Business Services."

15.4.3 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.4 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 the CommunicationsFulfillmentOrderEBSV1 by calling the ProcessFulfillmentOrderUpdate operation.

This service has one operation: Consume_Message.

15.4.5 CommunicationsFulfillmentOrderEBSV1

The CommunicationsFulfillmentOrderEBSV1 is a Mediator process that performs this routing operation:

ProcessFulfillmentOrderUpdate: Routes the ProcessFulfillmentOrderUpdateEBM message to the ProcessFulfillmentOrderUpdateOSMCFSCommsJMSProducer

For more information about this EBS, see Oracle Application Integration Architecture - Foundation Pack: Integration Developer's Guide, "Designing and Developing Enterprise Business Services" and Oracle Fusion Middleware Concepts and Technologies Guide for Oracle Application Integration Architecture Foundation Pack, "Understanding Enterprise Business Services."

15.4.6 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