Home
MATRIXX Engine Administration
Administering MATRIXX Engine
The topics in this section provide information about maintaining, monitoring, and resolving problems with a MATRIXX Engine installation.

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
- About MATRIXX Engine Administration
  MATRIXX Engine Administration describes how to monitor MATRIXX Engine components and to perform daily operations for maintaining a geographically redundant system. This includes administration for the engine, Traffic Routing Agent, MATRIXX Gateways and Web Apps, and Notification Framework. It also provides information about recovering from a total system failure.
- Administering MATRIXX Engine
  The topics in this section provide information about maintaining, monitoring, and resolving problems with a MATRIXX Engine installation.
  - Adding and Removing Blade Servers
    Follow the procedures in this section to add and remove blade servers from a running MATRIXX Engine.
  - Changing System Logging Behavior
    Follow the procedures in this section to change the default rsyslog behavior and the log level for a MATRIXX process.
  - Checking the Status of Blades, Clusters, Engines, and Storage
    Follow the procedures in this section to check whether a blade, cluster, or engine is running, and to validate the configuration and state of the shared storage.
  - Displaying Information About MATRIXX Engine Components
    Follow the procedures in this section to display information about MATRIXX Engine components, such as blade and engine IDs, software version numbers, MEF file contents, pricing configuration information, and MATRIXX Engine version information. For information about displaying MATRIXX Engine statistics, see MATRIXX Monitoring and Logging.
  - Fault Resolution
    The topics in this section describe how the MATRIXX Engine resolves failures that occur during runtime. All CRITICAL log messages are written to the /var/log/messages file. Service providers should monitor this log for help in debugging blade, cluster, and engine failures.
  - Cleaning the MATRIXX Engine Before Restarting
    It is important to clean your MATRIXX Digital Commerce environment between restarts to avoid contaminating new events with duplicate data. The process is different for test systems in which you have control over when the MATRIXX Engines are shut down, and production systems that are shut down involuntarily.
  - Maintenance and Scheduling
    The MATRIXX Engine clustered architecture supports periodic maintenance without disrupting service. You can perform maintenance on a blade server in a running MATRIXX Engine without compromising high availability or performance.
  - Maintaining Engine Redundancy
    There are several steps to take that can ensure a second engine is available and ready to take over in the case of an engine failure. The topics in this section describe a multi-engine environment, including how to set one up, monitor the system, and manage failover operations.
  - Managing System Memory
    Because the in-memory databases resize dynamically when needed, it is difficult to determine when an engine is almost out of free memory. There are several statistics to monitor that can indicate problems and several actions you can take to free up memory.
  - Managing Checkpoints and Transaction Logs
    Follow the procedures in this section to change the default checkpointing behavior, create a checkpoint manually, and delete old transaction logs and transaction log files.
  - Running Scripts on Blades, Clusters, and Engines
    The procedures in this section describe how to use the "run_cmd_on" scripts to run any MATRIXX script on a specified blade, a cluster of blades, or all clusters in an engine. In the latter cases, one command runs the script across all blades, one after the other.
  - Starting and Stopping MATRIXX Engine Components
    Follow the procedures in this section to start, stop, and restart blades, clusters, and engines.
  - Throttle the Incoming Event Rate
    Perform the tasks in this section if you did not set the incoming event rate as part of your base configuration process.
  - Revert to the Previous Pricing Database
    You can revert the pricing database to the previously-loaded pricing plan without interrupting transaction processing.
- Administering MATRIXX Gateways and Web Apps
  The topics in this section describe how to maintain runtime operations for MATRIXX Gateways and Web Apps, such as restarting the Gateway Proxy, viewing the firewall logs, and restarting Web apps.
- Administering the Notification Framework
  The topics in this section provide information on administering the components of the Notification Framework.
- Administering MATRIXX Traffic Routing Agent
  The topics in this section provide information on administering Traffic Routing Agent servers, including starting and stopping Traffic Routing Agent nodes and clusters. The information in this section applies to all Traffic Routing Agent functions unless otherwise noted.
- Administering the Route Cache
  The topics in this section provide information about administering the Route Cache.
- Troubleshooting Problems
  This section contains information to help identify and resolve system problems.
- Appendixes
MATRIXX Web App Administration
MATRIXX Engine Integration
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

Administering MATRIXX Engine

The topics in this section provide information about maintaining, monitoring, and resolving problems with a MATRIXX Engine installation.

Also see the discussion in gathering diagnostic data in MATRIXX Monitoring and Logging.