Home
MATRIXX Integration
MATRIXX Notification Framework
This section describes how the MATRIXX Engine publishes notifications to a JMS message broker and how you can customize the information included in notifications.
Extending the Notification Framework
You can extend the Notification Framework to include custom logic to enhance notification messages and to deliver messages to additional endpoints (such as an ActiveMQ queue) by adding more .jar and .classes files on startup.
Extending Notification Messages
You can extend notification messages by adding custom logic in Java classes defined in /opt/mtx/notifier_camel/classes. In general, notification messages are enhanced with additional information by querying RS Gateway.
Running the Purchase Offer Notification Sample
This section describes how to install and run the notification extension included in the NotificationExtension_src.jar file. You can run the extension with minor changes to the included files.
Upgrade the Sample
When you upgrade the MATRIXX software, you must upgrade the mtx_notifier_camel.jar file because files can change or be deprecated.

Welcome
MATRIXX Release Notes
MATRIXX Architecture
MATRIXX Installation and Upgrade
MATRIXX Configuration
MATRIXX Security
MATRIXX Integration
- About MATRIXX Integration
  MATRIXX Integration describes the tools and tasks for integrating MATRIXX functionality in a MATRIXX environment.
- MATRIXX System MDC Definitions
  The /opt/mtx/data/mdc_config_system.xml file has all system MATRIXX Data Container (MDC) definitions, subtype definitions, and relationship definitions.
- Cloud Native Utilities
  MATRIXX includes images that contain utilities to aid in the deployment, operation, and configuration of cloud native MATRIXX installations. You can run these utilities directly or scheduled as cron jobs using the MATRIXX Helm chart.
- MATRIXX Event Detail Records
  MATRIXX Engine generates an _glossary/edr.html for all activities that can trigger rating, such as usage, catalog item purchases and cancelations, recurring cycle processing, or the first use of a balance. MATRIXX Engine also generates EDRs for non-rated events such as forfeitures. You configure event generation in My MATRIXX, including the events to generate and whether to add a custom container with additional mapped fields.
- MATRIXX Event Files
  MATRIXX Event Files (MEFs) contain a list of usage and non-usage event types generated during transaction processing. MEFs are meant to be published to, and consumed outside of, MATRIXX, and can be input to third-party applications.
- Subscriber Data
  This section provides an overview of subscriber data relationships.
- Event Repository
  A MATRIXX Engine can optionally load EDRs (Event Detail Records) into the MATRIXX Event Repository, a database separate from the MATRIXX Engine platform that serves as a long-term event storage repository. The Event Repository is an optional component separate from MATRIXX Engine that is implemented in MongoDB (you must purchase and install MongoDB).
- MATRIXX Notification Framework
  This section describes how the MATRIXX Engine publishes notifications to a JMS message broker and how you can customize the information included in notifications.
  - Notification Overview
    MATRIXX Engine generates real-time notification messages that MATRIXX Event File (MEF) files use to transfer to external systems.
  - Notification Data Relationships
    Each notification MATRIXX Data Container (MDC) derives information from its base MDC and can be related to other MDCs based on their contained fields.
  - Configuring Notification Messaging
    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).
  - Extending the Notification Framework
    You can extend the Notification Framework to include custom logic to enhance notification messages and to deliver messages to additional endpoints (such as an ActiveMQ queue) by adding more .jar and .classes files on startup.
    - Extending Notification Messages
      You can extend notification messages by adding custom logic in Java classes defined in /opt/mtx/notifier_camel/classes. In general, notification messages are enhanced with additional information by querying RS Gateway.
      - Running the Purchase Offer Notification Sample
        This section describes how to install and run the notification extension included in the NotificationExtension_src.jar file. You can run the extension with minor changes to the included files.
        Sample Notification Extension Files
        The following files are included in the NotificationExtension_src.jar file.
        Install the mtx_notifier_camel.jar File
        Install the mtx_notifier_camel.jar file that the notification extension uses.
        Compile the Source Code
        Compile the source code in src/main/java into target/classes and generate the .jar file target/NotificationExtension_src.jar.
        Declare the GroupInfoProcessor Bean
        Declare a new bean of type GroupInfoProcessor and modify the workflow to route the message through the GroupInfoProcessor bean.
        Customize the Email Message Template
        Customize the default mtxSubscriberOfferPurchaseNotification.ftl FreeMarker template to add the group balance information.
        Test the Sample
        Purchase an offer for a subscriber to test the notification enhancements.
        Upgrade the Sample
        When you upgrade the MATRIXX software, you must upgrade the mtx_notifier_camel.jar file because files can change or be deprecated.
    - Selecting Notification Endpoints Based on Subscriber State
      The Notification Framework can select different endpoints for delivering notification messages based on the state of a subscriber.
  - Managing Notification Templates
    The Notification Server uses Apache Camel FreeMarker templates to format notification messages. For information about working with Apache FreeMarker templates, see the Apache FreeMarker documentation.
  - Notifications for Object Modification
    Primary objects include subscriptions, groups, devices, and users. Primary objects have a system assigned object identifier (OID) that uniquely identifies the object and is the primary way to specify the object instance. Primary objects can also have an optional ExternalId value. When you modify a primary object, MATRIXX Engine generates an object modification notification.
  - Support for Push Notifications
    Out-of-box support for sending push notifications is included in MATRIXX. The Notification Server provides support for sending push notifications by way of Apple Push Notification Service (APNs) and Firebase Cloud Messaging (FCM).
  - Sample Code and Example Camel Configuration for Notification Integrations
    The notification message payload is configurable in JSON and XML to enable external integration of notification delivery for JMS queue and REST API. This section provides sample code and example Camel configurations for common notification integrations.
  - Filter out MTX-Specific Headers from HTTP Headers
    By default all Camel Exchange headers are copied to the outgoing HTTP headers. To prevent leakage of non-standard headers, you can filter out MTX-specific headers. In this task, you add and define a new bean to filter out the MTX-specific headers phonenumber, subject, emailid, and language.
  - Add a Cleanup Thread to Manage Connection Pool
    To help manage the connection pool, add a cleanup thread that periodically trims off expired and invalid connections in the connection pool. Add the new class com.matrixx.camelNotifier.gateway.MtxPoolingHttpClientConnectionManager to extend PoolingHttpClientConnectionManager.
  - Sample Code to Route to Another Instance of ActiveMQ
    The notification message payload is configurable in JSON and XML to enable external integration of notification delivery for JMS queue and REST API.
  - Override a Notification Type Handler
    The Notification Framework allows you to override a notification type handler for a specific message.
- Business API Gateway
  The Business API Gateway is a development framework that includes the Business API SDK, Rest Services Gateway (RS Gateway), Gateway Proxy, and application tier. It allows custom mobile applications, web clients, and other custom implementations to integrate with MATRIXX.
- Extending MATRIXX Engine Functionality
  You can 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.
- Data Export
  The MATRIXX Data Export image (data-export) has the data-export.jar utility. This utility uses checkpoint files to transform database contents and MATRIXX Event Files (MEFs) to comma-separated value (CSV) files. This image also creates SQL files for creating RDBMS tables and loading the data from the CSV files.
- Selective Updates
  Selective updates are commands that enable the system to selectively update a MATRIXX Data Container (MDC) as it is processed. They perform basic transformations on the MDCs.
- MATRIXX Toolbox Utilities
  The MATRIXX Toolbox image has scripts and utilities to aid in the deployment and operation of cloud native MATRIXX installations.
- MATRIXX Miscellaneous Utilities
  The MATRIXX Misc image includes utilities and files to aid in the deployment and operation of cloud native MATRIXX.
- MATRIXX Third-Party Analysis Utilities
  You can use the third-party Linux tcpdump utility to capture network traffic for a MATRIXX application.
- General Ledger Records
  MATRIXX generates General Ledger (GL) information for accounts that you specify during rating. It then captures that information in MATRIXX Event Files (MEFs).
- Appendixes
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
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

Upgrade the Sample

When you upgrade the MATRIXX software, you must upgrade the mtx_notifier_camel.jar file because files can change or be deprecated.

Procedure

Extract the contents of the NotificationExtension_src.jar file to your workspace.
For example:
```
cd workspace
jar xf /opt/mtx/bin/NotificationExtension_src.jar
```
This creates the directory structure described in the discussion about the sample notification extension files.
Copy the mtx_notifier_camel.jar file to the location specified in ant.properties.
For example:
```
notifier.jar.file=/opt/mtx/bin/mtx_notifier_camel.jar
```
Change directory to the location of your project ANT directory.
For example:
```
cd ${path of project}/ant
```
Run the ANT clean command.
```
ant clean
```
Run the ANT command to install the mtx_notifier_camel.jar file in the ant/dist/jar directory.
```
ant install
```
Change to the project directory.
```
cd ..
```
Run the ANT clean command.
```
ant clean
```
Generate a new .jar file.
```
ant jar
```