Legacy features
Legacy features are features that are still supported for existing users, but are not recommended for new users.
- Installing the legacy API (in-process) Server Role
Only in order to maintain an old Content Delivery infrastructure, set up before SDL Web 8, does SDL suggest installing this legacy Server Role. In the vast majority of cases, a fresh install implies a fresh API Server Role: the API (RESTful) Server Role. - Adding the legacy in-process Experience Manager Web site extension to a legacy Web site
If your Web site still uses the deprecated in-process API Server Role, this section explains how to add the in-process version of the Experience Manager Web site extension to that Web site. - Other transport protocols than HTTP or HTTPS
As of SDL Web 8, protocols other than HTTP or HTTPS (both those included in the product or custom ones you developed yourself) are deprecated. You can continue using this functionality, but note that the Server Role called Content Deployer (other protocols) has now become a part of the new Server Role called Content Deployer, which is a microservice that encompasses all protocols. To use non-HTTP(S) transport protocols, ensure that in all your Content Deployer configuration files (cd_deployer_conf.xml) the rootDeployerelement has an attribute calledLegacyTransport, set totrue. Legacy transport protocols cannot be used in combination with a Redis database. - Setting up Publishing (Content Distribution) in the deprecated publishing framework
To be able to publish content from the Content Manager server to the Content Delivery server using the publishing framework that was deprecated in SDL Web 8, on the Content Manager server you need to create and configure Publication Targets, Protocols, Target Types, and the Transport Service. (To enable Content Distribution on the Content Delivery Server you need to configure (or customize) your Content Deployer and Storage Layer, and optionally Caching.) - Implementing publishing (Content Distribution) in the deprecated publishing framework
Content Distribution is the process of getting content out of the Content Manager and on to the Presentation Server. To implement Content Distribution on the Content Manager Server, perform configuration tasks on both sides. - Legacy Content Delivery storage on the file system
Published content is stored in the Content Data Store, which is normally a database. However, SDL Web still supports storage on a local file system (the hard disk of a Presentation server or a network-accessible hard disk) as a deprecated legacy feature. However, if you use the local file system as your Content Data Store, you restrict the functionality of SDL Web in many ways. - Setting up the Ambient Data Framework in a Java Web application
To install the Ambient Data Framework for a Content Delivery Java Web application, copy JAR files, copy a configuration file, and modify web.xml. - Installing the Ambient Data Framework in a .NET Web application
To install the Ambient Data Framework for a Content Delivery .NET Web application, copy JAR files, copy a configuration file, and modify Web.config. - Installing Audience Manager cartridge in a legacy in-process setup
The Audience Manager cartridge puts Segments, Contact details and Contact extended details into the Claim Store as Claims. You need to install and configure the Audience Manager cartridge in the Web application in which your website is running. - Installing Contextual Image Delivery in a legacy in-process setup
If you have upgraded your API (in-process) Server Role without migrating to API (RESTful), and you want to install Contextual Image Delivery in this deprecated setup, a legacy installation is required. - Setting up Context Engine Cartridge Custom Tags or Server Controls in the deprecated in-process API-based Web site
Context Engine Cartridge ships with a custom element for rendering content only if a certain context expression evaluates totrue, and another custom element for rendering the result of evaluating a context expression. You need to configure these custom elements only if you still use the deprecated in-process API on your Web site, rather than the new RESTful API. Regardless of which API you use, you always need to configure these elements in Content Deployer. This topic explains how to enable these custom elements for JSP as Custom Tags, or for ASP.NET as Server Controls, on your Web site. - Experience Optimization legacy features
Experience Optimization legacy features are still supported for existing users, but are not recommended for new users. - Installing the legacy Outbound E-mail feature
Install Outbound E-mail, a legacy feature, only if you are setting up a new machine to add to an old implementation. Outbound E-mail is for managing e-mail campaigns and requires that Audience Manager is set up. - Implementing Outbound E-mail
Outbound E-mail, a deprecated product feature, lets marketing departments implement and manage e-mail communication campaigns. You can configure and implement Outbound E-mail to make it meet the demands of your organization. You can also extend it using its extension points. - SpellChecker
You can configure the behavior of the deprecated SpellChecker feature, exposed (if installed) in Content Manager Explorer. You can also specify a custom dictionary for SpellChecker to use. In both cases, you modify the configuration file SpellCfg.xml.