Skip Headers
Oracle® Application Integration Architecture Installation and Upgrade Guide for Pre-Built Integrations
Release 11.5
E40086-02
Go to Documentation Home
Home		 Go to Book List
Book List		 Go to Table of Contents
Contents		 Go to Feedback page
Contact Us
Go to previous page
Previous		 Go to next page
Next
PDF · Mobi · ePub

7 Configuring and Deploying the Comms Order to Cash: SBL CRM and BRM Pre-Built Integration

This chapter discusses how to configure and deploy the Oracle Communications Order to Cash Integration Pack for Siebel Customer Relationship Management and Oracle Communications Billing and Revenue Management (Comms Order to Cash: SBL CRM and BRM Pre-Built Integration).

This option assumes integration with a Central Order Management system, other than Oracle OSM. On deployment, this option deploys Test Orchestration Process (TOP) to take order fulfillment requests from Siebel and hand them off to Oracle BRM. However, this process is for simple sanity testing of the order flow between Siebel CRM and Oracle BRM. You must replace this process with your Order Management system following the steps detailed in Section 7.7, "Replacing Test Order Orchestration with your Order Management System".

This chapter includes the following sections:

7.1 Deployment Configuration Wizard

The DCW screens prompt you to enter the data required for successful configuration of the Comms Order to Cash: SBL CRM and BRM Pre-Built Integration. Enter the details of the Comms Order to Cash: SBL CRM and BRM Pre-Built Integration screens below, take a printout and keep it ready when you run the DCW. This action enables faster and error free configuration.

7.1.1 Integration Server Details Screen

All artifacts associated with the integration infrastructure components are deployed to the integration server. This screen contains the following fields:

Table 7-1 Integration Server Details Screen Fields

Field Description

Admin Host Name

This is where the admin server resides. This can be a remote server or the same computer where the AIA Pre-Built Integrations Installer is launched. Example: server1.company.com.

The Admin Host Name is _________________________________

Admin Port

This is the port number on which Weblogic Admin server is started. To find this value contact WebLogic administrator. Example: 7001.

The Admin Port is _____________________________________

Domain Name

This is WebLogic server domain corresponding to the Admin Server. Example: domain1

The Domain Name is _____________________________________

Admin User

This value is the WebLogic admin user name. To find this value contact your WebLogic administrator.

The Admin User is __________________________________

Admin Password

This value is the WebLogic admin password. To find this value contact your WebLogic administrator.

The Admin Password is _____________________________________

Managed Server

After you enter the Admin Host name, Admin Port, Domain Name, Admin user name and Admin Password, this field gets populated with managed servers for the domain. Select the manager server from the list. If you are deploying the integration to a SOA cluster, you should select the cluster name in this field.

The Managed Server is _______________________________

Managed Port

This field gets updated automatically after you select the managed server. If you have configured a SOA Cluster the SOA Cluster port appears in the list.

7.1.2 Siebel CRM Server Details Screen

Use this screen to enter details related to your Siebel CRM server instance. The screen contains the following fields:

Table 7-2 Siebel CRM Server Details Screen Fields

Field Description

Siebel Host name

This is a computer name of the Siebel host. For example: example1.corp.siebel.com. To find the value, contact your administrator.

Siebel Host name is _____________________________

Siebel HTTP Port

This value is the Siebel application port. For example: 80. To find the value, contact your administrator.

Siebel HTTP Port is ________________________________

InternetProtocol

This value is the Siebel host internet protocol. For example, http://. To find the value, contact your administrator.

InternetProtocol is _______________________

Note: Our internal environments are always on http://. The default value is https// and must be changed for Siebel web services and Session Pool Manager services to work.

Siebel Enterprise Server Name

This value is the Siebel enterprise server name. For example, siebel. To find the value, contact your administrator.

Siebel Enterprise Server Name is _________________________

Note: This value must be in lowercase (siebel) for the Update Account flow to work.

Siebel EAI Application User

The Siebel application user is used for making EAI web service calls. For example: sadmin. To find the value, contact your administrator.

Siebel EAI Application User is ___________________________

Siebel EAI Application Password

This is the password for the EAI user. For example: sadmin. To find the value, contact your administrator.

Siebel EAI Application Password is ________________________

Siebel Version

Version of application, for example Siebel 8.1.1 SIA. To find the value, contact your administrator. Kindly ensure that the value is only 10 character long.

Siebel Version is __________________________

Siebel Language

This is the language used by the Siebel application. For example, enu. To find the value, contact your administrator.

Siebel Language is ________________________

7.1.3 Siebel CRM Database Details Screen

Use this screen to enter details related to your Siebel CRM database instance. The screen contains the following fields:

Table 7-3 Siebel CRM Database Details Screen Fields

Field Description

Siebel Database Host

This value is typically the computer name. For example: server1.oracle.com. To find the value, contact your database administrator.

Siebel Database Host is _________________________________

Siebel Database Port

This is the Siebel database port. For example: 1521. To find the value, contact your database administrator.

Siebel Database Port is _________________________________

Siebel Database SID

This is the Siebel database system ID. For example: qa7a. To find the value, contact your database administrator.

Siebel Database SID is ________________________________

Siebel Database Username

Specifies a database user that has access to loading the EIM tables Siebel. To find this value, contact the database administrator. Example: ora12345

Siebel Database Username is ______________________

Siebel Database Password

This is the Siebel Database Password. For example: ora07103. To find the value, contact your database administrator.

Siebel Database Password is _____________________

7.1.4 Oracle Communications BRM Screen

Use this screen to enter details related to your Oracle Communications BRM instance. The screen contains the following fields:

Table 7-4 Oracle Communications BRM Details Screen

Field Description

Primary CM Host Name

This is the host name of the primary Connection Manager (CM) of the BRM server. For example: example1.portal.com To find this value, contact your Oracle AQ system administrator.

Primary CM Host Name is ______________________________

Primary CM Port Number

This is the port number of primary Connection Manager (CM) of the BRM server. For example: 12600. To find this value contact your Oracle AQ database administrator System Administrator

Primary CM Port Number is ______________________________

Database Host

This is the database host name of the Oracle AQ for which the BRM DM_AQ is configured. For example: example2.portal.com. To find this value, contact your Oracle AQ database administrator

Database Host is _______________________

Database Port

This is the database port number of the Oracle AQ. For example: 1521. To find this value, contact your Oracle AQ database administrator.

Database Port is _________________________

Oracle AQ Database SID

This is the database instance of the Oracle AQ. For example: orcl. To find this value, contact your Oracle AQ database administrator.

Oracle AQ Database SID is _______________________________

Oracle AQ Username

This is the database user name of the Oracle AQ. For example, PIN7820. To find this value, contact your Oracle AQ database administrator.

Oracle AQ Username is _________________________

Note: This value must be in uppercase (PIN7820) for the OOTB PLM flow to work.

Oracle AQ Password

This is the database password of the Oracle AQ. To find this value, contact your Oracle AQ database administrator.

Oracle AQ Password is ___________________________

AQ Queue Name

This is the queue name configured for the BRM DM_AQ. For example: AqportalUser. To find this value, contact your Oracle AQ database administrator.

AQ Queue Name is _________________________________

7.1.5 Session Pool Manager Details Screen

The Session Pool Manager (SPM) details are optional and required only when your Siebel server is outside of the firewall. If all your servers are within the network, leave these fields blank.

In the java.net application programming interface (API) used by SPM, proxies are supported through two system properties: http.proxyHost and http.proxyPort. They must be set to the proxy server and port respectively. This value is only set when ProxySettings_Enabled is set to TRUE.

Table 7-5 Session Pool Manager Details Screen Fields

Field Description

Proxy host url

This determines the server to be set in the system properties for http.proxyHost property.

Proxy host url is ___________________________

Proxy port

This determines the port to be set in the system properties for the http.proxyPort property.

Proxy port is ______________________________

Caution:

These fields are optional so leave the values blank. These values are required only if the Siebel server is outside of the firewall.

7.2 Performing Predeployment Configurations

This section discusses predeployment configurations for the Comms Order to Cash: SBL CRM and BRM Pre-Built Integration.

7.2.1 Deploying BRM JCA Adapter

  1. Based on your process integration version, obtain the BRM JCA adapter from the BRM administrator.

  2. Deploy the JCA adapter by following the steps listed in section "Deploy resource adapters" of the Oracle Fusion Middleware Oracle WebLogic Server Administration Console Online Help 11g Release 1 (10.3.5).

  3. After deploying the JCA adapter, perform the following steps:

    • Click Outbound Connection Pools subtab and expand the link ”oracle.tip.adapter.api.OracleConnectionFactory” in the table.

    • Click Outbound Connection Pool instance and configure the properties that suits your process integration environment.

7.2.2 Configuring the Timeout Values

This section describes how to modify the JTA Transaction Value and the SyncMaxWaitTime values.

To modify JTA Transaction Value:

  1. Log in to the WebLogic Server console.

  2. Navigate to Services, JTA.

  3. Change the value of the property Timeout Seconds to 3600.

  4. Click Save and activate the changes.

To modify SyncMaxWaitTime values:

  1. Log in to the Oracle Enterprise Manager Fusion Middleware Control.

  2. Expand the SOA folder and right-click soa-infra.

  3. Select SOA Administration, BPEL Properties.

  4. Click the More BPEL Configuration Properties link.

  5. Change the value of SyncMaxWaitTime to 120.

  6. Click Apply.

Note:

These TimeOut values must be adjusted appropriately based on the environment configurations for each customer.

7.3 Configuring and Deploying the Comms Order to Cash: SBL CRM and BRM Pre-Built Integration

This section discusses the integration configuration and deployment process. There are two steps:

  1. Configure your integration using the DCW.

  2. Deploy the integration to the Fusion Middleware server.

7.3.1 Configuring the Comms Order to Cash: SBL CRM and BRM Pre-Built Integration

The screens that appear prompt you to enter the data that is required for successful configuration of the Comms Order to Cash: SBL CRM and BRM Pre-Built Integration. Keep the completed worksheets of the Comms Order to Cash: SBL CRM and BRM Pre-Built Integration screens ready before you launch the DCW.

To configure the Comms Order to Cash: SBL CRM and BRM Pre-Built Integration:

Note:

If you are harvesting content to Oracle Enterprise Repository (OER), perform the first three steps. Else start from step 4.

  1. Navigate to ../Middleware/user_projects/domains/<domain_name>/bin and open setDomainEnv.sh for Linux based systems and setDomainEnv.bat for Microsoft Windows.

  2. Replace WLS_JDBC_REMOTE_ENABLED="-Dweblogic.jdbc.remoteEnabled=false" with WLS_JDBC_REMOTE_ENABLED="-Dweblogic.jdbc.remoteEnabled=true".

  3. Restart the server.

  4. Navigate to <AIA_Instance>/bin and run the command source aiaenv.sh for Linux based systems and aiaenv.bat for Microsoft Windows to configure installation environment.

  5. Navigate to <AIA_HOME>/bin and run the command ./aiaconfig.sh for Linux based systems and aiaconfig.bat for Microsoft Windows.

    This launches the AIA DCW.

  6. Click Next.

  7. Expand Communications Pre-built Integrations and select Comms Order to Cash: Siebel CRM and BRM.

  8. Click Next.

7.3.1.1 Specify Integration Server Details

To specify integration server details:

  1. Enter information related to your integration server in the Integration Server Details screen.

  2. Click Next.

7.3.1.2 Specify Siebel CRM Server Details

To specify Siebel CRM server details:

  1. Enter information about your Siebel CRM application in the Application Details - Siebel CRM screen.

  2. Click Next.

7.3.1.3 Specify Siebel CRM Database Details

To specify Siebel CRM database details:

  1. Enter information about your Siebel CRM database in the Siebel CRM Database Details screen.

  2. Click Next.

7.3.1.4 Specify Oracle Communications BRM Details

To specify Oracle Communications BRM details:

  1. Enter Oracle Communications BRM information in the Oracle Communications BRM screen.

  2. Click Next.

7.3.1.5 Complete Configuration

To complete configuration:

  1. Review the configuration information on the Configuration Summary screen.

    Note:

    If you want to make changes to the configuration, use the navigation pane on the left and select the screen you want to edit.

    You can create a response file based on the input provided in the DCW and use it in future when you want to deploy the integration. You can configure using the steps described in Section 7.3.2, "Configuring using the Response File". Click Save Response File and save the response file with the name and location of your choice.

  2. Click Configure to accept this configuration and begin the installation.

    The system displays progress of configuration in the Configuration Progress screen.

    The system displays any warnings or errors as necessary. You can review the configuration log for additional details. The configuration log location is displayed in Configuration Progress screen.

  3. When configuration process finishes without errors, the AIA DCW displays the Configuration Complete screen.

  4. Click Finish to close the DCW.

7.3.2 Configuring using the Response File

To configure using the response file:

  1. Open the response file.

    When you create a response file through OUI, passwords get stored as <SECURE>.

  2. Replace the password fields with actual passwords in the response file.

  3. Navigate to <AIA_Instance>/bin and run the command source aiaenv.sh for Linux based systems and aiaenv.bat for Microsoft Windows to configure the environment.

  4. Navigate to <AIA_HOME>/bin and run the command ./aiaconfig.sh <Response File Location and Name> for Linux based systems and aiaconfig.bat <Response File Location and Name> for Microsoft Windows.

7.3.3 Deploying the Comms Order to Cash: SBL CRM and BRM Pre-Built Integration

To deploy the integration to Fusion Middleware server:

  1. Navigate to <AIA_Instance>/bin and run the command source aiaenv.sh for Linux based systems and aiaenv.bat for Microsoft Windows to configure the environment.

  2. Run the command for your platform.

    Note:

    In Windows 2008, 2008 R2 and Vista, run the command prompt as an administrator (elevated mode). If the command prompt is invoked in normal mode, the integrations are not displayed.

    Table 7-6 Deployment Commands for the Comms Order to Cash: SBL CRM and BRM Pre-Built Integration

    Platform Deployment Command

    Linux x86

    Solaris SPARC (64-bit)

    IBM AIX Based Systems (64-bit).

    HP-UX 11i (64 bit)

    		 
    $AIA_HOME/pips/Communications/O2B/DeploymentPlans/deployO2B.sh

    Microsoft Windows (32-bit)

    		 
    %AIA_HOME%\pips\Communications\O2B\DeploymentPlans\deployO2B.bat

  3. Review the log file in the location specified in the command or at the default location <AIA_Instance>/logs/O2BDP_Deployments_YYYY-MM-DD_HH-MI-SS.log to verify successful deployment of the integration.

Oracle AIA ships a few artifacts in AIA Lifecycle Workbench which can be used in your integrations. These native artifacts created using FMW technologies such as BPEL, Mediator are natively supported by AIA Foundation Pack tools such as Project Lifecycle Workbench, Harvester, Deployment Generator, and AIA Installer Driver (AID). These artifacts include SOA artifact types such as composites, DataSources, DVM, xRef, and so on. These can be modified or new natively supported artifacts can be added using AIA Lifecycle Workbench and a BOM.xml file can be generated.

Integrations, most often, also require deployment of artifact types that are beyond what is supported by the Project Lifecycle Workbench and AIA Harvester. For instance, you may want to deploy artifacts such as Java applications, Shell Scripts, ANT based build scripts which constitute part of integration landscape in addition to the artifacts that are delivered by AIA. AIA also supports deployment of these supplementary artifacts. However, you must modify and add new non native artifacts outside AIA Lifecycle Workbench.

For more information on deploying artifacts, see Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack, "Generating Deployment Plans and Deploying Artifacts".

7.4 Performing Postdeployment Configurations

This section discusses post deployment configuration for Comms Order to Cash: SBL CRM and BRM Pre-Built Integration. This section includes:

7.4.1 Suppressing Auto-Retry and Preventing Multiple Error Notifications and Trouble Tickets

To suppress auto-retry and prevent multiple error notifications and trouble tickets:

  1. Set the GlobalTxMaxRetry property for outbound adapters:

    1. Log in to the Oracle Enterprise Manager Fusion Middleware Control.

    2. Expand the SOA folder, right-click soa_infra.

    3. Select SOA Administration, Common Properties.

    4. Click More SOA Infra Advanced Configuration Properties.

    5. Search for the GlobalTxMaxRetry property and set the value as 0 (zero).

  2. Set the GlobalInboundJcaRetryCount property for inbound adapters:

    1. Log in to the Oracle Enterprise Manager Fusion Middleware Control.

    2. Expand the SOA folder, right-click soa_infra.

    3. Select Administration, System Mbean Browser.

    4. Search for oracle.as.soainfra.config, expand <Server>, expand AdapterConfig.

    5. Select Adapter.

    6. Search for the GlobalInboundJcaRetryCount property and set the value as 0 (zero).

  3. Change Audit Level from Development to Production for soa infrastructure:

    1. Log in to the Oracle Enterprise Manager Fusion Middleware Control.

    2. Expand the SOA folder, right-click soa_infra.

    3. Select SOA Administration, Common Properties.

    4. Choose Production from the Audit Level list.

    5. Click Apply.

  4. Stop and Start the SOA and Admin Server so that your changes can take effect.

7.4.2 Supporting Message Priority

As part of supporting message priority, follow the below steps to configure the queues (AIA_CRTBO_OUT_JMSQ, AIA_CRTCUST_OUT_JMS) so that the message is prioritized based on JMSPriority.

  1. Creating Destination Sort Key based on JMSPriority:

    1. Log in to Oracle Weblogic Administration Console

    2. Navigate to Services, Messaging, JMS Modules.

    3. Click AIAJMSModule.

    4. Click New and select Destination Sort Key option.

    5. Give a name AIA_SALESORDERJMSPRIORITY_KEY, click OK. The key is created.

    6. Click AIA_SALESORDERJMSPRIORITY_KEY link and choose JMSPriority from the Sort Key drop down list.

    7. Select Key Type as Int.

    8. Select Direction as Descending.

    9. Click Save.

  2. Attaching Destination Sort Key to JMS Queues:

    1. Click AIAJMSModule.

    2. Click AIA_CRTBO_OUT_JMSQ.

    3. In The Destination Keys section, newly created Key is displayed. Select and choose the key.

    4. Click Save.

  3. Repeat steps 2a to 2d for queue AIA_CRTCUST_OUT_JMSQ.

7.4.3 Updating Internal ID for the BRM Instance BRM_01

To update the internal ID for the BRM instance BRM_01 in the AIA Application Registry in the AIA application perform the following steps:

  1. Find the BRM instance ID that is specified in BRM Payload Configuration file:

    1. Go to the file system where your BRM portal is installed.

    2. Navigate to folder ../portal/7.4/sys/eai_js.

    3. Find the payload configuration file payloadconfig_crm_sync.xml.

    4. Open the file. The instance Id is specified as shown in Example 7-1.

    Example 7-1 Instance ID Specified in the BRM Payload Configuration File

    <ProductInfoChange Source="EVENT" Tag="ProductInfoChange"
                            StartEvent="/event/notification/price/products/modify">
          <Attribute Tag="InstanceId" Value="Portal"/>
          <Attribute Tag="xmlns" Value="http://www.portal.com/schemas/CRMSync"/>
          <Attribute Tag="xmlns:xsi" Value="http://www.w3.org/2001/XMLSchema-instance"/>
          <Attribute Tag="xsi:schemaLocation" Value="http://www.portal.com/schemas/CRMSync/ProductInfoChange.xsd"/>
          <Field PinFld="PIN_FLD_ACCOUNT_OBJ" Tag="AccountObj"/>
          <SubElement Name="ProductInfo" OnEvent="/event/notification/price/products/modify" />
</ProductInfoChange>

    If it is Portal, this value appears as brmproductabo:InstanceId in the Product Event message from BRM. See Example 7-2.

    Example 7-2 BRM Instance ID Specified in the Message Payload

    <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="Portal">

  2. Update the Internal ID column to the Instance ID from BRM to the value above. For example: Portal.

  3. In AIA Application, go to AIA Application Registry, Setup, System and find the entry for System Code "BRM_01".

  4. Change that value to the InstanceId from the BRM Payload Configuration file. For example: Portal.

7.4.4 Setting up the AIA FMW Server

Note:

This step is required if cluster is the deployment topology.

Perform the following steps to enable tunneling:

  1. Configure http proxy host

    1. Modify mod_wl_ohs.conf

      For example, $MW_HOME/Oracle_WT1/instances/instance1/config/OHS/ohs1/mod_wl_ohs.conf

    2. Add the following location:

      <Location / bea_wls_internal >

      SetHandler weblogic-handler

      WebLogicCluster adc1140309.example.com:8001,adc2101063.example.com:8011

      WLLogFile /tmp/web_log.log

      </Location>

    3. Restart using ./opmnctl stopall, ./opmnctl startall

  2. Configure WebLogic Server

    1. Log in to WebLogic Server console.

    2. Click Servers link and each manager server.

    3. Click Protocols, HTTP, Enable Tunneling.

    4. Save the configuration.

    5. Restart Admin and managed servers.

7.5 Verifying Deployment

To verify the Comms Order to Cash: SBL CRM and BRM Pre-Built Integration deployment:

  1. Open the log files from the following location and look for warnings and error messages:

    • For Linux x86, Solaris SPARC (64-bit), HP-UX 11i (64 bit) and IBM AIX Based Systems (64-bit): Review the install log located at <AIA_HOME>/aia_instances/<instance name>/logs to verify whether the integration is successfully installed.

  2. Confirm that the Comms Order to Cash: SBL CRM and BRM Pre-Built Integration components were successfully installed.

    1. Navigate to the Oracle Enterprise Manager Fusion Middleware Control: (http://<server name>:<port number>/em/).

    2. Log in with the server admin user name. For access details, contact the system administrator.

    3. Expand Farm_soa_domain, SOA, soa-infra, Default and look for the following items:

    • AIACOMOrderFalloutNotificationJMSConsumer

    • AIAOrderFalloutJMSBridgeService

    • BillingResponseConsumer

    • Comms2CoreCustomerPartybridge

    • CommsProcessBillingAccountListEBF

    • CommsProcessFulfillmentOrderBillingAccountListEBF

    • CommunicationsCustomerPartyEBSV2

    • CommunicationsCustomerPartyEBSV2Requencer

    • CommunicationsCustomerPartyResponseEBSV2

    • Core2CommsCustomerPartyBridge

    • CreateTroubleTicketAIACommsReqImpl

    • CreateTroubleTicketSiebelCommsProvABCSImpl

    • CustomerPartyEBSV2

    • CustomerResponseConsumer

    • OrderOrchestrationConsumer

    • ProcessFOBillingAccountListRespOSMCFSCommsJMSProducer

    • ProcessFufillmentOrderBillingAccountListOSMCFSCommsJMSConsumer

    • ProcessFulfillmentOrderBillingBRMCommsAddSubProcess

    • ProcessFulfillmentOrderBillingBRMCommsDeleteSubProcess

    • ProcessFulfillmentOrderBillingBRMCommsMoveAddSubProcess

    • ProcessFulfillmentOrderBillingBRMCommsProvABCSImpl

    • ProcessFulfillmentOrderBillingBRMCommsSuspendResumeSubProcess

    • ProcessFulfillmentOrderBillingBRMCommsUpdateSubProcess

    • ProcessFulfillmentOrderBillingOSMCFSCommsJMSConsumer

    • ProcessFulfillmentOrderBillingResponseOSMCFSCommsJMSProducer

    • ProcessInstalledProductSpecialRatingSetListBRMCommsProvABCSImpl

    • ProcessInstalledProductSpecialRatingSetListSiebelCommsJMSConsumer

    • ProcessInstalledProductSpecialRatingSetListSiebelCommsReqABCSImpl

    • ProcessSalesOrderFulfillmentOSMCFSCommsJMSProducer

    • ProcessSalesOrderFulfillmentSiebelCommsJMSConsumer

    • ProcessSalesOrderFulfillmentSiebelCommsReqABCSImpl

    • ProductOptimizedSyncPriceListListSiebelCommsProvABCSImpl

    • QueryClassificationListSiebelCommsProvABCSImpl

    • QueryCustomerPartyListSiebelProvABCSImplV2

    • QuerySpecificationListSiebelCommsProvABCSImpl

    • QuerySpecificationValueSetListSiebelCommsProvABCSImpl

    • SyncAccountSiebelAggregatorAdapter

    • SyncAccountSiebelReqABCSImpl

    • SyncAcctSiebelAggrEventConsumer

    • SyncAddressSiebelAggregatorAdapter

    • SyncBPSiebelAggregatorAdapter

    • SyncContactSiebelAggregatorAdapter

    • SyncCustomerPartyListBRM_01CommsJMSConsumer

    • SyncCustomerPartyListBRMCommsJMSProducer

    • SyncCustomerPartyListBRMCommsProvABCSImpl

    • SyncCustomerSiebelEventAggregator

    • SyncDiscountBRMCommsReqABCSImpl

    • SyncDiscountInfoChangeBRMAQ

    • SyncItemCompositionListSiebelCommsProvABCSImpl

    • SyncProductBRMCommsReqABCSImpl

    • SyncProductInfoChangeBRMAQ

    • TestOrderOrchestrationEBF

    • TransformAppContextSiebelService

    • UpdateSalesOrderOSMCFSCommsJMSConsumer

    • UpdateSalesOrderSiebelCommsProvABCSImpl

    • UpdateTroubleTicketSiebelCommsProvABCSImpl

7.5.1 Validating Security Policies

All SOA composites are protected by Global Policies provided by Foundation Pack as defined in the Security section of the Developer Guide. Additionally individual services for this integration have locally attached security policies.

To validate locally attached security policies:

  1. Log in to Oracle Enterprise Manager Fusion Middleware Control

  2. Expand WebLogic Domain.

  3. Select soa_domain.

  4. Right-click soa_domain.

  5. Select Web Services, Policies.

  6. Verify Service Policy attachment.

    1. Find no_authentication_service_policy in the list of policies.

    2. Click the number in Attachment Count column.

      This opens Usage Analysis screen.

    3. Change the Subject Type list box to SOA Service.

    4. Validate that all the composites are listed with local attachment to this service policy.

  7. Verify Client Policy attachment

    1. Navigate back to Web Services Policies screen.

    2. Navigate to Applies To LOV, select Service Clients and hit enter. Find no_authentication_client_policy.

    3. Click the number in Attachment Count column.

      This opens Usage Analysis screen.

    4. Change the Subject Type list box to SOA Reference.

    5. Validate that all the composites are listed with local attachment to this client policy and attached to the correct references.

      Table 7-7 No Authentication Service Policy Attachments for Comms Order to Cash: SBL and BRM

      Composite Service Policy

      SyncCustomerSiebelEventAggregator

      oracle/no_authentication_service_policy

      Table 7-8 No Authentication Client Policy Attachments for Comms Order to Cash: SBL and BRM

      Composite Service Policy

      SyncAccountSiebelReqABCSImpl

      oracle/no_authentication_client_policy

      QuerySpecificationListSiebelCommsProvABCSImpl

      oracle/no_authentication_client_policy

      ProductOptimizedSyncPriceListListSiebelCommsProvABCSImpl

      oracle/no_authentication_client_policy

      QuerySpecificationValueSetListSiebelCommsProvABCSImpl

      oracle/no_authentication_client_policy

      UpdateTroubleTicketSiebelCommsProvABCSImpl

      oracle/no_authentication_client_policy

      SyncItemCompositionListSiebelCommsProvABCSImpl

      oracle/no_authentication_client_policy

      UpdateSalesOrderSiebelCommsProvABCSImpl

      oracle/no_authentication_client_policy

      CreateTroubleTicketSiebelCommsProvABCSImpl

      oracle/no_authentication_client_policy

      QueryCustomerPartyListSiebelProvABCSImplV2

      oracle/no_authentication_client_policy

      QueryClassificationListSiebelCommsProvABCSImpl

      oracle/no_authentication_client_policy

For integration implementation, see 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.

Also see Oracle Application Integration Architecture Siebel CRM Integration Pack for Oracle Communications Billing and Revenue Management: Agent Assisted Billing Care Implementation Guide.

7.6 Undeploying the Comms Order to Cash: SBL CRM and BRM Pre-Built Integration

To undeploy the integration from Fusion Middleware Server:

  1. Navigate to <AIA_Instance>/bin and run the command source aiaenv.sh for Linux based systems and aiaenv.bat for Microsoft Windows to configure the environment.

  2. Run the command for your platform.

    Table 7-9 Undeployment Command for the Comms Order to Cash: SBL CRM and BRM Pre-Built Integration

    Platform Undeployment Command

    Linux x86

    Solaris SPARC (64-bit)

    IBM AIX Based Systems (64-bit).

    HP-UX 11i (64 bit)

    		 
    $AIA_HOME/pips/Communications/O2B/DeploymentPlans/undeployO2B.sh

    Microsoft Windows (32-bit)

    		 
    %AIA_HOME%\pips\Communications\O2B\DeploymentPlans\undeployO2B.bat

  3. Restart the SOA server.

  4. Uninstall the integration following the instructions in the Chapter 37, "Uninstalling Oracle AIA"

7.7 Replacing Test Order Orchestration with your Order Management System

After doing a simple flow test of order flow using TOP process, complete the following steps to replace TOP with your own Order Management System.

This step is mandatory before going into production. TOP is not a production quality code and not a supported product feature. So it must be replaced with your Order Management system after simple sanity testing of order flow between Siebel CRM and Oracle BRM.

  1. Navigate to the Oracle Enterprise Manager Fusion Middleware Control: (http://<server name>:<port number>/em/) using admin access and undeploy the following composites:

    • BillingResponseConsumer

    • CustomerResponseConsumer

    • OrderOrchestrationConsumer

    • TestOrderOrchestrationEBF

  2. Configure your Order Management system to interact to AIA through the JMS queues listed in Table 7-10. You can find these queues in Weblogic by following these steps:

    1. Go to Oracle Weblogic Server Administration Console, Domain Structure.

    2. Select your soa domain.

    3. Go to Services, Messaging, JMS Modules, AIAJMSModule.

    4. Find these queues by matching the JNDI names of the queue type JMS resources.

Table 7-10 JMS Queues for AIA Interactions with Order Management System

JMS Queues Description

jms/aia/AIA_CRTFO_IN_JMSQ

Inbound queue to your Order Management system for picking up incoming Sales Order from Siebel. The order message is of type ProcessSalesOrderFulfillmentEBM, wrapped into the SOAP envelope in the following way.

<tns:Envelope xmlns:tns="http://schemas.xmlsoap.org/soap/envelope/"><tns:Body><crtfo:CreateOrder xmlns:crtfo="http://xmlns.oracle.com/communications/ordermanagement"><sord:ProcessSalesOrderFulfillmentEBM xmlns:sord="http://xmlns.oracle.com/EnterpriseObjects/Core/Custom/EBO/SalesOrder/V2">...</sord:ProcessSalesOrderFulfillmentEBM> </crtfo:CreateOrder></tns:Body></tns:Envelope>

jms/aia/AIA_CRTCUST_OUT_JMSQ

Outbound queue from your Order Management system for creating customer in Oracle BRM. The message must confirm to ProcessFulfillmentOrderBillingAccountListEBM schema. Order Management must wait for response before doing further communication with Oracle BRM for the current order.

jms/aia/AIA_UPDCUST_IN_JMSQ

This is a response queue of jms/aia/AIA_CRTCUST_OUT_JMSQ. It contains success response message from AIA in ProcessFulfillmentOrderBillingAccountListResponseEBM schema.

jms/aia/AIA_CRTBO_OUT_JMSQ

Outbound queue from your Order Management system for creating billing order in Oracle BRM. The message must confirm to ProcessFulfillmentOrderBillingEBM schema. Order Management must wait for response before doing further communication with Oracle BRM for the current order message.

jms/aia/AIA_UPDBO_IN_JMSQ

This is a response queue of jms/aia/AIA_CRTBO_OUT_JMSQ. It contains success response message from AIA in ProcessFulfillmentOrderBillingResponseEBM schema.

jms/aia/AIA_UPDSO_OUT_JMSQ

Outbound queue from your Order Management system for updating Order information in Siebel CRM. The message must confirm to UpdateSalesOrderEBM schema. This is an asynchronous flow, so no response is sent back to Order Management.

Go to previous page
Previous		 Go to next page
Next
Go to Documentation Home
Home		 Go to Book List
Book List		 Go to Table of Contents
Contents		 Go to Feedback page
Contact Us