Page tree
Skip to end of metadata
Go to start of metadata

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.


Usage Engine 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 :

See information for respective deployment options in Installation Instructions[hide]2.2[/hide].

Original Webservices Client Request Payload Available

Issue number: XE-6547

Usage Engine now provides the original internal and output Webservices SOAP messages for both WS provider and WS requester. This is to allow the customer to log/archive these SOAP messages contents for audit purpose. See Web Service SOAPXML Trace UDR Type[hide]2.2[/hide] for more information.

Extended Support for MySQL in DB Profile

Issue numbers: XE-5651, XE-4214

Usage Engine now supports MySQL 8 when using the Database profile. See Database Profile[hide]2.2[/hide] 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[hide]2.2[/hide] for more information.

Support for Derby in DB Profile

Issue numbers: XE-6560

Usage Engine now supports Derby when using the Database profile. See Database Profile[hide]2.2[/hide] 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[hide]2.2[/hide] for more information.

Access Control for ECDs

Issue numbers: XE-6568

Usage Engine now offers the possibility of setting different user permissions for the ECDs.

  • 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[hide]2.2[/hide] for more information.

  • No labels