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.
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.
Pricing Domains
A domain defines a single instance of a working pricing plan and provides access to all items in that catalog. You can have multiple domains in a pricing repository, each of which is independent from the other and is password-protected so only authorized users can gain access.
Pricing Domain Best Practices
Each pricing administrator should have a unique My MATRIXX username and password that are only used to integrate changes from what may be multiple users. Use this login to update the master workspace with the latest repository files and not to perform local changes to files.

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.
    - MATRIXX Pricing Repository
      All items that comprise a pricing plan are based in XML and stored in a pricing repository in the Subversion version control system.
    - Pricing Domains
      A domain defines a single instance of a working pricing plan and provides access to all items in that catalog. You can have multiple domains in a pricing repository, each of which is independent from the other and is password-protected so only authorized users can gain access.
      - MATRIXX Sample Domains
        The Sample.zip file contains two sample domains, Sample and matrixxOne. When these domains are installed, you can have immediate access to My MATRIXX for testing purposes.
      - Shared Workspaces
        A shared workspace is a copy of an existing domain that allows multiple users to work on it simultaneously. User commits and updates are not required to see changes within a shared workspace. Use shared workspaces to allow users who have their own login to share their changes with other users who have their own login. For example, Users A and B are both working in a shared workspace. When User A does a build, that build contains the changes from both Users A and B. By default, all users have access to a shared workspace.
      - Pricing Domain Best Practices
        Each pricing administrator should have a unique My MATRIXX username and password that are only used to integrate changes from what may be multiple users. Use this login to update the master workspace with the latest repository files and not to perform local changes to files.
    - My MATRIXX Master Data Directory
      My MATRIXX has a master data directory that it uses to manage changes performed by multiple users on the same pricing domain. My MATRIXX supports hosting SVN repositories for pricing files in persistent storage outside of the My MATRIXX container.
    - Verify Access to My MATRIXX
      Use My MATRIXX to verify that the web services required by My MATRIXX are running and that My MATRIXX can read the pricing repository.
    - Administering the Pricing Repository
      Administering a domain includes adding domains to a pricing repository, enabling domain recreation, and importing and exporting domains.
    - Managing My MATRIXX Users
      Managing users in My MATRIXX includes tasks such as creating user accounts, granting access to pricing domains, assigning roles and privileges, resetting user passwords, and deleting user accounts.
  - 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.
- 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

Pricing Domain Best Practices

Each pricing administrator should have a unique My MATRIXX username and password that are only used to integrate changes from what may be multiple users. Use this login to update the master workspace with the latest repository files and not to perform local changes to files.

If you use the get_pricing.py script to compile the pricing XML configuration file rather than My MATRIXX, specify your login ID on the command line. Internally there is metadata in the pricing XML configuration file that contains the user who compiled the file, the pricing domain from which it was compiled, and the time it was compiled.