Deploying Reporting and Data Export

High-Level Architecture

The RDE is a microservice with its own release cycle. It is not included in the CloudBlue Commerce distribution package by default and must be installed on the platform as an APS application.

The RDE microservice consists of two components:

  • RDE UI, hosted on the management node
  • RDE backend, hosted in a separate container on the service node with installed Kubernetes

Installation Prerequisites

Before importing the RDE APS package, ensure that:

Hardware Requirements

The minimum Kubernetes resources required for the microservice deployment, including on-premise Kubernetes cluster deployment, are as follows:

Requests:
  • CPU:
1
  • Memory:
1280Mi

Firewall Requirements

The following ports must be open on the micro-service node and the BSS database replica node:

From To Protocol Port Purpose
CloudBlue Commerce Management Node Micro-service node TCP 8081 For access to the RDE service back end (HTTPS is used for communication)
Micro-services node BSS database replica node TCP 5432 For connection to the PostgreSQL database

How to Install RDE

Before installing the RDE application, select from one option:

You also need to restart the following services on the management node before RDE installation:

  • pau
  • pa-agent

After installing the RDE application, the following scenarios will be available for resellers:

  • Generating a one-time report with aggregated billing data
  • Configuring generation of periodic reports with aggregated billing data

How to Upgrade RDE to the Latest Version

The upgrade procedure is different depending on your currently installed RDE version.

Your current RDE version is 1.3-117 or later

  • To upgrade the existing application with MS Azure cloud storage, run this command:

    # helm upgrade rateddataexport a8n/rateddataexport --version <version>--set jdbcconnectionparams='?sslmode=require&ApplicationName=rateddataexport' --set devmode.enabled=false
  • To upgrade the existing application to store new reports in SFTP storage instead of MS Azure, run this command:

    helm upgrade rateddataexport a8n/rateddataexport --version <version> --set sftp_host=<SFTP_HOST> --set sftp_port=<SFTP_PORT> --set sftp_login=<SFTP_LOGIN> --set sftp_password=<SFTP_PASSWORD> --set azconnstr=' ' --reuse-values