Home
MATRIXX Administration
Appendixes
MATRIXX Engine Scripts
You can use the following scripts to support servers, clusters, engines, pricing domains, system logging, notification messaging, and event-repository storage. Use them to gather information, perform maintenance operations, such as starting and stopping servers, configure system behavior, and manage engine failover operations.
Engine Administration Scripts
Use the following engine administration scripts to administer the MATRIXX Engine.
check_engine.py
The check_engine.py script checks that the Cluster Manager is running on each server in the specified engine and returns status information.

Welcome
MATRIXX Release Notes
MATRIXX Architecture
MATRIXX Installation and Upgrade
MATRIXX Configuration
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
- About MATRIXX Administration
  MATRIXX 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 have information about maintaining, managing, and resolving issues with a MATRIXX Engine installation.
- Administering MATRIXX Traffic Routing Agent
  The topics in this section describe administering Traffic Routing Agent (TRA) 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 describe administering the Route Cache.
- Administering US Tax Data
  US tax data is imported from CCH tax data, compiled in My MATRIXX, and output as compact MATRIXX Data Container (MDC) files, including an MDC file containing tax database metadata and status information. MDC files are packaged into a .zip file and loaded into the MATRIXX tax database.
- Troubleshooting Issues
  This section has information to help identify and resolve system issues.
- Appendixes
  - Admin Service Commands
    The Admin Service includes commands for administering MATRIXX components.
  - Engine Validation Error Codes
    The following return codes can be written to the system log when a network message is processed.
  - Python Value Type to AVP Type Mapping
    The following table describes how Python value types are mapped to AVP types.
  - MATRIXX Engine Scripts
    You can use the following scripts to support servers, clusters, engines, pricing domains, system logging, notification messaging, and event-repository storage. Use them to gather information, perform maintenance operations, such as starting and stopping servers, configure system behavior, and manage engine failover operations.
    - Analytical and Informational Scripts
      Use the scripts in this section to gather information about system performance, system topology, performance statistics, system configuration, and MATRIXX Engine versioning. All scripts run locally on a server as user mtx.
    - Configuration, Demo, and Test Scripts
      Use these scripts to configure MATRIXX Engine, create demos, and test system functionality.
    - Server Administration Scripts
      Use the following server administration scripts to administer MATRIXX Engine servers.
    - Cluster Administration Scripts
      Use the cluster administration scripts to start, stop, restart, and check the status of all logical servers in a cluster and to sync all MATRIXX directories on all servers in the cluster.
    - Engine Administration Scripts
      Use the following engine administration scripts to administer the MATRIXX Engine.
      - Engine Administration Scripts — Command Line Options
        The scripts that can run on all servers in a MATRIXX Engine support the following command line options when they are initiated by the mtx user. Sometimes, the options are only valid for certain scripts. These cases are noted.
      - activate_engine.py
        The activate_engine.py script makes the target engine the ACTIVE processing engine. Its purpose is to make the standby cluster switch to an ACTIVE state so it can take over processing network data.
      - check_engine.py
        The check_engine.py script checks that the Cluster Manager is running on each server in the specified engine and returns status information.
      - check_engine_start_prereqs.py
        Run the check_engine_start_prereqs.py script before starting MATRIXX Engine or a cluster to check the start-up prerequisites for the local transaction log directories.
      - enable_disable_task_mgr_dynamic_throttling.py
        The enable_disable_task_mgr_dynamic_throttling.py script enables or disables Task Manager dynamic throttling. The script enables dynamic throttling only if the cluster is in an active or standby state. This prevents the engine having to be restarted after an upgrade, which can be time consuming.
      - print_engine_stats.py
        The print_engine_stats.py script calculates the number of transactions per second (TPS) for the servers on a MATRIXX Engine. Some statistics tables only calculate averages and totals for the processing servers, if the other server types are not handling transactions. The non-transacting servers still appear in the statistic output table but their statistics are not totaled or averaged to avoid misleading data. The processing-server-only statistics tables are marked with a footnote.
      - start_engine.py
        The start_engine.py script starts all servers in an engine at the same time. Run as the mtx user. By default, this script uses the --fast_start option. You can specify a prompt to warn you before using a fast start if necessary.
      - stop_engine.py
        The stop_engine.py script stops all servers in the engine, starting with the processing servers and then the publishing servers. Each server is allowed to finish processing in-flight transactions before it is stopped.
      - restart_engine.py
        The restart_engine.py script stops the servers in an engine and then starts them.
      - rsync_custom_dir_on_engine.py
        The rsync_custom_dir_on_engine.py script synchronizes the ${MTX_CUSTOM_DIR} directory on all servers in an engine with the ${MTX_CUSTOM_DIR} directory on the local server. Synchronization is required after making configuration changes and extending MATRIXX Data Containers (MDCs).
    - Control Scripts for Containerized Installations
    - Failover Scripts
      Use these scripts to publish MATRIXX and clean up orphaned transaction log files after an engine failover.
    - Provisioning Scripts
      Use these scripts to provision data in the MATRIXX database.
  - Scripts and Utilities for MATRIXX Gateways and Web Apps
    Use the following scripts to administer MDC Gateway, Gateway Proxy, RS Gateway, and other MATRIXX gateways and web apps.
  - Traffic Routing Agent Administration Scripts
    Use the following scripts to administer Traffic Routing Agents (TRAs), to check the status of a TRA server, or to validate the TRA configuration.
  - MATRIXX Data Container Field Data Types
    MATRIXX Engine supports several data types for its network message MATRIXX Data Containers (MDCs) and database object MDCs. When you define custom MDCs and MDC fields, you must specify one of these data types for the fields.
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

check_engine.py

The check_engine.py script checks that the Cluster Manager is running on each server in the specified engine and returns status information.

Syntax

check_engine.py [-h] [-d] [--debug_config_file_parsing] [--debug_function_calls] [--debug_output_formatting] [--debug_threading_code] -e engineId [--plain] [-s] [-u username] [--ssh_debug]

Options

Check the Local Engine

check_engine.py

Check Engine with ID 2

check_engine.py -e 2