New Features and Functionality (2.2)
In this section you can see information about the new features and functionality in this release.
Simplified Delivery
The delivery of Usage Engine has now been simplified, and you no longer have to have helm s3 plugin installed, or a docker hub account.
Note!
Helm and docker image repositories now reside in GitHub!
Helm charts and images are publicly available, hence no need for access credentials!
New helm chart URL : https://digitalroute-public.github.io/usage-engine-private-edition
See information for respective deployment options in Installation Instructions (2.2).
Original Webservices Client Request Payload Available
Issue number: XE-6547
The original internal and output Webservices SOAP messages for both WS provider and WS requester are now provided. This is to allow the customer to log/archive these SOAP messages contents for audit purpose. See Web Service SOAPXML Trace UDR Type (2.2) for more information.
Extended Support for MySQL in DB Profile
Issue numbers: XE-5651, XE-4214
MySQL 8 is now supported when using the Database profile. See Database(2.2) for more information.
The MySQL db type can now also be used for:
- Database Bulk Lookup Functions (APL)
- Event Notifications
- Prepared Statements (APL)
- SQL Loader Agent
- Task Workflows Agents (SQL)
See MySQL (2.2) for more information.
Support for Derby in DB Profile
Issue numbers: XE-6560
Derby is now supported when using the Database profile. See Database(2.2) for more information.
The Derby db type can be used for:
- Audit Profile
- Database Table Related Functions (APL)
- Event Notifications
- SQL Collection/Forwarding Agents
- Task Workflows Agents (SQL)
See Derby (2.2) for more information.
Access Control for ECDs
Issue numbers: XE-6568
The possibility of setting different user permissions for the ECDs is now available.
- ECD Developer/Administrator user - can create and maintain ECDs using all parameters
- ECD Operator user - can create and maintain ECDs but not use JVM Args and Patch parameters
Note that if you have done an upgrade, ECD permissions have to be manually granted for existing access groups.
See Managing ECDs Access Permission (2.2) for more information.