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.

The procedures below assume you have already configured the MATRIXX Traffic Routing Agents (TRAs) and the Virtual IP addresses (VIPs) that MATRIXX Digital Commerce requires to communicate among its components.

MATRIXX Engine is installed with a default platform configuration that integrators must change to suit their company's needs. All configuration procedures assume that the user is logged on to a blade server running in MATRIXX Engine and is running the configuration scripts locally, or is logged on remotely across a secure network connection, for example, by using Secure Shell (SSH).

Important: The MATRIXX Engine now accepts hostnames in addition to IP addresses. All fields in the create_config.info file that can be configured with an IP address can be configured with either a hostname or an IP address.

To configure MATRIXX Engine for high availability, you must configure a primary engine and a secondary engine for your data domain so their processing clusters can have an ACTIVE-STANDBY High Availability (HA) relationship. This is referred to as an engine chain. You can also add a third engine to an engine chain for additional HA and disaster recovery capabilities. Typically at least one engine is located at a geographically distant site. The script asks configuration questions for the main site (primary engine) before asking questions about the second site—and third site, if your environment contains three engines.

After configuration changes are verified on the local blade, they are propagated to all other blade servers running in the engine to ensure the configuration settings are same across all blades. After this is complete, run the configure_engine.py script again for each additional engine to synchronize its configuration with that defined for the primary engine. After all engines are configured, load the sample pricing configuration file.

For information about how to configure pricing and rating functionality, see Pricing and Rating. For information about extending MATRIXX Engine data, see the discussion about extending MATRIXX engine functionality.