About the BRM Cloud Native Deployment Packages

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 BRM Pods

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

Table 2-1 BRM Pods

Pod Name	Replica Type (1)	Container Port	Container Port Name	Service Type
cm	Multi-replica	11960 (cm) 11961 (perflib, metrics) 11932 (eai-java-server, metrics)	cm-pcp-port cm-perflib-port eai-prom-port	ClusterIP
dm-kafka	Multi-replica	12010 12012 (metrics)	dm-pcp-port dm-prom-port	ClusterIP
dm-oracle	Multi-replica	12950 12951 (perflib, metrics)	dm-pcp-port dm-perflib-port	ClusterIP
brm-sdk	Single-replica	N/A	N/A	ClusterIP
init-db	Single-replica	N/A	N/A	ClusterIP
dm-vertex	Single-replica	31247	dm-vertex-port	ClusterIP
dm-eai	Multi-replica	11970	dm-pcp-port	ClusterIP
dm-invoice	Multi-replica	27777	dm-pcp-port	ClusterIP
dm-ldap	Multi-replica	12850	dm-pcp-port	ClusterIP
dm-prov-telco	Multi-replica	20315	dm-pcp-port	ClusterIP
ecs	Multi-replica	9999	N/A	NodePort
configloader	Single-replica	9999	N/A	NodePort
pricingupdater	Single-replica	9999	N/A	NodePort
brmgateway	Multi-instance, 1 instance per schema	9999	N/A	NodePort
customerupdater	Multi-instance, 1 instance per schema	9999	N/A	NodePort
diametergateway	Multi-instance, each instance can have 1 replica	9999	N/A	NodePort
emgateway	Multi-replica	9999	N/A	NodePort
httpgateway	Multi-replica	9999	N/A	NodePort
radiusgateway	Multi-replica	9999	N/A	NodePort
ratedeventformatter	Multi-instance, 1 instance required for each role on each schema ⁽²⁾	9999	N/A	NodePort
realtime-pipe	Multi-replica	24000	rtp	ClusterIP
batch-wireless-pipe	Single-replica	24001	batchpipe	ClusterIP
roampipe	Single-replica	24002	roampipe	ClusterIP
rel-daemon	Multi-replica	N/A	N/A	ClusterIP
rem	Multi-instance, 1 instance per schema	8080	rem-metrics	ClusterIP
batch-controller	Multi-replica	N/A	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
dm-fusa	Multi-replica	15772	dm-fusa-port	ClusterIP
dm-email	Multi-replica	17777	cm-pcp-port	ClusterIP
pje	Multi-replica	31960	pje-pcp-port	ClusterIP
amt	Single-replica	N/A	N/A	ClusterIP
brm_apps_jobs	N/A	N/A	N/A	N/A
config_job	N/A	N/A	N/A	ClusterIP

Note:

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.
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-2 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-2 Client Pods and Images

Pod	Replica Type (1)	Image	Container Port	Service Type	Access URL
pdc	Single-replica	pdc:15.0.x.0.0	8001 (HTTP)⁽²⁾	NodePort	host:port/pdc
pdcrsm	Multi-replica	pdcrsm:15.0.x.0.0	31000 8080	Container Port, ClusterIP	host:port/productCatalogManagement
pcc	Single-replica	pcc:15.0.x.0.0	7012 (HTTPS)	NodePort	host:port/pcc
billingcare	Multi-replica⁽³⁾	billingcare:15.0.x.0.0	7011 (admin-server) 8001 (managed-serverN and cluster-1) 8080 (monitoring-exporter, if monitoring is enabled)	ClusterIP	host:port/bc
bcws	Multi-replica⁽³⁾	bcws:15.0.x.0.0	7011 (admin-server) 8001 (managed-serverN and cluster-1) 8080 (monitoring-exporter, if monitoring is enabled)	ClusterIP	host:port/bcws
boc	multi-replica	boc:15.0.x.0.0	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:15.0.x.0.0	30000/30001	NodePort	host:port/brm
wsm-wls	Multi-replica	brm_wsm_wls:15.0.x.0.0	7001 (admin-server) 8001 (managed-serverN and cluster-1) 8080 (monitoring-exporter, metrics)	default default metrics	host:port/BrmWebServices
N/A	N/A	webhook:15.0.x.0.0	N/A	N/A	N/A

Note:

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.
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.
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-3 lists the PVCs and pods in a BRM cloud native deployment.

Table 2-3 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
common-semaphore	batch-wireless-pipe realtime-pipe roampipe
ctqdir	dm-vertex
custom-job-file	brm-apps-job cm
data	batch-wireless-pipe roampipe
fusa-temp	dm-fusa
oms-rel-archive	rel-daemon
oms-rel-input	rel-daemon
oms-rel-reject	rel-daemon
oms-uel-archive	batch-controller
oms-uel-input	batch-controller
oms-uel-reject	batch-controller
outputcdr	batch-wireless-pipe rel-daemon
outputreject	batch-wireless-pipe rel-daemon
pipelinelog	batch-wireless-pipe roampipe
pdc-app-pvc	PDC pod (PDC Application Container)
pdc-brm-pvc	PDC pod (PDC BRM Integration Pack)
roamoutputcdr	roampipe rel-daemon
roamoutputreject	roampipe rel-daemon
service-order	dm-prov-telco brm-apps-job
virtual-time	All pods

Table 2-4 lists the services associated with ECE.

Table 2-4 ECE Services

Service Name	Service Type	Port	Description
ece-brmgateway	NodePort	External port	BRM Gateway service
ece-dgw	NodePort	External port	Diameter Gateway service
ece-emg	NodePort	External port	EM Gateway service
ece-http	NodePort	External port	HTTP Gateway service
ece-rgw	NodePort	External port	RADIUS Gateway service