2 About the BRM Cloud Native Deployment Packages

Learn about the Helm charts and images in the Oracle Communications Billing and Revenue Management (BRM) cloud native deployment package that help you deploy and manage pods of BRM product services in Kubernetes.

Topics in this document:

Overview of the BRM Cloud Native Deployment Package

The BRM cloud native deployment package includes the following:

  • Ready-to-use images and Helm charts to help you orchestrate containers in Kubernetes.

  • Sample Dockerfiles and scripts that you can use as a reference for building your own images.

You can use the images and Helm charts to help you deploy and manage pods of BRM product services in Kubernetes. Communication between pods of services of BRM products is preconfigured in the Helm charts.

About the BRM Component Packages

The BRM cloud native deployment package contains ready-to-use Docker images, a Helm package for deployment in Kubernetes, as well as sample Dockerfiles and scripts that you can use as a reference for building your own images.

Table 2-1 lists all of the component packages that are included with the BRM cloud native deployment package.

Table 2-1 BRM Component Packages

Component Package Name File Name

Oracle Communications Cloud Native Advanced Queuing Data Manager

oc-cn-brm-dm-aq-12.0.0.x.0.tar

Oracle Communications Cloud Native Batch Controller

oc-cn-brm-batch-controller-12.0.0.x.0.tar

Oracle Communications Cloud Native Batch Pipeline

oc-cn-brm-batch-pipeline-12.0.0.x.0.tar

Oracle Communications Cloud Native Billing Care

oc-cn-billingcare-12.0.0.x.0.tar

Oracle Communications Cloud Native BRM Applications

oc-cn-brm-apps-12.0.0.x.0.tar

Oracle Communications Cloud Native BRM Configurator Job

oc-cn-brm-config-jobs-12.0.0.x.0.tar

Oracle Communications Cloud Native Business Operations Center

oc-cn-boc-12.0.0.x.0.tar

Oracle Communications Cloud Native Connection Manager

oc-cn-brm-cm-12.0.0.x.0.tar

Oracle Communications Cloud Native Database Initializer

oc-cn-brm-init-db-12.0.0.x.0.tar

Oracle Communications Cloud Native Database Upgrade

oc-cn-brm-upgrade-12.0.0.x.0.tar

Oracle Communications Cloud Native Email Data Manager

oc-cn-brm-dm-email-12.0.0.x.0.tar

Oracle Communications Cloud Native Enterprise Application Integration Data Manager

oc-cn-brm-dm-eai-12.0.0.x.0.tar

Oracle Communications Cloud Native Enterprise Application Integration Java Server

oc-cn-brm-eai-js-12.0.0.x.0.tar

Oracle Communications Cloud Native Fusa Data Manager

oc-cn-brm-dm-fusa-12.0.0.x.0.tar

Oracle Communications Cloud Native Fusa Simulator

oc-cn-brm-fusa-simulator-12.0.0.x.0.tar

Oracle Communications Cloud Native Invoice Data Manager

oc-cn-brm-dm-invoice-12.0.0.x.0.tar

Oracle Communications Cloud Native Invoice Formatter

oc-cn-brm-invoice-formatter-12.0.0.x.0.tar

Oracle Communications Cloud Native LDAP Data Manager

oc-cn-brm-dm-ldap-12.0.0.x.0.tar

Oracle Communications Cloud Native Oracle Database Manager

oc-cn-brm-dm-oracle-12.0.0.x.0.tar

Oracle Communications Cloud Native Pipeline Configuration Center

oc-cn-pcc-12.0.0.x.0.tar

Oracle Communications Cloud Native Pricing Design Center

Note: PDC REST Services Manager is supported only in PDC 12.0.0.3.0 with Interim Patch 31848489 and later releases.

oc-cn-pdc-12.0.0.x.0_part1of2.tar

oc-cn-pdc-12.0.0.x.0_part2of2.tar

oc-cn-pdcbrminteg-12.0.0.x.0.tar

oc-cn-pdc-rsm-12.0.0.3.0-31848489.tar

Oracle Communications Cloud Native Provisioning Data Manager

oc-cn-brm-dm-prov-telco-12.0.0.x.0.tar

Oracle Communications Cloud Native Rated Event Loader

oc-cn-brm-rel-12.0.0.x.0.tar

Oracle Communications Cloud Native Real-Time Pipeline

oc-cn-brm-realtime-pipeline-12.0.0.x.0.tar

Oracle Communications Cloud Native Roaming Manager

oc-cn-brm-roam-pipeline-12.0.0.x.0.tar

Oracle Communications Cloud Native Synchronization Queue Data Manager

oc-cn-brm-dm-ifw-sync-12.0.0.x.0.tar

Oracle Communications Cloud Native Vertex Data Manager

oc-cn-brm-dm-vertex-12.0.0.x.0.tar

Oracle Communications Cloud Native Web Services Manager

oc-cn-brm-brm_wsm_wls-12.0.0.x.0.tar

oc-cn-brm-brm_wsm_wl_init-12.0.0.x.0.tar

Oracle Communications Cloud Native Database Initializer Helm Chart

oc-cn-init-db-helm-chart-12.0.0.x.0.tgz

Oracle Communications Cloud Native ECE Docker Image

oc-cn-ece-12.0.0.x.0.tar

Oracle Communications Cloud Native Docker Build Files

oc-cn-docker-files-12.0.0.x.0.tgz

Oracle Communications Cloud Native ECE Helm Chart

oc-cn-ece-helm-chart-12.0.0.x.0.tgz

Oracle Communications Cloud Native Helm Chart

oc-cn-helm-chart-12.0.0.x.0.tgz

Oracle Communications Cloud Native Operator Job Chart

oc-cn-op-job-helm-chart-12.0.0.x.0.tgz

About BRM Pods

Table 2-2 lists the pods for BRM whose containers are created and services are exposed through them.

Table 2-2 BRM Pods

Pod Name Replica Type (1) Container Port Container Port Name Service Type

amt

Single-replica

N/A

N/A

N/A

batch-controller

Multi-replica

N/A

N/A

N/A

batch-wireless-pipe

Single-replica

 24001

batchpipe

ClusterIP

brm_apps_jobs

 N/A

N/A

N/A

N/A

brmgateway

Multi-instance, 1 instance per schema

15502

brmgateway

ClusterIP

brm-sdk

Single-replica

N/A

N/A

N/A

cm

Multi-replica

11960 (cm)

11961 (perflib, metrics)

11932 (eai-java-server, metrics)

cm-pcp-port

cm-perflib-port

eai-prom-port

ClusterIP

config_job

N/A

N/A

N/A

N/A

configloader

Single-replica

N/A

N/A

N/A

customerupdater

Multi-instance, 1 instance per schema

31022

N/A

N/A

diametergateway

Multi-instance, each instance can have 1 replica

3868

N/A

NodePort

dm-eai

Multi-replica

11970

dm-pcp-port

ClusterIP

dm-email

Multi-replica

17777

dm-pcp-port

ClusterIP
dm-fusa

Single-replica

15772

dm-fusa-port

ClusterIP

dm-invoice

Multi-replica

27777

dm-pcp-port

ClusterIP

dm-kafka

Multi-replica

12010

12012 (metrics)

dm-pcp-port

dm-prom-port

ClusterIP

dm-ldap

Multi-replica

12850

dm-pcp-port

ClusterIP

dm-oracle

Multi-replica

12950

12951 (perflib, metrics)

dm-pcp-port

dm-perflib-port

ClusterIP

dm-prov-telco

Multi-replica

20315

dm-pcp-port

ClusterIP

dm-vertex

Multi-replica

31274

dm-vertex-port

ClusterIP

ecs

Multi-replica

31022

N/A

N/A

emgateway

Multi-replica

15502

N/A

ClusterIP

formatter

Multi-replica

22272

formatter-port

ClusterIP

fusa-simulator

Single-replica

9780 (answer_s, online simulator)

8780 (answer_b, online simulator)

answer-s-port

answer-b-port

ClusterIP

httpgateway

Multi-replica

8080

N/A

NodePort

init-db

Single-replica

N/A

N/A

N/A

pje

Multi-replica

 31960

pje-pcp-port

ClusterIP

pricingupdater

Single-replica

9999

N/A

N/A

radiusgateway

Multi-replica

1812

N/A

NodePort

ratedeventformatter

Multi-instance, 1 instance required for each role on each schema (2)

9999

N/A

N/A

realtime-pipe

Multi-replica

24000

rtp

ClusterIP

rel-daemon

Multi-replica

N/A

N/A

N/A

rel-job

Single-replica

N/A

N/A

N/A

rel-manager-job

Single-replica

N/A

N/A

N/A

rated-event-manager

Multi-instance, 1 instance per schema

8080

rem-metrics

N/A

roampipe

Single-replica

24002

roampipe

ClusterIP

Note:

  1. The BRM cloud native pods support the following replica types:

    • Multi-replica: You can scale these pods at the Kubernetes level to the number of replicas needed.

    • Single-replica: You cannot scale these pods.

    • Multi-instance: You can scale these pods but not at the Kubernetes level. Instead, a new instance needs to be created and scaling is usually limited.

  2. The ratedeventformatter pod requires one instance for each role on each schema. For example, suppose you have two schemas on two sites. In that case, you create primary and secondary instances for each schema in site 1 and primary and secondary instances for each schema in site 2, for a total of 8 instances.

About Client Pods and Images

Table 2-3 lists the pods and images for PDC, PDC REST Services Manager, Pipeline Configuration Center, Billing Care, Business Operations Center, and BRM REST Services Manager.

Note:

For the list of pods and images for Offline Mediation Controller, see "About Offline Mediation Controller Pods and Images" in Offline Mediation Controller Cloud Native Installation and Administration Guide.

Table 2-3 Client Pods and Images

Pod Replica Type (1) Image (2) Container Port Service Type Access URL

bcws

Multi-replica (4)

bcws:tag

7011 (admin-server)

8001 (managed-serverN and cluster-1)

8080 (monitoring-exporter, if monitoring is enabled)

 ClusterIP host:port/bcws

billingcare

Multi-replica (4)

billingcare:tag

7011 (admin-server)

8001 (managed-serverN and cluster-1)

8080 (monitoring-exporter, if monitoring is enabled)

 ClusterIP host:port/bc

boc

Multi-replica

boc:tag

7011 (admin-server)

8001 (managed-serverN and cluster-1)

8080 (monitoring-exporter, if monitoring is enabled)

 ClusterIP host:port/opsdashboard
brm-rest-services-manager

Multi-replica

 brm-rest-services-manager:tag

9090 (HTTP)

8080 (HTTPS)

9060 (adminPort)

 ClusterIP host:port/brm

brm-wsm

Multi-replica

brm_wsm:tag

8080 (HTTP)

8443 (HTTPS)

ClusterIP

host:port/metro

host:port/configurations/endpoints

host:port/configurations/endpoints/default

pcc

Multi-replica

pcc:tag

7012 (HTTPS)

 ClusterIP host:port/pcc

pdc

Single-replica

pdc:tag

8001 (HTTP) (3)

 ClusterIP host:port/pdc

pdcrsm

Multi-replica

pdcrsm:tag

8080

ClusterIP

 host:port/productCatalogManagement

brmdomain

Multi-replica

brm_wsm_wls:tag

7001 (admin-server)

8001 (managed-serverN and cluster-1)

8080 (monitoring-exporter, metrics)

default

default

metrics

 host:port/BrmWebServices
webhook Single-replica

webhook:tag

8080

 ClusterIP N/A

Note:

  1. The BRM cloud native pods support the following replica types:

    • Multi-replica: You can scale these pods at the Kubernetes level to the number of replicas needed.

    • Single-replica: You cannot scale these pods.

    • Multi-instance: You can scale these pods but not at the Kubernetes level. Instead, a new instance needs to be created and scaling is usually limited.

  2. Replace tag with the release version number, such as 15.1.0.0.0.

  3. If the PDC user sets the t3ChannelPort and t3sChannelPort keys in the values.yaml file, the HTTP, HTTPS, t3Channel, and t3sChannel ports will be NodePort.

  4. The Billing Care and Billing Care REST API pods support multi-replica managed services with scaling done through WebLogic Kubernetes Operator.

About BRM PVCs and Pods

Table 2-4 lists the PVCs and pods in a BRM cloud native deployment.

Table 2-4 List of PVCs in BRM Server

PVC Name Pods

bcws-domain-domain-pvc

bcws-domain-deployer

bcws-domain-admin-server

bcws-domain-managed-serverN

bcws-domain-batch-payment-pvc

bcws-domain-deployer

bcws-domain-admin-server

bcws-domain-managed-serverN

billingcare-domain-domain-pvc

billingcare-domain-deployer

billingcare-domain-admin-server

billingcare-domain-managed-serverN

billingcare-domain-batch-payment-pvc

billingcare-domain-deployer

billingcare-domain-admin-server

billingcare-domain-managed-serverN

boc-domain-domain-pvc

boc-domain-deployer

boc-domain-admin-server

boc-domain-managed-serverN

brm-sdk

brm-sdk

cmt-pvc

brm-apps-job

pje

common-semaphore

batch-wireless-pipe

realtime-pipe

roampipe

ctqdir

dm-vertex

custom-job-file

brm-apps-job

cm

data

batch-wireless-pipe

roampipe

dm-kafka

dm-kafka

fusa-temp

dm-fusa

oms-rel-archive

rel-daemon

rel-job

oms-rel-data

rel-daemon

rel-manager-job

oms-rel-input

rel-daemon

rel-job

oms-rel-reject

rel-daemon

rel-job

oms-rem-archive

rated-event-manager

rel-manager-job

oms-rem-data

rated-event-manager

rel-manager-job

oms-rem-input

rated-event-manager

rel-manager-job

oms-rem-reject

rated-event-manager

rel-manager-job

oms-uel-archive

batch-controller

oms-uel-input

batch-controller

oms-uel-reject

batch-controller

outputcdr

batch-wireless-pipe

rel-daemon

rel-job

outputreject

batch-wireless-pipe

rel-daemon

rel-job

pipelinelog

batch-wireless-pipe

roampipe

pdc-app-pvc

PDC pod (PDC Application Container)

pdc-brm-pvc

PDC pod (PDC BRM Integration Pack)

roamoutputcdr

rel-daemon

rel-job

roampipe

roamoutputreject

rel-daemon

rel-job

roampipe

service-order

brm-apps-job

dm-prov-telco

virtual-time

All pods

Table 2-5 lists the services associated with ECE.

Table 2-5 ECE Services

Service Name Service Type Port Description

ece-brmgateway

ClusterIP

15502

BRM Gateway service

ece-cdrgateway

ClusterIP

8084

CDR Gateway service

ece-dgw

NodePort

3868

Diameter Gateway service

ece-emg

ClusterIP

External port

EM Gateway service

ece-jmx-service-external

NodePort

External port

JMX service

ece-http

NodePort

8080

31500

HTTP Gateway service

ece-monitoringagent-service-external

NodePort

External port

Monitoring agent service

ece-rgw

NodePort

1812

RADIUS Gateway service

Software Compatibility

To run, manage, and monitor your BRM cloud native deployment, ensure you use the latest versions of all compatible software. See BRM Compatibility Matrix.

Migrating from On-Premise BRM to BRM Cloud Native

Learn how to migrate from an on-premise release of Oracle Communications Billing and Revenue Management (BRM) 7.5.x or 12.x to a BRM 15.1 cloud native release.

Topics in this document:

Merging Split TAR Files

To improve download performance, BRM images that have TAR files larger than 4 GB have been split into multiple parts. You can merge the split TAR files before tagging and pushing them to the registry by entering this command:

cat oc-cn-Component-12.0.0.x.0_part* > oc-cn-Component-12.0.0.x.0.tar

where Component is the short name of the BRM component, such as pdc for Pricing Design Center (PDC).

For example, to merge the PDC TAR files into a single TAR file, you'd enter this command:

cat oc-cn-pdc-12.0.0.x.0_part* > oc-cn-pdc-12.0.0.x.0.tar

Loading BRM Component Images from OSDC

If you download from the Oracle software delivery website, the images are provided in TAR files. After downloading the TAR files, load them as images into the Docker system.

For example, to load the Oracle Communications Cloud Native Connection Manager image into Podman, you would do this:

  1. Download the oc-cn-brm-cm-15.0.0.x.0.tar file to the system where Docker is installed.

  2. Load the Connection Manager image using the following command:

    podman load --input oc-cn-brm-cm-15.0.0.x.0.tar

  3. Verify that the image is loaded correctly using the following command:

    podman images cm:15.0.0.x.0

    The image details should be listed in one row.

If you use an internal registry to access images from different Kubernetes nodes, push the images from the local system to the registry server. For example, if the registry is identified by RepoHost:RepoPort, you'd push the CM image to the registry like this:

  1. Tag the image with the registry server using the following command:

    podman tag cm:15.0.0.0.0 RepoHost:RepoPort/cm:15.0.0.x.0

  2. Push the image to the registry server using the following command:

    podman push RepoHost:RepoPort/cm:15.0.0.x.0