Home
Installation and Configuration
Installing the Notification Server
The Notification Server delivers notification messages to configured delivery channels and returns the notification message text and delivery ID to the Charging Server. Read on to learn how to install and set up the Notification Server.

Welcome
Release Notes
Architecture Overview
MATRIXX Cloud Native Installation and Configuration
MATRIXX Cloud Native Integration
Implementing MATRIXX in a Cloud
Installation and Configuration
- About Installation and Configuration
  Installation and Configuration provides information about the requirements and steps needed to install and configure the MATRIXX Digital Commerce software suite.
- Installing MATRIXX Digital Commerce
  MATRIXX Digital Commerce has a set of installation requirements, which are summarized below with installation and setup procedures.
- System Requirements
  The servers running the MATRIXX Digital Commerce software must meet specific hardware, software, operating system, and network requirements. In addition, certain third-party applications must be installed to run the MATRIXX Engine and measures must be taken to ensure the system is secure.
- MATRIXX Digital Commerce Software Packages
  The MATRIXX Digital Commerce software is delivered in RPM Package Manager (RPM) files.
- Installing MATRIXX Engine
  For production systems, the software must be installed on multiple blade servers that together form MATRIXX Engine. An environment can contain multiple engines for high availability. Installation prerequisites and instructions for installing the MATRIXX Engine software are provided below.
- Installing MATRIXX Gateways and Web Apps
  Install and set up the MATRIXX Gateways and Web Apps, including a secure communications channel to MATRIXX Engine. A production system can include more than one installation of the gateways and Web apps to facilitate high availability (HA).
- Installing MATRIXX Traffic Routing Agent
  Topics below provide information about how to install the Traffic Routing Agent (TRA) software.
- Installing MATRIXX Network Enabler
  Topics below provide information about how to install the Network Enabler software.
- Installing the Notification Server
  The Notification Server delivers notification messages to configured delivery channels and returns the notification message text and delivery ID to the Charging Server. Read on to learn how to install and set up the Notification Server.
  - Install the Notification Server
    Follow this procedure to install the Notification Server RPM on a server that is remote from MATRIXX Engine.
  - Start, Stop, or Restart the Notification Server
    This procedure describes how to start, stop, or restart the Notification Server.
  - Configuring Notification Setting Override
    You can override a setting in the mtx_notifier_camel.yaml or mtx_notifier_camel.properties file using a mtx_notifier_camel-local.yaml or mtx_notifier_camel-local.properties file. The -local file contains local overrides necessary for a specific scenario and is optional; no error displays if the -local file is not found.
- Installing Diameter Event Logger
  Consider the following before installing Diameter Event Logger.
- Configuring MATRIXX Engine
  You can customize the installation of MATRIXX Engine for a system that has not yet been deployed. Setup tasks include setting up business rules for MATRIXX Charging Application, MATRIXX Policy Application, and Call Control Framework (CCF). For information about changing the configuration of a running engine, see the discussion about changing the configuration of an engine.
- Configuring Gateway Proxy
  The Gateway Proxy service facilitates communication with MATRIXX Engine and is installed with default logging behavior, connection, and security information that you can configure for your environment. You must also configure the Linux Firewall with an allow list for accessing a MATRIXX Engine.
- Configuring MATRIXX Traffic Routing Agent
  You must configure traffic routing for a new installation of MATRIXX Digital Commerce using the Traffic Routing Agent (TRA) servers. All TRA servers should be configured as clusters (HA pairs) to provide failover capabilities.
- Configuring RS Gateway
  Configuring RS Gateway includes configuring the gateway to communicate with Gateway Proxy, configuring RS Gateway security, and configuring RS Gateway to connect to the Event Repository.
- Configuring ActiveMQ High Availability
  MATRIXX Engine supports high availability for the Notification Framework.
- Configuring Notification Messaging
  To enable notification messaging, you must configure the notification-specific global configuration questions during engine configuration, configure ActiveMQ, and configure the MATRIXX Notification Server. All components are required for publishing notifications to third-party systems. If you do not configure a JMS server address, notifications are published to MATRIXX Event Files (MEFs).
- Configuring Sub-Domain Routing (Multiple Sub-domains)
  In a MATRIXX Digital Commerce 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 Digital Commerce for sub-domain routing to work.
- Configuring MATRIXX Call Control Framework
  Call Control Framework (CCF), which provides the communication services between Intelligent Networks and a MATRIXX Engine, is installed with default connection information that you can configure for your environment.
- Configuring MATRIXX Network Enabler
  MATRIXX Network Enabler should be configured as a HA pair to provide failover capabilities.
- Configuring CDR Processing
  The MATRIXX Engine can import and rate Solution42® 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.
- Extending MATRIXX Engine Functionality
  You can easily 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.
- Uninstalling MATRIXX Digital Commerce
  If necessary, you can follow these instructions to uninstall the MATRIXX Engine software. This process will uninstall the following components: Proxy Server, Traffic Routing Agent, Network Enabler, My MATRIXX, and their related files. For information about uninstalling the MATRIXX Web apps, see MATRIXX Web App Administration.
- Appendixes
MATRIXX Digital Commerce Upgrade
MATRIXX Security
MATRIXX Engine Administration
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

Installing the Notification Server

The Notification Server delivers notification messages to configured delivery channels and returns the notification message text and delivery ID to the Charging Server. Read on to learn how to install and set up the Notification Server.

For production systems, the Notification Server RPM must be installed on a non-engine server.

The Notification Server RPM installs the following files:

Notification Server
- /opt/mtx/bin/mtx_notifier_camel.jar
Administration Files
- /etc/init.d/mtx_notifier_camel — Configures the Apache Camel routes and endpoints.
- /opt/mtx/bin/restart_notifier_camel.sh — A shell script that restarts the Notification Server.
- /opt/mtx/bin/start_notifier_camel.sh — A shell script that starts the Notification Server.
- /opt/mtx/bin/stop_notifier_camel.sh — A shell script that stops the Notification Server.
- /opt/mtx/bin/notifier_vars.sh — A shell script that allows you to add additional directories to the loader.path property.
Configuration Files
- /opt/mtx/conf/log4j2-mtx_notifier_camel.xml — Configures the logging parameters for the Notification Server.
- /opt/mtx/conf/mtx_notifier_camel.yaml — Configures the connection and authentication parameters (RS Gateway, ActiveMQ queues, SMTP server, and so forth) for the Notification Server.
- /opt/mtx/conf/mtx_notifier_camel.xml — Configures the Apache Camel routes and endpoints.
Sample Files
- /opt/mtx/data/log4j2-mtx_notifier_camel.xml
- /opt/mtx/data/mtx_notifier_camel.yaml
- /opt/mtx/data/mtx_notifier_camel.xml
During installation, if the sample files exist in /opt/mtx/data, they are copied to /opt/mtx/conf.

Note: The Notification Server reads the mdc_config_custom.xml file from the RS Gateway, which gets it from the MATRIXX Engine through the Gateway Proxy. However, if the RS Gateway does not start correctly, the Notification Server reads the mdc_config_custom.xml file from the local /opt/mtx/conf directory. For this reason, after upgrading your version of MATRIXX Digital Commerce, you should copy the new version of the mdc_config_custom.xml from the MATRIXX Engine to the /opt/mtx/conf directory on the Notification Server host.