...

The following provides important information related to MediationZone 9.0:

Web Desktop no Longer Available

With the new Desktop that is accessible from a browser, not requiring a local client installation, there is no need to maintain the Web Desktop anymore and consequently it is no longer available from this release and onwards.

Standalone Execution Context replaced with Standalone Workflows

The PICO type ECSA (Execution Context - Standalone) has been replaced with a generic EC (Execution Context) in MediationZone 9.0. Standalone execution is instead controlled on a workflow level (workflow can execute either in "Normal" mode, or "Standalone" mode) and the generic EC can run both Normal and Standalone workflows.

ECSAs are upgraded to ECs, and the process to control workflow execution mode is described here: Execution Tab

Replaced and Sunset Functionality

...

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.

Special Handling When Upgrading

...

System Insight is now using a Prometheus backend instead of InfluxDB.

In order to 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.

...

Configuration Spaces is replaced with the new Workflow Packages functionality. Prior to Before upgrading, make sure to export the configuration from inactive configuration spaces as only the active space is carried across during the upgrade process.

...

If agents and/or plug-ins developed using DTK are present in the system to be upgraded, these must be:

1. Removed from the system prior to before upgrade

2. Rebuilt using the MediationZone 9.1 DTK and Java 17

3. The new, rebuilt, versions applied to the system after the upgrade has finished
   

Full upgrade instructions are available here: Standard Upgrade Procedure

...

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.

...

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

...

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 begins 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.

...

...