D ECE Configuration File Reference

This appendix describes Oracle Communications Billing and Revenue Management Elastic Charging Engine (ECE) configuration files.

Topics in this document:

• System Configuration Files

• Business Configuration Files

System Configuration Files

Table D-1 summarizes configuration files relevant to tuning the ECE system, such as tuning Oracle Coherence and JVM parameters. All system configuration files are in ECE_home/config.

Table D-1 ECE System Configuration File Reference

File Name	Description
charging-cache-config.xml	Used for configuring Coherence.
charging-coherence-override-dev.xml	Used for configuring Coherence. Used for development.
charging-coherence-override-prod.xml	Used for configuring Coherence. Used for production.
charging-coherence-override-secure-prod.xml	Used for configuring Coherence. Used for production. When you enable SSL, the key and store passwords must be set in this file.
charging-context.xml	System configuration file. Do not modify.
charging-pof-config.xml	System configuration file. Do not modify.
coherence-jaas.config	Used for Java security. Do not modify.
defaultTuningProfile.properties	Used for setting JVM tuning parameters, such as those for garbage collection and heap size. Typically, the default values do not need to be modified. See "Configuring JVM Tuning Parameters".
ece.properties	System configuration file.
eceTopology.conf	Used for specifying the physical server machines for each Coherence node in the cluster.
groovysh.profile	System configuration file. Do not modify.
JMSConfiguration.xml	Used for configuring the JMS credentials for the JMS server on which the notification queue (JMS topic) resides. See "Modifying JMS Credentials for Publishing External Notifications" in ECE Implementing Charging.
jmxremote.password	Used for JXM security. See "Performing a Secure ECE Installation " in BRM Security Guide.
jrds.groovy	System configuration file. Do not modify.
log4j2.xml	Used for configuring logging for each node in the cluster. This file is used only initially before the ECE system is running. After ECE is running, you use JConsole to set logging.
Notification.xsd	XSD schema file for XML notification messages generated by ECE.
permissions.xml	Used for authorization of nodes in the Coherence cluster. See "Performing a Secure ECE Installation " in BRM Security Guide.
sdkTuningProfile.properties	Used for configuring tuning parameters for the sample programs included in the ECE SDK. Typically, the default values do not need to be modified.
server.jks	Used for authentication of nodes in the Coherence cluster (Coherence cluster security). Do not modify. See "Setting Up and Managing Elastic Charging Engine Security".

Business Configuration Files

Table D-2 summarizes configuration files relevant to setting ECE charging business parameters and runtime configurations. All business configuration files are in ECE_home/config/management.

For information about configuring usage-charging parameters, see "Managing Online Charging Sessions" in BRM ECE Implementing Charging.

Table D-2 ECE Business Configuration File Reference

File Name	Description
charging-settings.xml	Used for configuring charging business rules and runtime configurations. See "Managing Online Charging Sessions" in BRM ECE Implementing Charging.
migration-configuration.xml	Used for specifying the directories from which you want the data-loading utilities (configuration loader, pricing loader, and customer loader) to load data.
test-tools.xml	Used for specifying developer tool settings.