Installation and Configuration provides information about the requirements and steps needed to install and configure the MATRIXX Digital Commerce software suite.
MATRIXX Digital Commerce has a set of installation requirements, which are summarized below with installation and setup procedures.
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.
The MATRIXX Digital Commerce software is delivered in RPM Package Manager (RPM) files.
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.
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).
Topics below provide information about how to install the Traffic Routing Agent (TRA) software.
Topics below provide information about how to install the Network Enabler software.
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.
Consider the following before installing Diameter Event Logger.
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.
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.
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 includes configuring the gateway to communicate with Gateway Proxy, configuring RS Gateway security, and configuring RS Gateway to connect to the Event Repository.
MATRIXX Engine supports high availability for the Notification Framework.
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).
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.
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.
MATRIXX Network Enabler should be configured as a HA pair to provide failover capabilities.
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.
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.
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.
Scripts for managing MATRIXX Digital Commerce are delivered in the RPM Package Manager (RPM) files with the software itself.
You can use the following scripts to maintain blades, 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 blades, configure system behavior, and manage engine failover operations.