This chapter provides reference information for Oracle Communications Billing and Revenue Management Elastic Charging Engine (ECE) utilities that are used for implementing ECE in a BRM charging system.
Use the configLoader utility to load the mediation specification data required for Diameter Gateway into ECE. The mediation specification file enables Diameter Gateway to associate each Diameter request with its respective usage-request builder. Diameter Gateway uses the mediation specification file to determine which product and event type combination applies to an incoming Diameter request.
For more information, see "Network Integration for Gy Interface Requests".
The configLoader utility loads the mediation specification file into configuration objects in the ECE cluster-replicated cache.
For information about editing the mediation specification file, see "Editing the Mediation Specification File".
The configLoader utility supports incremental loading of configuration data held in mediation specification files. If you are updating the mediation specification file, running the configLoader utility loads only the new data.
The configLoader utility also deploys the RADIUS mediation specification file into the ECE cluster.
Any previous RADIUS mediation specification that was in the ECE cluster is overwritten. See ”Configuring the ECE System” in ECE System Administrator's Guide for more information.
Starts configLoader.
Stops configLoader.
Displays the syntax for configLoader.
Look in the ECE_home/oceceserver/logs/configLoader.log file for errors.
To verify that the mediation specification configuration objects were loaded into the ECE cluster-replicated cache, use the query tool to form CohQL queries on the cache name that stores the respective object. For example, for mediation specification files, you would look in the MediationSpecification cache.For more information, see "Testing Scenarios in an Integrated System".
To configure the configLoader utility:
Verify the configuration in the mediation specification file.
Open the ECE_home/oceceserver/config/management/migration-configuration.xml file.
Set the configObjectsDataDirectory parameter to the path of the directory that contains the ECE mediation specification file.
The configLoader utility loads the mediation specification file from this directory into configuration objects in the ECE cluster-replicated cache.
By default, this parameter is set to ECE_home/oceceserver/sample_data/config_data.
Save and close the file.
Use the customerLoader utility to load customer data into ECE from XML files.
In a test environment, use the customerLoader utility to load sample customer data into the ECE customer cache from XML files.
In a production environment, use the customerLoader utility with the -incremental parameter to load customer data incrementally.
Caution:
Do not run the customerLoader utility without the -incremental parameter in a production environment.ECE customer XML data files are used by the customerLoader utility to load customer data into ECE.
ECE customer XML data files contain customer data in ECE XML data file format.
Use the customer file generator to create ECE customer XML data files.
For more information, see the following topics:
About Customer Data
About Customer File Generator
Starts customerLoader.
Stops customerLoader.
Incrementally loads customer from customer_updater_schema_name, the schema name specified for Customer Updater in the connectionconfiguration section of the ECE_home/config/management/charging-settings.xml file.
Displays the syntax for customerLoader.
Look in the ECE_home/oceceserver/logs/customerLoader.log file for errors.
To verify that the customer objects were loaded in the ECE cluster-distributed cache, use the query tool to form CohQL queries on the cache name that stores the respective object. For example, you would look in the Customer cache.For more information, see "Testing Scenarios in an Integrated System".
To configure the customerLoader utility:
Open the ECE_home/oceceserver/config/management/migration-configuration.xml file.
Set the configObjectsDataDirectory parameter to the path of the directory that contains the credit profile and offer profile XML data files.
The customerLoader utility loads the sample profile data from the XML data files in this directory into the ECE customer cache.
By default, this parameter is set to ECE_home/oceceserver/sample_data/config_data.
Set the productOfferingCrossRefFilePath parameter to the path of the directory for the product-offering cross-reference XML data file.
The customerLoader utility loads the product-offering cross-reference data from the XML data files in this directory into the ECE customer cache.
By default, this parameter is set to ECE_home/oceceserver/config/management/sample_data/customer_data.
Set the customerDataDirectory parameter to one of the following:
To load the sample customer data files in ECE, specify the path of the directory for the ECE customer XML data file.
The customerLoader utility loads the customer data in the XML data files published to this directory into the ECE customer cache.
By default, this parameter is set to ECE_home/oceceserver/config/management/sample_data/customer_data.
To incrementally load the customer data from BRM into ECE, specify the schema from which the data has to be loaded into ECE. The schema and file name associations are found in the connectionconfiguration section of the ECE_home/config/management/charging-settings.xml file.
Set the customerXmlPattern parameter to the pattern of the customer XML data file name that you want customerLoader to load. The files with a name that starts with this pattern are loaded.
By default, this parameter is set to customer.
Set the remoteWmThreads parameter to the number of parallel work manager threads to be used for the customerLoader utility.
By default, this parameter is set to 1.
Set the batchSize parameter to the number of customers to put into the repository in one put operation.
Use batchSize to optimize performance of put operations into the repository. The more customers you insert into the repository in one put operation (rather than inserting each one individually), the better the performance.
By default, this parameter is set to 5000.
Save and close the file.
Use the pricingLoader utility to load sample pricing data into the ECE pricing cache from XML files.
Important:
When you use Pricing Design Center (PDC), you run the ECE Pricing Updater for loading pricing data into ECE. Pricing Updater loads pricing data into ECE from the Java Message Service (JMS) queue to which PDC publishes the data.Do not run both the pricingLoader utility and Pricing Updater on the same ECE system.
Use the pricingLoader utility only on a standalone installation when PDC is not used.
To configure the pricingLoader utility:
Open the ECE_home/oceceserver/config/management/migration-configuration.xml file.
Set the pricingDataDirectory parameter to the path of the directory that contains the ECE pricing component XML data file.
The pricingLoader utility loads the pricing data in the XML data files published to this directory into ECE caches.
By default, this parameter is set for loading sample pricing component data from the ECE_home/oceceserver/config/management/sample_data/pricing_data directory.
Save and close the file.
The query tool provides access to ECE cache content, enabling you to execute queries on ECE Coherence caches. For information about using the query tool, see "Using the Query Tool to Test ECE".