Lesezeit: 2 Minuten
Autor: Jan Falkenberg, Head of Product TRANSCONNECT
With the release of TRANSCONNECT 5.0, we're ushering in a new era for our integration platform. This major release is much more than just an update: it's the new standard for modern, future-proof, and high-performance integration. The TRANSCONNECT 5.0 release adopts a platform-centric approach, offers stable tools for developers, and is consistently aligned with modern cloud environments. We expect to take this step in late 2025 or early 2026.
Key Innovations in TRANSCONNECT Version 5.0 at a Glance
Maximum Security for Custom Developments
Following a successful beta phase, our Connector SDK is now officially stable. Develop your own connectors based on clearly defined and versioned interfaces to create long-term security for your projects. Comprehensive documentation and practical examples will make it easier for you to get started and support consistent quality assurance.
Full Transparency and Improved Performance
We've completely redesigned the Logging System. Your administrators can now precisely determine which components log which information. This speeds up troubleshooting and avoids unnecessary log entries, which in turn improves performance. Traceability remains fully intact, even in complex cloud environments.
Simpler Administration from the Start
The new TRANSCONNECT Launcher makes it significantly easier to set up and and manage the integration platform. It replaces the previous, error-prone scripts, reducing your manual effort and ensuring a smoother start for TRANSCONNECT 5.0.
New Connectors for Modern Systems
The new version also offers a range of state-of-the-art connectors. These include the Microsoft SharePoint Online Connector (based on the MS Graph API), a new HTTP Connector (in/out), an updated SFTP Connector, and the SMB Connector, which now supports SMB 3.0.
Important Note: Support Status
With the release of TRANSCONNECT 5.0, the support cycles for older versions will change.
-
TRANSCONNECT 4 will transition to maintenance mode. You will still receive new connectors, critical bug fixes, and security updates.
-
TRANSCONNECT 3 will no longer be maintained and is considered obsolete. It is discontinued.
Deprecated and Removed Components
Please check if your installations are affected by the following changes.
Transitioning to Maintenance Mode: These adapters and components will no longer be developed, as modern technologies are now the preferred choice.
TRANSCONNECT Installer: It will be replaced by a simple unzipping procedure.
JMS-Adapter: Its relevance has decreased, as modern broker solutions like Kafka are now the preferred choice.
EDIFACT-Adapter: EDI standards are increasingly being replaced by REST APIs or structured JSON formats.
OSCI-Adapter: It is losing importance in e-government as web service-based procedures and standardized API solutions are gaining traction.
SAP-Adapter: Connectivity to SAP systems is now primarily done via official and standardized interfaces.
SOAP-Adapter: It is increasingly being replaced by RESTful web services, which are easier to maintain and use.
Office-Adapter: The processing of Office files is now mostly handled by specialized external software or services.
LDAP-Adapter: Modern authentication methods like OAuth2 or SCIM are replacing classic LDAP integrations.
PDF-Adapter: The creation and processing of PDF documents are now mostly done with specialized external tools.
UDP-Adapter: The use of the UDP protocol for integration is not recommended in modern architectures for security reasons.
Completely Removed: These adapters and components will no longer be available in TRANSCONNECT 5.0, as they have either been replaced by new connectors or are obsolete.
E-Mail (EWS) Adapter: It has been replaced by the new EWS E-Mail Connector, which is easier to maintain and extend.
SNMP-Adapter: This functionality is being phased out in favor of modern, API-based monitoring integrations.
File (Microsoft SharePoint Online) Adapter: The implementation used an authentication mechanism no longer supported by Microsoft. It has been replaced by the Microsoft SharePoint Online Connector.
LDT-Adapter: The proprietary LDT interface has lost its significance and has been removed.
MQTT (HiveMQ) Adapter: The specific implementation for HiveMQ has been discontinued.
jTDS-Database Driver: This outdated JDBC driver is no longer supported for security and maintenance reasons.
Integrated Manager Update Function: The automatic update is being removed; the Manager is now available as a separate download with each release.
Scripted-Startup: This method has been completely replaced by the new Launcher.
Resource Owner Password Flow (for E-Mail and HTTP Adapters): This flow no longer meets current security standards and is therefore no longer supported.
We recommend that you start planning a migration early to benefit from the new possibilities. If you have any questions, our support team is happy to help.
What does “deprecated or removed” mean?
When we mark a function as deprecated, you can still use it, but it is no longer actively developed. In a later version, it may be removed entirely. In such cases, we usually recommend an alternative approach so that you can plan necessary adjustments in advance.
A function marked as removed is permanently unavailable. The reasons for such steps are often technical progress, performance or security aspects, as well as the goal of a clearer API structure.
What this means for you in practice – and how to best deal with such changes – is explained in detail in our Community article: https://community.transconnect-online.de/thema/5474/