My Oracle Support Banner

BRM12 CN - How To Deploy New Billingcare After Adding New Custom Fields (Doc ID 2831500.1)

Last updated on JANUARY 07, 2022

Applies to:

Oracle Communications Billing and Revenue Management - Version and later
Information in this document applies to any platform.


On : Cloud Native Billing and Revenue Management (BRM) version, Billing Care (BC), Billing Care Web Services (BCWS)

Given the following scenario:

- out of the box (OOTB) /payinfo/cc class has been customized by adding 4 new custom fields

- and customfields.jar were generated as per procedure from here:

- in cloud native environment running BRM, manually added new custom fields definition in of both BC and BCWS by executing this procedure:

  1. Change the inside the PVC. To be noted customfields.jar has not been added to PVC
  2. Stop BCWS by scaling it down to 0. kubectl edit domain bcws-domain and change serverStartPolicy: IF_NEEDED to serverStartPolicy: NEVER . This will stop BCWS
  3. Start BCWS . kubectl edit domain bcws-domain and change serverStartPolicy back to IF_NEEDED

- after above changes, BC and BCWS were able to get details of accounts having /payinfo/cc linked

- one is now trying to create new docker image to include these changes, as "the manual installation has been removed and base files restored by the cluster".

How it can be done?


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.