...
The following provides important information related to MediationZone 9.2:
| Table of Contents |
|---|
...
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
...
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.
Special Handling When Upgrading
When upgrading to 9.1 you may need to adjust some of your configurations if you are using:
System Insight
System Insight is now using a Prometheus backend instead of InfluxDB.
To use the new version Prometheus needs to be installed, and workflows using the System Insight forwarding agent need to be updated to leverage the Prometheus forwarding agent instead.
Note that the System Insight collection agent is not replaced with a Prometheus Collection agent, as data can be retrieved directly in Prometheus instead.
Configuration Spaces
Configuration Spaces is replaced with the new Workflow Packages functionality. Before upgrading, make sure to export the configuration from inactive configuration spaces as only the active space is carried across during the upgrade process.
DTK Agents and plug-ins
If agents and/or plug-ins developed using DTK are present in the system to be upgraded, these must be:
Removed from the system before upgrade
Rebuilt using the MediationZone 9.1 DTK and Java 17
The new, rebuilt, versions applied to the system after the upgrade has finished
Full upgrade instructions are available here: Standard Upgrade Procedure
WebService Proxy Support
If you want to use proxying in Web Service you must run the regenerateconfigs command and recreate the workflow packages that have Web Service workflows.
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
MediationZone is now downloadable from GitHub, and apart from the license key that is delivered separately, the link to all release deliverables can be found in the Delivery of MediationZone has been revised, see more details in the Release Information MediationZone Release Information page.
...
As a result of our performance testing for MediationZone 9.0 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.0.
Removal of Interactive Mode in MZSH
The Interactive mode has been removed from mzsh.
Invalid IPDR Workflows
When upgrading, there is a possibility that workflows with the IPDR SP agent could become invalid if they contain legacy configurations from MediationZone versions 8.1 and 8.2. This is due to an issue with compiling when the package name of the IPDR SP UDR has component names that begin with numbers. Due to the renaming of the IPDR SP UDR package names, existing workflows using these UDRs will no longer be valid. To fix the invalid workflows, you may need to reset the input in the Analysis agents that are receiving these UDRs or update the IPDR SP UDR type cast in APL code accordingly.
Importing Old IPDR SP Agent Workflow Configurations Returned Validation Errors
...
Unavailable mzsh Commands
In MediationZone 9.2 the following mzsh commands from 8.x are not available:
Command | Comment | |
|---|---|---|
| ||
|
| |
| ||
| Not needed anymore since the structure of the model can now be viewed in the user interface. | |
| ||
| ||
| ||
| Not valid any more since Configuration Spaces is no longer available. | |
| ||
| ||
|
| Anchor | ||||
|---|---|---|---|---|
|
Proxy support has been added for:
Web Service agents
...
Amazon S3
HTTP/2 Server agent
REST Client
See Amazon S3 Agents, HTTP/2 Server Agent, and REST Client Agent for more information
| Tip |
|---|
Hint! Since before, proxy is also supported Proxy support was previously available for:
|
Open API Incorrectly Validates Request Body
Users are encountering an issue with request body validation when using a schema file that includes discriminator and oneOf keywords. This issue arises due to a limitation in the library implementation.
...
|
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.