Home
MATRIXX Configuration
Configuration Input Settings
In a cloud native MATRIXX installation, MATRIXX Engine configuration specified in the create_config.info file is applied with a configuration source. This file contains a list of the questions asked by the configuration script during the configuration process and the answers provided by the administrator. Each question sets a configuration parameter. The engine(s) are configured with these parameters with a helm upgrade command.
Task Manager Configuration
You can use the configuration parameters in create_config.py to configure the MATRIXX Task Manager, which scans the databases on a scheduled interval for tasks that require processing by MATRIXX Charging Application.
Task Manager Dynamic Load Throttling Parameters
Task manager dynamic throttling is controlled by thresholds defined in mtx_config_base.xml. Adjust these thresholds with lines specifying new values in mtx_config_base_xml_sed.extra. For more information, see the discussion about task manager dynamic load throttling configuration.

Welcome
MATRIXX Release Notes
MATRIXX Architecture
MATRIXX Installation and Upgrade
MATRIXX Configuration
- About MATRIXX Configuration
  MATRIXX Configuration describes the tasks required to configure MATRIXX components.
- Configuring MATRIXX Using Helm
  Configure MATRIXX by adding values for properties from the MATRIXX Helm chart in your Helm values file. The MATRIXX Helm chart includes component sub-charts in a hierarchy of reusable components.
- Configuring MATRIXX Engine
  MATRIXX Engine configuration can be applied from a configuration source.
- Configuring Traffic Routing Agent
  Traffic Routing Agent (TRA) configuration can be added to the deployment with a configuration source.
- Configuring Sub-Domain Routing (Multiple Sub-domains)
  In a MATRIXX environment where multiple customer sub-domains are implemented in separate engine chains, you configure sub-domain routing so that traffic is directed to the correct customer sub-domain where the subscriber is homed. You must configure different components across MATRIXX for sub-domain routing to work.
- Example Single Domain Deployments
  Example configurations are provided for single-engine, dual-engine, and dual-engine with Traffic Routing Agent in disaster recovery mode (TRA-DR) cloud native MATRIXX examples.
- Configuring MATRIXX Gateways and Web Apps
  In a non-containerized installation of MATRIXX, configure MATRIXX gateways and web apps using files in the /opt/mtx/conf directory in the pod(s) hosting those components. In a cloud native deployment, configuration files can be provided in the /opt/mtx/conf directory of the component container(s) using the following methods:
- Configuring CDR Processing
  The MATRIXX Engine can import and rate Solution42® call detail records (CDRs) and generate MATRIXX Event Detail Records (EDRs) from them. Generally, this is used only when integrating with an Oracle BRM system. Other projects should use external mediation to convert external CDRs into Diameter messages for MATRIXX processing.
- Configuration Input Settings
  In a cloud native MATRIXX installation, MATRIXX Engine configuration specified in the create_config.info file is applied with a configuration source. This file contains a list of the questions asked by the configuration script during the configuration process and the answers provided by the administrator. Each question sets a configuration parameter. The engine(s) are configured with these parameters with a helm upgrade command.
  - Site Configuration
    You can use the configuration parameters in create_config.py to identify all physical components in a site, including servers, shared storage devices, and load balancers.
  - Tenant Placement Configuration
    You can use the configuration parameters in create_config.py to enable multi-tenancy and add or rehome tenants to a sub-domain.
  - Engine Configuration
    You can use the configuration parameters in create_config.py to identify the domain and customer sub-domains in your configuration, including identifying the engines, clusters, servers, IP addresses, multi-cast information, and network interfaces.
  - Engine Sub-Domain Configuration
    To implement multiple customer sub-domains in MATRIXX you must configure the create_config.info parameters described below.
  - Engine Multiple Sub-Domain Routing Configuration
    If you implement multiple customer sub-domains in your MATRIXX environment, use the configuration parameters in create_config.py to configure the connection for the engine's route-cache processing components. The Route Cache Proxy (RCP) port is specified and the processing servers that connect to the RCP. Each processing server in all engines for all customer sub-domains are configured to connect to the RCP.
  - Checkpoint and Transaction Replay Configuration
    Use the configuration questions in create_config.info to configure database checkpoint and transaction replay behavior.
  - File System Configuration
    You can use the configuration parameters in create_config.py to configure the MATRIXX Engine directories. These directories hold data required for system configuration, runtime processing, and recovery operations.
  - MATRIXX Event File (MEF) Publication Configuration
    You can use the configuration parameters in create_config.py to configure MEF publishing. If you enable _glossary/mef.html publication, you must manually create the directory on the publication host before running the MATRIXX Engine.
  - Event Streaming Publishing Server Configuration
    You use the create_config.info parameters to configure event streaming and the Event Stream Server on the publishing server.
  - Process Control Configuration
    Use the configuration parameters in create_config.py to configure the MATRIXX process behavior, including NFS monitoring, service start up and shut down timeouts, heartbeat timeout, and the number of attempts to try restarting a server after it fails.
  - Memory Buffer Configuration
    You can use the configuration parameters in create_config.py to configure memory for MATRIXX Engine.
  - Cluster Manager Configuration
    The Cluster Manager controls processing and publishing servers, and monitors the local cluster for availability, fencing off problematic servers, and initiating the shut down and switch-over of a processing cluster when a server quorum is lost. The parameters in create_config.py mainly apply to processing servers.
  - Diameter Protocol Configuration Parameters
    You can use the configuration parameters in create_config.py to configure the Diameter protocol implementation.
  - MDC Gateway Configuration
    You can use the configuration parameters in create_config.py to configure MATRIXX MDC Gateway.
  - MATRIXX Engine SNMP Configuration
    You can use the configuration parameters in create_config.py to configure the MATRIXX SNMP agent that runs on MATRIXX Engine servers, including security strings, trap destinations, and response time behavior.
  - Global System Configuration
    Use the configuration parameters in create_config.py to determine global system behavior. These parameters are subscription-related and include notification behavior, Diameter Re-Auth-Request (RAR) behavior, active session behavior, policy behavior, and interim bill cycle settings. Questions related to global settings are prefaced with Global.
  - Task Manager Configuration
    You can use the configuration parameters in create_config.py to configure the MATRIXX Task Manager, which scans the databases on a scheduled interval for tasks that require processing by MATRIXX Charging Application.
    - Configure Task Manager Dynamic Load Throttling
      Task manager dynamic throttling is controlled by thresholds defined in mtx_config_base.xml. Adjust these thresholds with lines specifying new values in mtx_config_base_xml_sed.extra and configure and restart the engine.
    - Task Manager Dynamic Load Throttling Parameters
      Task manager dynamic throttling is controlled by thresholds defined in mtx_config_base.xml. Adjust these thresholds with lines specifying new values in mtx_config_base_xml_sed.extra. For more information, see the discussion about task manager dynamic load throttling configuration.
  - Network Enabler Configuration
    Use the configuration parameters in create_config.py to configure MATRIXX Network Enabler.
  - CAMEL Gateway Configuration
    CAMEL Gateway is a CAMEL Application Part (CAP) server that allows communication between MATRIXX Engine and Network Enablers through the CAP protocol. Use the following information to configure the MATRIXX Call Control Framework (CCF) CAMEL Gateway create_config.py configuration parameters.
  - Signaling Connection Control Part Address Configuration
    You can configure MATRIXX Call Control Framework for calling party address fields that are sent in Signaling Connection Control Part (SCCP) messages sent through CAMEL Gateway and for the SCCP calling party address used in requests, such as MAP call out requests, USSD notifications, and MATRIXX initiated call requests for USSD call back services.
  - Subscriber Database Sizing Configuration
    You can use the configuration parameters in create_config.py to configure the subscriber database. If you are unsure about the number of balances, devices, and services each subscriber will have or the number of subscribers, groups, or users in your data domain, use the default values.
  - Database Sizing and Memory Configuration
    You use the configure_engine.py parameters to configure the size of the in-memory databases, including the number of database objects, object size, and size of the memory buffer. If you are unsure about how much space each object requires, use the default values.
  - Timer Index Sizing Configuration
    You can use the configuration parameters in create_config.py to configure the MATRIXX Engine timer index sizing. The timer index facilitates alert look-ups, task recurring processing, and event scanning using a trigger time.
  - Message Processing and Pricing File Configuration
    You can use the configuration parameters in create_config.py to configure message processing, including system time zone, maximum number of concurrent sessions, duplicate message detection, the default pricing file naming convention, and type of pricing XML configuration file that can be loaded into the pricing database.
  - MDC and MDC Field Extension Configuration
    You can use the configuration parameters in create_config.py to create custom MATRIXX Data Containers (MDCs) and add fields to custom MDCs. To add fields to an MDC, you must create a custom MDC that is based off of a system MDC and add the fields to the new custom MDC.
  - Selective Update Configuration
    You can use the configuration parameters in create_config.py to define custom behavior by using selective updates. They allow you to customize the behavior of MATRIXX Data Containers (MDCs) and their fields. They do not work directly on AVPs.
  - Transaction Server and Logging Configuration
    Use the configuration questions in create_config.py to configure Transaction Server and system logging behavior.
  - Publishing Server Transaction and Logging Configuration
    Use the configuration questions in create_config.info to configure Transaction Server and system logging behavior for the MATRIXX Engine publishing server.
  - Transaction Server Hash Index Scheduling and Sizing Configuration
    You can use the questions in create_config.info to configure the hash index scheduling:
  - ActiveMQ Gateway Configuration
    The ActiveMQ Gateway must be enabled to support the MATRIXX Notification Framework and MATRIXX Pay Now. If you are using an LDAP service, you must also configure ActiveMQ connections to the LDAP Gateway. Details are provided below for configuring the create_config.py parameters for the ActiveMQ Gateway.
  - MATRIXX Engine Port Configuration
    You can use the configuration parameters in create_config.py to configure MATRIXX Engine communication ports.
  - Event Repository Configuration
    You can use the configuration parameters in create_config.py to configure the Event Repository implementation.
MATRIXX Security
MATRIXX Integration
MATRIXX Diameter Integration
MATRIXX Call Control Framework Integration
MATRIXX TM Forum Integration
MATRIXX 5G Integration
MATRIXX 5G Event Streaming
MATRIXX Event Streaming
MATRIXX Administration
MATRIXX Web App Administration
MATRIXX Monitoring and Logging
MATRIXX Policy
MATRIXX Kafka CDR Consumer
MATRIXX Pricing and Rating
MATRIXX Pay Now
MATRIXX Subscriber Management
MATRIXX Subscriber Management API
MATRIXX Business API SDK
My MATRIXX Help
MATRIXX Backoffice Customer Tool Help
MATRIXX Third-Party Licenses
Glossary

Task Manager Dynamic Load Throttling Parameters

Task manager dynamic throttling is controlled by thresholds defined in mtx_config_base.xml. Adjust these thresholds with lines specifying new values in mtx_config_base_xml_sed.extra. For more information, see the discussion about task manager dynamic load throttling configuration.

Task Manager throttles its output traffic based on the following queues:

txnSvrInputQueue (blade_engine_cluster_blade_txn.1.1.input)
taskMgrRespInputQueue (blade_engine_cluster_blade_TaskMgrResponse.1.input)
chrgSvrInputQueue1 (blade_engine_cluster_blade_chrg.1.2.input)
chrgSvrInputQueue2 (blade_engine_cluster_blade_chrg.1.3.input)
chrgSvrInputQueue3 (blade_engine_cluster_blade_chrg.1.4.input)

Dynamic Throttling Parameters describes the dynamic load throttling configuration elements defined in mtx_config_base.xml.

Table 1. Dynamic Throttling Parameters
Property	Description
queue_throttle	The monitored object name, as specified with the `name` attribute of the `monitored-object` element in sysmon_config.xml.
throttle_to_zero_percent	The usage percentage maximum at which Task Manager stops generating traffic.
throttle_enable_percent	The percentage of usage at which throttling starts.
throttle_reset_percent	The percentage of usage at which throttling stops.
max_throttle_allowed	The percentage maximum of throttling that is allowed.
incremental_dynamic_throttle_in_percent	The factor by which resource usage is throttled each time the value of throttle_enable_percent is reached.