MATRIXX Digital Commerce core components receive network messages, perform event-transaction processing, archive
data needed for engine high-availability or disaster-recovery purposes, and publish or store
event-transaction data for use by other systems.
MATRIXX Digital Commerce Components Overview
Figure 1 shows the core components that you
configure to process network traffic. Traffic Routing Agents (TRAs) load balance
network traffic to a MATRIXX Engine, the heart of a MATRIXX implementation. The Business API Gateway, SBA Gateway, and TRA and MATRIXX Engine architecture are described in more detail in the sections that follow.
A MATRIXX Digital Commerce 5G environment accepts traffic into the SBA Gateway, which is a 5G charging function (CHF). The SBA Gateway
converts outside traffic into MDCs (MATRIXX data containers) that other MATRIXX
components use to communicate.
From an event processing perspective, a MATRIXX Engine consists of the MATRIXX processes and services required to accept network and BSS
messages and convert them to events. You then rate and charge the events, or
optionally apply policy rules triggered by the event, or both. A MATRIXX Engine is made up of two or three processing servers, two publishing servers, a
checkpointing server and shared storage (a SAN device). The processing servers
accept incoming messages, and use the Charging Server to turn them into events (EDRs). Events can then be transmitted as data structures for further
processing, or stored as event objects. The checkpointing server creates database
checkpoints. The processing servers, publishing servers, checkpointing servers, and
shared storage are described in more detail in the sections that follow.
Note: The
components added for the optional event streaming feature are omitted from this
discussion. See Event Streaming for a discussion of the additional components that
event streaming uses and how they fit into a MATRIXX Digital Commerce implementation.
Figure 1. MATRIXX Digital Commerce Main Components
