4 Performing Post-Deployment Tasks

This chapter describes the tasks you perform after deploying the Digital Business Experience solution.

Integrating Launch and CXIF

This section describes the tasks you perform to integrate Launch and CX Industries Framework (CXIF) applications with the Digital Business Experience solution.

See Integrate Launch with Digital Business Experience in Oracle Communications Launch Cloud Service Implementation Guide for information about Launch integration with Digital Business Experience solution and other applications.

Prerequisites

Before integrating Launch and CXIF, you must:

  • Request a Launch environment. Contact Oracle Support for assistance.

  • Request a CXIF environment. Contact Oracle Support for assistance.

  • Request Launch and CXIF integration. Contact Oracle Support for assistance.

Integrating Launch and CXIF with Siebel CRM and PDC

After the prerequisites are completed, perform the following:

  • Integrate Launch and CXIF with Siebel CRM. See Launch Cloud Service Siebel CRM Integration in Oracle Communications Launch Cloud Service Integration Guide for more information.
  • Integrate Launch and CXIF with Pricing Design Center (PDC) a part of the Oracle Communications Billing and Revenue Management (BRM) suite. See Launch Cloud Service PDC (BRM) Integration in Oracle Communications Launch Cloud Service Integration Guide for more information.

Integrating Siebel CRM on Containers with AIA Cloud Native

This section provides instructions for integrating Siebel CRM on Containers with Application Integration Architecture (AIA) cloud native.

To integrate Siebel CRM on Containers with AIA cloud native:
  1. Get the following JAR files:
    • From Siebel containers, get siebel.jar and SiebelJI_enu.jar.
    • From the Oracle WebLogic Server container, get wlthint3client.jar.
  2. Log in to Siebel eCommunication Web UI as SADMIN user and update the JAVA64 profile parameters to include the JAR files you copied in the previous step:
    /sfs/aiacn/jms:/sfs/aiacn/jms/Siebel.jar:/sfs/aiacn/jms/SiebelJI_enu.jar:/sfs/aiacn/jms/wlthint3client.jar:.

    Note:

    Ensure that the path /sfs/aiacn/jms is a persistent store so that the files are retained after the pod restarts.
  3. Relocate the JAR files:
    1. Connect to the Siebel SES pod.
    2. Create a folder with the same name as what is listed in step 2 (/sfs/aiacn/jms), where /sfs is a shared persistent folder, and then copy the 3 JAR files into the folder.
  4. In the same folder, create the jndi.properties file with the following contents:

    Note:

    • Ensure that the AIACN t3 channel URL and user name and password are set with the correct values.

    • In the below example, Siebel and AIA are in the same cluster and different namespace.

    java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory
java.naming.provider.url=t3://soa_cluster_service_name.soa_namespace.svc.cluster.local:soa_service_cluster_port
java.naming.security.principal=soa_console_username
java.naming.security.credentials=soa_console_password
  5. Copy the three JAR files into the Apache Tomcat /siebel/mde/applicationcontainer/lib folder.
  6. Restart Apache Tomcat server inside Siebel Enterprise Server (SES) pod.
  7. Configure Siebel Web Service in the Siebel database.
    1. Create the update_siebel_ws.sql SQL script with the following content:
      UPDATE S_WS_PORT SET PORT_ADDRESS='jms://jms/aia/AIA_SALESORDERJMSQUEUE@jms/aia/COMMS_SUBMITORDER_CONSUMER', PORT_TRANSPORT='JMS' WHERE NAME='SWISubmitOrderPort';
UPDATE S_WS_PORT SET PORT_ADDRESS='jms://jms/aia/AIA_SALESORDERJMSQUEUE@jms/aia/COMMS_SUBMITORDER_CONSUMER', PORT_TRANSPORT='JMS' WHERE NAME='SWISubmitOrder_o2cPort';
UPDATE S_WS_PORT SET PORT_ADDRESS='jms://jms/aia/AIA_SALESORDERJMSQUEUE@jms/aia/COMMS_SUBMITORDER_CONSUMER', PORT_TRANSPORT='JMS' WHERE NAME='SWISubmitQuote_o2cPort';
UPDATE S_WS_PORT SET PORT_ADDRESS='jms://jms/aia/AIA_SPECIALRATINGJMSQ@jms/aia/COMMS_SPECIALRATINGLIST_CONSUMER', PORT_TRANSPORT='JMS' WHERE NAME='SWISpecialRatingListPort';
UPDATE S_WS_PORT SET PORT_ADDRESS='jms://jms/aia/AIA_CMUREQADJIOJMSQUEUE@jms/aia/COMMS_ADJUSTMENT_CONSUMER', PORT_TRANSPORT='JMS' WHERE NAME='SWICreateAdjustmentPort';
UPDATE S_WS_PORT SET PORT_ADDRESS='http://aiacn_clusterService_name.aiacn_kubernetes_name:aiacn_clusterService_port/soa-infra/services/default/AccountBalanceSiebelCommsReqABCS/AccountBalanceSiebelCommsReqABCS_ep' WHERE NAME='_soap_AccountBalanceSiebelCommsReqABCS_AccountBalanceSiebelCommsReqABCS';
UPDATE S_WS_PORT SET PORT_ADDRESS='http://aiacn_clusterService_name.aiacn_kubernetes_name:aiacn_clusterService_port/soa-infra/services/default/AdjustmentSiebelCommsReqABCS/AdjustmentSiebelCommsReqABCS_ep' WHERE NAME='AdjustmentSiebelCommsReqABCSPort';
UPDATE S_WS_PORT SET PORT_ADDRESS='http://aiacn_clusterService_name.aiacn_kubernetes_name:aiacn_clusterService_port/soa-infra/services/default/InvoiceSiebelCommsReqABCS/InvoiceSiebelCommsReqABCS_ep' WHERE NAME='_soap_InvoiceSiebelCommsReqABCS_InvoiceSiebelCommsReqABCS';
UPDATE S_WS_PORT SET PORT_ADDRESS='http://aiacn_clusterService_name.aiacn_kubernetes_name:aiacn_clusterService_port/soa-infra/services/default/PaymentSiebelCommsReqABCS/PaymentSiebelCommsReqABCS_ep' WHERE NAME='PaymentSiebelCommsReqABCSPort';
UPDATE S_WS_PORT SET PORT_ADDRESS='http://aiacn_clusterService_name.aiacn_kubernetes_name:aiacn_clusterService_port/soa-infra/services/default/UnbilledUsageSiebelCommsReqABCS/UnbilledUsageSiebelCommsReqABCS_ep' WHERE NAME='_soap_UnbilledUsageSiebelCommsReqABCS_UnbilledUsageSiebelCommsReqABCS';
UPDATE S_WS_PORT SET PORT_ADDRESS='http://aiacn_clusterService_name.aiacn_kubernetes_name:aiacn_clusterService_port/soa-infra/services/default/SyncCustomerSiebelEventAggregator/Client' WHERE NAME='SyncCustomerSiebelEventAggregatorPort'; 
UPDATE S_WS_PORT SET PORT_ADDRESS='http://aiacn_clusterService_name.aiacn_kubernetes_name:aiacn_clusterService_port/soa-infra/services/default/UpdateCreditAlertSiebelCommsReqABCSImpl/UpdateCreditAlertSiebelCommsReqABCSImpl' WHERE NAME='UpdateCreditAlertSiebelCommsReqABCSImplServicePort';
SET ESCAPE ON; 
UPDATE S_WS_PORT SET PORT_ADDRESS='https://Siebel_hostname:Siebel_port/siebel/eai/enu/start.swe?SWEExtSource=SecureWebService\&SWEExtCmd=Execute\&WSSOAP=1' WHERE NAME='SWIOrderUpsert';
UPDATE S_WS_PORT SET PORT_ADDRESS='https://Siebel_hostname:Siebel_port/siebel/eai/enu/start.swe?SWEExtSource=SecureWebService\&SWEExtCmd=Execute\&WSSOAP=1' WHERE NAME='SWI Product Attribute Import';
UPDATE S_WS_PORT SET PORT_ADDRESS='https://Siebel_hostname:Siebel_port/siebel/eai/enu/start.swe?SWEExtSource=SecureWebService\&SWEExtCmd=Execute\&WSSOAP=1' WHERE NAME='SWI Product Class Import';
UPDATE S_WS_PORT SET PORT_ADDRESS='https://Siebel_hostname:Siebel_port/siebel/eai/enu/start.swe?SWEExtSource=SecureWebService\&SWEExtCmd=Execute\&WSSOAP=1' WHERE NAME='SWIProductImport';
UPDATE S_WS_PORT SET PORT_ADDRESS='https://Siebel_hostname:Siebel_port/siebel/eai/enu/start.swe?SWEExtSource=SecureWebService\&SWEExtCmd=Execute\&WSSOAP=1' WHERE NAME='SWIPromotionImport';
UPDATE S_WS_PORT SET PORT_ADDRESS='https://Siebel_hostname:Siebel_port/siebel/eai/enu/start.swe?SWEExtSource=SecureWebService\&SWEExtCmd=Execute\&WSSOAP=1' WHERE NAME='SWIUpsertQuote';
UPDATE S_WS_PORT SET PORT_ADDRESS='https://Siebel_hostname:Siebel_port/siebel/app/eai/enu?SWEExtSource=WebService\&SWEExtCmd=Execute\&WSSOAP=1' WHERE NAME='COMMSCancelOrderPort';
UPDATE S_WS_PORT SET PORT_ADDRESS='https://Siebel_hostname:Siebel_port/siebel/app/eai/enu?SWEExtSource=WebService\&SWEExtCmd=Execute\&WSSOAP=1' WHERE NAME='COMMSCustomServicesPort';
UPDATE S_WS_PORT SET PORT_ADDRESS='https://Siebel_hostname:Siebel_port/siebel/app/eai/enu?SWEExtSource=WebService\&SWEExtCmd=Execute\&WSSOAP=1' WHERE NAME='COMMSOrderUpsert';
UPDATE S_WS_PORT SET PORT_ADDRESS='https://Siebel_hostname:Siebel_port/siebel/app/eai/enu?SWEExtSource=WebService\&SWEExtCmd=Execute\&WSSOAP=1' WHERE NAME='COMMSSubmitBillingOrder';
commit;
quit;
    2. Connect to the Siebel database and run the SQL script with the database user name and the corresponding password.
  8. Configure the Siebel repository in the Siebel database:
    1. Create the update_siebel_repository.sql SQL script with the following contents:
      UPDATE S_SYS_PREF SET VAL='TRUE' WHERE SYS_PREF_CD='Enable AIA Comms';
UPDATE S_SYS_PREF SET VAL='TRUE' WHERE SYS_PREF_CD='Enable AIA MDM';
UPDATE S_SYS_PREF SET VAL='TRUE' WHERE SYS_PREF_CD='Enable AIA Testing';
UPDATE S_SYS_PREF SET VAL='FALSE' WHERE SYS_PREF_CD='Enable AIA Utility';
UPDATE S_SYS_PREF SET VAL='No' WHERE SYS_PREF_CD='Enable Promotion Group';
UPDATE S_SYS_PREF SET VAL='/siebel/mde/siebsrvr/temp/OrderBackup/' WHERE SYS_PREF_CD='AIA Order Backup Path';
UPDATE S_SYS_PREF SET VAL='Yes' WHERE SYS_PREF_CD='Enable Promotion Group';
UPDATE S_SYS_PREF SET VAL='Y' WHERE SYS_PREF_CD='Promotion Group Compatibility';
commit;
quit;
    2. Connect to the Siebel database and run the SQL script with the database user name and the corresponding password.
  9. Configure EAI File Transfer Folder:
    1. Connect to the SES pod of the Siebel CRM on Containers instance.
    2. Run the following two Siebel commands and set "EAIFileTransportFolders" with the created "OrderBackup" sub-folder's full path as follows:

      Note:

      Ensure that the /siebel/mde/siebsrvr/temp/OrderBackup folder is created in the Siebel SES container. If not, then create the folder and proceed with below commands. 
      [aiacn_pod-0:/siebel/mde]#srvrmgr /g cgw-aiacn-0.ses-aiacn.siebel-cn.svc.cluster.local:2320 /e aiacn /u username /p password 
      srvrmgr> change ent param EAIFileTransportFolders=/siebel/mde/siebsrvr/temp/OrderBackup
      srvrmgr> change ent param EAIFileTransportFolders=/siebel/mde/siebsrvr/temp/OrderBackup for server aiacn_pod-0
    3. Restart the SES service using the kubectl command:
      kubectl -n siebel_namespace, delete pod Siebel_Enterprise_Server_pod_name-0
    4. After the pod is recreated and you have verified that it is running, follow Step 5 and Step 6.
  10. (Optional) Import products into Siebel CRM on Containers by using the Siebel eCommunication application. Refer to Siebel CRM documentation for instructions.
  11. Import Siebel CRM on Containers SSL/TLS security certificates and configure AIA cloud native with the certificates. See Installing SSL Certificates in Oracle Application Integration Architecture Cloud Native Deployment Guide for more details.
    1. Validate that keystore custom identity and custom trust are created successfully. To do this, log in to the Enterprise Manager Console for AIA and navigate to the Keystore section.
    2. Validate that Siebel trust certificate is available in the custom trust keystore in the Keystore section.
    3. Log in to the Weblogic Console of AIA cloud native. For each managed server, in the Keystore section, ensure the following:
      • kss://system/custom_identity_keystorename is displayed for Custom Identity Store.
      • kss://system/custom_trust_keystorename is displayed for Custom Trust Store.
    4. Validate /u01/oracle/user_projects/domains/domain_name/bin/setDomainEnv.sh with custom trust:
      1. Connect to any managed server pod.
      2. Open the /u01/oracle/user_projects/domains/domain_name/bin/setDomainEnv.sh using the vi tool.
      3. Validate that -Djavax.net.ssl.trustStore=kss://system/custom_trust_keystorename -Djavax.net.ssl.trustStoreType=kss -Djavax.net.ssl.keyStorePassword=password -Djavax.net.ssl.trustStorePassword=password is configured in EXTRA_JAVA_PROPERTIES.
  12. Configure Siebel credentials in the Enterprise Console of AIA cloud native.
    1. Navigate to the Credentials section and edit participatingapplications.siebel.server.eai.password to specify the username and password.
    2. Repeat step a. for participatingapplications.siebel.server.db.password if you want to change the Siebel DB credentials.
    3. Restart the AIA cloud native services by using the domain-lifecycle scripts.
  13. Configure AIA cloud native MetaData with Siebel Connection details, Business Unit ID, and PRICELIST.
    1. Get the latest AIAConfigurationProperties.xml and PRICELIST.dvm files:
      1. In the Enterprise Manager Console for AIA, navigate to the MDS Configuration section and export the zip file.
      2. Copy the following files from the zip: soa/configuration/default/AIAConfigurationProperties.xml and apps/AIAMetaData/dvm/PRICELIST.dvm. For more information on MDS operations, refer to Managing the Metadata Repository in Administering Oracle Fusion Middleware.
    2. Update Siebel connection details:
      1. In the AIAConfigurationProperties.xml file, update all the values of the XML tag SEBL_01.EndpointURI with correct details if required.
    3. Update the Business Unit ID details:
      1. Log in to Siebel and get Siebel Business Unit ID by navigating to Organizations. Navigate to About Record, and copy the Row Number.
      2. In the AIAConfigurationProperties.xml file, update all the values of the XML tag Siebel.SEBL_01.BusinessUnit, with the copied Default Organization Row Number.
    4. Update Pricelist details:
      1. Pricelists:

        1. Log in to Siebel and create or confirm pricelists as required on Siebel. Copy the Row Number of the required pricelist. For more information, refer to Siebel Price List in the Application Services Interface Reference Guide.

        2. In the PRICELIST.dvm file, update or add the values for SEBL_01 column of row with the copied Row Number and with the other required values.

          For more information, refer to Working with the PRICELIST DVM in the Order to Cash Implementation Guide .

        3. Repeat steps 1 and 2 for each pricelist.
      2. Default Pricelist:

        1. In the AIAConfigurationProperties.xml file, update all the values of XML tag Siebel.SEBL_01.PriceList.ID with Row Number from Siebel for default pricelist.

          Note:

          Mention the default pricelist details in the AIAConfigurationProperties.xml file. In case of multi-pricelist configuration, do not mention the default pricelist section in the PRICELIST.dvm file.
    5. Update AIA MDS with the updated PRICELIST.dvm and the AIAConfigurationProperties.xml files. For more information about updating files in AIA MDS, refer to Updating Files in AIA MDS in the Application Integration Architecture Cloud Native Deployment Guide.
    6. Restart AIA cloud native using the domain-lifecycle scripts.
  14. Enable the eai_enu application configuration using the Siebel Management Console. Refer to the Siebel Management Console documentation for instructions.
  15. Update Maximum Number of Records in Siebel:
    1. Create and activate a workspace:
      1. Log in to Siebel Web Tools.
      2. Click the Workspaces icon in the top menu bar.

        Ensure the Main workspace is selected.

      3. Click Create.
      4. Enter the required Workspace Name and Comments.
      5. Click Save.
      6. Confirm that the new workspace is active.

        The workspace name appears in the top menu bar instead of Main.

      7. Click X.
    2. Update maximum number of records:
      1. Navigate to Integration Object and query CMU Request Billed Usage IO.
        If the integration object is hidden,
        • Click the pencil icon to view the hidden menus.
        • Select the integration object.
        • Click Save.
      2. Navigate to Integration Component Field, then select Integration Component Field User Props, and query Maximum*.
      3. Update the PREDEFAULT value present under Integration Component Field User Props to 30.
      4. Click Save.
    3. Submit and deliver the workspace:
      1. Navigate back to Workspaces.

        Ensure your workspace is selected.

      2. Click Version, enter the comments, and verify if the status is changed to Checkpointed.
      3. Click Submit and verify if the status is changed to Submitted for delivery.
      4. Click Deliver and verify if the status is changed to Delivered.
      5. After the workspace is delivered, the system switches to the Main workspace, and your changes will be visible in the Main workspace.
    4. Validation:
      1. Log out of Siebel Web Tools.
      2. Log in again.
      3. Verify that your changes are visible in the workspace.
    5. Restart Siebel to ensure your changes are visible.
  16. Update SWI Trouble Ticket Service in Business Service Access:
    1. Add the business service:
      1. Log in to Siebel application using your credentials.
      2. Navigate to Site Map, select Administration - Application, and then click Business Service Access.
      3. In the Business Service Access view, click the Add (+) button.
      4. In the new record, enter the business service name (for example, SWI Trouble Ticket Service).
      5. Click Save.
    2. Assign Responsibility:
      1. In the same view, locate the newly added business service (for example, SWI Trouble Ticket Service).
      2. Update the Responsibility details as required.
      3. Click Save.

    Note:

    After adding the business service and assigning the responsibilities, you must clear cache in Business Service and Responsibility applets.
  17. Enable Dynamic Pricing:
    1. Log in to Siebel application using your credentials.
    2. Navigate to Site Map, and then select Administration - Pricing.
    3. In the Price Lists view, click the Settings icon.
    4. From the menu, select Enable Dynamic Pricing.
    5. Click the Settings icon again, and then click Save.

Integrating BRM Cloud Native with AIA Cloud Native

This section provides instructions for integrating BRM cloud native with AIA cloud native.

To integrate BRM cloud native with AIA cloud native:

  1. Validate the BRM cloud native CM parameter by running the following command:

    Note:

    Ensure that the BRM CM service is configured with the dnsName of the cluster, so that the CM service can be connected using the dnsName in the cluster. 
    kubectl -n brmcn_namespace get deployment/cm -o yaml
    A sample output is as follows:
    - name: CM_DNS_NAME
  value: dns:<cm service>.<brm ns>.svc.cluster.local
  2. Deploy the BRM JCA Adapter. See Deploying the BRM JCA Adapter in Oracle Communications Application Integration Architecture Cloud Native Deployment Guide for more information.
  3. (Optional) Validate the connection between AIA cloud native and BRM cloud native by deploying the BRM JCA Adapter test client (Web application) and sending a test request with the test client Web UI. See Testing JCA Resource Adapter Configuration and BRM Connectivity in Oracle Communications BRM JCA Resource Adapter Guide for more information.
  4. Enable notification and Product Sync in BRM cloud native.
    1. Ensure that the fm_publish enable_publish parameter is set to 1 in the CM pin.conf. You can set this by using the helm chart or by editing the Kubernetes config manager entry of cm cm-pin-conf-config.
    2. For EAI (eai-java-server container in the cm pod), ensure that payload for Infranet.properties is set to payloadconfig_crm_sync.xml. This payload contains the required events (ProductInfoChange and DiscountInfo change) for generating the XML for EAI. Ensure that the DB is 0.0.0.0, which points to EAI. The DB entries mapping can be found in dm-oracle pin.conf. You can set this by using the helm chart or by editing the Kubernetes config manager entry of the EAI eai-java-server-infranet-properties-config and eai-java-server-payload.

      Note:

      Bounce the CM pod after the change to reflect the changes.

      Publisher DB=\"0.0.0.0

    3. In the dm-oracle-aq-event-map-config config file, uncomment ALL in aq_event_map.
    4. Ensure that notifications are enabled for the following: 
      /event/notification/price/products/modify
/event/notification/price/discounts/modify
/event/notification/price/sponsorships/modify
/event/customer/status
/event/notification/amt/AccountInfoChange
    5. Run helm command from the BRM Helm charts path to publish Prod Sync data.
      cd $BRM_CNTK/artifacts
$ helm upgrade --namespace <brm_namespace> brm-cn-apps helm-charts/ --values profiles/deploy-oci.yaml --values profiles/pdc-publish.yaml
    6. Restart the cm, dm-oracle, and dm-ifw-sync pods of the BRM cloud native instance.
  5. Enable Sequential Cycle Discounting Using Utility:
    1. Access the Pin Job Executor (PJE) pod from the dbe_monetization namespace.
    2. Navigate to the configuration directory cd /oms/sys/data/config/.
    3. Open the configuration file using the following command:
      vi bus_params_billing.xml
    4. Locate and enable the SequentialCycleDiscounting parameter as follows:
      <SequentialCycleDiscounting>enabled</SequentialCycleDiscounting>
    5. Save and close the file.
    6. Run the following command to load the updated XML into the BRM database:
      pin_bus_params -v bus_params_billing.xml
    7. Verify that the command completes without errors.
    8. Restart the CM pod to apply the changes.

Integrating OSM Cloud Native with AIA Cloud Native

This section provides instructions for integrating OSM cloud native with AIA cloud native.

To integrate OSM cloud native with AIA cloud native:
  1. Create a t3 channel in the AIA cloud native instance:
    • For a single cluster scenario, where in AIA cloud native, Siebel CRM cloud native, BRM cloud native, and OSM cloud native are deployed in the same cluster, create a t3 channel in the WebLogic Administration Console for AIA cloud native.
      1. Log in to AIA cloud native WebLogic Administration Console.
      2. Navigate to the Servers section in the Domain Structure pane and then select a managed server (for example, select soa_server1).
      3. In Protocols, go to the Channels tab, and create a new channel (for example, T3Channel).
      4. Specify the following:
        • Listen Address as soainfra-cluster-soa-cluster.namespace.svc.cluster.local.
        • External Listen Port as soa-cluster-service-name.namespace.svc.cluster.local
      5. Ensure that Tunneling Enabled is selected.
      6. For each managed server, repeat steps b. to e.
    • If AIA cloud native and OSM cloud native are deployed in different clusters, do the following:
      1. Connect to the AIA cloud native cluster and create an ingressroute that includes route rules for all common names and the respective ports. 
        apiVersion: traefik.containo.us/v1alpha1
kind: IngressRoute
metadata:
  name: aia-ingress
  namespace: namespace
spec:
  entryPoints:
  - web
  routes:
  - kind: Rule
    match: Host(`soa.domain_name.namespace.aia.org`)
    services:
    - name: soa_cluster_service_name
      port: soa_ms_port
      sticky:
        cookie:
          httpOnly: true
  - kind: Rule
    match: Host(`t3.domain_name.namespace.aia.org`)
    services:
    - name: soa_cluster_service_name  
      port: soa_cluster_service_port
      sticky:
        cookie:
          httpOnly: true
  - kind: Rule
    match: Host(`admin.domain_name.namespace.aia.org`)
    services:
    - name: soa_admin_server_service_name
      port: soa_admin_server_port
      sticky:
        cookie:
          httpOnly: true
      2. Apply the yaml file to create the ingressroute:
        kubectl apply -f aia-ingress.yaml
      3. Edit the AIA cloud native domain configuration to specify the following settings for integrating with the OSM cloud native instance:

        Note:

        If the previous node is cordoned, deleted, or repaved, update the values for hostAliases and change the IP addresses to new IP addresses of a working node. 
        spec:
.........
.........
  serverPod:
.........
.........
    hostAliases:
    - hostnames:
      - t3.instance.project.osm.org
      - instance.project.osm.org
      - admin.instance.project.osm.org
      ip: osm_node_IP_address
    - hostnames:
      - soa.soainfra.soa_namespace.aia.org
      - t3.domain_name.namespace.aia.org
      - admin.domain_name.namespace.aia.org
      ip: soa_node_IP_address
      4. Edit the OSM cloud native domain configuration to specify the same settings as described in step 1.b for integrating with the AIA cloud native instance.

        Note:

        Ensure that the AIA cloud native and OSM cloud native instance pods restart automatically after steps b and c. If they do not restart automatically, run the corresponding scripts to manually restart the AIA and OSM instances.
      5. Create a t3 channel in the WebLogic Admin Console for AIA cloud native, ensuring that the External Listen Address is set to the hostname defined earlier. In addition, ensure that HTTP Enabled for This Protocol is selected.
  2. Deploy the Order-to-Activate cartridge into the OSM cloud native instance. See Creating Order-to-Activate Credentials and Accounts and Deploying the Sample Cartridge for instructions.
  3. Set the AIA cloud native SAF t3 value which was created earlier, in the OSM project specification file as follows:
    • For single cluster, specify the following:
      safConnectionConfig:
  - name: O2A_SAFImportedDestinations
    t3Url: t3://soa_cluster_servicename.namespace.svc.cluster.local:soa_cluster_serviceport
    secretName: osm_project_instance__saf_credentials_aia_secret_name

      Note:

      osm_project_instance__saf_credentials_aia_secret_name is the secret you created while setting up and deploying OSM.
    • For multiple clusters, specify the following:
      safConnectionConfig:
  - name: O2A_SAFImportedDestinations
    t3Url: http://t3_hostname_in_ingressroute:t3_port_created
    secretName: osm_project_instance__saf_credentials_aia_secret_name
  4. Restart the OSM instance to deploy the O2A cartridge with the AIA cloud native configuration. See Restarting the Instance in Oracle Communications Order and Service Management Cloud Native Deployment Guide.
  5. Log in to the WebLogic Administration Console for OSM cloud native and verify that the SAF setting is configured with the expected t3 Url value.
  6. Log in to the OSM Task Web client and verify that the O2A cartridge is deployed.
  7. In WebLogic Admin Console for OSM cloud native, copy the t3 URL displayed for T3ClustChannel for single cluster or the value of T3Channel (HTTP) for multi-cluster channel.
  8. In the WebLogic Admin Console for AIA cloud native, navigate to the JMS Modules page, for the OSM and SOM AIAJMSModules, set the URL test fields with the copied t3 URLs.

    Note:

    You must set a username and password for the WebLogic Admin Console for AIA cloud native.
  9. Restart the AIA cloud native domain services by using the domain-lifecycle scripts.
  10. In the WebLogic Administration Console for the AIA domain, navigate to the Store and Forward Agents page. In the Remote Endpoints tab for OSM_SAFAgent, ensure that for each Remote Endpoint, the t3 URL is displayed for single-cluster environment.
  11. Log in to Oracle Enterprise Manager Fusion Middleware Control for AIA cloud native, and add the singleton property. See the AIA Installation Guide for instructions.
  12. Configure the AIA queues to support JMS Priority. See the AIA Installation Guide for instructions.
  13. Add the No Authentication security policy to the Product class service. See the AIA Installation Guide for instructions. Ensure that you select QueryProductClassAndAttributesSCECommsReqABCSImpl in the Service and References region.
  14. Ensure that the JAVA_OPTIONS parameter -Dweblogic.rjvm.allowUnknownHost=true is added into AIA cloud native domain setting.
  15. In Oracle Enterprise Manager Fusion Middleware Control, for SOA Infrastructure, set the Callback Server URL and Server URL common properties with the SOA infrastructure URL.

Integrating ODI with AIA Cloud Native

This section describes tasks to be performed to integrate Oracle Data Integrator (ODI) with Oracle Communications Application Integration Architecture (AIA) cloud native.

Prerequisites and Assumptions

Ensure the following:

  • The Master Repository and the Work Repository are created in ODI.
  • ODI is installed with the J2EE Enterprise Agenttemplate and has the encode.sh script in $ODI_HOME/bin directory.
  • The ODI agent is available and the agent's WSDL is reachable inside the AIA cloud native installation pods.
  • Collections is installed properly.. Within the admin pod, verify that the following are present in the DVM path /u01/shared/aia-comms/commsOracleHome/comms_home/source/soainfra/apps/AIAMetaData/dvm:
    • CURRENCY_CODE.dvm
    • COLLECTION_STATUS.dvm
    • COLLECTION_ACTIONNAME.dvm
    • COLLECTION_PRIORITY.dvm
    • COLLECTION_SUBSTATUS.dvm
  • Confirm the URL for composite definition for SyncCollectionHeaderInfoBRMCommsReqImpl composite is correct.

Perform the following tasks before integrating ODI with AIA:

  • Mount AIA PV on the machine where ODI is installed. Mount the PV at /u01/shared/.
  • Configure a unified collections action view and a unified collections scenario view in single-schema or multischema environment to be queried by Oracle AIA. See Configuring Views for Oracle Application Infrastructure Architecture for detailed instructions about configuring views for Oracle AIA.

Integrating ODI with AIA

To integrate ODI with AIA cloud native:

  1. Update the email details in the /u01/shared/aia-comms/commsOracleHome/comms_home/source/soainfra/apps/config/AIAConfigurationProperties.xml file as required. Update the properties for the below CollectionsParameters module file:
    • FromMailAddress
    • ToMailAddress
    • MailServer
    • MailSMTPPort
  2. Encode the AIA XREF password:

    To encode the XREF password, run the following command and note the encoded password:

    $ODI_HOME/bin/encode.sh -INSTANCE=OdiInstanceName AIA_XREF_DB_Password

    Update the $AIA_PV/aia-comms/commsOracleHome/comms_home/source/soainfra/apps/services/industry/Communications/BulkDataProcess/BRMToSiebel/Collections/ODI/Oracle/V1/ODI_Master_Repository/CONN_AIADS.xml file with the encoded password.

  3. Encode the BRM password:
    To encode the BRM password, run the following command and note the encoded password:
    $ODI_HOME/bin/encode.sh -INSTANCE=OdiInstanceName BRM_Database_Advanced_Queuing_user_password

    Update the $AIA_PV/aia-comms/commsOracleHome/comms_home/source/soainfra/apps/services/industry/Communications/BulkDataProcess/BRMToSiebel/Collections/ODI/Oracle/V1/ODI_Master_Repository/CONN_OracleBRMDS.xml file with the encoded password.

  4. Encode the Siebel password:
    To encode the Siebel password, run the following command:
    $ODI_HOME/bin/encode.sh -INSTANCE=OdiInstanceName Siebel_database_user_password

    Update the $AIA_PV/aia-comms/commsOracleHome/comms_home/source/soainfra/apps/ services/industry/Communications/BulkDataProcess/BRMToSiebel/ Collections/ODI/Oracle/V1/ODI_Master_Repository file with the encoded password.

  5. Import the AIA connections to ODI Studio. If the AABC installation is successful, then the importAIAODIConnections.sh script will be generated in the AIA_PV directory. Run the following command to import:
    sh importAIAODIConnections.sh \
    -a AIA_PV_Path \
    -o ODI_DOMAIN_HOME_path \
    -i ODI Instance Name. Example: OracleDIAgent \
    -w ODI Workrep name. Example: WORKREP

Verifying the Integration

To verify the Siebel CRM on Containers and BRM integration deployment:
  1. Log in to ODI Studio with ODI user credentials.
  2. Verify and confirm that the AIA Collections Project is imported into the Designer section.
  3. Verify and confirm the connection details under Topology - Physical Architecture - Oracle and XML.
    • Oracle - AIA DS
    • Oracle - Oracle BRM DS
    • Oracle - Siebel DS
    • XML - AIA Config Properties DS
    • XML - Collection Action Name
    • XML - Collection Priority DS
    • XML - Collection Status Mapping
    • XML - Collection Substatus model
    • XML - Currency DS

Applying Tuning Parameters on BRM and AIA

Apply the following tuning parameters to improve performance, scalability, and resource utilization during high-volume operations.

Updating the Front-End and Back-End Configuration in BRM

To update the front-end and back-end configuration in Oracle Communications Billing and Revenue Management (BRM):

  1. Navigate to the BRM Helm chart directory and open the values.yaml file.
  2. Under dm-oracle/config, update the following parameters:
    totalFrontEnds: 8
totalBackEnds: 64
connectionsPerFrontEnd: 16
totalTransBackEnds: 52
  3. In the same values.yaml file, increment the restart_count value by 1.
  4. Run a Helm upgrade for BRM.

    The dm-oracle pod restarts automatically after the upgrade.

Validation

  1. Access the dm-oracle pod using the following command:
    kubectl exec -it <dm-oracle-pod> -- /bin/bash
  2. Navigate to the /oms/sys/dm_oracle directory.
  3. Verify the updated configuration by running the following commands:
    Check connectionsPerFrontEnd: echo $DM_MAX_PER_FE
	Check totalFrontEnds: echo $DM_NO_FRONT_ENDS
	Check totalBackEnds: echo $DM_NO_BACK_ENDS
	Check totalTransBackEnds: echo $DM_NO_TRANS_BE_MAX
  4. Confirm that the output values match the configuration in the values.yaml file.

Verifying and Updating the Java Heap Space in AIA Deployment

To verify and update the Java heap space in Oracle Communications Application Integration Architecture (AIA) deployment:

  1. Run the following commands to verify the current Java heap configuration for AIA pods:
    kubectl exec -n <aia_namespace> <soa_server1_pod> -- printenv | grep USER_MEM_ARGS
kubectl exec -n <aia_namespace> <soa_server2_pod> -- printenv | grep USER_MEM_ARGS
kubectl exec -n <aia_namespace> <soa_adminserver_pod> -- printenv | grep USER_MEM_ARGS
  2. Review the output. If the heap size is low (for example, -Xms256m -Xmx1024m), increase it by editing the USER_MEM_ARGS domain of Java heap.
  3. Before making changes, create a backup of the domain resource:
    kubectl get domain -n <namespace> <domain_name> -o yaml > <domain_name>-backup.yaml
  4. Update Java heap size:
    1. Edit the domain configuration:
      kubectl edit domain -n <namespace> <domain_name>
    2. Locate USER_MEM_ARGS under spec.serverPod.env and update the heap values. For example:
      serverPod:
  env:
  - name: USER_MEM_ARGS
   value: "-Djava.security.egd=file:/dev/./urandom -Xms4g -Xmx8g"
    3. Adjust -Xms (initial heap) and -Xmx (maximum heap) based on the system capacity and requirements.
  5. Restart the domain to apply the updated configuration.
  6. After the restart, run the verification commands (see Step 1) again to confirm that the new heap settings are applied correctly.

Testing the Solution Deployment

To test the end-to-end deployment of the solution, do the following:

Testing the Solution using the Smoke Test Validation

The smoke test validation includes validating your access to UIs of all the applications integrated with the Digital Business Experience solution and validating if the load balancer is working properly.

Checking the URLs of the Deployed Applications

To check if all the deployed application UIs are accessible:

  1. For each of the URLs in the email you received, open the application URLs one-by-one and log in using your credentials.
  2. Verify if you can access all the URLs.

    Note:

    If you have trouble logging in to any of the application URLs, contact Oracle Support.

Validating the Access to Load Balancer

To validate if the load balancer is working fine:

  1. Open Postman on the environment you wish to test the load balancer from.
  2. Click New, and then click Request.
  3. From the Request Type drop-down list, select GET.

    The GET method page opens.

  4. In the GET URL field, enter the URL for the public DNS name of your load balancer.
    Example load balancer URL for PDC:
    https://public_load_balancer_dns_name:31200/pdc/config
    Example load balancer URL for Siebel:
    https://<public_load_balancer_dns_name:32200/siebel/config
  5. Under the Authorization tab, set the header for authorization.
  6. Click Send.
  7. Validate the response.
    • If the status code is 200 OK, the load balancer is working fine.
    • If the status code is 503 Service Unavailable, there might be a back-end issue.

Testing the Integrations using Functional Testing (Smoke Test)

This section provides information about the functional testing of the application integrations by manually creating a smoke test offer.

Prerequisites

  • You must create Siebel and PDC destinations in Launch.
  • The Lookup code for /service/telco/gsm/telephony must be added in Launch and Service Event must be added in PDC.

To create a Siebel destination in Launch:

  1. Log in to the Launch application using your credentials.
  2. Navigate to Product Management, select Enterprise Catalog, then select Administration, then select Manage Lifecycle Status, then select Destinations, and then click Create.
  3. Provide the values to the following fields:
    • Domain Name: Siebel
    • Domain Instance: siebel-test
    • Publish Sequence: 1
    • Turn on the Internal toggle.
  4. Click Save.

To create a PDC destination in Launch:

  1. Log in to the Launch application using your credentials.
  2. Navigate to Product Management, select Enterprise Catalog, then select Administration, then select Manage Lifecycle Status, then select Destinations, and then click Create.
  3. Provide the values to the following fields:
    • Domain Name: PDC
    • Domain Instance: pdc-test
    • Publish Sequence: 2
    • Turn on the Internal toggle.
  4. Click Save.

After Siebel and PDC destinations are created:

  1. From the Launch UI, navigate to Manage Lifecycle Status, and then click Save as New Version.
  2. Set the Lifecycle Status to Ready to publish for both the destinations.
  3. Click Activate.
Creating a Smoke Test Offer in Launch (Design Time)

Note:

The procedure mentioned below is for creating a smoke test offer in Launch manually.

To create a smoke test offer in Launch:

  1. Verify that the Siebel and PDC destinations are created in Launch:
    1. Log in to the Launch application using your credentials.
    2. Navigate to Administration, and then click Manage available on the Lifecycle status card.

      The Entity lifecycle page opens.

    3. Click View on the Destinations card.
    4. Ensure that Siebel and PDC destinations are configured with appropriate details.
    5. Click Back (<) to go back to the Entity lifecycle page.
    6. Click Manage available on the Lifecycle status card.

      The Lifecycle Status page opens.

    7. Confirm that the Lifecycle Status column displays Ready to publish for Destinations (2).
  2. Create the smoke test offer in Launch:
    1. From the Launch home page, navigate to Administration, and then click Create available on the Initiatives card.

      The Initiative create page opens.

    2. Create an initiative by providing values for the Name and ID fields under the Identifying information tab. For example, the value can be SmokeTest_initiative.
    3. Create a Balance Element (as Balance Element is a seeded data in Launch) for USD in Launch using the following API details:
      • API Endpoint: POST {{host_url}}/crmRestApi/atcProductCatalog/11.13.18.05/productCatalogReferenceManagement/v1/balanceElement
      • host_url: FA URL of Launch
      • Authorization: Basic Auth with Launch credentials
      • Use the following sample payload as the body of the POST request:
        {
        "id": "USDCurrency",
        "name": "USD Currency",
        "version": "1.0",
        "lifecycleStatus": "In design",
        "@type": "BalanceElementOracle",
        "validFor": {
            "startDateTime": "2023-09-29T03:50:48.000Z"
        },
        "project": {
            "id": "SmokeTest_initiative",
            "version": "1.0",
            "@referredType": "ProjectOracle"
        },
        "consumptionRule": "LST",
        "balanceElementType": "CURRENCY",
        "code": "USD",
        "numericCode": 840,
        "symbol": "$",
        "roundingMethod": "CALC",
        "decimalPlaces": "2"
    }
    4. After the Balance Element is created, from the Launch home page, navigate to Administration, and then click Manage available on the Pricing strategies card.
    5. Click Create Pricelist.
    6. In the Name field, enter NA Pricelist.

      Note:

      You must enter the name as NA Pricelist only as it is the default pricelist in the AIA DVM configuration.
    7. From the Price List Type drop-down list, select USD.
    8. Navigate to Workbench, select Specifications, and then select Create Service Specification.
    9. To create a service specification, enter any value in the Name (for example, SmokeTest_SS) and ID fields.
    10. Navigate back to the Specifications page, and click Create Product Specification.

      Note:

      You must create VoIP PS and CME VoIP PS product specifications in the offer as they are part of the O2A cartridge by default.
    11. Create the VoIP PS as follows:
      1. In the Name field, enter VoIP PS.
      2. In the Other information section, from the Initiative drop-down list, select your initiative (for example, SmokeTest_initiative).
      3. Click Save.
    12. Create the CME VoIP PS as follows:
      1. In the Name field, enter CME VoIP PS.
      2. From the Parent Product Specification drop-down list, select VoIP PS.
      3. In the Other information section, from the Initiative drop-down list, select your initiative (for example, SmokeTest_initiative).
      4. In the Other information section, in the Service Specification field, select your service specification (for example, SmokeTest_SS).
      5. Click Save.
    13. After the product specifications are created:
      1. Navigate back to the Specifications page.
      2. Under the Action column for each product specification, click ..., then select Change Status, and then click Design Complete.

        Note:

        This step is mandatory for the specifications to be available to use in Offers.
    14. From the Launch home page, click the Offerings tab and click Create Simple Offering.
    15. Enter the general information as follows:
      • Name: Any name (for example, SmokeTest_Offer)
      • ID: Any ID (for example, SmokeTest_Offer)
      • Offering Type: Service
      • Product Specification: CME VoIP PS
      • Service Specification: SmokeTest_SS
      • Billing Type: Subscription
      • Billing Service Type: /service/telco/gsm/telephony
      • Enable the Service Instance flag (to make it a Simple Service Bundle)
      • Fulfillment Item Code: VoIP PS
      • Enable Orderable, Track as Asset, Shippable, and Bill on Purchase
    16. Click the Pricing tab, and from the Add Fee drop-down list, select Recurring Fee.
    17. In the Price plan page, provide the following information:
      • Name: Any name (for example, SmokeTest_Offer_POP)
      • ID: Any ID
      • From the Price Lists drop-down list, select NA Pricelist.
      • From the Recurring Fee Type drop-down list, select Cycle.
      • From the Period drop-down list, select Monthly.
      • Click the Edit icon available on the Price and effective period section, and add the Price (for example, $1.00).
    18. Click Update to update the price in the offer.
    19. Click Create to create the smoke test offer.
  3. Publish the initiative containing the smoke test offer:
    1. From the Launch home page, navigate to Administration, and then click View available on the Initiatives card.
    2. Click ... available under Actions of your initiative, select Change status to, and then click Ready to publish.
    3. After the status is updated to Ready to publish, click ..., and then click Publish.
    4. After the Publish action is initiated, two tasks are created to sync the data to Siebel and PDC as per the initiative configuration.
    5. After the publish is successfully completed, the two tasks will move to Success status and the status of the initiative changes to In Test.
Validating the Offer in PDC

To validate the smoke test offer data in PDC:

  1. Log in to the Oracle Communications Pricing Design Center (PDC) application using your credentials.
  2. From the PDC home page, click Search Pricing available on the bottom left of the navigation pane.
  3. Click the Advanced link.

    The Advanced Search page opens.

  4. In the Advanced Search page:
    1. From the Pricing Component drop-down list, select Charge Offer.
    2. From the Name drop-down list, select Starts with, and in the text box enter the offer name (for example, SmokeTest_Offer).
    3. Click Search.
  5. From the results list, click the name of the test offer.

    The details of the offer are displayed.

  6. Validate the details.
  7. Check if em-gateway and pricingupdater are up and running in the environment using the following command:

    "kubectl get pods -n <namespace>" | grep -e em -e pricingupdater

Validating the Offer in Siebel

To validate the smoke test offer data in Siebel:

  1. Log in to Siebel using your credentials.
  2. Click the Site Map icon and then select Siebel UI.
  3. Search for Administration - Product.
  4. From the results list, click the offer name (for example, SmokeTest_Offer).
  5. Validate if the Service Instance check box is selected.
  6. Validate the details of the offer.
Validating the Offer in BRM

To validate the smoke test offer data in BRM:

  1. Ensure that SQL Developer is installed in your system.
  2. Connect with the Oracle Communications Billing and Revenue Management (BRM) DB by clicking New Collection and following steps:
    1. Name: BRM PIN DB:
    2. username: pin
    3. password: (password given in file)
    4. hostname: localhost:1521
    5. port: 1521
    6. service name: (Service name given in the Excel file)
  3. Run the following query to get the product details:

    select * from product_t where name ='<product_name>';

  4. Run the following query to get the price of the product and validate it with Siebel and PDC:
    select SCALED_AMOUNT from RATE_BAL_IMPACTS_T where OBJ_ID0 IN (
select POID_ID0 from RATE_T where RATE_PLAN_OBJ_ID0 IN
( select POID_ID0 from RATE_PLAN_T where PRODUCT_OBJ_ID0 IN 
(select POID_ID0 from pin.product_t where name like 'product-name'))))

    Note:

    The product name is the smoke test offer name you have created in Launch.
Validating the AIA XREFs

To validate the smoke test offer data in AIA:

  1. Ensure that SQL Developer is installed in your system.
  2. Connect with the Oracle Communications Application Integration Architecture (AIA) DB by clicking New Collection and following steps:
    1. Name: AIA XREF:
    2. username: AIAFP_XREF
    3. password: (password given in file)
    4. hostname: localhost:1521
    5. port: 1521
    6. service name: (Service name given in the Excel file)
  3. Run the following query by replacing <BRM POID> with the POID you get from BRM DB:
    SELECT
    BRM_01,
    COMMON,
    SEBL_01
FROM
    XREF_ITEM_ITEMID
WHERE
    BRM_01 LIKE '0.0.0.1 /product <BRM POID> 0%'
 
UNION
 
SELECT
    t1.BRM_01,
    t1.COMMON,
    t1.SEBL_01
FROM
    XREF_ITEM_ITEMID t1
    INNER JOIN XREF_PRICELINETYPE_ID t2 ON t1.COMMON = t2.ITEM_ID_COMMON
WHERE
    t2.BRM_01 LIKE '0.0.0.1 /product <BRM POID> 0%'

    Check that SEBL_01, COMMON, and BRM_01 are not null, and validate if the SEBL_01 from the Siebel Administration UI is same.

  4. Run the following query to get the ITEM_ID_COMMON, and all four fields should not be null.:
    SELECT
    BRM_01,
    COMMON,
    SEBL_01,
    ITEM_ID_COMMON
FROM
    XREF_PRICELINE_ID
WHERE
    BRM_01 LIKE '0.0.0.1 /product <BRM POID> 0%'
  5. Run the following query to get the priceline type:
    SELECT
    BRM_01,
    COMMON,
    SEBL_01,
    ITEM_ID_COMMON
FROM
    XREF_PRICELINETYPE_ID
WHERE
    BRM_01 LIKE '0.0.0.1 /product <BRM POID> 0%'
  6. Run the following query to get the Siebel product reference:
    SELECT
    t1.ITEM_ID_COMMON,
    t1.LINEPRICETYPECODE
FROM 
    XREF_SIEBELPRODUCTEV_118 t1
    INNER JOIN XREF_PRICELINETYPE_ID t2 ON t1.LINEPRICETYPECODE = t2.COMMON
WHERE
    t2.BRM_01 LIKE '0.0.0.1 /product <BRM POID> 0%'
Deleting the Initiative From Launch

Note:

You must delete the smoke test initiative after successful completion of all the validations.

To delete the smoke test initiative from Launch:

  1. Log in to the Launch application using your credentials.
  2. Navigate to Administration, and then click View available on the Initiative card.
  3. From the results list, click ... against your smoke test initiative name (for example, SmokeTest_initiative), then select Change status to, and then click In design.
  4. After the status of the initiative changes to In design, click ..., and then select Delete.
Creating and Submitting the Order From Siebel (Run Time)

To create and submit an order for the smoke test offer created in Launch:

  1. Log in to the Siebel application using your credentials.

    The Siebel home screen opens.

  2. In the Account field, enter the account name (for example, smoke_test), and then click Add & Go.
  3. In the Accounts page, provide the following information:
    1. From the Account Type drop-down list, select Residential.
    2. Click the Address icon, select the appropriate address from the Account Addresses page.
    3. From the Pricelist drop-down list, select NA Pricelist.
  4. From the Account Summary drop-down list, select Contacts, and then click the ++ icon.
  5. In the First Name and Last Name fields, enter any name (for example, smoke_test).
  6. Click the Settings icon and select Save.
  7. In the Billing Profile section, click +, and provide the following information:
    • Payment Method: Bill Me
    • Bill Type: Summary
    • Frequency: Monthly
    • Bill Media: Email
    • Click the Settings icon and select Save.
  8. In the Orders section, click the Settings icon, and then select New Record.
  9. Click the link in the Order # column.

    The Order Details page opens.

  10. In the Due field, click the Calendar icon, and select the date same as the Order Date field.
  11. In the Line Items section, enter the name of the published offer from Launch, validate the price for that service, and add service ID for service bundles.
  12. Click Submit.
  13. After validating the order in Oracle Communications Application Integration Architecture (AIA), refresh the page, and verify if the order status is changed to Completed.
Validating the Order in AIA

To validate the order data in AIA:

  1. Log in to the Oracle Communications Application Integration Architecture (AIA) application using your credentials.
  2. Click the aia-fp icon, expand SOA, and then select soa-infra(soa_server1).
  3. Click the Flow Instances tab, click Recent Instances and verify composite state [running or completed or failed].
  4. For the successful orders, the Flow State column displays Completed.
Validating the Order in OSM

To validate the order data in OSM:

  1. Log in to the Oracle Communications Order and Service Management (OSM) application using your credentials.
  2. Click the Query tab.
  3. In the Order Number field, enter the order number generated in Siebel.
  4. From the Order State drop-down list, select All.
  5. From the Failure drop-down list, select All, and then click Search.
  6. The system displays both COM_ and SOM_ instances as Completed.
Validating the Order in BRM

To validate the order data in BRM:

  1. Log in to the Oracle Communications Billing and Revenue Management (BRM) application using your credentials.
  2. From the Search drop-down list, select Accounts, and then click Search.
  3. From the results list, select your account, and then click Open.

    The Account Details page opens

  4. Verify the account details, such as Services, First Name, Last Name, and so on are created correctly in BRM.
  5. Click Assets tab, verify the products and services, and validate the Service status is Active.
  6. Navigate to the Bills tab, and verify the total amount due.
  7. Click Bill Now to generate the bill in BRM.
  8. Click OK.
Validating the Account in ECE Cache

Check if the prices are in the Oracle Communications Elastic Charging Engine (ECE) cache:

  1. Run the following command to check the pod ID for PDC and ECE pods in namespace.

    kubectl get pods -n brmcn15 | grep -e pdc -e upd

  2. Run the following command to log in to the pod:

    kubectl exec -it ecs-0 -n brmcn15 -- bash

  3. Go to temp and run the following command to run the shell script:

    [eceuser@ecs-0 temp]$ sh /home/charging/opt/ECE/oceceserver/bin/query.sh

  4. Query for the ChargeOffering using the query CohQL> Select value() from ChargeOffering

    Note:

    • The above query ensures the offer is present and externalId is populated.
    • For detailed information, run the query.sh script in ECE pod and query for ChargeOffering, Status, and so on.
  5. Select value() from Customer where customerId='<cust_id_from_brm_acc_url>'

    This ensures the account is present in the ECE cache.

Validating the Siebel Order Completion

To validate the Siebel order completion:

  1. Log in to the Siebel application using your credentials.
  2. Open your account from the Accounts page.
  3. From the Installed Assets section, verify that all assets included in the order are purchased.
  4. From the Billing Items section, verify that all items included in the order are billed.
  5. From the Orders section, click the link from the Order # column.

    The Order Details page opens.

  6. Verify that the order status is Complete.
  7. Verify the First Name and Last Name in Siebel and Billing Care.
  8. From the Billing Profile section, click the Name link, and validate the bill details in Siebel UI.