| 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 |
|
|
PDF · Mobi · ePub |
This appendix provides an overview of how system codes are used to identify each system instance in Oracle Application Integration Architecture (Oracle AIA) and describes how to configure additional Oracle Communications Billing and Revenue Management (Oracle BRM) instances for the process integrations in Oracle AIA for Communications.
This appendix includes the following sections:
Section F.2, "Configuring Multiple Oracle BRM Instances - General Steps"
Section F.3, "Creating a Data Source and Connection Factory"
Section F.6, "Configuring Routing Rules for Agent Assisted Billing Care Pre-Built Integration"
Section F.7, "Merging Logical Oracle BRM Instances into a Single Oracle BRM Instance"
Each system instance is identified in Oracle AIA by a unique identifier, called a system code. The system codes help Oracle AIA identify the source or destination of a message.
Table F-1 describes the system codes that comes with Oracle AIA as delivered:
Table F-1 System Code Descriptions
| System Code | Description |
|---|---|
|
SEBL_01 |
The Siebel Customer Relationship Management (Siebel CRM) instance for order capture and trouble ticketing. |
|
BRM_01 |
One Oracle BRM instance for order billing. |
|
OSMCSF_01 |
The central fulfillment system (CFS) instance of Oracle Order and Service Management (Oracle OSM) system. This is the instance responsible for customer orders in order management. |
|
OSMPROV_01 |
The provisioning system instance of Oracle OSM. |
Oracle AIA uses cross-reference (xref) tables to maintain mapping of system-specific identifiers (account ID, product ID, and so on). One xref table exists per entity. In an xref table, columns are created for each system instance. System codes are used as column names.
Oracle AIA uses domain value maps (DVMs) to map values of enumeration type attributes (such as country code, state code, price type, and so on). One DVM exists for each enumeration type attribute. Columns are created for each system instance. System codes are used as column names.
System codes are also used to identify the sender and target in the enterprise business message (EBM) header for a given EBM message. Also in AIAConfigurationProperties.xml, system code values are used to name the properties that require instance-specific values such as EndPointURI (each system has a different end point URI). An example of such a property is:
<Property name="Routing.BRMSUBSCRIPTIONService.BRM_01.EndpointURI">eis/BRM</Property>
Because Oracle OSM communicates to Oracle AIA using AIA EBMs, AIA Common IDs, and AIA DVM values, you do not require separate columns for OSMCFS_01 and OSMPROV_01 in DVMs and xrefs. Also, because Oracle AIA-OSM communications is using automatic queue synchronizations, no Oracle OSM-specific properties are in AIAConfigurationProperties.xml.
For more information, see Oracle Fusion Middleware Concepts and Technologies Guide for Oracle Application Integration Architecture Foundation Pack, "Building AIA Integration Flows."
Oracle OSM also recognizes the fulfillment topologies and assigns logical names to each system instance. These logical names should match the system codes configured in Oracle AIA.
Use this sample information as an overview of the process.
Assume that you have three billing instances. As shown in the previous section, the installation as delivered configures one Oracle BRM instance. To configure the second and third Oracle BRM instances, follow these steps. These steps guide you through the process to add billing instances. Repeat them for each additional Oracle BRM instance.
These abbreviations are used in this example:
BRM_01: The first Oracle BRM instance that is installed as delivered.
BRM_02: the second Oracle BRM instance for which the following sample configuration should be followed.
BRM_03: The third Oracle BRM instance for which the following sample configuration should be followed.
Caution:
The person performing this setup must have minimum knowledge of Composite, Oracle Mediator, and JDeveloper IDE.
To configure a second Oracle BRM instance:
Modify all of the DVMs that have BRM columns to include the BRM_02 and BRM_03 columns.
Copy the values from BRM_01 to BRM_02 and BRM_03 for all columns in the DVM table.
The following is a list of the DVMs for which BRM_02 and BRM_03 column and values must be added:
PRICE_TYPE.dvm
ACCOUNTBALANCEADJUSTMENT_TAXTREATMENT.dvm
PLANTIER_EFFECTIVITYMODE.dvm
CONTACT_SALUTATION.dvm
PRICE_OVERRIDETYPECODE.dvm
ACCOUNTBALANCEADJUSTMENT_STATUS.dvm
RATEDATA_DISCOUNTBRACKETCODE.dvm
COLLECTION_ACTIONNAME.dvm
PRICE_BILLINGPERIODCODE.dvm
ACCOUNTBALANCEADJUSTMENT_REASON.dvm
SALESORDER_LINESTATUS.dvm
RATEPLAN_TAXAPPLICABILITYCODE.dvm
COLLECTION_SUBSTATUS.dvm
RECEIVEDPAYMENT_TYPE.dvm
ADDRESS_COUNTRYID.dvm
CUSTOMERPARTY_PAYPROFILE_DELIVERYPREF.dvm
RESOURCE.dvm
INSTALLEDPRODUCT_STATUS.dvm
ACCOUNTBALANCEADJUSTMENT_USAGEALLOCATION_TAXTREATMENT.dvm
MULTIPLE_DISCOUNT_PER_EVENT.dvm
CUSTOMERPARTY_PAYPROFILE_PAYMETHODCODE.dvm
COLLECTION_PRIORITY.dvm
CUSTOMERPARTY_TYPECODE.dvm
CUSTOMERPARTY_PAYPROFILE_PAYTERMCODE.dvm
CUSTOMERPARTY_STATUSCODE.dvm
PRICETYPE_EVENT.dvm
STATE.dvm
ACCOUNTBALANCEADJUSTMENT_SUBSTATUS.dvm
SALESORDER_ACTIONCODE.dvm
PHONENUMBER_TYPE.dvm
ENTITY_TO_TARGET_APPLICATION.dvm
STOP_DISCOUNTING.dvm
PROVISIONING_TAG.dvm
PRICECHARGETYPEUOM.dvm
COLLECTION_STATUS.dvm
PLANTIER_RESTRICTIONTYPE.dvm
APPLIES_TO.dvm
PRICE_DISCOUNTTYPECODE.dvm
DAYS_OF_WEEK.dvm
CUSTOMERPARTY_PAYPROFILE_CREDIT_CARDTYPE.dvm
DISCOUNT_VALIDITY.dvm
RATEDATA_CANCELATIONPRORATIONCODE.dvm
LINEPRICE_TYPECODE.dvm
CUSTOMERPARTY_BILLPROFILE_BILLTYPECODE.dvm
RATEPLAN_TYPECODE.dvm
PRICECHARGETYPE.dvm
CUSTOMERPARTY_ACCOUNTTYPECODE.dvm
TARGET_ID.dvm
CURRENCY_CODE.dvm
RATEPLAN_UNITCODE.dvm
CUSTOMERPARTY_BILLPROFILE_FREQUENCYCODE.dvm
PRICE_IMPACTCLASSIFICATIONCODE.dvm
SALESORDER_STATUS.dvm
RATEDATA_PURCHASEPRORATIONCODE.dvm
ACCOUNTBALANCEADJUSTMENT_TYPE.dvm
CUSTOMERPARTY_PAYPROFILE_BANKACCOUNTTYPE.dvm
ADDRESS_COUNTRYSUBDIVID.dvm
GL_CODE.dvm
PRICE_MARKUPBASISCODE.dvm
ITEM_BILLING_TYPE_CODE.dvm
PLANIMPACT_UNITCODE.dvm
ITEM_BILLINGTYPECODE.dvm
PARTIAL_PURCHASE.dvm
LINEPRICE_UOMCODE.dvm
PROVINCE.dvm
TROUBLETICKET_AREA.dvm
Once all the columns have been added, load the DVMs to the Metadata Services (MDS) repository using the update deployment plan.
For more information, see Oracle Fusion Middleware Concepts and Technologies Guide for Oracle Application Integration Architecture Foundation Pack, "Building AIA Integration Flows."
Add BRM_02 and BRM_03 columns to the following XRef tables:
INSTALLEDPRODUCT_ID
CUSTOMERPARTY_LOCATIONREFID
CUSTOMERPARTY_CONTACT_PHONECOMMID
PaymentTermXREF
CUSTOMERPARTY_ADDRESSID
CUSTOMERPARTY_ACCOUNT_FAXCOMMID
PRICELINETYPE_ID
CUSTOMERPARTY_BILLPROFILEID
ITEMFORMULAMATERIAL_ID
PRICELINE_ID
CUSTOMERPARTY_PARTYCONTACTID
CUSTOMERPARTY_ACCOUNT_PHONECOMMID
CUSTOMERPARTY_CONTACT_FAXCOMMID
MANUFACTURINGROUTING_ID
CUSTOMERPARTY_PARTYID
SALESORDER_LINEID
CUSTOMERPARTY_ACCOUNT_COMMID
ITEMFORMULA_ID
ITEM_ITEMID
CUSTOMERPARTY_CONTACT_EMAILCOMMID
CUSTOMERPARTY_ACCOUNTID
SALESORDER_ID
ORGANIZATION_ID
CUSTOMERPARTY_CONTACTID
CUSTOMERPARTY_DEFAULTBALANCEGROUPID
CUSTOMERPARTY_PAYPROFILEID
CUSTOMERPARTY_CONTACT_COMMID
PRODUCTIONRECIPE_ID
CUSTOMERPARTY_PARTYLOCATIONID
After adding the columns, load the Xrefs to the MDS repository using update deployment plan.
The values are populated automatically into the new columns when the products are synchronized.
Add additional Oracle BRM connection factories that point to the new BRM_02 and BRM_03 instances:
Go to the WebLogic Console, navigate to Deployments, OracleBRMJCA15Adapter.
Add the following two new instances under the Configuration, Outbound Connection Pools tab:
eis/BRM2
eis/BRM3
Enter the Connection String property value as ip <host name/IP> <port>. For example, ip kappa.us.oracle.com 12345.
Enter the Username property value as root.0.0.0.1
Save your changes.
Update and start the adapter.
Modify all the BRM Provider service configurations in the AIAConfigurationProperties.xml file, which is located here:
$AIA_HOME/aia_instances/INSTANCE_NAME/AIAMetaData/config
The service configuration contains the Partner link details to Oracle BRM services used in that particular BPEL Service. For example, Endpoint URI. This Endpoint URI determines which edge application to use and the location to reach the application.
To route the messages to the appropriate Oracle BRM instance:
Modify the BRM Provider service configuration for all the partner links.
In the Communications pre-built integrations for this release the following services are used to route the messages to the Oracle BRM instance. Change the properties for these services:
ProcessFulfillmentOrderBillingBRMCommsProvABCSImpl
ProcessFulfillmentOrderBillingBRMCommsAddSubProcess
ProcessFulfillmentOrderBillingBRMCommsUpdateSubProcess
ProcessFulfillmentOrderBillingBRMCommsSuspendResumeSubProcess
ProcessFulfillmentOrderBillingBRMCommsDeleteSubProcess
ProcessFulfillmentOrderBillingBRMCommsMoveAddSubProcess
UpdateCreditAlertBRMCommsProvABCSImpl
SyncCustomerPartyListBRMCommsProvABCSImpl
QueryServiceUsageBRMCommsProvABCSImpl
QueryReceivedPaymentListBRMCommsProvABCSImpl
QueryInvoiceListBRMCommsProvABCSImpl
QueryInstalledProductListBRMCommsProvABCSImpl
QueryCustomerPartyListBRMCommsProvABCSImpl
QueryAccountBalanceAdjustmentBRMCommsProvABCSImpl
ProcessInstalledProductSpecialRatingSetListBRMCommsProvABCSImpl
CreateReceivedPaymentBRMCommsProvABCSImpl
CreateAccountBalanceAdjustmentBRMCommsProvABCSImpl
To update the AIAConfigurationProperties.xml file in the MDS repository, login to the AIA Console (http://host:port/AIA). Go to Setup and then select the AIAConfigurations tab. Click Reload.
The following is a sample service configuration. Enter the highlighted statements:
<Property name="Routing.BRMBALService_ptt.BRM_01.EndpointURI">eis/BRM</Property> <Property name="Routing.BRMBALService_ptt.BRM_02.EndpointURI">eis/BRM2</Property> <Property name="Routing.BRMBALService_ptt.BRM_03.EndpointURI">eis/BRM3</Property> <Property name="Routing.BRMSUBSCRIPTIONService.BRM_01.EndpointURI">eis/BRM</Property> <Property name="Routing.BRMSUBSCRIPTIONService.BRM_02.EndpointURI">eis/BRM2</Property> <Property name="Routing.BRMSUBSCRIPTIONService.BRM_03.EndpointURI">eis/BRM3</Property> <Property name="Routing.BRMCUSTService.BRM_01.EndpointURI">eis/BRM</Property> <Property name="Routing.BRMCUSTService.BRM_02.EndpointURI">eis/BRM2</Property> <Property name="Routing.BRMCUSTService.BRM_03.EndpointURI">eis/BRM3</Property>
The following steps must be followed to create a consumer for every new Oracle BRM instance. This consumer is used for product synchronization:
To create a consumer for product sync:
Create a new SOAProject project in Oracle JDeveloper, using the name SyncProductInfoChangeBRMAQ2.
Drag a new AQ Adapter component in the exposed services swimlane to display the Adapter Configuration Wizard - Welcome page, as shown in Figure F-2.
Click Next to display Step 2 (Service Name).
Go to the Service Name field and enter SyncProductInfoChangeBRMAQ2, as shown in Figure F-3.
Click Next to display Step 3 (Service Connection).
Go to Connection and select the Oracle BRM Database Connection. Go to the JNDI Name field and enter eis/AQ/PortalEventSyncAQ2, as shown in Figure F-4.
Caution:
The JNDI name is not created here by default. You must manually create the JNDI for the consumer that you are creating using the steps provided in Section F.3, "Creating a Data Source and Connection Factory."
Click Next to display Step 4 (Adapter Interface).
Go to the Interface field and select Define from operation and schema (specified later), as shown in Figure F-5.
Click Next to display Step 5 (Operation).
Go to the Operation Name field and enter Dequeue, as shown in Figure F-6.
Click Next to display Step 6 (Queue Name).
Go to the Database Schema field and select the additional Oracle BRM Instance's database schema, and then enter the queue name configured for this Oracle BRM instance, as shown in Figure F-7.
Click Next to display Step 7 (Queue Parameters).
Go to the Correlation Id field and enter ProductInfoChange, as shown in Figure F-8.
Click Next to display Step 8 (Object Payload).
Go to the Business Payload field and select Whole Object PIN_EVENT_TY, as shown in Figure F-9.
Click Next to display Step 9 (Finish), as shown in Figure F-10.
Click Finish to create the AQ Adapter service.
You must now: create a routing rule for the associated routing service.
Create a routing rule for the associated routing service.
Add a routing rule from the Adapter service created to Oracle Mediator.
Create an External Reference for SyncProductBRMVCommsReqABCSImpl web service.
Add a routing rule from Oracle Mediator to SyncProductBRMCommsReqABCSImpl web service for SyncProduct operation.
In composite.xml, provide the port and location information from concrete wsdl of the SyncProductBRMCommsReqABCSImpl web service.
<reference name="SyncProductBRMCommsReqABCSImpl" ui:wsdlLocation="oramds:/apps/AIAMetaData/AIAComponents/ApplicationConnectorServiceLibrary/BRM/V1/RequesterABCS/SyncProductBRMCommsReqABCSImpl.wsdl">
<interface.wsdl interface="http://xmlns.oracle.com/ABCSImpl/BRM/Industry/Comms/SyncProductBRMCommsReqABCSImpl/V1#wsdl.interface(SyncProductBRMReqABCSImpl)"/>
<binding.ws port="http://xmlns.oracle.com/ABCSImpl/BRM/Industry/Comms/SyncProductBRMCommsReqABCSImpl/V1#wsdl.endpoint(SyncProductBRMReqABCSImpl/SyncProductBRMReqABCSImpl)" location="http://<host name>:<Port>/soa-infra/services/default/SyncProductBRMCommsReqABCSImpl/SyncProductBRMCommsReqABCSImpl?WSDL"/>
</reference>
Create a mapping file PIN_EVENT_TY_To_ProductChangeInfo.xsl.
Double-click Mediator to open the mplan.
Add the transformation file PIN_EVENT_TY_To_ProductInfoChange.
This file can be copied from the SyncProductInfoChangeBRMAQ/xsl folder, which is shipped with the Oracle Communications Order to Cash pre-built integration.
Make the following modification:
The name space http://xmlns.oracle.com/xdb/<BRM_CAPS_USERNAME> must be changed. The name space can be found in <USERNAME>_PIN_EVENT_TY.xsd, which is created during the adapter creation.
Caution:
Make sure that this name space gets changed at the two places in the xsl file.
Deploy the Composite after the routing rule has been configured.
The same process must be followed for each additional Oracle BRM instance.
The following steps must be followed to create a consumer for every new Oracle BRM instance. This consumer is used for discount synchronization:
To create a consumer for product sync:
Create a new SOAProject project in Oracle JDeveloper, using the name SyncDiscountInfoChangeBRMAQ2.
Drag a new AQ Adapter component in the exposed services swimlane to display the Adapter Configuration Wizard - Welcome page, as shown in Figure F-11.
Click Next to display Step 2 (Service Name).
Go to the Service Name field and enter SyncDiscountInfoChangeBRMAQ2, as shown in Figure F-12.
Click Next to display Step 3 (Service Connection).
Go to Connection and select the Oracle BRM Database Connection. Go to the JNDI Name field and enter eis/AQ/PortalEventSyncAQ2, as shown in Figure F-13.
Caution:
The JNDI name is not created here by default. You must manually create the JNDI for the consumer that you are creating using the steps provided in Section F.3, "Creating a Data Source and Connection Factory."
Click Next to display Step 4 (Adapter Interface).
Go to the Interface field and select Define from operation and schema (specified later), as shown in Figure F-14.
Click Next to display Step 5 (Operation).
Go to the Operation Name field and enter Dequeue, as shown in Figure F-15.
Click Next to display Step 6 (Queue Name).
Go to the Database Schema field and select the additional Oracle BRM Instance's database schema, and then enter the queue name configured for this Oracle BRM instance, as shown in Figure F-16.
Click Next to display Step 7 (Queue Parameters).
Go to the Correlation Id field and enter DiscountInfoChange, as shown in Figure F-17.
Click Next to display Step 8 (Object Payload).
Go to the Business Payload field and select Whole Object PIN_EVENT_TY, as shown in Figure F-18.
Click Next to display Step 9 (Finish), as shown in Figure F-19.
Click Finish to create the AQ Adapter service.
You must now: create a routing rule for the associated routing service.
Create a routing rule for the associated routing service.
Add a routing rule from the Adapter service created to Oracle Mediator.
Create an External Reference for SyncDiscountBRMVCommsReqABCSImpl web service.
Add a routing rule from Oracle Mediator to SyncDiscountBRMCommsReqABCSImpl web service for SyncDiscount operation.
In composite.xml, provide the port and location information from concrete wsdl of the SyncDiscountBRMCommsReqABCSImpl web service.
<reference name="SyncDiscountBRMCommsReqABCSImpl" ui:wsdlLocation="oramds:/apps/AIAMetaData/AIAComponents/ApplicationConnectorServiceLibrary/BRM/V1/RequesterABCS/SyncDiscountBRMCommsReqABCSImpl.wsdl">
<interface.wsdl interface="http://xmlns.oracle.com/ABCSImpl/BRM/Industry/Comms/SyncDiscountBRMCommsReqABCSImpl/V1#wsdl.interface(SyncDiscountBRMReqABCSImpl)"/>
<binding.ws port="http://xmlns.oracle.com/ABCSImpl/BRM/Industry/Comms/SyncDiscountBRMCommsReqABCSImpl/V1#wsdl.endpoint(SyncDiscountBRMReqABCSImpl/SyncDiscountBRMReqABCSImpl)" location="http://<host name>:<port>/soa-infra/services/default/SyncDiscountBRMCommsReqABCSImpl/SyncDiscountBRMCommsReqABCSImpl?WSDL"/>
</reference>
Create a mapping file PIN_EVENT_TY_To_DiscountChangeInfo.xsl.
Double-click Mediator to open the mplan.
Add the transformation file PIN_EVENT_TY_To_DiscountInfoChange.
This file can be copied from the SyncDiscountInfoChangeBRMAQ/xsl folder, which is shipped with the Oracle Communications Order to Cash pre-built integration.
Make the following modification:
The name space http://xmlns.oracle.com/xdb/<BRM_CAPS_USERNAME> must be changed. The name space can be found in <USERNAME>_PIN_EVENT_TY.xsd, which is created during the adapter creation.
Caution:
Make sure that this name space gets changed at the two places in the xsl file.
Deploy the Composite after the routing rule has been configured.
The same process must be followed for each additional Oracle BRM instance.
The following steps must be followed to create a consumer for every new Oracle BRM instance. This consumer is used for customer updates:
To create a consumer for customer updates:
Create a new SOAProject project in Oracle JDeveloper, using the name SyncCustomerPartyList<BRMInstanceID>CommsJMSConsumer, where the BRM Instance Id is the Id of the new Oracle BRM instance to be added. For example, SyncCustomerPartyListBRM_02CommsJMSConsumer.
Drag a new JMS Adapter component in the exposed services swimlane to display the Adapter Configuration Wizard - Welcome page, as shown in Figure F-20.
Click Next to display Step 2 (Service Name).
Go to the Service Name field and enter SyncCustomerPartyListBRM_02CommsJMSConsumer, as shown in Figure F-21.
Click Next to display Step 3 (JMS Provider).
Select Oracle Enterprise Messaging Service (OEMS) as the JMS Provider and then select Oracle WebLogic JMS, as shown in Figure F-22.
Click Next to display Step 4 (Service Connection).
Create an Application Server Connection to the Fusion Middleware (FMW) server. Go to AppServer Connection and select the corresponding FMW server connection from the dropdown, as shown in Figure F-23.
Click Next to display Step 5 (Adapter Interface).
Go to the Interface field and select Define from operation and schema (specified later), as shown in Figure F-24.
Click Next to display Step 6 (Operation).
Go to the Operation Type field and select Consume Message. Then go to the Operation Name field and enter Consume_Message, as shown in Figure F-25.
Click Next to display Step 7 (Consume Operation Parameters), as shown in Figure F-26.
Go to the Destination Name (Topic) field and click Browse to select the required topic, as shown in Figure F-27. Click OK to return to Step 7.
Then go to the JNDI Name field and enter the JNDI name for this JMS Connection.
Click Next to display Step 8 (Messages).
Go to the URL field and enter oramds:/apps/AIAMetaData/AIAComponents/EnterpriseObjectLibrary/Industry/Communications/EBO/CustomerParty/V2/CustomerPartyEBM.xsd. Go to the Schema Element field and enter SyncCustoerPartyListEBM, as shown in Figure F-28.
Click Next to display Step 9 (Finish), as shown in Figure F-29.
Click Finish to create the JMS Adapter service.
You must now create a routing rule for the associated routing service.
Create a routing rule for the associated routing service.
Add a routing rule against the Consumer_Message operation.
Select the Endpoint service to be SyncCustomerPartyListBRMCommsProvABCSImpl.
The filter expression should be like this:
xref:lookupXRef('oramds:/apps/AIAMetaData/xref/CUSTOMERPARTY_ACCOUNTID.xref','COMMON',$in.body/imp1:SyncCustomerPartyListEBM/imp1:DataArea/imp1:SyncCustomerPartyList/imp1:CustomerPartyAccount/ns4:Identification/ns4:BusinessComponentID,'BRM_01',false()) != ''
Along with the filter expression, a xsl must be added. Name the file SetActionCodeandTargtID_BRM_02.xsl. The xsl should be like this:
<corecom:Target>
<corecom:ID>
<xsl:text disable-output-escaping="no">BRM_02</xsl:text>
</corecom:ID>
<corecom:ApplicationTypeCode>
<xsl:value-of select="aia:getSystemType('BRM_02')"/>
</corecom:ApplicationTypeCode>
</corecom:Target>
Deploy the Composite after the routing rule has been configured.
This flow synchronizes Friends and Family List updates from Siebel CRM to Oracle BRM. Per the documented restriction, given a Friends and Family List, the flow can synchronize to one and only one Oracle BRM instance.
For each Oracle BRM instance, one routing rule must exist for the ProcessInstalledProductSpecialRatingSetList operation in CommunicationsInstalledProductEBSV2. As delivered, Oracle AIA ships routing rules to route to the BRM_01 instance.
To add the additional Oracle BRM instances:
Copy the CommunicationsInstalledProductEBSV2 EBS with routing rules from this location:
$AIA_HOME/pips/Communications/O2C/EBS/InstalledProduct
Open the composite in Oracle JDeveloper.
Create new transformation files (.xsl) similar to QueryInstalledProductListEBM_BRM_01_PopulateTargetID.xsl, which populates the target section of the EBMHeader with the appropriate Oracle BRM internal system ID, (for example, BRM_02).
Name the new transformation file appropriately, (such as QueryInstalledProductListEBM_BRM_02_PopulateTargetID.xsl).
Click the portion highlighted in Figure F-30 to open the routing service.
The routing service appears as shown in Figure F-31.
For the ProcessInstalledProductSpecialRatingSetList operation, click the Add (+) icon located against the operation to create a routing rule.
The Target Type selection pop-up appears as shown in Figure F-32.
Click Service.
Select the target service from the services that are available under the same project, as shown in Figure F-33.
This is the same target service as the BRM_01 routing rule is using.
Click the Transformations button to select the transformation file.
The Request Transformation Map pop-up appears.
Select Use Existing Mapper file, and then select the mapping file for BRM_02
For example, QueryInstalledProductListEBM_BRM_02_PopulateTargetID.xsl, as shown in Figure F-34.
In the Filter expression box, copy the filter expression used for the BRM_01 routing rule and replace BRM_01 with BRM_02, as shown in Example F-1 and Example F-2.
Example F-1 Original Filter Expression Example
count($in.ProcessInstalledProductSpecialRatingSetListEBM/ebo:ProcessInstalledProductSpecialRatingSetListEBM/corecom:EBMHeader/corecom:MessageProcessingInstruction/corecom:EnvironmentCode[text()='CAVS']) = 0 and xref:lookupXRef('oramds:/apps/AIAMetaData/xref/INSTALLEDPRODUCT_ID.xref','COMMON',$in.ProcessInstalledProductSpecialRatingSetListEBM/ebo:ProcessInstalledProductSpecialRatingSetListEBM/ebo:DataArea[1]/ebo:ProcessInstalledProductSpecialRatingSetList/corecom:InstalledProductIdentification/corecom:BusinessComponentID,'BRM_01',false()) != ''
Example F-2 Replacement Filter Expression Example
count($in.ProcessInstalledProductSpecialRatingSetListEBM/ebo:ProcessInstalledProductSpecialRatingSetListEBM/corecom:EBMHeader/corecom:MessageProcessingInstruction/corecom:EnvironmentCode[text()='CAVS']) = 0 and xref:lookupXRef('oramds:/apps/AIAMetaData/xref/INSTALLEDPRODUCT_ID.xref','COMMON',$in.ProcessInstalledProductSpecialRatingSetListEBM/ebo:ProcessInstalledProductSpecialRatingSetListEBM/ebo:DataArea[1]/ebo:ProcessInstalledProductSpecialRatingSetList/corecom:InstalledProductIdentification/corecom:BusinessComponentID,'BRM_02',false()) != ''
Add the filter expression.
Save the files and deploy the Composite.
This section provides the instructions for creating the data source and connection factory.
To create the data source and connection factory:
Go to the WebLogic Server - Administration Console and navigate to Services, DataSource, New Generic Data Source.
Enter the data source name as BRMEventSyncAQ2. Enter the JDBC name as jdbc/aia/BRMEventSyncAQ2.
Click, Next, Next, Next to display the Connection Properties page, as shown in Figure F-35.
Enter all the Oracle BRM connection properties and then
Click Next to display the Test Configuration page, as shown in Figure F-36.
Click Test Configuration to verify that the provided details are correct. If the test is successful, click Finish.
Navigate to Deployments and click AQAdapter.
Go to the Configuration tab and expand the connection factory. Click New and select the connection factor.
Click Next. Provide the JNDI name as eis/AQ/PortalEventSyncAQ2.
Click Finish.
Click the newly created connection factory and go to the XADataSourceName field and enter jdbc/aia/BRMEventSyncAQ2. Click Enter and then click Save.
The same process must be followed for each additional Oracle BRM instance.
Whenever the product is synchronized to Oracle AIA (through the product lifecycle management (PLM) flows, Oracle BRM sends the instance ID in the payload to Oracle AIA to synchronize to Siebel CRM as follows:
<SyncProductReqMsg> <part xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance name="SyncProduct"> <brmproductabo:ProductInfoChange xmlns:brmproductabo="http://www.portal.com/schemas/CRMSync" brmproductabo:InstanceId="BRM_01">
Logical instances are defined in the Oracle AIA Console. The logical instance, shown in Figure F-37 must be added or changed accordingly by the value given by Oracle BRM for each instance. For example, for the second Oracle BRM instance an entry must be added as shown in Figure F-37 in the AIA_SYSTEM table.
Caution:
You must restart the server after adding entries. Otherwise, the changes are not recognized.
The logical instance name must be used in the AIAConfigurationProperties.xml, as specified in "To configure a second Oracle BRM instance:". For example, in Figure F-37, BRM_02 is the logical instance. Therefore, in the AIAConfigurationProperties.xml file, the end point configurator should be:
<Property name="Routing.BRMBALService_ptt.BRM_02.EndpointURI">eis/BRM2</Property>
The value eis/BRM2 is the JNDI name specified when creating new consumers.
The same process must be followed for each additional Oracle BRM instance.
Currently, in Typical and Reserved topologies, Oracle OSM uses the following configuration to stamp the instances. This can be changed or configured in Oracle OSM according to customer requirements so you must consult your Oracle OSM administrator before configuring the instances.
OSMCFS_01 - Oracle OSM Central Fulfillment (ALL Topologies)
BRM_01 - Billing for broadband business (Typical Topology)
BRM_02 - Billing for broadband residential (Typical Topology)
BRM_03 - Billing for voip (Typical Topology)
BRM_04 - Billing for both voip and broadband for all business and residential (Simple Topology)
BRM_05 - Billing for voip and broadband business (Reserved Topology)
BRM_06 - Billing for voip and broadband residential (Reserved Topology)
OSMPROV_01 - Oracle OSM provisioning fulfillment for voip (Reserved Topology)
OSMPROV_02 - Oracle OSM provisioning fulfillment for broadband US (Reserved and Typical Topology)
OSMPROV_03 - Oracle OSM provisioning fulfillment for broadband UK (Typical Topology)
OSMPROV_04 - Oracle OSM provisioning fulfillment for voip and broadband (Simple Topology)
WFM_01 - Work force management (Typical Topology)
SHP_01 - Shipping partnership Inc (Typical Topology)
SHP_02 - Shipping in house (Typical Topology).
| Typical Topology |
|---|
|
BRM_01 - Billing for broadband business |
|
BRM_02 - Billing for broadband residential |
|
BRM_03 - Billing for voip |
|
OSMCFS_01 - Oracle OSM Central Fulfillment |
|
OSMPROV_02 - Oracle OSM provisioning fulfillment for broadband US |
|
OSMPROV_03 - Oracle OSM provisioning fulfillment for broadband UK |
|
WFM_01 - Work force management |
|
SHP_01 - Shipping partnership Inc |
|
SHP_02 - Shipping in house |
| Reserved Topology |
|---|
|
BRM_05 - Billing for voip and broadband business |
|
BRM_06 - Billing for voip and broadband residential |
|
OSMCFS_01 - Oracle OSM Central Fulfillment |
|
OSMPROV_01 - Oracle OSM provisioning fulfillment for voip |
|
OSMPROV_02 - Oracle OSM provisioning fulfillment for broadband US |
The purpose of doing this change is to enable the enterprise business services (EBSs) in the Agent Assisted Billing Care pre-built integration (AABC) to route the billing profile-related query, create, and update sync requests to the new Oracle BRM instance. The requests are sent only to the Oracle BRM instance, where the billing profile exists. Per AABC restrictions, one billing profile cannot exist in multiple Oracle BRM systems.
To ensure that this is done, for each relevant ESB operation, add additional routing rules, one for each additional Oracle BRM instance. These are the general steps:
To add routing rules for AABC integration:
Copy the EBS services with routing rules from the setup location $AIA_HOME/pips/Communications/AABC/EBS/.
The following general steps must be repeated for each EBS service.
Open the composite in Oracle JDeveloper.
Create transformation files (.xsl) similar to the transformation file existing in the project, which populates the Target section of the EBMHeader with the appropriate Oracle BRM internal system Id, such as BRM_02.
This must be done for all the EBSs that are used across the AABC integration. These are:
EBS: CommunicationsAccountBalanceAdjustmentEBSV2
File Location: $AIA_HOME/pips/Communications/AABC/EBS/AccountBalanceAdjustment/CommunicationsAccountBalanceAdjustmentEBSV2
File Name: PopulateTargetId_BRM_01.xsl
EBS: CommunicationsInstalledProductEBSV2
If the Oracle Communications Order to Cash - Oracle BRM pre-built integration option is installed: $AIA_HOME/pips/Communications/O2C/EBS/InstalledProduct/CommunicationsInstalledProductEBSV2
If the Oracle Communications Order to Cash - Oracle BRM pre-built integration option is not installed: $AIA_HOME/pips/Communications/AABC/EBS/InstalledProduct/CommunicationsInstalledProductEBSV2
File Name: QueryInstalledProductListEBM_PopulateTargetID.xsl
EBS: CommunicationsInvoiceEBSV2
File Location: $AIA_HOME/pips/Communications/AABC/EBS/Invoice/CommunicationsInvoiceEBSV2
File Name: Populate_Target_Info_BRM_01.xsl
EBS: CommunicationsReceivedPaymentEBSV1
File Location: $AIA_HOME/pips/Communications/AABC/EBS/ReceivedPayment/CommunicationsReceivedPaymentEBSV1
File Name: Populate_Target_Info_BRM_01.xsl
EBS:CommunicationsServiceUsageEBSV2
File Location: $AIA_HOME/pips/Communications/AABC/EBS/ServiceUsage/CommunicationsServiceUsageEBSV2
File Name: Populate_Target_Info_BRM_01.xsl
EBS: CommunicationsCustomerPartyEBSV2 (only for QueryCustomerPartyList operation going to Oracle BRM)
File Location: $AIA_HOME/pips/Communications/AABC/EBS/CustomerParty/CommunicationsCustomerPartyEBSV2
File Name: AddTargetID_BRM01.xsl (for QueryCustomerPartyList going to BRM).
Click the portion circled in Figure F-38 to open the routing service.
The routing service is like the routing service shown in Figure F-39.
For each operation, create a routing rule by clicking + against the operation and then selecting static routing rule, as shown in Figure F-40.
Select Service from the Target Type pop-up.
The Target service equals what the BRM_01 routing rule is using. Select the required target service from the services available under the same project, as shown in Figure F-41.
Click the button indicating the transformations to select the transformation file, as shown in Figure F-42.
A pop-up window Request Transformation Map appears.
Select Use Existing Mapper File, and select the mapping file for BRM_02, as shown in Figure F-43.
In the Filter expression box, copy the filter expression used for the BRM_01 routing rule and replace BRM_01 with BRM_02 and add the filter expression.
For example, replace the content in Example F-3 with the content in Example F-4.
Example F-3 Original Filter Expression
$in.CreateReceivedPaymentEBM/receivedpaymentebo:CreateReceivedPaymentEBM/corecom:EBMHeader/corecom:MessageProcessingInstruction/corecom:EnvironmentCode != 'CAVS' and xref:lookupXRef('oramds:/apps/AIAMetaData/xref/CUSTOMERPARTY_BILLPROFILEID.xref','COMMON',$in.CreateReceivedPaymentEBM/receivedpaymentebo:CreateReceivedPaymentEBM/receivedpaymentebo:DataArea/receivedpaymentebo:CreateReceivedPayment/corecom:PayFromPartyReference/corecom:BillingProfileReference/corecom:BillingProfileIdentification/corecom:BusinessComponentID, 'BRM_01',false())!=''
Example F-4 Replacement Filter Expression Example
$in.CreateReceivedPaymentEBM/receivedpaymentebo:CreateReceivedPaymentEBM/corecom:EBMHeader/corecom:MessageProcessingInstruction/corecom:EnvironmentCode != 'CAVS' and xref:lookupXRef('oramds:/apps/AIAMetaData/xref/CUSTOMERPARTY_BILLPROFILEID.xref','COMMON',$in.CreateReceivedPaymentEBM/receivedpaymentebo:CreateReceivedPaymentEBM/receivedpaymentebo:DataArea/receivedpaymentebo:CreateReceivedPayment/corecom:PayFromPartyReference/corecom:BillingProfileReference/corecom:BillingProfileIdentification/corecom:BusinessComponentID, 'BRM_02',false())!=''
If there is an assign activity in the original routing rule for request or reply, you must add the assign to all of the multi-BRM routing rules.
Go to the Assign Values pop-up and click the Add (+) button. The Assign Value page displays, as shown in Figure F-44.
Complete the following steps for both the From and To fields.
Select expression from the Type dropdown.
Click the Expression Builder icon to display the Expression Builder page.
Go to Variables and expand either in or out. Select the immediate part after in or out, as shown in Figure F-45.
Click OK to save your changes and return to the Assign Value page. Click OK.
Save the files and deploy the Composite.
In this case the change is related to combining multiple system instances into one.
If, for example, you start with two logical Oracle BRM instances and then later you decide to consolidate to a single instance. The only changes that must be done are in the AIAConfigurationProperties.xml.
In the AIAConfigurationProperties.xml file, change the End Point configuration URI to the same JNDI name.
For example, to point both these Oracle BRM instances to go to the BRM_01 instance, just change the highlighted information:
Change this:
<Property name="Routing.BRMCUSTService.BRM_01.EndpointURI">eis/BRM</Property> <Property name="Routing.BRMCUSTService.BRM_02.EndpointURI">eis/BRM2</Property>
To this:
<Property name="Routing.BRMCUSTService.BRM_01.EndpointURI">eis/BRM</Property> <Property name="Routing.BRMCUSTService.BRM_02.EndpointURI">eis/BRM</Property>
|
 Copyright © 2001, 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
