Open

The following provides important information related to MediationZone 9.2:

Step-wise Upgrade

In 9.1 we made a deviation in our regular support procedure with step-wise upgrades, allowing upgrades directly from 8.3 to 9.1. However with this release we are reverting back to regular procedure, which requires you to upgrade to 9.1 before upgrading to 9.2.

Deprecated Agents or Features

When the term deprecated is used for an agent or a feature, this means:

• The agent or feature is still available for use in the current version.

• You are not encouraged to use the agent or feature long-term.

• You need to switch to an alternative soon as the agent and feature will be replaced, or sunset in upcoming versions.

Replaced and Removed Functionality

Functionality that has been replaced with a functional equivalent or sunset from the product is described in the MediationZone 9 Product Catalog here: 12. APPENDIX - Changes from 8.3 Product Catalog

Support for Insecure Ciphers Removed

Support for using the old RC4 or ARCFOUR ciphers in the SFTP agents have been removed since these ciphers are considered insecure.

Some Functionality only Available in Legacy Desktop Client

Certain features have not yet made it into the new Desktop and are only available in the Legacy Desktop client. These are described in Legacy Desktop.

Auto Edit Mode in UDR File Editor

While editing UDRs in bulk, there is a mode available called Auto Edit. Using this mode you can edit multiple UDRs using matchers and assignments. See Editing a Bulk of UDRs. This mode is available in Legacy Desktop only.

REST is not Supported for Conditional Trace

In this new version of Conditional Trace, REST is not supported, configurations can be done in Desktop only.

New Delivery Procedure

Delivery of MediationZone has been revised, see more details in the Release Information MediationZone Release Information page.

Context-Sensitive Help and Offline Documentation in Browser Not Available

For this release, documentation is available in InfoZone and PDF format only.

Performance Degradation When Using Unsupported Oracle versions and Oracle JDBC drivers

As a result of our performance testing for MediationZone 9.2 and using Oracle database, there is noticeable performance degradation when connecting to Oracle versions older than Oracle 19 and using Oracle JDBC drivers older than OJDBC 10. We recommend that you use the latest supported Oracle versions and Oracle JDBC drivers when using MediationZone 9.2.

Importing Old IPDR SP Agent Workflow Configurations Returned Validation Errors

If you have an old IPDR Workflow configuration from version 8. x, it is possible that validation errors about invalid IPDR SP agents may occur.

Example error during import:

To resolve this, you will need to open the workflow and save the workflow configuration.

Alternatively, you can manually add “#” to each “Default value is …” in the IPDR SP agent’s Advanced Properties tab.

Unavailable mzsh Commands

In MediationZone 9.2 the following mzsh commands from 8.x are not available:

Proxy Support

Proxy support has been added for:

• Amazon S3

• HTTP/2 Server agent

• REST Client

See Amazon S3 Agents, HTTP/2 Server Agent, and REST Client Agent for more information

Support for “wfexport” and “wfimport” mzsh Commands

Both “wfexport” and “wfimport” have been added to MediationZone 9.2.0.2 onwards.

SAP CC agents only support SAP CC version 2023

SAP CC server version 2023 requires client applications to run on Java 17. Since MediationZone 9.x is based on Java 17 , SAP CC agents only support SAP CC server version 2023. When upgrading from MediationZone 8.3.x to MediationZone 9.x, it is essential to ensure simultaneous upgrade to both Java 17 and SAP CC version 2023 as well.

For SAP CC server version 2022 or earlier, please use Java 8-based clients, such as on MediationZone 8.3.x.