6 Downloading and Deploying the Reference Solution

This chapter provides information about downloading and deploying the Digital Business Experience Reference Solution.

Before you start to download and deploy the reference solution:

  1. Learn about the reference solution. See About the Reference Solution in Oracle Communications Digital Business Experience Concepts for more details.

  2. Learn about the reference product models and seed data available in the reference solution. See Reference Product Models and Seed Data in Oracle Communications Digital Business Experience Concept to Market Guide for more details.

  3. Learn about the order to cash reference library, which consists of a few sample preconfigured order-to-cash end-to-end features. See Using the Order to Cash Reference Library in Oracle Communications Digital Business Experience Order to Cash Implementation Guide for more details.

  4. Download and install Oracle Communications Solution Test Automation Platform (STAP) in your Digital Business Experience environment. See Installing STAP for more details.

    Note:

    The reference solution is packaged with STAP, so you must install STAP before you can deploy the reference solution package.

  5. Set up STAP Design Experience (STAP DE). See Setting Up The STAP Design Experience for more information.

Downloading the Reference Solution Package

You must download the packages in the following order:

  • Reference Solution package, which contains scripts for:
    • Prerequisite and Seed data: Preconfigured Launch, Siebel, BRM, and PDC data.
    • STAP helper scripts: These scripts help you to publish various scenarios to STAP.
    • Design-time product models: Includes all the business-to-business and business-to-customer product models.
    • Smoke test suite: Includes a smoke test scenario for your Digital Business Experience environment.
    • Feature extensions: These are Siebel and BRM custom extensions available under the B2BSolutionPack folder of the oc-dbe-rs-<version>.zip file. To apply these extensions to your Digital Business Experience environment, follow the Standard Operating Procedures (SOPs) documented under the B2BSolutionPack folder. The B2BSolutionPack folder also contains details about the automation test cases covered for various features. To run the automation test cases using STAP, see the TestPlan_Execution_SOP SOP available at oc-dbe-rs-<version>/Test Automation/TestPlan_Execution_SOP.pdf.
  • Order-to-cash test library (hosted with STAP), which consists of the end-to-end run-time test catalog.

To download the reference solution package:

  1. Download the reference solution pack from the Oracle software downloads website, located at:
    https://www.oracle.com/downloads/applications/communications/dbe-downloads.html
  2. Run the following commands from the STAP environment to unzip the reference solution pack: 
    unzip oc-dbe-rs-<version>.zip
    unzip -d oc-dbe-rs-<version>/B2CSolutionPack/ oc-stap-otc-testlib-<version>.zip

    Note:

    You can delete the zip file after unzipping it.
  3. Edit the stap.properties file: 
    cd oc-dbe-rs-<version>/B2CSolutionPack/
vi stap.properties
Replace:
export JAVA_HOME="/home/java/jdk-xx.x.x" with the correct path to JDK
export STAP_HOME="/home/STAP-DE"  with the correct path to STAP-DE jar
For example:
export JAVA_HOME="/home/user/java/jdk-21.0.6"
export STAP_HOME="/home/user/STAP-DE"
  4. Edit the config files for Publish-Automation.

    Set up the Tdaas and TES environment files to point them to the STAP deployment to which you want to publish them: 

    /oc-dbe-rs-<version>/B2CSolutionPack/Publish-Automation/config/environments/TdaasEnvironment.properties
/oc-dbe-rs-<version>/B2CSolutionPack/Publish-Automation/config/environments/TaaS-TES-environment.properties

Prerequisites

The prerequisites for installing the reference solution are:
  • Ensure that the ENABLE_PRODUCT_ATTRIBUTE_VALIDATION property is disabled in Oracle Communications Order to Activate (O2A) application.
  • Ensure that Oracle Communications Order and Service Management (OSM) image is extended to include UIM and TOM emulators if actual UIM and TOM applications are not available in the Digital Business Experience stack.
  • Verify all the REST API end points for various applications and SSH keys, ensuring proper connectivity.
  • Ensure that you enabled the REST calls for BCWS and TMF. See Configuring REST Services in Oracle Communications Billing and Revenue Management Cloud Native Deployment Guide for detailed instructions about configuring the rest services in BRM and PDC.
  • Edit the config files for pre-automation.
    oc-dbe-rs-<version>/B2CSolutionPack/Pre-Automation/config/publish/tdaasEnvironment.properties
oc-dbe-rs-<version>/B2CSolutionPack/Pre-Automation/config/publish/environment.properties
oc-dbe-rs-<version>/B2CSolutionPack/Pre-Automation/config/publish/persistence-volume-environment.properties
oc-dbe-rs-<version>/B2CSolutionPack/Pre-Automation/config/publish/publish-automation.properties
oc-dbe-rs-<version>/B2CSolutionPack/Pre-Automation/config/environments/* --> all files
oc-dbe-rs-<version>/B2CSolutionPack/path.properties
  • Run the following command to update the scenario files:
    sh replace_path.sh
  • Run the publish_workspace.sh script for pre-automation.
    sh publish_workspace.sh -w Pre-Automation
  • Run the run_scenarios.sh script for pre-automation.
    sh run_scenarios.sh -w Pre-Automation
  • Run the Seed Data (SD) Automation:
    • Edit the config files for SD Automation as follows:
      oc-dbe-rs-<version>/B2CSolutionPack/SD-Automation/config/publish/tdaasEnvironment.properties
oc-dbe-rs-<version>/B2CSolutionPack/SD-Automation/config/publish/environment.properties
oc-dbe-rs-<version>/B2CSolutionPack/SD-Automation/config/publish/persistence-volume-environment.properties
oc-dbe-rs-<version>/B2CSolutionPack/SD-Automation/config/publish/publish-automation.properties
oc-dbe-rs-<version>/B2CSolutionPack/SD-Automation/config/environments/* --> all files
oc-dbe-rs-<version>/B2CSolutionPack/token.properties
oc-dbe-rs-<version>/B2CSolutionPack/SD-Automation/scenarios/5.AIA/data/config.properties
    • Run the following command to check if the token refresh is working fine:
      sh refresh_token.sh
    • Run the following commands for SD Automation:
      sh publish_workspace.sh -w SD-Automation
      sh run_scenarios.sh -w SD-Automation
  • Verify that the seed data has been created correctly in Launch, PDC, and BRM. See About the Seed Data in Oracle Communications Digital Business Experience Concept to Market Implementation Guide for more information.
  • Check if the destinations for PDC and Siebel are created in Launch.
  • Verify if the pdc-test destination has destination exclusion rule to avoid publishing bundles to PDC as it is not supported by Digital Business Experience.
  • Ensure that the Lifecycle Status for the destinations in the Launch UI is Ready to publish.

Deploying the Reference Solution Package

To deploy the reference solution package:

  1. Run the Design-Time (DT) automation:
    1. Edit the config files for DT automation:
      oc-dbe-rs-<version>/B2CSolutionPack/DT-Automation/config/publish/tdaasEnvironment.properties
oc-dbe-rs-<version>/B2CSolutionPack/DT-Automation/config/publish/environment.properties
oc-dbe-rs-<version>/B2CSolutionPack/DT-Automation/config/publish/persistence-volume-environment.properties
oc-dbe-rs-<version>/B2CSolutionPack/DT-Automation/config/publish/publish-automation.properties
oc-dbe-rs-<version>/B2CSolutionPack/DT-Automation/config/environments/* --> all files
    2. Update the token.properties file with the newly generated token, then run the following command to update the scripts:
      sh refresh_token.sh
    3. Run the following commands for DT automation:
      sh publish_workspace.sh -w DT-Automation
    4. Run the script in the following order to publish all the product models required for DT automation:
      sh run_dt_automation.sh MobileProductModels
sh run_dt_automation.sh BroadbandProductModels
sh run_dt_automation.sh DigitalTVProductModels
sh run_dt_automation.sh HomePhoneProductModels
sh run_dt_automation.sh FamilySharePlan
sh run_dt_automation.sh QuadPlayProductModels
sh run_dt_automation.sh TriplePlayProductModels
sh run_dt_automation.sh DualPlayProductModels
sh run_dt_automation.sh AddPromotionBundles

      Note:

      You must follow the publish order mentioned above because models in DT automation are interdependent.
  2. Run the Run-Time (RT) automation:
    1. Edit the config files for RT automation.
      oc-dbe-rs-<version>/B2CSolutionPack/RT-Automation/config/publish/tdaasEnvironment.properties
oc-dbe-rs-<version>/B2CSolutionPack/RT-Automation/config/publish/environment.properties
oc-dbe-rs-<version>/B2CSolutionPack/RT-Automation/config/publish/persistence-volume-environment.properties
oc-dbe-rs-<version>/B2CSolutionPack/RT-Automation/config/publish/publish-automation.properties
oc-dbe-rs-<version>/B2CSolutionPack/RT-Automation/config/environments/* --> all files
    2. Run the following command for RT automation:
      sh publish_workspace.sh -w RT-Automation

After the RT automation is published, you can run either full or partial automation based on product models as follows:

  • To run all the run-time scenarios, run the following command:
    sh run_rt_automation.sh --all

    or

  • To run bundled sample orders (functional smoke test) scenario, run the following command:
    sh run_rt_automation.sh --scenario_name/subfolder_name
For example: sh run_rt_automation.sh --MobileProductModels/Supremo5GUnlimited/SampleOrder

    or

  • To run a specific run-time scenario, you can run the script with the corresponding path to the scenario. You can see the list of scenarios by passing the --list option to the script:
    sh run_rt_automation.sh --list
For example:
sh run_rt_automation.sh --BroadbandProductModels/SupremoBroadbandBasic/SalesOrderCreation
sh run_rt_automation.sh --BroadbandProductModels/SupremoBroadbandGigabit/CancelOrderBeforePONR

Troubleshooting the Reference Solution

This section provides troubleshooting information for problems while deploying the reference solution.

Problem: BRM Seed Data Fails to Load

If BRM data fails to load:

  • Load the following files from the BRM scenario data folder in the cm pod:
    • customservices_proximity.podl
    • customservices_OTT_VOIP_dtv_dmusic.podl

    See BRM PDC Seed Data in Oracle Communications Digital Business Experience Concept to Market Implementation Guide for a list of supported BRM Services, Events, and ServiceEvent maps.

  • Sync the new events and services by restarting the cm, dm, and syncpdc pods.

Problem: PDC Seed Data Fails to Import

If PDC data fails to import, create the ServiceEvent map manually from the PDC UI. See BRM PDC Seed Data in Oracle Communications Digital Business Experience Concept to Market Implementation Guide for a list of supported PDC Services, Events, and ServiceEvent maps.

Problem: Reimporting Service Event Map Files for PDC

This section provides a solution for running and reimporting Service Event Map files (attributeSpecMap.xml) multiple times in Oracle Communications Pricing Design Center (PDC) environments.

Issue: You need to import the Service Event Map file (attributeSpecMap.xml) multiple times during configuration, either in a new or an existing PDC environment.

Scenario 1: New PDC Environment

You have a newly installed PDC environment and need to import the attributeSpecMap.xml file multiple times.

Resolution

  • Import the Automated ASM file (attributeSpecMap.xml) as needed.
  • Use the -ow (Overwrite) and -ignoreID command-line options to avoid import conflicts:
    • -ow: Overwrites matching components in the PDC database.
    • -ignoreID: Ignores internal IDs to prevent ID conflicts.

Import Command Example

To reimport the same ASM file, use the following Helm upgrade command configuration:

ocpdc:
  configEnv:
    importExport:
      IE_Operation: "import"
      IE_Component: "config"
      IE_File_OR_Dir_Name: attributeSpecMap.xml
      extraCmdLineArgs: "-ow -ignoreID"
      IE_LogLevel: WARNING
      IE_PersistLog: failed
      persistIELogs: "enabled/all"

Note:

No additional steps are required in a fresh installation; multiple imports will not cause issues when using these options.
Scenario 2: Existing PDC Environment

You are working with an existing PDC environment where the Service Event Map has already been loaded, and you need to load additional or updated events for the same service.

Workaround

  1. Export the already loaded map.
    • Export the current Service Event Map from the existing PDC system (for example, E_ASM.xml).
  2. Compare with the new map.
    1. Obtain the new attribute specification map file to be imported (for example, N_ASM.xml).
    2. Manually compare E_ASM.xml and N_ASM.xml to identify differences or new entries.
  3. Create a merged map.
    • Merge the required changes (new or updated entries) from N_ASM.xml into E_ASM.xml to create a combined file (for example, E_ASM_merged.xml).
  4. Reimport the merged file.
    • Use -ow -ignoreID options while importing to overwrite existing entries and ignore internal IDs.

Import Command Example

  • E_ASM.xml: Contains the existing event map (for example, for service TelcoGsmTelephony). The following is a sample E_ASM.xml file:
    <?xml version="1.0" encoding="UTF-8" standalone="yes"?><cim:ConfigObjects xmlns:cim="http://xmlns.oracle.com/communications/platform/model/Config"><attributeSpecMaps xmlns:cim="http://xmlns.oracle.com/communications/platform/model/Config">
<name>ConvergentVoice_ASM</name>
<internalId>4fe9a625-839e-4135-a6cd-9818feb75ce6</internalId>
<priceListName>Default</priceListName>
<obsolete>false</obsolete>
<eventRUMSpec>
<name>EventBillingCycleRolloverMonthly_ERS</name>
<internalId>df0080b0-7e52-4bb7-a533-df60b02040dd</internalId>
<priceListName>Default</priceListName>
<obsolete>false</obsolete>
<eventSpecName>EventBillingCycleRolloverMonthly</eventSpecName>
<rumSpec>
<rumExpression>
<numericRumExpression>
<value>1.0</value>
</numericRumExpression>
</rumExpression>
<rumName>Occurrence</rumName>
</rumSpec>
</eventRUMSpec>
<eventRUMSpec>
<name>EventBillingProductFeeCycleCycle_forward_monthly_ERS</name>
<internalId>43f53235-57db-455e-9033-a8ec33e15a58</internalId>
<priceListName>Default</priceListName>
<obsolete>false</obsolete>
<eventSpecName>EventBillingProductFeeCycleCycle_forward_monthly</eventSpecName>
<rumSpec>
<rumExpression>
<numericRumExpression>
<value>1.0</value>
</numericRumExpression>
</rumExpression>
<rumName>Occurrence</rumName>
</rumSpec>
</eventRUMSpec>
<eventRUMSpec>
<name>EventDelayedSessionTelcoGsm_ERS</name>
<internalId>ccdf11ed-aac6-45eb-9487-ee77043a3643</internalId>
<priceListName>Default</priceListName>
<obsolete>false</obsolete>
<eventSpecName>EventDelayedSessionTelcoGsm</eventSpecName>
<rumSpec>
<rumExpression>
<binaryRUMExpression>
<leftOperand>
<eventFieldExpression>
<fieldName>EventDelayedSessionTelcoGsm.END_T</fieldName>
</eventFieldExpression>
</leftOperand>
<rightOperand>
<eventFieldExpression>
<fieldName>EventDelayedSessionTelcoGsm.START_T</fieldName>
</eventFieldExpression>
</rightOperand>
<operation>SUBTRACT</operation>
</binaryRUMExpression>
</rumExpression>
<rumName>Duration</rumName>
</rumSpec>
</eventRUMSpec>
<productSpecName>TelcoGsmTelephony</productSpecName>
</attributeSpecMaps></cim:ConfigObjects>
  • N_ASM.xml: Contains new or modified events (for example, added Purchase Fee event, updated RUM for "Event delayed session telco GSM"). The following is a sample N_ASM.xml file:
    <?xml version="1.0" encoding="UTF-8" standalone="yes"?><cim:ConfigObjects xmlns:cim="http://xmlns.oracle.com/communications/platform/model/Config">             <attributeSpecMaps xmlns:cim="http://xmlns.oracle.com/communications/platform/model/Config">
   <name>ConvergentVoice_ASM</name>
   <internalId>4fe9a625-839e-4135-a6cd-9818feb75ce6</internalId>
   <priceListName>Default</priceListName>
   <obsolete>false</obsolete>
   <eventRUMSpec>
      <name>EventDelayedSessionTelcoGsm_ERS</name>
      <internalId>ccdf11ed-aac6-45eb-9487-ee77043a3643</internalId>
      <priceListName>Default</priceListName>
      <obsolete>false</obsolete>
      <eventSpecName>EventDelayedSessionTelcoGsm</eventSpecName>
      <rumSpec>
         <rumExpression>
            <binaryRUMExpression>
               <leftOperand>
                  <eventFieldExpression>
                     <fieldName>EventDelayedSessionTelcoGsm.END_T</fieldName>
                  </eventFieldExpression>
               </leftOperand>
               <rightOperand>
                  <eventFieldExpression>
                     <fieldName>EventDelayedSessionTelcoGsm.START_T</fieldName>
                  </eventFieldExpression>
               </rightOperand>
               <operation>SUBTRACT</operation>
            </binaryRUMExpression>
         </rumExpression>
         <rumName>Duration_M</rumName>
      </rumSpec>
   </eventRUMSpec>
   <eventRUMSpec>
      <name>EventBillingProductFeePurchase_ERS</name>
      <internalId>d090943b-1287-48db-a3e3-5f971a1753cf</internalId>
      <priceListName>Default</priceListName>
      <obsolete>false</obsolete>
      <eventSpecName>EventBillingProductFeePurchase</eventSpecName>
      <rumSpec>
         <rumExpression>
            <numericRumExpression>
               <value>1.0</value>
            </numericRumExpression>
         </rumExpression>
         <rumName>Occurrence</rumName>
      </rumSpec>
   </eventRUMSpec>
<productSpecName>TelcoGsmTelephony</productSpecName>
</attributeSpecMaps></cim:ConfigObjects>
  • E_ASM_merged.xml: Manually merged file containing all required events and updates. The following is a sample E_ASM_merged.xml file:
    <?xml version="1.0" encoding="UTF-8" standalone="yes"?><cim:ConfigObjects xmlns:cim="http://xmlns.oracle.com/communications/platform/model/Config"><attributeSpecMaps xmlns:cim="http://xmlns.oracle.com/communications/platform/model/Config">
<name>ConvergentVoice_ASM</name>
<internalId>4fe9a625-839e-4135-a6cd-9818feb75ce6</internalId>
<priceListName>Default</priceListName>
<obsolete>false</obsolete>
<eventRUMSpec>
<name>EventBillingCycleRolloverMonthly_ERS</name>
<internalId>df0080b0-7e52-4bb7-a533-df60b02040dd</internalId>
<priceListName>Default</priceListName>
<obsolete>false</obsolete>
<eventSpecName>EventBillingCycleRolloverMonthly</eventSpecName>
<rumSpec>
<rumExpression>
<numericRumExpression>
<value>1.0</value>
</numericRumExpression>
</rumExpression>
<rumName>Occurrence</rumName>
</rumSpec>
</eventRUMSpec>
<eventRUMSpec>
<name>EventBillingProductFeeCycleCycle_forward_monthly_ERS</name>
<internalId>43f53235-57db-455e-9033-a8ec33e15a58</internalId>
<priceListName>Default</priceListName>
<obsolete>false</obsolete>
<eventSpecName>EventBillingProductFeeCycleCycle_forward_monthly</eventSpecName>
<rumSpec>
<rumExpression>
<numericRumExpression>
<value>1.0</value>
</numericRumExpression>
</rumExpression>
<rumName>Occurrence</rumName>
</rumSpec>
</eventRUMSpec>
<eventRUMSpec>
<name>EventDelayedSessionTelcoGsm_ERS</name>
<internalId>ccdf11ed-aac6-45eb-9487-ee77043a3643</internalId>
<priceListName>Default</priceListName>
<obsolete>false</obsolete>
<eventSpecName>EventDelayedSessionTelcoGsm</eventSpecName>
<rumSpec>
<rumExpression>
<binaryRUMExpression>
<leftOperand>
<eventFieldExpression>
<fieldName>EventDelayedSessionTelcoGsm.END_T</fieldName>
</eventFieldExpression>
</leftOperand>
<rightOperand>
<eventFieldExpression>
<fieldName>EventDelayedSessionTelcoGsm.START_T</fieldName>
</eventFieldExpression>
</rightOperand>
<operation>SUBTRACT</operation>
</binaryRUMExpression>
</rumExpression>
<rumName>Duration</rumName>
</rumSpec>
<rumSpec>
<rumExpression>
<binaryRUMExpression>
<leftOperand>
<eventFieldExpression>
<fieldName>EventDelayedSessionTelcoGsm.END_T</fieldName>
</eventFieldExpression>
</leftOperand>
<rightOperand>
<eventFieldExpression>
<fieldName>EventDelayedSessionTelcoGsm.START_T</fieldName>
</eventFieldExpression>
</rightOperand>
<operation>SUBTRACT</operation>
</binaryRUMExpression>
</rumExpression>
<rumName>Duration_M</rumName>
</rumSpec>
</eventRUMSpec>
<eventRUMSpec>
<name>EventBillingProductFeePurchase_ERS</name>
<internalId>d090943b-1287-48db-a3e3-5f971a1753cf</internalId>
<priceListName>Default</priceListName>
<obsolete>false</obsolete>
<eventSpecName>EventBillingProductFeePurchase</eventSpecName>
<rumSpec>
<rumExpression>
<numericRumExpression>
<value>1.0</value>
</numericRumExpression>
</rumExpression>
<rumName>Occurrence</rumName>
</rumSpec>
</eventRUMSpec>
<productSpecName>TelcoGsmTelephony</productSpecName>
</attributeSpecMaps></cim:ConfigObjects>

To reimport the merged file, configure the Helm upgrade as follows:

ocpdc:
  configEnv:
    importExport:
      IE_Operation: "import"
      IE_Component: "config"
      IE_File_OR_Dir_Name: E_ASM_merged.xml
      extraCmdLineArgs: "-ow -ignoreID"
      IE_LogLevel: WARNING
      IE_PersistLog: failed
      persistIELogs: "enabled/all"

Note:

  • Always create backups of configuration files before performing merges or imports.
  • Manual merging is required to ensure that the Reference Solution test cases run without issues, as well as retain any current service event maps that are already available.

Problem: Pre Seed Model Fails to Import or Publish During SD Automation

If pre seed model fails to import or publish, verify if the pre seed model is available under the Initiatives tab in the Launch UI. If not, rerun the import or publish jobs accordingly.

Problem: AIA DVM Script Fails to Run During SD Automation

If the AIA DVM script (dvm_update.sh) fails to run, check the config.properties file available in the AIA_FILE_TARGET_DIR folder from path.properties, and rerun the dvm_update.sh script manually from the bastion host from the AIA_FILE_TARGET_DIR folder.

Problem: restartDomain.sh Script Fails to Run During SD Automation

If the AIA pods are not starting or the restartDomain.sh script fails to run, rerun the restartDomain.sh script from the AIA_FILE_TARGET_DIR folder and check the AIA WebLogic console to start soa_server1 and soa_server2 properly.

Problem: Product Models Fail to Import or Publish During DT Automation

If product models fail to import or publish, verify if the product model is available under Initiatives tab in the Launch UI. Check if there are any failed import or publish jobs and rerun those jobs from the Launch UI in the correct order.

For information about the correct order, see the "Prerequisite Setup for Product Models" table from the "Reference Product Models and Seed Data" chapter in Oracle Communications Digital Business Experience Concept to Market Implementation Guide.

Problem: Sales Order Status Verification Failed in Siebel During RT Automation

Issue: When you submit a sales order from Siebel, it fails intermittently due to AIA or BRM-related issues.

The failure occurs at the validation step with the following validation timeout error:
Timeout - endAfter reached: test condition not satisfied within the wait duration

To verify the intermittent issues using the AIA Enterprise Manager (EM) console:

  1. Login to the EM Console using your credentials.
  2. Navigate to the soa-infra server.
  3. Search for the order and look for instances corresponding to the order number.
  4. Identify failures and click Flow ID for failed instances to view detailed errors.

    Common error messages include failure of composite ProcessFulfillmentOrderBillingOSMCFSCommsJMSConsumer [1.0] with different errors.

    Sample error message:
    [Exception in oneway execution]Unexpected exception in one-way operation "processBilling" on reference "ProcessFulfillmentOrderBillingBRMCommsProvABCSImpl".Possible Fix:Check whether the reference service is properly configured and running or look at exception for analyzing the reason or contact Oracle Support Services. Cause: ORABPEL-02199

JTA transaction is not in active state.
The transaction became inactive when executing activity "" for instance "342,494", bpel engine can not proceed further without an active transaction. please debug the invoked subsystem on why the transaction is not in active status. the transaction status is "ROLLEDBACK".
The reason was The execution of this instance "342494" for process "ProcessFulfillmentOrderBillingBRMCommsProvABCSImplMasterProcess" is supposed to be in an active jta transaction, the current transaction status is "ROLLEDBACK", the underlying exception is "javax.transaction.xa.XAException: Internal error: XAResource 'eis/BRM' is unavailable" .
Consult the system administrator regarding this error.

Solution:

  • Rerun the failed scenario using the following command:
     sh run_rt_automation.sh <scenario_path>
  • If the issue still exists, create a service ticket for more assistance.

Problem: Bill Generation Failed in BRM During RT Automation

Issue: Bill generation fails in Oracle Communications Billing Revenue Management (BRM) due to intermittent environment issues.

The failure occurs in the generate-bill.brm.case file with a 504 response as follows:

"{"extension":null,"errorCode":10013,"errorMessage":"The operation has timed out!","isValidationError":false,"paramInfo":[]}"

Solution:

  • Rerun the failed scenario using the following command:
    sh run_rt_automation.sh <scenario_path>
  • If the issue still exists, create a service ticket for further assistance.

Problem: Issue While Generating Triggers in Siebel During RT Automation

Issue: If you do not configure triggers correctly in Siebel, the account synchronization requests fail to reach BRM.

The failure occurs in the following scenarios:

  • Updating first name and last name after the sales order is created for Supremo TV Basic.
  • Updating address details after the sales order is created for Supremo TV Basic.
  • Suspending services and terminating an account.

Solution:

  • Verify that Enable Account Status Sync is configured correctly.
  • If the issue exists, check the Siebel server logs for errors and work accordingly based on the error.
  • If the issue still persists, create a service ticket for further assistance.

Problem: Usage Validation Issues During RT Automation

Issue: If the required usage consumption configuration is not configured correctly in Oracle Communications Elastic Charging Engine (ECE) and Oracle Communications Offline Mediation Controller, the usage scenarios fail.

The failure occurs in all the following zone-based pricing and special rating usage scenarios:
MobileProductModels/Supremo5GLite/ZoneBasedPricingUsage/ItalyAndSpain
MobileProductModels/Supremo5GPremium/ZoneBasedPricingUsage/GreeceAndROW
MobileProductModels/Supremo5GUnlimited/ZoneBasedPricingUsage/Mexico&Germany
HomePhoneProductModels/SupremoStarterHomePhone/ZoneBasedPricingUsage/GreeceAndGermany
HomePhoneProductModels/SupremoStarterHomePhone/ZoneBasedPricingUsage/ItalyIndiaAndLocal
HomePhoneProductModels/SupremoStarterHomePhone/SpecialRating/ModifySpecialRatingListAndRunUsage/DeleteAndAddSpecialRatingNumbers
HomePhoneProductModels/SupremoStarterHomePhone/SpecialRating/NonSpecialRatingNumbersUsage
HomePhoneProductModels/SupremoStarterHomePhone/SpecialRating/SpecialRatingNumbersUsage
HomePhoneProductModels/SupremoPremiumHomePhone/ZoneBasedPricingUsage/SpainAndMexico
HomePhoneProductModels/SupremoPremiumHomePhone/SpecialRating/ModifySpecialRatingListAndRunUsage/AddNewSpecialRatingNumbers
HomePhoneProductModels/SupremoPremiumHomePhone/SpecialRating/ModifySpecialRatingListAndRunUsage/DeleteSpecialRatingNumbers
HomePhoneProductModels/SupremoPremiumHomePhone/SpecialRating/SpecialRatingNumbersUsage

Solution:

  • Verify if all accounts are available in ECE.

    If accounts are missing, validate the BRM to AIA integration and ensure account synchronization is correctly configured.

  • Check EPDC pod logs for any builder-related failures, which may occur due to improper synchronization between ECE and Offline Mediation Controller.
    Restart the ECE and Offline Mediation Controller services using the below command:
     kubectl rollout restart sts ecs -n <Monetisation_namespace>
  • Ensure all required configurations are correctly set up in Offline Mediation Controller as per the deployment and integration guidelines. For more information on the deployment and integration guidelines, see Oracle Communications Offline Mediation Controller Cloud Native Installation and Administration Guide.
  • If the issue still exists, create a service ticket for further assistance.