3 Exposing Directories as ConfigMaps

Learn how to expose any directory as a ConfigMap in your Oracle Communications Billing and Revenue Management (BRM) cloud native environment. This decouples environment-specific configuration from your container images.

Topics in this document:

• Configuring a CM ConfigMap Directory

• Configuring an EAI Publisher ConfigMap

Configuring a CM ConfigMap Directory

You can expose the CM directory as a ConfigMap so your BRM cloud native deployment can access custom input files.

To expose the oc-cn-helm-chart/cm_custom_files directory as a ConfigMap, do this:

1. Move your custom input files to the oc-cn-helm-chart/cm_custom_files directory.

2. In your override-values.yaml file for oc-cn-helm-chart, set these keys:

   • ocbrm.cm.custom_files.enable: Set this to true.

   • ocbrm.cm.custom_files.path: Set this to the location of your custom input files, such as /oms/load.

3. In the CM ConfigMap file (configmap_pin_conf_cm.yaml), set the path to your custom input files.

4. Run the helm upgrade command to update your Helm release:

   helm upgrade BrmReleaseName oc-cn-helm-chart --values OverrideValuesFile -n BrmNameSpace

   where:

   • BrmReleaseName is the release name for oc-cn-helm-chart and is used to track this installation instance.

   • OverrideValuesFile is the file name and path to your override-values.yaml file.

   • BrmNameSpace is the namespace in which to create BRM Kubernetes objects for the BRM Helm chart.

Exposing the taxcode_map File Example

This example shows how to expose the taxcodes_map file using the CM ConfigMap.

1. Edit the taxcodes_map file and move it to the oc-cn-helm-chart/cm_custom_files directory.

2. Set these keys in your override-values.yaml file for oc-cn-helm-chart:

   ocbrm.cm.custom_files.enable=true
   ocbrm.cm.custom_files.path=/oms/load

3. In the CM ConfigMap (configmap_pin_conf_cm.yaml), set the path to the taxcodes_map file:

   - fm_rate taxcodes_map /oms/load/taxcodes_map

4. Run the helm upgrade command to update your Helm release:

   helm upgrade BrmReleaseName oc-cn-helm-chart --values OverrideValuesFile -n BrmNameSpace

Configuring an EAI Publisher ConfigMap

The payload configuration file used by the EAI Java Server (eai_js) process can be loaded as a Kubernetes ConfigMap and consumed by eai_js from /oms/payload.

The following payload configuration files are included in the BRM Helm chart and can be mounted as a Kubernetes ConfigMap:

• payloadconfig_ece_sync.xml: This configuration file synchronizes BRM with the ECE rating engine.

• payloadconfig_ifw_sync.xml: This configuration file synchronizes BRM with the batch and real-time rating engine.

• payloadconfig_kafka_sync: This configuration file is for publishing business events from BRM to the Kafka server.

By default, the EAI Java Server uses the payloadconfig_ifw_sync.xml file. To configure it to use a different payload configuration XML file, do the following:

1. Configure your payload configuration file.

2. Copy your payload configuration file to the oc-cn-helm-chart/payload_xml directory.

3. In your override-values.yaml file for oc-cn-helm-chart, set the ocbrm.eai_js.deployment.eaiConfigFile key to the name of your payload configuration file.

4. Run the helm upgrade command to update your Helm release:

   helm upgrade BrmReleaseName oc-cn-helm-chart --values OverrideValuesFile -n BrmNameSpace

   where:

   • BrmReleaseName is the release name for oc-cn-helm-chart and is used to track this installation instance.

   • OverrideValuesFile is the file name and path to your override-values.yaml file.

   • BrmNameSpace is the namespace in which to create BRM Kubernetes objects for the BRM Helm chart.