Adobe Campaign Classic comes with a set of modules and options. The availability of these modules and their use can depend on the type of deployment of your installation. This article shares some details about the main differences for certain features between fully hosted (Managed Services) and on-premise deployments.
The different types of deployment available for Adobe Campaign Classic are detailed in this page.
This article shows the main differences between hosted (Managed Services) and on-premise deployments. Hybrid deployments specificities depend on the elements hosted by Adobe and hosted in your premises.
You can also visit the Adobe Campaign Classic product description page.
|Connecting to an external database (FDA - Federated Data Access)||Not available||Available||Available||The external database needs to be exposed to the Campaign server. As a consequence, FDA is only available for deployments that are not fully hosted by Adobe.|
|Configuring Campaign server||Request to support||Available||Available||
The server configuration files and all the parameters they contain can only be modified by Adobe when hosted by Adobe. If you want a specific configuration to be enabled or modified, contact Adobe to have it done. For example:
|Archiving emails||Request to support||Request to support||Available||For fully hosted and hybrid architectures, contact your account executive to activate email archiving. For on-premise installations, follow the guidelines from documentation.|
|Managing Message Center execution instance||Request to support||Request to support||Available||Certain actions, such as creating users on Message Center execution instance, can only be done by Adobe for fully Adobe hosted deployments.|
|Managing Mid-sourcing platform||Request to support||Request to support||Available||Mid-sourcing platforms hosted by Adobe can only be configured by Adobe.|
|Inbox rendering via Litmus||Request to support||Request to support||Available||You need a Litmus account. If you don't have a Litmus account, you can request an account to Adobe, who will provide the necessary details or perform the configuration.|
|Integrating with IMS (Adobe ID)||Request to support||Request to support||Request to support||IMS provisioning is performed by Adobe. Integrating with IMS is a prerequisite for several Adobe Experience Cloud integrations, such as Audience Manager/People core service, Assets core service.|
|Connecting with ACS (Adobe Campaign Standard)||Available||Available||Not available||The ACS Connector is only available for Adobe Campaign Prime (v7). It connects with Adobe Campaign Standard, which is hosted by Adobe.|
|Encrypting/Decrypting data for file transfers||Request to support||Available||Available||Enabling file pre- or post-processing requires installing the necessary utility on the Adobe Campaign server. For example, pgcrypto.|
|Zipping/Unzipping files||Request to support||Available||Available||Enabling file pre- or post-processing requires installing the necessary utility on the Adobe Campaign server. For example, gzip.|
|Updating your Adobe Campaign instance||Request to support||Request to support||Available||New builds are made available regularly. You can choose to update your application server and your client console. For instances hosted by Adobe, the update can be performed after sending a request to Support.|
|Domain Name Delegation||Request to support||Request to support||Not available|
|Installing SpamAssassin||Request to support||Available||Available||Installing SpamAssassin requires editing the server configuration file.|
|Accessing deliverability reports||Available||Request to deliverability team||Available||In certain cases of hybrid deployments, deliverability reports cannot be accessed from the marketing instance.|
|Configuring LDAP authentication||Not Available||Available||Available|