Home
MATRIXX Engine Integration
Subscriber Data
This section provides an overview of subscriber data relationships.

Welcome
Release Notes
Architecture Overview
MATRIXX Cloud Native Installation and Configuration
MATRIXX Cloud Native Integration
Implementing MATRIXX in a Cloud
Installation and Configuration
MATRIXX Digital Commerce Upgrade
MATRIXX Security
MATRIXX Engine Administration
MATRIXX Web App Administration
MATRIXX Engine Integration
- About MATRIXX Engine Integration
  MATRIXX Engine Integration provides information about the MATRIXX Engine notification functionality, MATRIXX Event File (MEF) publication, Subscriber database SQL mapping, and importing and exporting pricing data.
- MATRIXX System MDC Definitions
  The /opt/mtx/data/mdc_config_system.xml file contains all system MDC definitions, subtypes definitions, and relationship definitions.
- MATRIXX Event Detail Records (EDRs)
  The MATRIXX Engine generates EDRs for all activities that can trigger rating, such as usage, catalog item purchases and cancellations, recurring cycle processing, or the first use of a balance. MATRIXX Engine also generates EDRs for non-rated events such as forfeitures. You configure event generation in My MATRIXX, including the events to generate and whether to add a custom container with additional mapped fields.
- MATRIXX Event Files (MEFs)
  MATRIXX Event Files (MEFs) contain a list of usage and non-usage event types generated during transaction processing. MEFs are meant to be published to, and consumed outside of, MATRIXX Digital Commerce, and can be input to third-party applications.
- General Ledger (GL) Records
  A General Ledger is a record of a company's financial transactions. Once configured, MATRIXX Digital Commerce generates GL information for accounts that you specify during rating. It then captures that information in MATRIXX Event Files (MEFs) and stores it in event objects in the MATRIXX Event Repository. You then use the MATRIXX GL utilities to process the GL information and generate daily GL summary records. That GL data is then available to post to a third-party General Ledger or enterprise resource planning (ERP) system.
- Subscriber Data
  This section provides an overview of subscriber data relationships.
  - MATRIXX In-Memory Databases
    The MATRIXX Engine uses an in-memory database set to hold all transactional data. This object-oriented database works seamlessly with the non-locking transaction model. It allows multiple reads and updates to the same objects to occur simultaneously while maintaining full transactional integrity.
  - Database Checkpoints
    Database checkpoints contain an exact snapshot of the in-memory databases and configuration files at a specific point in time. Periodic database checkpoints are used to recover data from whole cluster failures, and to reinstate an active processing cluster from a standby processing cluster after a disaster recovery operation. Use on-demand checkpoints for data analysis, setting up test environments, troubleshooting, and so on. You validate checkpoints using the validateCheckpoint.jar program.
  - Implementation Overview and Constraints
    Object Relational Mapping (O/R Mapping) creates a map from MATRIXX MDC-based objects to a relational database model for various use cases. A database version of an MDC can be created from a checkpoint and used for queries, data reporting, and analysis.
  - Database Schema Design
    The MATRIXX Subscriber database consists of four principal objects, all derived from MtxObject: MtxSubscriberObject, MtxGroupObject, MtxDeviceObject, and MtxWalletObject. Each one is mapped onto a corresponding physical table following the one-table-per-concrete-type model.
  - Exporting Subscription Data
    MATRIXX provides a Java program, data_export.jar, which uses checkpoint files to transform the database contents and MATRIXX Event File (MEF) files to comma-separated value (CSV) files. The data_export.jar file also creates SQL files for creating RDBMS tables and loading the data from the CSV files.
- Event Repository
  A MATRIXX Engine can optionally load MATRIXX event details records (EDRs) into the MATRIXX Event Repository, a database separate from the MATRIXX Engine platform that serves as a long-term event storage repository. The Event Repository is an optional component separate from MATRIXX Engine that is implemented in MongoDB (you must purchase and install MongoDB separately).
- MATRIXX Notification Framework
  This section describes how the MATRIXX Engine publishes notifications to a JMS message broker and how you can customize the information included in notifications.
- Business API Gateway
  The Business API Gateway is a development framework that includes the Business API SDK, Rest Services Gateway (RS Gateway), Gateway Proxy, and application tier. It allows custom mobile applications, Web clients, and other custom implementations to integrate with MATRIXX Digital Commerce.
- Network Protocol Gateway
  The MATRIXX Network Protocol Gateway communicates with "northside" (mobile) network traffic protocols. You use Network Protocol Gateway as an entry point to communicate with network nodes, and you can rate and bill for services from those protocols. Currently, Network Protocol Gateway processes and bills for SMPP traffic by using the MATRIXX SMPP Adapter.
- Appendixes
Call Control Framework Integration
MATRIXX Diameter Integration
MATRIXX 5G Integration
MATRIXX Monitoring and Logging
Pricing and Rating
MATRIXX Pay Now
MATRIXX Policy
MATRIXX Event Streaming
Subscriber Management
Subscriber Management (SubMan) API
MATRIXX Business API SDK
My MATRIXX Help
MATRIXX Backoffice Customer Tool Help
Third-Party Licenses
Glossary

Subscriber Data

This section provides an overview of subscriber data relationships.

The information in this section provides the conceptual information important for understanding MATRIXX in-memory databases, subscriber and event data, and how this information is used for database exports.