Home
MATRIXX Digital Commerce Upgrade
Performing Ancillary Upgrade Tasks
The tasks below are not mandatory and do not apply to all MATRIXX Digital Commerce implementations.

Welcome
Release Notes
Architecture Overview
MATRIXX Cloud Native Installation and Configuration
MATRIXX Cloud Native Integration
Implementing MATRIXX in a Cloud
Installation and Configuration
MATRIXX Digital Commerce Upgrade
- About Upgrading MATRIXX Digital Commerce
  MATRIXX Digital Commerce Upgrade describes how to upgrade the MATRIXX Digital Commerce software to version 5226. During this process, you upgrade these important MATRIXX Digital Commerce components: MATRIXX Engines in multiple sub-domains, Traffic Routing Agent, Network Enabler, and MATRIXX Gateways and Web apps, including the REST Services (RS) Gateway and MY MATRIXX.
- Upgrade Paths
  Several MATRIXX Digital Commerce upgrade scenarios are tested and supported for this release.
- Upgrade Overview
  Upgrading MATRIXX Digital Commerce has several stages.
- Upgrade Pre-Deployment Tasks
  Perform the following tasks before upgrading MATRIXX Digital Commerce.
- Upgrading My MATRIXX
  You can use the following procedures to upgrade your pricing plan from an older version of My MATRIXX to the latest version.
- Upgrading MATRIXX Gateways and Web Apps
  To upgrade MATRIXX Digital Commerce you first need to upgrade and configure each of the MATRIXX Gateways and Web Apps. During the upgrade process, the upgraded services that communicate with the MATRIXX Engines are pinned to the schema version you are upgrading from. After all of the services and their sub-domains have been upgraded, you reconfigure the MATRIXX Gateways and Web Apps to use the new schema version by unpinning them from the previous version.
- Upgrade the MATRIXX Engine Chain
  You can follow the procedure below to upgrade an engine chain for a single sub-domain to the latest version of MATRIXX Digital Commerce.
- Upgrading the TRA-RT-(SI/DR) HA Pair
  Follow this procedure to install the Traffic Routing Agent (TRA) software for TRA servers configured as a TRA-RT-(SI/DR) disaster-recovery and sub-domain routing agent HA Pair. If your MATRIXX implementation uses the MATRIXX Network Enabler, use the instructions in the discussion about upgrading the Network Enabler in related links instead of this upgrade task.
- Unpinning Schema Versions
  After upgrading all subdomain chains and TRA-RT-(SI/DR) remove the schema version pinning in all of the MATRIXX Gateways and Web apps. See the steps for unpinning at the end of the procedures in the related links.
- Upgrading the Service Provider Schema
  Upgrading the service provider schema involves a subset of the steps to perform a full MATRIXX Digital Commerce upgrade.
- Performing Ancillary Upgrade Tasks
  The tasks below are not mandatory and do not apply to all MATRIXX Digital Commerce implementations.
  - Upgrade the Event Repository
    Perform this task to upgrade the MATRIXX Event Repository to the latest software version.
  - Upgrade the Network Enabler
    Perform this task to upgrade the MATRIXX Network Enabler to the latest software version. If Network Enabler is installed on a Traffic Routing Agent (TRA) TRA-RT-(SI/DR) server, this task also upgrades the TRA-RT-(SI/DR) to a new software version.
  - Upgrade a Standalone Engine
    You can follow the procedure below to upgrade a single-engine system to the latest release of MATRIXX Digital Commerce.
  - Migrating Channel Server Functionality
    Starting with release 5100, the APIs and functionality of the MATRIXX Channel Server are now provided by the RS Gateway. Apps developed for the pre-5100 MATRIXX Channel Server can be migrated by changing the base URI for all requests within your apps to use the RS Gateway instead.
  - Migrating Client Applications
    You must copy your custom MDC definitions (from mtx_config.xml) to the /opt/mtx/conf/mdc_config_custom.xml file on every machine where those MDCs are used by MATRIXX Java code.
  - Updating ASN.1 MDC Fields Used in Selective Updates
    Starting in release 5110, some Boolean fields in MDCs that are used by Call Control Framework (CCF) when processing voice calls, have been replaced with new unsigned integer32 fields so that they can be used in normalizers. Each of the replaced fields represents an ASN.1 NULL or ASN.1 BOOLEAN field type.
  - Updating Correlation ID Configuration
    Call Control Framework (CCF) uses correlation IDs when playing announcements on an external IVR for correlating the TCAP dialogues used in the message sequence. For MSCs that cannot handle 10 digit correlation IDs, CCF supports configurable correlation IDs.
  - Upgrade the Operating System Hosting MATRIXX Digital Commerce
    When necessary, upgrade the operating system (OS) on severs before actually upgrading MATRIXX Digital Commerce. To upgrade the Operating System (OS) hosting MATRIXX Digital Commerce, first upgrade the OS of the standby cluster, then upgrade the OS of what is normally the active cluster, then upgrade the OS hosting the TRA-RT pairs, one pair at a time. Lastly, upgrade the OS of each host of Proxy Server (pre-5200 releases) or host of MATRIXX gateways and Web apps (post-5200 releases.)
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

Performing Ancillary Upgrade Tasks

The tasks below are not mandatory and do not apply to all MATRIXX Digital Commerce implementations.