See Offline Mediation Controller Compatibility Matrix for more information.

The new Offline Mediation Controller web-based UI runs on top of Offline Mediation Controller. You can use it to create, design, and manage nodes, node chains, and Node Managers within the mediation processes.

See "Installing the Offline Mediation Controller Web-Based UI" in the Offline Mediation ControllerCloud Native Installation and Administration Guide for information about installing Offline Mediation Designer.

See Offline Mediation Designer Help for more information on how to use Offline Mediation Designer.

StatefulSets are a Kubernetes workload API designed to manage stateful applications that require persistent storage and stable, unique network identities. Unlike traditional deployments, StatefulSets ensure that each pod retains a consistent identity, including a unique hostname and persistent storage volume.

In the Offline Mediation Controller cloud native environment, Node Managers are now deployed using StatefulSets to take advantage of these capabilities. With StatefulSets, each pod is assigned a stable network identity and is bound to its own persistent volume.

The integration of StatefulSets with Kubernetes' Horizontal Pod Autoscaler (HPA) simplifies dynamic scaling. Pods can be added or removed seamlessly while maintaining their unique identities and associated resources.

See "About StatefulSet Implementation" in the Offline Mediation ControllerCloud Native Installation and Administration Guide for more information.

Offline Mediation Controller cloud native now supports the Kubernetes Horizontal Pod Autoscaler (HPA), enabling dynamic scaling of Node Manager pods to handle varying workloads. With this feature, the Node Manager pods are replicated as the application scales up, distributing the load evenly and ensuring optimal resource utilization during processing.

See "Enabling Scaling Replication" in Offline Mediation Controller Cloud Native Installation and Administration Guide for information.

The following endpoint has been added to the Offline Mediation Controller REST API:

POST /v1/actions/nodes/state - Start or Stop a Node by ID

This endpoint lets you start or stop nodes in a specified Node Manager.

See REST API Reference for Offline Mediation Controller for more information.

Offline Mediation Controller REST Services Manager now supports OAuth 2.0 authentication. You can use it to authenticate a client application's identity and to authorize the client application to access its REST API. It does this by validating an OAuth access token that is passed in the header of the client's HTTP/HTTPS request to the Offline Mediation Controller REST Services Manager.

You can use either Oracle Identity Cloud Service (IDCS) or Oracle Access Management (OAM), to set up authentication and authorization for your client.

See "Offline Mediation Controller REST Services Manager Security" to see how to set up authentication for your client.

You can now automate REST Services Manager (RSM) workflows in Offline Mediation Controller cloud native by using the RSM Request Automation feature. This feature uses a Kubernetes job to run workflows dynamically based on a structured JSON payload file, this file defines the sequence of API requests, response handling, and conditional logic that governs the execution flow. You can use this feature to run any API exposed by the RSM.

With this feature, you can:

• Automatically define and execute a sequence of steps based on predefined rules and conditions.
• Use data from API responses to set environment variables for subsequent requests.
• Leverage predefined flows for error handling and retries.
• Support multipart file uploads as part of API requests.
• Use response data to apply conditions that control the execution of the process flow.
• Chain requests based on the output of previous ones.

For information, see "Automating Workflows Using RSM Request Automation" in Offline Mediation Controller Cloud Native Installation and Administration Guide.

RSM metrics are exposed through the Helidon framework's http:// RSM_hostname:RSM_port/metrics endpoint, where RSM_hostname and RSM_port are the host name and port of the machine on which RSM is installed. The endpoint exposes metrics information in both JSON format (according to the MicroProfile Metrics specification) and plain text format suitable for Prometheus.

You can use the OCOMC_RSM_JVM_Dashboard.json sample dashboard provided in the OMC_home/sampleData/dashboards directory to view JVM-related metrics for Offline Mediation Controller RSM.

See "Using Prometheus to Monitor Offline Mediation Controller Cloud Native" in the Offline Mediation Controller Cloud Native Installation and Administration Guide for more information.

Using the Test Node Chain page in the Offline Mediation Designer UI, you can simulate the flow of data through a node chain to ensure that each node processes data as expected. This allows for thorough validation of your mediation logic. You can test an entire node chain, or you can isolate individual cartridges by disconnecting them from other nodes in the Node Manager for focused debugging. This helps confirm that each component is working correctly in isolation and as part of the larger system.

See "About Testing Node Chains" in the Offline Mediation Designer Help for more information.

You can now enable multi-threading for Remote Data Manager (RDM) to efficiently move Network Accounting Records (NAR) files between different Node Managers in Offline Mediation Controller. When multiple remote routes are configured, the RDM ensures reliable file transfers while maintaining the correct processing order.

See "Using the Remote Data Manager (RDM)" in the Offline Mediation Controller System Administrator's Guide for more information.