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.
The /opt/mtx/data/mdc_config_system.xml file contains all system MDC definitions, subtypes definitions, and relationship definitions.
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) 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.
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.
This section provides an overview of subscriber data relationships.
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).
This section describes how the MATRIXX Engine publishes notifications to a JMS message broker and how you can customize the information included in notifications.
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.
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.
Use these scripts to publish MEFs and clean up orphaned transaction log files after an engine failover.
Use these programs to publish MEF and SEF files from transaction log files.
The add_custom_field_to_export.py script is used to add custom MDC fields to a configuration .yaml file that is used by the data_export.jar program.
The data_export.jar program generates the Java classes that are used to extract data from a database checkpoint or MEF and export the data to comma-separated values (CSV) files.
The JavaApiGenerator.jar program generates the Java classes that can be used by Java applications to communicate with MATRIXX Engine.
The print_mtx_jar_version.py script prints the Manifest information for one or more specified JAR files. The Manifest includes the JAR version, Ant version, and main Java class for the JAR file.