Table 10-1 lists the keys that directly impact ECE deployment. Add these keys to your override-values.yaml file for oc-cn-ece-helm-chart. In the table, component-name should be replaced with the name of the ECE component, such as emgateway, radiusgateway, diametergateway, httpgateway, and ratedeventformatter.

BRMDATABASEPASSWORD:  
   - schema: 1     
     PASSWORD: Password   
   - schema: 2     
     PASSWORD: Password

To complete the configuration for SSL setup in ECE:

1. Configure the SSL KeyStores by doing one of the following:

   • Generate the Identity and Trust KeyStores and then move your files, such as identity.p12 and trust.p12, under the oc-cn-ece-helm-chart/ece/keystore directory.

   • Pre-create the Kubernetes Secret for the Identity and Trust KeyStore files and set the secretEnv.extECESecret key in your override-values.yaml file for both oc-cn-ece-helm-chart.

     For more information, see "Managing KeyStore Certificates and Wallets" in BRM Cloud Native System Administrator's Guide.

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

   • sslconnectioncertificates.SSLENABLED: Set this to true.

   • sslEnabled: Set this to true in emGatewayConfigurations, httpGatewayConfigurations, and BRMConnectionConfiguration.

   • migration.pricingUpdater.keyStoreLocation: Set this to /home/charging/opt/ECE/oceceserver/config/client.jks.

   • charging.brmWalletServerLocation: Set this to /home/charging/wallet/brmwallet/server/cwallet.sso.

   • charging.brmWalletClientLocation: Set this to /home/charging/wallet/brmwallet/client/cwallet.sso.

   • charging.brmWalletLocation: Set this to /home/charging/wallet/brmwallet.

   • charging.emGatewayConfigurations.emGatewayConfigurationList.emGateway1Config.wallet: Set this to the BRM wallet location.

   • charging.emGatewayConfigurations.emGatewayConfigurationList.emGateway2Config.wallet: Set this to the BRM wallet location.

   • charging.radiusGatewayConfigurations.wallet: Set this to the BRM wallet location.

   • charging.connectionConfigurations.BRMConnectionConfiguration.brmwallet: Set this to the BRM wallet location.

3. Deploy your ECE cloud native services by following the instructions in "Deploying BRM Cloud Native Services".

You specify where the SSL certificates are located by using the createWalletsAsSecrets key in your override-values.yaml file for oc-cn-ece-helm-chart. Set the key to true if your SSL certificates are in the ECE Helm chart, and to false if they are in PVs.

To connect your ECE cloud native services to an SSL-enabled Oracle database:

1. If your SSL certificates are in the ECE PVs (createWalletsAsSecrets is false), do the following:

   1. Prepare for persistence schema creation.

      1. Go to the oc-cn-ece-helm-chart directory, and create a directory named secrets/db_wallets/ece_ssl_db_wallet/schema1.

      2. Save the ECE SSL database wallet to the schema1 directory.

      3. From the oc-cn-ece-helm-chart directory, grant the necessary permissions to the secrets directory:

         chmod -R 775 secrets

      4. (For multischema systems only) Create a directory named schema2 in the ece_ssl_db_wallet directory and copy the ECE SSL database wallet to the schema2 directory.

   2. Configure the SSL database wallets in the external volume mount.

      1. Go to the external volume mount location (external-pvc).

      2. Create a directory named ece_ssl_db_wallet/schema1.

      3. Save the ECE SSL database wallet to the ece_ssl_db_wallet/schema1 directory.

      4. From the external volume mount location, create a directory named brm_ssl_db_wallet/schema1.

      5. Save the BRM SSL database wallet to the brm_ssl_db_wallet/schema1 directory.

      6. From the external volume mount location, grant the necessary permissions to both new directories:

         chmod -R 775 ece_ssl_db_wallet brm_ssl_db_wallet

      7. (For multischema systems only) Create a schema2 directory inside both the ece_ssl_db_wallet and brm_ssl_db_wallet directories. Then, copy the ECE SSL certificates to the ece_ssl_db_wallet/schema2 directory, and the BRM SSL certificates to the brm_ssl_db_wallet/schema2 directory.

2. If your SSL certificates are in the ECE Helm chart (createWalletsAsSecrets is true), do the following:

   1. Place your ECE certificate files in the appropriate oc-cn-ece-helm-chart/secrets/db_wallets/ece_ssl_db_wallet/scheman directory, where n is the schema number.

   2. Place your BRM certificate files in the appropriate oc-cn-ece-helm-chart/secrets/db_wallets/brm_ssl_db_wallet/scheman directory, where n is the schema number.

3. Configure ECE for an SSL-enabled Oracle persistence database.

   Under the charging.connectionConfigurations.OraclePersistenceConnectionConfigurations section, set the following keys:

   • dbSSLEnabled: Set this to true.

   • dbSSLType: Set this to the type of SSL connection required for connecting to the database: oneway, twoway, or none.

   • sslServerCertDN: Set this to the SSL server certificate distinguished name (DN). The default is DC=local,DC=oracle,CN=pindb.

   • trustStoreLocation:

     1. If createWalletsAsSecrets is false, set this to /home/charging/ext/ece_ssl_db_wallet/schema1/cwallet.sso.

     2. If createWalletsAsSecrets is true, set this to certificate file name.

   • trustStoreType: Set this to the TrustStore file type: SSO or PKCS12.

4. Configure customerUpdater for an SSL-enabled Oracle AQ database queue.

   Under the customerUpdater.customerUpdaterList.oracleQueueConnectionConfiguration section, set the following keys:

   • dbSSLEnabled: Set this to true.

   • dbSSLType: Set this to the type of SSL connection required for connecting to the database: oneway, twoway, or none.

   • sslServerCertDN: Set this to the SSL server certificate distinguished name (DN). The default is DC=local,DC=oracle,CN=pindb.

   • trustStoreLocation:

     1. If createWalletsAsSecrets is false, set this to /home/charging/ext/brm_ssl_db_wallet/schema1/cwallet.sso.

     2. If createWalletsAsSecrets is true, set this to certificate_file_name.

   • trustStoreType: Set this to the TrustStore file type: SSO or PKCS12.

   Note:

   For database connectivity, ECE supports only the database service name and not the database service ID. Therefore, set the following keys to the database service name:

   • charging.connectionConfigurations.OraclePersistenceConnectionConfigurations.sid

   • customerUpdater.customerUpdaterList.oracleQueueConnectionConfiguration.sid

5. Configure your Oracle database to connect to the SSL-enabled BRM and ECE databases:

   1. Copy the tnsnames.ora and sqlnet.ora files from your SSL database host to your ECE cloud native instance.

   2. On your ECE cloud native instance, go to the ECE Helm chart directory.

   3. Create the ora_files/ece and ora_files/brm directories.

   4. Copy the ECE database tnsnames.ora and sqlnet.ora files to the oc-cn-ece-helm-chart/ora_files/ece/ directory.

   5. In the oc-cn-ece-helm-chart/ora_files/ece/sqlnet.ora file, set the wallet location to /home/charging/opt/ECE/oceceserver/config/ece_ssl_db_wallet/schema1:

      WALLET_LOCATION =
         (SOURCE =
           (METHOD = FILE)
           (METHOD_DATA =
             (DIRECTORY = /home/charging/opt/ECE/oceceserver/config/ece_ssl_db_wallet/schema1)
             )
         )

   6. Copy the BRM database tnsnames.ora and sqlnet.ora files to the oc-cn-ece-helm-chart/ora_files/brm directory.

   7. In the oc-cn-ece-helm-chart/ora_files/brm/sqlnet.ora file, set the wallet location to /home/charging/opt/ECE/oceceserver/config/brm_ssl_db_wallet/schema1:

      WALLET_LOCATION =
         (SOURCE =
           (METHOD = FILE)
           (METHOD_DATA =
             (DIRECTORY = /home/charging/opt/ECE/oceceserver/config/brm_ssl_db_wallet/schema1)
             )
         )

   8. From the ECE Helm chart directory, grant the permissions for the ora_files directory:

      chmod -R 775 ora_files/

   9. Copy the ora_files directory to the external PV mount location.

6. If createWalletsAsSecrets is true, do the following in the ECE Cloud Native environment:

   1. Place the SSL Certificates in the following directory structure inside the Helm chart:

      • secrets/jms/brmgateway/

      • secrets/jms/diametergateway/

      • secrets/jms/ecs/

      • secrets/kafka/

      • secrets/pdc/

   2. If the SSL certificates are deployed as external secrets, provide the respective secret names and certificate keys in your values.yaml file or in an override file:

      secretEnv: 
        extECESecret: external_secret_name
      customerUpdater: 
        customerUpdaterList: 
          - oracleQueueConnectionConfiguration:
               trustStoreLocation: certificate_key
               extBRMDBSSLWalletSecret: external_secret_name 
      charging: 
        connectionConfigurations: 
          oraclePersistenceConnectionConfigurations: 
            - trustStoreLocation: certificate_key 
              extPersistenceDBSSLWalletSecret: external_secret_name
      charging:
        kafkaConfigurations:
          kafkaConfigurationList:
            - kafkaTrustStoreLocation: certificate_key
              extKafkaTrustStoreSecret: external_secret_name
      migration:
        pricingUpdater:
          keyStoreLocation: certificate_key
          extPDCKeyStoreSecret: external_secret_name
      JMSConfiguration:
        NotificationQueue:
          - KeyStoreLocation: certificate_key
            extJMSKeyStoreSecret: external_secret_name
        BRMGatewayNotificationQueue:
          - KeyStoreLocation: certificate_key
            extJMSKeyStoreSecret: external_secret_name
        DiameterGatewayNotificationQueue:
          - KeyStoreLocation: certificate_key
            extJMSKeyStoreSecret: external_secret_name

      For more information on this configuration for the HTTP Gateway, see "Adding Elastic Charging Engine Keys".

The ECE container requires Kubernetes volume mounts for third-party libraries. The third-party volume mount shares the third-party libraries required by ECE from the host system with the container file system. For the list of third-party libraries to download, see BRM Compatibility Matrix. Place the library files under the third-party volume mount.

The default configuration comes with a hostPath PersistentVolume. For more information, see "Configure a Pod to Use a PersistentVolume for Storage" in Kubernetes Tasks.

To use a different type of PersistentVolume, modify the oc-cn-ece-helm-chart/templates/ece-pvc.yaml file.

To load custom Diameter AVPs into your ECE cloud native environment:

1. Create a diameter directory inside external-pvc.

2. Move the custom AVP file, such as dictionary_custom.xml, to the diameter directory.

3. If you need to load a custom AVP after ECE is set up, restart the diametergateway pod by doing the following:

   1. Increment the diametergateway.diametergatewayList..restartCount key by 1.

   2. Run the helm upgrade command to update the release.

You can configure ECE cloud native to capture any overage amounts by prepaid customers during an active session, which can help you prevent revenue leakage. If the network reports that the number of used units during a session is greater than a customer's available allowance, ECE cloud native charges the customer up to the available allowance. It can then create an overage record with information about the overage amount and sends it to the ECE Overage topic. You can create a custom solution for reprocessing the overage amount later on.

For example, assume a customer has a prepaid balance of 100 minutes, but uses 130 minutes during a session. ECE cloud native would charge the customer for 100 minutes, create an overage record for the remaining 30 minutes of usage, and then write the overage topic to the ECE Overage Kafka topic.

When the prepaid usage overage is disabled, ECE cloud native charges the customer for the full amount regardless of the amount of funds in the customer's balance.

To configure ECE cloud native to support prepaid usage overage, do the following:

• Ensure that ECE cloud native is connected to your Kafka Server

• Enable ECE cloud native to support prepaid usage overage

• Create an ECE Overage topic in your Kafka Server

To do so, set the following keys in your override-values.yaml file for oc-cn-ece-helm-chart and then run the helm upgrade command:

• charging.kafkaConfigurations.kafkaConfigurationList.*: Specify how to connect ECE to your Kafka Server.

• charging.server.checkReservationOverImpact: Set this to true.

• charging.kafkaConfigurations.kafkaConfigurationList.overageTopicName: Set this to the name of the Kafka topic where ECE will publish overage records.

ECE cloud native may occasionally fail to process usage requests. For example, a data usage request could fail because a customer has insufficient funds. You can configure ECE cloud native to publish details about failed usage requests, such as the user ID and request payload, to the ECE failure topic in your Kafka server. Later on, you can reprocess the usage requests or view the failure details for analysis and reporting.

To configure ECE cloud native to record failed ECE usage requests:

• Ensure that ECE cloud native is connected your Kafka Server

• Enable the recording of failed ECE usage requests

• Create an ECE failure topic in your Kafka Server

BRM is configured by using the pin_notify and payloadconfig_ece_sync.xml files. To ensure that the BRM pod can access these files for configuring the EAI Java Server (eai_js), they are exposed through the brm_config PVC within the pricingupdater pod. When new metadata is synchronized with ECE, if there are updates to the payload configuration file, it will create a new file in the location which can be accessed and configured in BRM.

For more information, see "Enabling Real-Time Synchronization of BRM and ECE Customer Data Updates" in ECE Implementing Charging.

You can configure ECE cloud native to send notifications to a client application or an external application during an online charging session. For example, ECE cloud native could send a notification when a customer has breached a credit threshold or when a customer needs to request reauthorization.

You can set up ECE cloud native to send notifications by using either Apache Kafka topics or Oracle WebLogic queues:

• Creating an Apache Kafka Notification Topic

• Creating an Oracle WebLogic Notification Queue

If your BRM database contains multiple schemas, you must configure ECE to connect to each schema.

To configure ECE for a BRM multischema database:

1. Open your override-values.yaml file for the oc-cn-ece-helm-chart chart.

2. Specify the password for accessing each schema in the BRM database. To do so, configure these keys for each schema:

   • secretEnv.BRMDATABASEPASSWORD.schema: Set this to the schema number. Enter 1 for the primary schema, 2 for the secondary schema, and so on.

   • secretEnv.BRMDATABASEPASSWORD.PASSWORD: Set this to the schema password.

   This shows example settings for two schemas:

   secretEnv:
      BRMDATABASEPASSWORD:   
         - schema: 1     
           PASSWORD: Password   
         - schema: 2     
           PASSWORD: Password

3. Configure a customerUpdater pod for each schema. To do so, add a -schemaNumber list for each schema. In the list:

   • Set the SchemaNumber key to 1 for the primary schema, 2 for the secondary schema, and so on.

   • Set the amtAckQueueName key to the fully qualified name of the acknowledgment queue to which the pin_amt utility listens to Account Migration Manager (AMM)-related acknowledgment events. The value is in the format primarySchema.ECE_AMT_ACK_QUEUE, where primarySchema is the name of the primary schema.

   • Set the hostName and jdbcUrl keys to their corresponding values for each schema.

   This shows example settings for two schemas:

   customerUpdater:
      customerUpdaterList:
         - schemaNumber: "1"
           coherenceMemberName: "customerupdater1"
           replicas: 1
           jmxEnabled: true
           coherencePort: ""
           jvmGCOpts: ""
           jvmJMXOpts: ""
           jvmCoherenceOpts: ""
           jvmOpts: ""
           jmxport: ""
           restartCount: "0"
           oracleQueueConnectionConfiguration:
              name: "customerupdater1"
              gatewayName: "customerupdater1"
              hostName: ""
              port: "1521"
              sid: "pindb"
              userName: "pin"
              jdbcUrl: ""
              queueName: "IFW_SYNC_QUEUE"
              suspenseQueueName: "ECE_SUSPENSE_QUEUE"
              ackQueueName: "ECE_ACK_QUEUE"
              amtAckQueueName: "pin0101.ECE_AMT_ACK_QUEUE"
              batchSize: "1"
              dbTimeout: "900"
              retryCount: "10"
              retryInterval: "60"
              walletLocation: "/home/charging/wallet/ecewallet/"
    
         - schemaNumber: "2"
           coherenceMemberName: "customerupdater2"
           replicas: 1
           jmxEnabled: true
           coherencePort: ""
           jvmGCOpts: ""
           jvmJMXOpts: ""
           jvmCoherenceOpts: ""
           jvmOpts: ""
           jmxport: ""
           oracleQueueConnectionConfiguration:
              name: "customerupdater2"
              gatewayName: "customerupdater2"
              hostName: ""
              port: "1521"
              sid: "pindb"
              userName: "pin"
              jdbcUrl: ""
              queueName: "IFW_SYNC_QUEUE"
              suspenseQueueName: "ECE_SUSPENSE_QUEUE"
              ackQueueName: "ECE_ACK_QUEUE"
              amtAckQueueName: "pin0101.ECE_AMT_ACK_QUEUE"
              batchSize: "1"
              dbTimeout: "900"
              retryCount: "10"
              retryInterval: "60"
              walletLocation: "/home/charging/wallet/ecewallet/"

4. Configure a ratedEventFormatter pod for processing rated events belonging to each BRM schema. To do so, add a -schemaNumber list for each schema. In the list, set the schemaNumber and partition keys to 1 for the primary schema, 2 for the secondary schema, and so on.

   This shows example settings for two schemas:

   ratedEventFormatter:
      ratedEventFormatterList:
         - schemaNumber: "1"
           replicas: 1
           coherenceMemberName: "ratedeventformatter1"
           jmxEnabled: true
           coherencePort:
           jvmGCOpts: ""
           jvmJMXOpts: ""
           jvmCoherenceOpts: ""
           jvmOpts: ""
           jmxport: ""
           restartCount: "0"
           ratedEventFormatterConfiguration:
              name: "ratedeventformatter1"
              primaryInstanceName: "ratedeventformatter1"
              partition: "1"
              noSQLConnectionName: "noSQLConnection"
              connectionName: "oraclePersistence1"
              threadPoolSize: "6"
              retainDuration: "0"
              ripeDuration: "600"
              checkPointInterval: "6"
              maxPersistenceCatchupTime: "60"
              siteName: ""
              pluginPath: "ece-ratedeventformatter.jar"
              pluginType: "oracle.communication.brm.charging.ratedevent.formatterplugin.internal.BrmCdrPluginDirect"
              pluginName: "brmCdrPlugin1"
              noSQLBatchSize: "25"
    
         - schemaNumber: "2"
           replicas: 1
           coherenceMemberName: "ratedeventformatter2"
           jmxEnabled: true
           coherencePort:
           jvmGCOpts: ""
           jvmJMXOpts: ""
           jvmCoherenceOpts: ""
           jvmOpts: ""
           jmxport: ""
           ratedEventFormatterConfiguration:
              name: "ratedeventformatter2"
              primaryInstanceName: "ratedeventformatter2"
              partition: "2"
              noSQLConnectionName: "noSQLConnection"
              connectionName: "oraclePersistence1"
              threadPoolSize: "6"
              retainDuration: "0"
              ripeDuration: "600"
              checkPointInterval: "6"
              maxPersistenceCatchupTime: "60"
              siteName: ""
              pluginPath: "ece-ratedeventformatter.jar"
              pluginType: "oracle.communication.brm.charging.ratedevent.formatterplugin.internal.BrmCdrPluginDirect"
              pluginName: "brmCdrPlugin1"
              noSQLBatchSize: "25"

5. Save and close your override-values.yaml file for oc-cn-ece-helm-chart.

6. In the oc-cn-ece-helm-chart/templates/charging-settings.yaml ConfigMap, add poidIdConfiguration in itemAssignmentConfig for each schema.

   This shows example settings for three schemas:

   <itemAssignmentConfigconfig-class="oracle.communication.brm.charging.appconfiguration.beans.item.ItemAssignmentConfig" itemAssignmentEnabled="true" delayToleranceIntervalInDays="0" poidPersistenceSafeCount="12000">
      <schemaConfigurationGroup config-class="java.util.ArrayList">                    
         <poidIdConfigurationconfig-class="oracle.communication.brm.charging.appconfiguration.beans.item.PoidIdConfiguration" schemaName="1" poidQuantity="2000000">
         </poidIdConfiguration>                    
         <poidIdConfigurationconfig-class="oracle.communication.brm.charging.appconfiguration.beans.item.PoidIdConfiguration" schemaName="2" poidQuantity="2000000">
         </poidIdConfiguration>                    
         <poidIdConfigurationconfig-class="oracle.communication.brm.charging.appconfiguration.beans.item.PoidIdConfiguration" schemaName="3" poidQuantity="2000000">
         </poidIdConfiguration>                
      </schemaConfigurationGroup>            
   </itemAssignmentConfig>

After you deploy oc-cn-ece-helm-chart in "Deploying BRM Cloud Native Services", the ECE pods will be connected to your BRM database schemas.