1. Cloud Native Deployment Guide
  2. Getting Started with BRM Cloud Native Deployment
  3. About Configuring and Deploying Your BRM Cloud Native Environment

3 About Configuring and Deploying Your BRM Cloud Native Environment

Learn about the high-level steps for configuring and deploying your Oracle Communications Billing and Revenue Management (BRM) cloud native environment.

Topics in this document:

About Configuring and Deploying BRM Cloud Native

You install the BRM cloud native deployment package by configuring and deploying its Helm charts. The Helm charts include YAML template descriptors for all Kubernetes resources and a values.yaml file that provides default configuration values for each chart.

When you install a Helm chart, it generates valid Kubernetes manifest files by replacing default values from the values.yaml file with custom values from your override-values.yaml file, and creates Kubernetes resources. Helm calls this a new release. You use the release name to track and maintain this installation.

Note:

This documentation uses the override-values.yaml file name for ease of use, but you can name the file whatever you want.

Table 3-1 describes the Helm charts that are included in the BRM cloud native deployment package.

Table 3-1 BRM Cloud Native Helm Charts

Chart Name Description When to Use

oc-cn-init-db-helm-chart

This chart initializes and upgrades the database schema for BRM server.

  • In initialize mode, it:

    • Creates tables, views, procedures, indexes, and other database objects needed by BRM Server
    • Loads seed data

  • In upgrade mode, it modifies the existing database schema to match the current patch set data model.

Use this chart in initialize mode when you are preparing a new setup of BRM and have an empty database schema.

Use this chart in upgrade mode when you have to upgrade your schema to the latest patch set or interim patch release.

oc-cn-op-job-helm-chart

This chart does the following:

  • Creates WebLogic Server domains for Billing Care, the Billing Care REST API, and Business Operations Center.

  • Installs applications in their respective domains.

  • Populates persistent volumes with domain and application files for sharing between WebLogic Server runtimes.

  • Creates the PDC WebLogic Server RCU prefix. This must be created before deploying PDC WebLogic Application server.

If you want to use Billing Care, Business Operations Center, Pricing Design Center, or the Billing Care REST API, install this chart before you install oc-cn-helm-chart.

oc-cn-helm-chart

This chart does the following:

  • Deploys BRM server, PDC, and PCC.

  • Starts the WebLogic servers for Billing Care, the Billing Care REST API, and Business Operations Center.

  • Exposes web clients as services outside of the cluster.

  • Shares persistent volumes between its services through persistent volume claims.

Install this chart to use the services of BRM server, PDC, PCC, Billing Care, Business Operations Center, or the Billing Care REST API.

oc-cn-ece-helm-chart

This chart does the following:

  • Deploys ECE and its services.

  • Sets up the connection with BRM server and PDC.

  • Configures sharing of persistent volumes with BRM server.

Install this chart to use ECE as your convergent charging solution.

High-Level Installation Tasks

You install BRM cloud native on your system by performing these high-level tasks:
  1. Install all prerequisite software for your BRM cloud native environment.
  2. Prepare your deployment environment by downloading the BRM cloud native deployment package, extracting the Helm charts, and loading the BRM component images.
  3. Configure and deploy the BRM database schema in your cloud native environment.
  4. Configure the BRM cloud native services that you want to include in your system, including:
  5. Deploy the BRM cloud native services in your cloud native environment.