Deprecated and removed features deprecated-and-removed-features
Adobe constantly evaluates product capabilities to identify older features that should be replaced with more modern alternatives to improve overall customer value, always under careful consideration of backward compatibility. As Adobe Campaign Classic works with 3rd party tools, compatibility is updated on a regular basis, in order to implement supported versions only. Versions which are no longer compatible with Adobe Campaign Classic are listed below and in the Compatibility matrix.
To communicate the impending removal/replacement of Campaign Classic capabilities, the following rules apply:
- Announcement of deprecation comes first. While deprecated capabilities can still be available and supported for existing users, they will not be further enhanced, nor documented.
- Removal of deprecated capabilities will occur in the following release at the earliest. Actual target date for removal is announced in this page.
This process gives customers at least one release cycle to adapt their implementation to a new version or successor of a deprecated capability, before actual removal.
Deprecated features deprecated-features
This section lists features and capabilities that have been marked as deprecated with latest Campaign Classic releases.
Generally, features that are planned to be removed in a future release are set to deprecated first. These features and capabilities are either no longer available for new Campaign Classic customers, or should not be used for any new implementation. They are also removed from product documentation.
Customers are advised to review if they make use of the feature/capability in their current deployment, and make plans to change their implementation. Please refer to the target removal date to plan your environment and project updates accordingly.
Removed features removed-features
This section lists features and capabilities that have been removed from Campaign Classic.
End of compatibility end-of-compatibility
Client console client-console-eol
Adobe Campaign Classic Client Console can no longer run on the following systems as they have been deprecated by their editor. Customers running Campaign Client Console on one of these versions need to upgrade to newest version before target removal date. Refer to the Compatibility matrix.
- Windows Server 2003, 2008, 2008 R2
- Windows 7, XP, Vista
Operating systems o-s-eol
-
Starting 22.1 release, Adobe Campaign is no longer compatible with CentOs 8.x (64 bits). CentOS Linux 8 reached End Of Life (EOL) on December 31st, 2021. Learn more.
If you were using this operating system, adapt your implementation accordingly. CentOS 7.x (64 bits) and RHEL 8.x/7.x (64 bits) are still supported.
-
Starting 21.1.3 release, Adobe Campaign is no longer compatible with Debian 8.
-
Starting 19.1 release, Adobe Campaign is no longer compatible with the following operating systems.
- CentOS 6. Learn more
- Debian 7. Learn more
- RHEL 6.x. Learn more
- Windows Server 2008. Learn more
- SLES 11. Learn more
Web servers web-server-eol
Starting 19.1 Spring Release, Adobe Campaign is no longer compatible with the following web server.
- Apache 2.2. Learn more
- Microsoft IIS 7. Learn more
Tools tools-eol
Starting 19.1 Spring Release, Adobe Campaign is no longer compatible with the following tools.
- Java JDK 7. Learn more
- Libre Office 3.5 / 4.3 / 5.x, except when embedded in another tool. Learn more
Database engines dbe-eol
Adobe does not support the following database engines as they have been deprecated by their editor. Customers running in these versions need to upgrade to newest version or move to another one.
Refer to Campaign Compatibility matrix to access the list of compatible versions.
FEDERATED DATA ACCESS (FDA)
Starting 20.2 release, Adobe Campaign is no longer compatible with the following FDA Server:
- DB2 UDB 10.5
Starting 19.1 Spring Release, Adobe Campaign is no longer compatible with the following FDA Servers:
- PostgreSQL 9.3.
- MySQL 5.5.
- DB2 9.5.
- Teradata 14 – 14.1.
Campaign Classic is not compatible with the following servers in Federated Data Access (FDA). Please use more recent versions, or systems.
- DB2 UDB 9.5, 9.7.
- Oracle 9i, 10G R2.
- PostgreSQL versions up to 9.6 reached end of life.
- MSSQL 2000, 2005, 2008 R2.
- MySQL 5.1.
- InfiniDB reached end of life.
- Teradata 13, 13.1.
- Netezza 6.02, 7.0. Netezza reached end of life.
- AsterData 5.0. AsterData reached end of life.
- Sybase IQ 15.2, 15.4, 15.5 and Sybase ASE 15.0.
- Hadoop via HiveSQL: Hadoop 2.7.3, HiveSQL 1.2.1. Adobe Campaign Classic still support the listed versions of Hadoop via HiveSQL through Federated Data Access (FDA), but these versions are merged with: HortonWorks (HDP 2.4.X, 2.5.x, 2.6.x) and HDInsight 3.4 (HDP 2.4), 3.5 (HDP 2.5), 3.6 (HDP 2.6)
RDBMS SERVER
Starting 19.1 Spring Release, Adobe Campaign is no longer compatible with the following RDBMS Servers:
- Oracle 10GR2
- PostgreSQL 9.0 to 9.3
- SQL Server 2005
- MySQL 5.1
- DB2 UDB 9.7
PostgreSQL versions up to 9.6 reached end of life. They are therefore not supported by Adobe Campaign.
SMS connectors sms-eol
Starting 20.2 release, Legacy SMS connectors are deprecated. Adobe Campaign is not compatible with:
- Generic SMPP (SMPP version 3.4 supporting binary mode)
- Sybase365 (SAP SMS 365)
- CLX Communications
- Tele2
- O2
- iOS
CRM connectors crm-connectors
Starting Campaign 21.1 release, the following CRM connectors are no longer compatible with Campaign:
- Soap API - On-premise: 2007, 2015, 2016
- Soap API - Online: 2015, 2016
- Web API – Microsoft Dynamics CRM 2016
- Web API – Microsoft Dynamics CRM 2016 Update 1
- Oracle On Demand API