Home
MATRIXX Web App Administration
Configuring My MATRIXX
Configure My MATRIXX by configuring properties, setting up a pricing repository, configuring authentication, and importing or exporting third-party pricing data.
Importing and Exporting Third-Party Data
This section provides information about how to import pricing data into My MATRIXX and export the data into third-party software applications.
My MATRIXX REST APIs
My MATRIXX supports GET, PUT, and POST REST bindings. The { } notation around text represents a URL parameter.
Normalizer REST Bindings
The normalizer REST bindings get, create, and update normalizers.

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
MATRIXX Web App Administration
- About MATRIXX Web App Administration
  MATRIXX Web App Administration describes the tasks required to install and administer MATRIXX web apps as containers, using Docker and Kubernetes.
- MATRIXX Web Apps
  MATRIXX includes the following MATRIXX web apps.
- Configuring MATRIXX Gateways and Web Apps
  In a non-containerized installation of MATRIXX, configure MATRIXX gateways and web apps using files in the /opt/mtx/conf directory in the pod(s) hosting those components. In a cloud native deployment, configuration files can be provided in the /opt/mtx/conf directory of the component container(s) using the following methods:
- Configuring My MATRIXX
  Configure My MATRIXX by configuring properties, setting up a pricing repository, configuring authentication, and importing or exporting third-party pricing data.
  - Configure My MATRIXX Properties
    Perform this task to give My MATRIXX access to database schema extensions for validation purposes, define the location of the master data directory and the logging directory, and to define the number of pricing revisions to compile into a pricing XML configuration file.
  - Setting Up a Pricing Repository
    MATRIXX uses the Apache™ Subversion™ source control system to maintain all pricing files contained in a pricing repository. The pricing repository is comprised of one or more independent pricing domains, each of which contains the files that make up a pricing plan for that domain. The pricing repository holds all the versions of files from all the pricing domains managed by an instance of My MATRIXX.
  - Lock a Pricing Compilation by Default
    Pricing compilations created in My MATRIXX can be configured to be locked by default by defining the lockPriceCompilation property in the matrixx.yaml file. Locked pricing compilations cannot be deleted even if they are not in use. If the lockPriceCompilation property is not added to the matrixx.yaml file, then pricing compilations are unlocked by default.
  - Disable Schema Validation for Deployments
    Before deployment, the system and provider schema versions of pricing and tax compilations are validated against the system and provider schema versions of the engine on which these compilations are being deployed. This validation can be disabled by setting the pricingDeployment and taxDeployment properties in the matrixx.yaml file to false. Validation is enabled by default.
  - Configuring the Pricing Controller
    Before performing price compilation tasks in My MATRIXX, configure the _glossary/pricing_controller.html, which is responsible for retrieving an engine status, transmitting a pricing compilation to an engine, and loading a pricing compilation onto an engine. The configuration is done through the Pricing Controller Helm sub-chart. For more information, see MATRIXX Configuration.
  - Configure My MATRIXX Session Timeout
    You can configure the period of session inactivity after which a user is logged out of My MATRIXX.
  - Configuring the My MATRIXX Security Warning Message
    My MATRIXX administrators can enable and customize a security warning message that displays when logging into My MATRIXX by adjusting the settings in their Helm values file as follows:
  - My MATRIXX Connection Properties
    config/r_mm_config_properties.html#reference_bbm_ndg_zwb__table_wrb_fdd_mhb lists the connection properties for My MATRIXX.
  - Importing and Exporting Third-Party Data
    This section provides information about how to import pricing data into My MATRIXX and export the data into third-party software applications.
    - Supported Pricing Objects and Flows
      My MATRIXX supports many different types of MATRIXX pricing components (objects) that are stored as individual XML files in the file system. The data format stored for these objects occasionally changes. To provide a stable API, while still allowing the format to change, MATRIXX Engine uses named flows, where each flow is a set of XSLT transformations.
    - My MATRIXX REST APIs
      My MATRIXX supports GET, PUT, and POST REST bindings. The { } notation around text represents a URL parameter.
      - List Queries
        List queries return information about service types, normalizers, product offers, price components, and rate tables.
      - Catalog Item REST Bindings
        The REST bindings described in this section operate on catalog items in My MATRIXX.
      - Matrix REST Bindings
        The Matrix REST bindings create and update rate tables.
      - Normalizer REST Bindings
        The normalizer REST bindings get, create, and update normalizers.
        Basic Normalizer
        The REST binding for a basic normalizer flow can use any normalizer in its raw XML form. The sample in this section describes how to create and modify a device type normalizer using the string match normalization algorithm.
        Apn Normalizer
        The Apn normalizer binding creates a normalizer to map access point names into defined values for pricing.
        Country Code Determination Normalizer
        The country code determination (CCD) normalizer determines country code zones.
        IP Mapping Normalizer
        The IP mapping normalizer maps IP addresses into MCC codes.
        Restricted IP Normalizer
        The restricted IP normalizer determines whether an IP address is in a restricted list.
        Zone Normalizer
        The Zone Normalizer flow is used to normalize an incoming field on the Diameter Ro message and determine the pricing zone that should be applied.
      - Product Offer REST Bindings
        The product offer REST bindings create new product offers, return information about existing product offers, and update existing product offers.
      - Price Component REST Bindings
        The price component REST bindings create new price components, return information about existing price components, and update existing price components. Price components are always based on usage.
      - Service Type Beats
        Use the service type REST binding to query a service type definition and the beats defined for it.
    - Price Control REST Bindings
      The HTTP Price Controller service enables the price control REST APIs. Use these APIs to automate pricing file management and loading.
- Configuring MATRIXX Backoffice Customer Tool
  MATRIXX Backoffice Customer Tool can be deployed on the local host or a remote system that communicates with MATRIXX Engine through Gateway Proxy and RS Gateway.
- Troubleshooting
  This section has information to help identify and resolve web app issues.
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

Normalizer REST Bindings

The normalizer REST bindings get, create, and update normalizers.

Attention: MATRIXX Support recommends that you do not create or update rate tables using this API. You should create rate tables in My MATRIXX because it provides safeguards and validations when creating and updating rate tables that the My MATRIXX REST bindings do not.

You can configure the following with the normalizer REST bindings:

Name
EffectiveDate
ValueList
ResultList (determined by the type of normalizer)
NormalizerList (multiplexing normalizers only)
DefaultMetadataArray

The normalizer REST bindings support the following attributes:

algorithm
datatype
name
description
type (This attribute is obsolete. Use the type_id attribute when creating or updating normalizers.)
type_id (Must be a valid normalizer type ID.)
external_id
selectedBalance
selectedBalanceTag
selectedBalanceClass
normalized_value
units
default
no_field_normalization_value
null_balance_value
max_thresholds
threshold_type
threshold_container
threshold_value
effective_date
tier
quantity_unit
is_prefix_match
is_case_sensitive
match_mode
feature_id
feature_value

The following attributes are used only in balance difference normalizers:

balance_class_1
balance_template_1
tier_1
balance_tag_1
from_period_1
to_period_1
balance_class_2
balance_template_2
tier_2
balance_tag_2
from_period_2
to_period_2
normalizer_value_list_id (Used when the normalizer uses a normalizer value list to supply the values for the normalizer. Must be a valid normalizer value list ID.)

The following are used only in difference range normalizers:

FieldOrParameter1
FieldOrParameter2
DifferenceRangeArray

The following examples show how to use the REST bindings on specific types of normalizers. The basic normalizer flow does everything shown in the other examples, but in a general way. These examples are specific use cases.