THE MATRIXX RERATING SOFTWARE PROGRAM IS EXPERIMENTAL AND IS NOT AUTHORIZED FOR PRODUCTION USE. IT IS PROVIDED “AS-IS” WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED.
Use MATRIXX Rerating to reprocess messages for a range of dates previously processed by the Charging Server that were determined to have incorrect results due to errors in the pricing or tax configuration, or when a subscription was incorrectly provisioned, after the issue is resolved. MATRIXX Rerating supports past billing cycle periods for postpaid subscriptions.
A deployment of the MATRIXX Rerating components consists of containers installed with a Helm chart in a multi-node Kubernetes cluster.
rerating/c_rerating_administering.html#concept_x5d_qbv_lwb__fig_hck_cxz_5wb illustrates the MATRIXX Rerating components and process.
Use this section to understand events delivered to the billing system when a job is approved by the operator in Rerating Workbench, and transaction events which are generated by the live system when messages are rerated.
An operator manges rerating through the Rerating Workbench user interface.
This section has information to help identify and resolve system issues.
YAML configuration files are used to manage general information and to specify how to store streamed events for use in rerating subscription IDs through row keys in Google Cloud Bigtable. Additional configuration files are used by Rerating Orchestrator, Rerating Director, and the Event Streaming Framework to write and query MATRIXX Rerating data.
The following tables define Rerating Director configuration properties, error codes, technical exceptions, and business logic exceptions.
The following tables define Rerating Orchestrator configuration properties and error codes.