Synergy/DE Compatibility
Select your Synergy/DE version in the drop-down below to view its compatibility information.
This page includes requirements and other important information about Synergy/DE 12.3. Refer to the Quick Migration Guide (PDF) for more information about upgrading.
- Product Keys
- Runtime Compatibility (Compilation Requirements)
- ISAM File Compatibility
- Server Compatibility
- RDBMS Support (with SQL Connection)
- Third-Party Products
Product Keys
(Windows, Unix) When you upgrade to version 12.3, License Manager will automatically start polling and contact the Synergy License Web Service.
- If you have already placed an order for v12, new product keys will be downloaded and installed.
- If you haven’t yet placed an order, fuzzy matching will enable you to run version 12 as long as your subscription or ALM is current. Synergex Customer Service will contact you to complete the upgrade process.
See “Synergy/DE Licensing” in the Synergy/DE documentation for additional information about licensing.
(OpenVMS) Version 12 license PAKs must be installed before upgrading to Synergy/DE 12.3. You can obtain license PAKs online from the Licenses area of the Synergex Resource Center or by contacting Synergex Customer Service.
Runtime Compatibility (Compilation Requirements)
We recommend that you rebuild your Synergy applications with 12.3 to benefit from all the new features and fixes. If you choose not to rebuild, your application should still work fine with the 12.3 runtime, with the following exceptions:
- If your application was built with a Synergy/DE version prior to 9.1, you must recompile.
- If your Synergy application uses DDLIB (an executable library that contains routines that access the Synergy Repository) and is built with a Synergy/DE version prior to 7.1, you must recompile.
- If you want to debug your code with Synergy/DE 12.3 and your application is built with a version prior to 10.3, you must recompile.
- If you use UI Toolkit code with Synergy .NET and your application is built with version 9.5.3, you must recompile.
- If you have a Synergy .NET application built with a version prior to 9.5.3, you must recompile.
ISAM File Compatibility
We recommend that you convert your REV2 and 3 files to REV4 or higher. This will improve performance and ensure future compatibility. Synergy/DE 12.3 can access REV2 and 3 files but cannot create them; by default it creates REV6 and can also create REV4. In addition, isutl does not support pre-REV4 files (other than to convert them). REV4 files can be accessed by Synergy/DE 7.1 and higher. REV6 files can be accessed by Synergy/DE 10.1 and higher. See the Quick Migration Guide (PDF) for more information.
Server Compatibility
We recommend that you update all Synergy/DE products to version 12.3. If you choose to update your server(s) only, refer to the table below for the minimum client versions supported with Synergy/DE 12.3 servers.
For SQL OpenNet, the server version must be equal to the client version. For other Synergy/DE client/server products, the server version must be equal to or higher than the client.
| Server product | Supported client version |
| xfServer | Synergy/DE 6.1 and higher (9.3 or higher clients are required for encryption support, 9.5 or higher to use the Select class, and 10.3.1 or higher for connection recovery.) |
| xfServerPlus | xfNetLink 7.1 and higher (For encryption support, 9.3 or higher clients are required for xfNetLink .NET and xfNetLink Synergy and 9.5.1a or higher for xfNetLink Java.) |
| SQL OpenNet | xfODBC or SQL Connection 12.3 |
| License Manager | (Windows) Synergy/DE 6.3 and higher (UNIX) Synergy/DE 6.1 and higher |
RDBMS Support (with SQL Connection)
SQL Connection 12.3 supports the following databases:
- Oracle
- SQL Server
- MySQL
- Synergy DBMS
See Third-Party Products for specific version information.
In addition, fee-based support from our Professional Services Group is available for the following databases:
- Informix
- Oracle Rdb
- IBM DB2
- PostgreSQL
- Other ODBC-compliant
Third-Party Products
Synergy/DE interfaces or integrates with a number of third-party products. Synergex supports these interfaces and integration points but does not support the third-party products themselves. We strongly encourage you to maintain support contracts for any third-party products that are important to your applications. The table below specifies the versions of third-party products that we expect to work successfully with Synergy/DE. In most cases, higher versions than those listed will also work.
An asterisk* in the version column indicates a new minimum version requirement.
| Third-party product | Version with which Synergy/DE 12.3 is expected to work | Notes |
| HTTP | TLS 1.2, TLS 1.3 | For use with the HTTP document transport API. |
| Java Virtual Machine (JVM) | 8 and higher | For xfNetLink Java, which requires a JVM that is compatible with JDK version 8 or higher. |
| Microsoft .NET Framework | *4.8 | Version 4.8 or higher is required for installation and for most Synergy/DE products that use the .NET Framework. Device licensing requires 4.8 or higher. |
| Microsoft Visual Studio | *2022 (17.8 or higher) | For use with Synergy DBL Integration and xfNetLink .NET. The latest Synergy/DE SDI requires Visual Studio 2022 version 17.8 or higher. Developers should stay current with all VS and SDI updates. |
| MySQL | *5.7 and higher, 8 (64-bit) | For use with SQL Connection. |
| OpenSSL | Unix: IBM AIX: 1.0.2r or higher; Linux: 1.0.*x or higher OpenVMS: SSL111version 1.1.1b; SSL1 1.0-2C and higher |
For use with the HTTP document transport API, data encryption, and xfServer and xfServerPlus client/server encryption, and Connectivity Series data packet encryption. (OpenVMS) SSL1 1.0-2C is based on OpenSSL 1.0.2C. Synergy/DE installs the libraries compatible with the SSL version your OS version supports. Connectivity Series requires SSL1 1.0-2C and higher. See also “OpenSSL requirements” in the Synergy/DE documentation. (Windows) Synergy Interfaces with Microsoft Secure Channel (Schannel) for xfServer, xfServerPlus, the HTTP document transport API, and SQL OpenNet encryption. For data encryption, Microsoft CNG (Cryptography API: Next Generation) routines are used. |
| Oracle | *12 and higher | For use with SQL Connection. |
| SQL Server (Microsoft) | *2019 and higher | For use with SQL Connection. Synergy/DE 12.3 supports SQL Server accessed via Microsoft ODBC Driver 17 or 18 for SQL Server. |
| Synergy DBMS | REV 4 and higher ISAM files | |
| Terminal emulator | At least limited VT100 terminal compatibility | For use with the remote debugging feature. |