Event Repository System Requirements

The Event Repository has specific operating system and third-party software requirements. For information about installing software components, see the discussion about MongoDB recommendations for Event Repository.

Event Repository Operating System Requirements

Important: To protect from security vulnerabilities, ensure you have the latest critical updates for the running OS of your MongoDB system.

This section lists operating system (OS) requirements for servers that run the Event Repository. The host servers running the MongoDB server instances of the Event Repository replica set (or shards, in a sharded deployment) require the same Red Hat Enterprise Linux (RHEL) 64-bit operating system version as servers running MATRIXX Engine.

Important: Starting in MongoDB 4.0, you cannot specify the --nojournal option or

storage.journal.enabled:
						false

for replica set members that use the WiredTiger storage engine. Refer to the MongoDB product documentation for compatibility changes in MongoDB 4.0.

For best performance, either install Red Hat on its own hard disk drive (HDD) or install Red Hat on the same RAID10 HDDs where the Event Repository database (MongoDB) data files reside. For more information about where to install the OS and where to place MongoDB data files and indexes, see the discussion about Event Repository hardware requirements in this section.

Event Repository Third-Party Software Requirements

This section lists the third-party software requirements for servers that run the Event Repository.

Important: MongoDB is an open source platform non-relational database. The Event Repository is implemented in MongoDB. You must purchase and install MongoDB. Your instance of MongoDB must be solely dedicated to holding data that has been processed by the MATRIXX Engine. Do not store data from other applications in the MongoDB database and do not run applications for non-MATRIXX software on the MongoDB server. Doing so is likely to result in performance degradation of the engine. See the discussion about MongoDB recommendations for Event Repository for information about recommended and minimum configurations of MongoDB servers for the Event Repository.

Table 1. Event Repository Software Requirements
Software	Version	Description
MongoDB Enterprise	4.4, 5.0, 6.0, or 7.0	The supported MongoDB versions. To upgrade an existing MongoDB deployment to version 4.0 or later, you must be running a 3.6-series release. To upgrade from an earlier version, you must first successively upgrade major releases until you have upgraded to version 3.6. Refer to the MongoDB product documentation for upgrade recommendations and checklists. Note: Starting with MongoDB version 4.4, the MongoDB Database Tools and the MongoDB shell are each released separately from the MongoDB Server. Install MongoDB through the RPM Package Managers to install the MongoDB Database Tools and the MongoDB shell. If you do not use the RPMs, you must manually install these components. MongoDB Database Tools version 100.3.1 supports MongoDB version 4.4. To ensure you install compatible versions of these components on your server, see the MongoDB documentation.
PyMongo Driver	4.8	The Event Repository administration scripts require PyMongo libraries from your PyMongo installation. Refer to the MongoDB product documentation for instructions on installing PyMongo. The libraries can be saved to their default installation directory (/usr/lib64/python3.8/site-packages/pymongo). This driver works with all the MongoDB Enterprise versions supported in the MATRIXX system. Refer to the MongoDB product documentation for compatibility information between versions of MongoDB Python driver and versions of MongoDB.

The following drivers work with MongoDB Enterprise 5.0, 6.0, and 7.0 in the MATRIXX system and are included with the MATRIXX Engine image:

MongoDB C and C++ Drivers — These drivers are required by the Event Loader.
MongoDB Java Driver — This driver is used by the MATRIXX GL utilities for GL information processing and is bundled with the JAR files of the MATRIXX GL utilities and Event Repository API.

Event Repository System Requirements for a Sharded Cluster

The Event Repository system requirements for a sharded MongoDB deployment are the same as those for a non-sharded MongoDB deployment. For a sharded cluster, you use the mongos package (which is included in the MongoDB Enterprise package).

Event Repository Hardware Requirements

The number and configuration of the computers you use for your Event Repository is dependent on the requirements of your online charging system in terms of scale and the type of deployment. Work with your performance team to determine your sizing requirements.

The following are best practices for where to install the OS and where to place the Event Repository database (MongoDB) data files and indexes on the hardware.

Best practice 1 (ideal setup):

Install the OS on its own hard disk drive (HDD).
Have the Event Repository database (MongoDB) data files on their own RAID 10 HDDs.
Have the Event Repository database (MongoDB) indexes on the RAID 10 solid-state drives (SSDs).

Best practice 2:

Install the OS and the Event Repository database (MongoDB) data files on the same RAID10 HDDs.
Have the Event Repository database (MongoDB) indexes on the RAID 0 solid-state drives (SSDs).

Placing non-data or non-index files on these devices is discouraged:

Storing other files (non-index files) on the SSDs is discouraged, especially those that take up a lot of space or need regular access.
Storing other files (non-data or non-OS files) on the HDDs is discouraged, especially those that take up a lot of space or need regular access.

The index files could be placed on a dedicated disk volume made up of solid-state drives (SSDs) in a RAID 0 configuration. The data files could be placed on a dedicated disk volume made up of Serial Attached SCSI (SAS) disks in a RAID 10 configuration. If index file redundancy is required, RAID 1 or RAID 10 can be used instead of RAID 0, assuming write performance remains enough for your workload.

If you plan to enable MATRIXX Event File (MEF) publication, in addition to enabling the loading of events into the Event Repository, ensure that you have enough disk space. More disk space might be required when MEF publication is enabled, particularly if publishing MEFs in element_xml or attribute_xml MEF format (not in compact_mdc format).

Event Repository Information Requirements

You configure the MATRIXX Engine software for an Event Repository by answering questions about your event repository when running the create_config.py script. For more information about the requirements you must specify about your event repository when configuring MATRIXX Engine, see the discussion about Event Repository configuration.