Downloading and Deploying the Reference Solution

6 Downloading and Deploying the Reference Solution

This chapter provides information about downloading and deploying the Digital Business Experience Reference Solution (the reference solution).

Before you start to download and deploy the reference solution:

Learn about the reference solution. See About the Reference Solution in Oracle Communications Digital Business Experience Concepts for more details.
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.
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.
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. Hence, you must install STAP first so that you can deploy the reference solution package.
After installing STAP, set up STAP Design Experience (STAP DE). See Setting Up The STAP Design Experience for more information.

Prerequisites

Following are the prerequisites for installing the reference solution:

Verify all the REST API end points for various applications and SSH keys, ensuring proper connectivity before running the automation.
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.
Ensure to edit the config files for pre-automation. See Editing the config files for more information.
Run the run_publish.sh script for pre-automation. See Running the script for more information.
Verify if the seed data is created properly on Launch, PDC, and BRM. See About the Seed Data in Oracle Communictions 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 on the Launch UI is Ready to Publish.

Deploying the Reference Solution Package

To deploy the reference solution package:

Download the reference solution pack from the Oracle software delivery website, located at:
```
http://edelivery.oracle.com
```
Run the following command from the STAP environment to unzip the reference solution pack:
```
unzip oc-stap-otc-testlib-version.zip
```

Run the following command to edit the run_publish.sh file:

vi  oc-stap-otc-testlib-version/run_publish.sh
Replace:
export JAVA_HOME="/home/java/jdk-xx.x.x" with the correct path to JDK
export STAP_HOME=/home/STAP-DE-PATH  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"

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:
```
/E2E-Automation/Publish-Automation/config/environments/TdaasEnvironment.properties
/E2E-Automation/Publish-Automation/config/environments/TaaS-TES-environment.properties
```
Run the following commands in stages to deploy and publish the reference solution pack to the Digital Business Experience environment:
```
sh run_publish.sh -h
      Usage: sh publish.sh -w <STAP_WORKSPACE_NAME>
      Step 1 - Edit the run_publish.sh files to point to your STAP DE location.
      Step 2 - Edit the TaaS-TES-environment.properties and TdaasEnvironment.properties files to
      point to your STAP target deployment location.
      Step 3 - Edit the config.properties and environment files in your workspace.
      Step 4 - Run the run_publish.sh script with the workspace you want to publish and run on your
      STAP deployment.
      For example:
      /E2E-Automation/STAP_Workspace_Name/config/publish/tdaasEnvironment.properties
      /E2E-Automation/STAP_Workspace_Name/config/publish/environment.properties
      /E2E-Automation/STAP_Workspace_Name/config/publish/persistence-volume-environment.properties
      /E2E-Automation/STAP_Workspace_Name/config/publish/publish-automation.properties
      /E2E-Automation/STAP_Workspace_Name/config/environments/* --> all files
```
Note:
- In the above command, you can replace STAP_WORKSPACE_NAME with Pre-Automation, SD-Automation, DT-Automation, or RT-Automation based on the workspace you want to publish.
- You must publish the workspaces in the following order:
  1. Edit the config files for Pre-Automation workspace, then run the sh replace_token_paths.sh command to update the scenario files, and then publish the Pre-Automation workspace.
  2. Edit the config files for SD-Automation workspace, and then publish the SD-Automation workspace.
  3. Edit the config files for DT-Automation workspace, and then publish the DT-Automation workspace.
  4. Edit the config files for RT-Automation workspace, and then publish the RT-Automation workspace.
To implement all the run time scenarios, run the following command:
```
sh run_rt_automation.sh --all
```

To implement a specific run time scenario, run the following command:

sh run_rt_automation.sh --scenario_name
For example: sh run_rt_automation.sh --BroadbandProductModels

To implement the bundled sample orders, run the following command:

sh run_rt_automation.sh --scenario_name/subfolder_name
For example: sh run_rt_automation.sh --MobileProductModels/Supremo5GUnlimited/SampleOrder

Troubleshooting the Reference Solution

This section provides guidelines to help you troubleshoot problems while deploying the reference solution.

Seed Data Issues

If the loading of BRM data fails:
- Load the following files from the BRM scenario data folder in the cm pod:
  - customservices_proximity.podl
  - customservices_OTT_VOIP_dtv_dmusic.podl
- Sync the new events and services by restarting the cm, dm, and syncpdc pods.
If the importing of PDC data fails, 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.