Use these scripts to publish MEF and SEF files from transaction log files.
MATRIXX Integration describes the tools and tasks for integrating MATRIXX functionality in a MATRIXX environment.
The /opt/mtx/data/mdc_config_system.xml file has all system MATRIXX Data Container (MDC) definitions, subtype definitions, and relationship definitions.
MATRIXX includes images that contain utilities to aid in the deployment, operation, and configuration of cloud native MATRIXX installations. You can run these utilities directly or scheduled as cron jobs using the MATRIXX Helm chart.
MATRIXX Engine generates an _glossary/edr.html for all activities that can trigger rating, such as usage, catalog item purchases and cancelations, 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, and can be input to third-party applications.
This section provides an overview of subscriber data relationships.
A MATRIXX Engine can optionally load EDRs (Event Detail Records) 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).
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.
You can extend MATRIXX Engine functionality to capture new subscriber-related data and then use the extended fields as a basis for pricing, rating, and policy decisions. You can also add new Diameter AVPs to capture information from the network and base rating and post-rating operations on this data.
The MATRIXX Data Export image (data-export) has the data-export.jar utility. This utility uses checkpoint files to transform database contents and MATRIXX Event Files (MEFs) to comma-separated value (CSV) files. This image also creates SQL files for creating RDBMS tables and loading the data from the CSV files.
Selective updates are commands that enable the system to selectively update a MATRIXX Data Container (MDC) as it is processed. They perform basic transformations on the MDCs.
The MATRIXX Toolbox image has scripts and utilities to aid in the deployment and operation of cloud native MATRIXX installations.
The MATRIXX Misc image includes utilities and files to aid in the deployment and operation of cloud native MATRIXX.
You can use the third-party Linux tcpdump utility to capture network traffic for a MATRIXX application.
MATRIXX generates General Ledger (GL) information for accounts that you specify during rating. It then captures that information in MATRIXX Event Files (MEFs).
Use the Event Repository administration scripts to display the Event Repository configuration, check the status of the Event Loader service that loads events into the Event Repository, and check the status of the database application running the Event Repository.
Use these scripts to publish MATRIXX and clean up orphaned transaction log files after an engine failover.
The create_event_files_from_txn_logs script reads MATRIXX Engine transaction log files and creates an output file containing events from a given _glossary/global_transaction_counter.html range. Use the -k option to recover events from Streamed Event Files (SEFs). The output filename is built to conform to the output format.
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.
