| Oracle® Application Integration Architecture Pre-Built Integrations 11.2: Functional Interoperability Configuration Guide Release 11.2 Part Number E27102-03 |
|
|
PDF · Mobi · ePub |
| Oracle® Application Integration Architecture Pre-Built Integrations 11.2: Functional Interoperability Configuration Guide Release 11.2 Part Number E27102-03 |
|
|
PDF · Mobi · ePub |
This chapter discusses the interoperable group of pre-built integrations: Oracle Product Master Data Management Integration Base Pack (Product MDM: Base), Oracle Product Master Data Management Integration Option for Siebel CRM (Product MDM: SBL CRM), Oracle Product Master Data Management Integration Option for Oracle Communications Billing and Revenue Management (Product MDM: Comms BRM) and Oracle Communications Order to Cash Integration Pack for Siebel CRM, Oracle OSM, and Oracle BRM (Comms Order to Cash). This chapter includes the routing rules that must be changed to enable interoperability.
This chapter includes the following sections:
In the Product MDM integration, billing products and billing discounts are defined in Oracle Product Hub (OPH). These billing products and discounts are bundled to create service bundles and promotions in OPH. These promotions are published to the target applications. The corresponding entities are created in the target applications. For example, products, discounts, bundles, and promotions are created in Siebel, but only billing products and billing discounts are created in BRM.
For more information, see the Oracle Application Integration Architecture Product Master Data Management Integration Pack Implementation Guide and the Oracle Application Integration Architecture Oracle Communication Order to Cash Integration Pack Implementation Guide for Siebel CRM, Oracle Order and Service Management, and Oracle Billing and Revenue Management.
In the Comms Order to Cash integration, billing products and billing discounts are defined in Oracle Communications Billing and Revenue Management (BRM) and synchronized to Siebel CRM. The billing products and discounts are bundled in Siebel to create service bundles and promotions. These service bundles and promotions are used in the order submission process.
The Item Catalog categories, attributes, and their associated value sets are manually created by the product administrator in Oracle Product Hub. These are synchronized as product classes and attributes in Siebel. These are no longer created in Siebel.
Bundles (service bundles, nested service bundles, and non service bundles) and promotions are manually created by the product administrator in Oracle Product Hub and synchronized to Siebel. Service bundles and Promotions are no longer created in Siebel.
The service instance-enabled flag that identifies a simple service bundle is set in Oracle Product Hub and synchronized to Siebel. The value is no longer set manually in Siebel.
Note:
The flag value must not be changed or reset after the flag is set for a product in Oracle Product Hub, synchronized to target CRM system, and transactions are submitted for processing.
The association of one-time charges (suspend fee, resume fee, cancel fee, and so forth) to the corresponding bundles and account level products must be done in Siebel.
The following promotion-based information is defined in Oracle Product Hub and synchronized to Siebel. These are no longer manually defined during promotion definition in Siebel:
Promotion-based discounts.
Promotion-based component exclusions.
Promotion-based transaction attribute value exclusions.
The following promotion-based information is defined in Siebel:
Penalty set up for promotion cancellation or upgrade.
Note:
There may be other set up steps for participating applications. See the appropriate integration implementation guide for the participating application set up steps.
The following scenarios are not tested and are not supported out-of-the-box for interoperability between the Product MDM integration and the Comms Order to Cash integration:
An implementation where OPH is introduced as the Product Master when there is a single BRM instance and the product synchronization from BRM to Siebel is continued to be used. That is, one set of products are defined in OPH and synched to BRM and Siebel and another set of products are defined in the same BRM instance and are synched to Siebel.
An implementation where OPH is introduced as the Product Master for Siebel and one of the many BRM instances and the product synchronization from BRM to Siebel is continued to be used. But the BRM instance used to synchronize products and discounts to Siebel is different from the BRM instance that is mastered by OPH.
An implementation that combines 1 and 2.
This section includes the following topics:
Products and discounts are manually created by the product administrator in Oracle Product Hub (OPH). All types of billing products and discounts are supported in OPH. All the fulfillment and communications specific attributes associated with billing products and discounts are set in OPH and synchronized to Siebel. These are synchronized to BRM and to Siebel. Products and discounts are no longer created and published from BRM.
When OPH is used as the product master to define various entities, any product publishing mechanism that exists in other applications must be disabled. For example, in the Comms Order to Cash integration, BRM is used as the product master and publishes the products and discounts to Siebel.
So in this case, when Oracle Product Hub is used as the product master, the publish mechanism in Oracle BRM must be disabled. To disable the publish, see the BRM documentation.
For more information about disabling the publish, see the BRM documentation, "Service Integration Components", "Synchronization Queue Data Manager", "Installing and Configuring the Synchronization Queue DM", "Starting and Stopping the Synchronization Queue DM".
The pricing associated with billing products is defined in Oracle Product Hub and synchronized to Siebel and BRM.
The following details that are associated with products are now defined in Oracle Product Hub and are synchronized to Siebel. These are no longer defined in Siebel:
Price overrides
Discount overrides
Special Rating Products
Friends and Family lists
Fulfillment-related information:
Success dependency
Fulfillment Item Code
The following details that are associated with discounts are now defined in Oracle Product Hub and are synchronized to Siebel.
Duration-based discount information.
The following flags that are associated with products, discounts, bundles, and promotions are now set in Oracle Product Hub and are no longer set in Siebel:
Orderable flag
Track as Asset flag
The following information associated with billing products are enriched in BRM:
Rate plan selectors for billing products.
Pipeline rating for usage based billing products.
Pricing for friends and family lists.
Discount models for billing discounts that are associated with billing discounts are enriched in BRM.
The following details are enriched in Siebel:
Matrix discounts.
Proration plan for promotions.
This section describes the routing rule changes that must be made to enable interoperability. There may be deployment sequence considerations.
For more information about deployment sequence considerations, see Section 1.2, "Deployment Dependencies".
For more information about creating and using routing rules, see Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite, "Creating Oracle Mediator Routing Rules."
Tip:
When OPH is used as the product master to define various entities, any product publishing mechanism that exists in other applications must be disabled.
CommunicationPriceListResponseEBSV2 in the Comms Order to Cash integration has routing to CAVS because the requester does not expect a response.
However, in the Product MDM integration, the CommunicationPriceListResponseEBSV2 provides routing to the Comms2CorePriceListBridge service.
If the Comms Order to Cash integration is deployed first, and then the MDM Product integration is deployed, then CommunicationPriceListResponseEBSV2 in the MDM Product integration has to be deployed which has the following routing rule.
If the Comms Order to Cash integration is deployed first and the MDM Product integration is deployed second, before deploying the MDM Product integration, the following routing rule has to be removed from $AIA_HOME/pips/MDMProduct/EBS/CommunicationsItemComposition/CommunicationsItemCompositionResponseEBSV1.
Table 7-2 Routing Rules for CommunicationsItemCompositionResponseEBSV1
| Operation | Filter Condition | Service Invoked | Description |
|---|---|---|---|
|
SyncItemCompositionListResponse |
$in.SyncItemCompositionListResponseEBM/ebo:SyncItemCompositionListResponseEBM/corecom: EBMHeader/corecom:MessageProcessingInstruction/corecom:EnvironmentCode='PRODUCTION'and $in.SyncItemCompositionListResponseEBM/ebo:SyncItemCompositionListResponseEBM/corecom: EBMHeader/corecom:Sender/corecom:WSAddress/ns0:ReplyTo/ns0:ServiceName='SyncProductBRMComms ReqABCSImpl' |
SyncProductBRMCommsReqABCSImpl:CallbackSyncItemCompositionList |
N/A |
The service configuration changes are required when Communication Order To Cash Pre-Built Integration version 11.2 is used in Interopability.
These configuration property changes are required for the ProductOptimizedSyncPriceListListSiebelCommsProvABCSImpl service. In the interop scenario on item sync, SyncItemListPIMReqABCS service waits for the response. The response from the ProductOptimizedSyncPriceListListSiebelCommsProvABCSImpl service is sent to the requester through CommunicationsPriceListResponseEBSV2.
The changes must be made in the AIAConfigurationProperties.xml for ProductOptimizedSyncPriceListListSiebelCommsProvABCSImpl service
Table 7-3 and Table 7-4 detail the property values before and after the modification. The modified property values must point to CommunicationsPriceListResponseEBSV2.
Table 7-3 Property Values Before Modification in AIAConfigurationProperties.xml for ProductOptimizedSyncPriceListListSiebelCommsProvABCSImpl service
| Service | Property Values Before Modification |
|---|---|
|
ProductOptimizedSyncPriceListListSiebelCommsProvABCSImpl |
<Property name="EBSOverride.CommunicationsPriceListResponseEBS. SyncPriceListListResponse.Address">http://[HTTP HOSTNAME]:[ADMIN PORT] /soa-infra/services/default/ProductOptimizedSyncPriceListListSiebelCommsProvABCSImpl/ ProductOptimizedSyncPriceListListSiebelCommsProvABCSImpl</Property> |
|
ProductOptimizedSyncPriceListListSiebelCommsProvABCSImpl |
<Property name="EBSOverride.CommunicationsPriceListResponseEBS.
SyncPriceListListResponse.PortType">{http://xmlns.oracle.com/ABCSImpl/Siebel/Industry
/Comms/ProductOptimizedSyncPriceListListSiebelCommsProvABCSImpl/V1}
ProductOptimizedSyncPriceListListSiebelCommsProvABCSImpl</Property>
|
|
ProductOptimizedSyncPriceListListSiebelCommsProvABCSImpl |
<Property name="EBSOverride.CommunicationsPriceListResponseEBS.
SyncPriceListListResponse.ServiceName">
{http://xmlns.oracle.com/ABCSImpl/Siebel/Industry/Comms/
ProductOptimizedSyncPriceListListSiebelCommsProvABCSImpl/V1}
ProductOptimizedSyncPriceListListSiebelCommsProvABCSImpl</Property>
|
Table 7-4 Property Values After Modification in AIAConfigurationProperties.xml for ProductOptimizedSyncPriceListListSiebelCommsProvABCSImpl service
| Service | Property Values After Modification |
|---|---|
|
ProductOptimizedSyncPriceListListSiebelCommsProvABCSImpl |
<Property name="EBSOverride.CommunicationsPriceListResponseEBS. SyncPriceListListResponse.Address">http://[HTTP HOSTNAME]:[ADMIN PORT] /soa-infra/services/default/CommunicationsPriceListResponseEBSV2/ CommunicationsPriceListResponseEBSV2_ep</Property> |
|
ProductOptimizedSyncPriceListListSiebelCommsProvABCSImpl |
<Property name="EBSOverride.CommunicationsPriceListResponseEBS.
SyncPriceListListResponse.PortType">{http://xmlns.oracle.com/ABCSImpl
/Siebel/Industry/Comms/ProductOptimizedSyncPriceListListSiebelCommsProvABCSImpl/
V1}ProductOptimizedSyncPriceListListSiebelCommsProvABCSImpl</Property>
|
|
ProductOptimizedSyncPriceListListSiebelCommsProvABCSImpl |
<Property name="EBSOverride.CommunicationsPriceListResponseEBS.
SyncPriceListListResponse.ServiceName">
{http://xmlns.oracle.com/EnterpriseServices/Core/PriceList/V2}
CommunicationsPriceListEBSResponse</Property>
|
The Product MDM integration and the Comms Order to Case integration can be deployed in any order of sequence, but if this is a fresh environment, it is recommended that you deploy the Product MDM integration first and then the Comms Order to Cash integration.
If you do so, there are no routing rule setup required.
However, if you have deployed Comms Order to Cash integration first and then the Product MDM integration, follow the respective MDM Product section to complete the routing rule configuration
For Product MDM and Comms Order to Cash interoperability, configuration depends on the order of deployment.
If the Product MDM integration with its BRM spoke is deployed first, and then the Comms Order to Cash integration is deployed, then no extra action is required.
If the Comms Order to Cash integration is deployed first, and then the Product MDM integration is deployed:
Use the deployment plan MDMProductDP.xml at $AIA_HOME/pips/MDMProduct/DeploymentPlans to redeploy CommunicationsPriceListResponseEBSV2 and CommunicationsItemCompositionResponseEBSV1 with overwrite flag set to true by updating the deployment plan as follows:
<Composite compositeName="CommunicationsPriceListResponseEBSV2" compositedir="${AIA_HOME}/pips/MDMProduct/EBS/CommunicationsPriceList/CommunicationsPriceListResponseEBSV2" revision="1.0" wlserver="pips.MDMProductPIM" action="deploy" overwrite="true"/>
<Composite compositeName="CommunicationsItemCompositionResponseEBSV1" compositedir="${AIA_HOME}/pips/MDMProduct/EBS/CommunicationsItemComposition/CommunicationsItemCompositionResponseEBSV1" revision="1.0" wlserver="pips.MDMProductPIM" action="deploy" overwrite="true"/>
Comment out rest of the composites and run the MDMProductDP.xml deployment plan.
You may also have to manually redeploy all the extra routing rules that you have deployed as part of the implementation of multiple BRM systems.
|
 Copyright © 2001, 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
