Known issues in OpenEdge 12.8.9

Beginning with OpenEdge version 12.8.9, Remote RMI is disabled by default as part of a security enhancement. This change affects remote calls made by utilities related to the following components:

• NameServer
• DataServer for Microsoft SQL Server
• DataServer for Oracle
• dbman

If your environment relies on Remote RMI functionality, you can re-enable it by updating the $DLC/properties/AdminServerPlugins.properties configuration as follows:

1. In both the AdminServer and ProAdsv sections, add the enableRemoteRMI property to true within jvmargs.

   For example:

   
   												[PluginPolicy.Progress.AdminServer]
   												pluginclasspath=!{value-of:classpath}
   												classpath=...
   												jvmargs=-DenableRemoteRMI=true
   												
   												[PluginPolicy.Progress.ProAdsv]
   												pluginclasspath=!{value-of:classpath}
   												classpath=...
   												jvmargs=-DenableRemoteRMI=true
   											

By default, EnableHSM will set the HSM token into autostart if the TDE keystore is enabled for either user or admin autostart. The -HSMAutostart parameter can be used to explicitly enable or disable autostart in the HSM, ignoring the TDE keystore’s autostart configuration.

OpenEdge stores some data in the public storage space of the token. This data is used to support HSM autostart. Some HSM products do not allow public storage in their HSM. For these HSM products, EnableHSM will fail unless -HSMPrivate is supplied. If this error is encountered, EnableHSM can be rerun with -HSMPrivate added as an argument. Note that using -HSMPrivate prevents the ability to use autostart in the HSM; the -HSMAutostart disable parameter may also be required with -HSMPrivate if the TDE keystore is configured for autostart.

If -HSMPrivate was specified for EnableHSM, opening the DB and logging in to the keystore will always require a PIN. If a PIN was not specified, a new error message stating “A PIN may be required” will be displayed.

Starting with OpenEdge 12.8.9, update releases are delivered as both incremental and complete installations. This means that a previous version of OpenEdge 12.8 does not need to be installed before running the 12.8.9 installer.

Starting with OpenEdge 12.8.8, ESAM installation fails on Windows Server 2025 if you use a JDK version other than JDK 17.0.3+7. To ensure successful ESAM installation, specify the path to JDK 17.0.3+7 when installing OpenEdge 12.8.8 or later. This workaround solution is documented in the following Knowledge Base (KB) article also: https://community.progress.com/s/article/esam-fails-to-install-during-OpenEdge-12-8-8-upgrade.

Starting with OpenEdge 12.8.9, update releases are provided as complete installations. You no longer need to install a  previous version of 12.8 JMS Adapter before applying the update. In other words, you can directly add the OpenEdge JMS Adapter version 12.8.9 or later to an existing OpenEdge installation, even if the JMS Adapter was not previously installed.

Starting with OpenEdge 12.8.9, update releases are provided as full installations. You no longer need to install a  previous version of 12.8 ESB Adapter before applying the update. In other words, you can directly add the OpenEdge ESB Adapter version 12.8.9 or later to an existing OpenEdge installation, even if the ESB Adapter was not previously installed.

OpenEdge Memory Profiler provides ABL developers with a powerful visual tool to process the OEMP recording files, explore trend graphs, inspect object-level details via snapshots, apply tag-based filters, and compare snapshots within a recording.

However, working with large recording files that exceed 1GB or contain a high number of snapshots or application objects may degrade the performance, causing longer import times, slower graph rendering, and delays during snapshot inspection and comparison. For optimal performance and responsiveness, Progress recommends using smaller recording files when performing these actions.

When installing an update for WebClient, the update installer .msi file must reside in the same directory as the .msi file from the previous installation or the installation will fail. Once the installation fails, move a copy of the previous .msi installer to the same directory where the new update .msi resides and reinstall.

More information is available in the KB Article https://community.progress.com/s/article/Cannot-install-webclient-12-8-x-update.