Executive Summary (2.3.1)
is the latest generation of DigitalRoute's usage data processing software. It is an enterprise-grade data processing platform, combining integration capabilities with class-leading data processing functionality to derive useful information and drive real-time decision-making for a large number of applications such as: billing, operations, revenue assurance, service assurance, entitlement enforcement, service control and business intelligence.
Usage Engine has been designed for a modern cloud-native architecture and associated operational model, focusing on the following areas:
- Cloud-native design, with a clear separation between application and infrastructure, elasticity, and automated Life Cycle Management
- Operational framework, using best of breed industry standards for non-core functions, using a plug-n-play approach
- CI/CD support, with package management for solutions and test framework for automated test suite execution
- Usability, with clearly defined user interfaces for different user personas
New Functionality
This release contains no new functionality. For information about new functionality in the 2.3 main release, see New Features and Functionality (2.3).
System Requirements
For information about system requirements, see /wiki/spaces/UEPED2/pages/2130826.
Important Information and Known Issues
Configurations can be imported from MediationZone 8.x, but since there are different agent sets in the two products, a black box agent will replace any agents not available in your workflows, allowing you to retain your routes and other workflow configurations.
Other important information is:
See Important Information (2.3.1) for full details
And the following are known issues:
- mzcli Commands Do Not Provide Return Codes
- OpenAPI Validation Error for Type enum
- Encrypted Dynamic Workflows Uneditable in Web Interface
- Importing Old Configurations with Web Services Using Keystore Requires Additional Configuration
- The mzcli Command 'disconnect' is not Working on Containerized Solutions
- Usage Engine terraform template does not support M1 Mac with darwin_arm64 architecture
- Known Vulnerability CVE-2019-10797 when Using Netty 3
- Importing Old Data Veracity Collection Agent Workflow Configurations Returned Validation Errors
- Open API Profile Schemas that Require a UDR Must Be Named
See Known Issues (2.3.1) for full details.
Installation, Upgrade and Downgrade
For instructions on how to install, upgrade and downgrade, refer to Installation Instructions (2.3), Upgrade/Downgrade/Removal (2.3).