Configuring General Ledger Information Processing

General Ledger (GL) information is produced by the Charging Server if you configured MATRIXX Engine to include GL information in events and used My MATRIXX to configure the GL account, transaction types, profiles, profile selectors, profile selector mappings, and account selectors. Perform the tasks in this section to enable MATRIXX GL utilities to process GL information that is produced.

Note: The following information is about configuring the Event Repository with MongoDB. For more information about PostgreSQL for GL processing, see the discussion about integrating with a PostgreSQL database.

To enable GL utilities to process GL information:

  • Set up the Event Repositories and the GL databases. If you have a multi-tenant installation of MATRIXX, a MongoDB database is created to store the tenant's events and another MongoDB database is created to store GL data for the tenant. The name of the MongoDB GL database for a tenant with a xxx ID is MtxGlDatabasexxx. There is no restriction on the database name for the tenant Event Repository, but the tenant GL database name must be MtxGlDatabasexxxx. The name of the base Event Repository is MtxEventDatabase and the name of the base GL database is MtxGlDatabase.
    Important: The GL utilities only support events loaded into the Event Repository in compact MDC (CMDC) format. When you run the create_config.py script and are prompted to answer the question: EventLoader:What is the format to use for loading the event objects to the Event Repository?, you must enter either compact_mdc or compact_mdc_and_bson. These formats are how events are stored in the MongoDB database. The default is compact_mdc. While the compact_mdc_and_bson format takes up more space, it offers more visibility to each field in the event.
  • Create a MongoDB user to be used by the GL utilities. For more information, see the discussion about setting user credentials for GL utilities.
  • Add MongoDB indexes for query optimization for each Event Repository. Indexing supports a multi-partitioned Event Repository. For more information, see the discussion about adding indexes to MongoDB for GL.
  • Configure the GL utilities by editing properties in their properties files. If you use multi-tenancy, define the tenants array in each properties file (located in /sync/conf).

    Sample gl_processor.yaml and gl_posting.yaml files are in /opt/mtx/data.

  • To run the utilities with log tracing enabled, create a log4j properties file and use it in the Java command line.

    For more information about the log4j properties, see the discussions about gl_processor.jar and gl_posting_jar.