Content Delivery implementation
Content Delivery provides modules for getting content out of the Content Manager and on to the Presentation Server and APIs for implementing dynamic Web site functionality.
- Content Delivery API namespaces and Java packages
Content Delivery modules turn the content in your Content Manager into a fully-functional, dynamic Web site. - Versions of microservices (Content Interaction Services)
By default, any code you write that interacts with the Content Delivery microservices, also called Content Interaction Services (CIS), is assumed to work with any version of the microservices. But both in Java and in .NET, you can use annotations to specify exactly which version(s) of the CIS your code will work with. - Restarting microservices
If you change the configuration, resources or anything else about a standalone microservice, you need to restart the microservice to apply the changes you made. This topic explains how to restart your microservice. - Configuring logging of HTTP requests to microservices
In an application.properties or application.yml file for your microservice, ensure the presence of a number of properties in order to enable the logging of HTTP requests. - Developing Web sites
Content Delivery is about getting content out of the Content Manager and on to the Presentation Server and implementing dynamic functionality in Web sites. This section provides an overview of how to implement Content Delivery and develop your Web sites using Content Delivery Modules. - Implementing and extending Content Deployer
You can tweak the settings of your Content Deployer Workers, and you can extend your Content Deployer implementation by creating or modifying a Module. - Storage Layer
The Content Deployer deploys incoming content from the Content Manager to the Storage Layer, which stores the content in the Content Data Store, which is a database or the file system ). You can extend the Storage Layer to enable storage to any medium. You configure storage in the Storage Layer configuration file. - Caching
Caching speed up your Web site by storing commonly used or resource-intensive objects in a server-side cache. The server-side cache keeps these objects available rather than reinitializing them each time they are requested. In a scaled-out scenario, synchronize the various caches using remote synchronization. Content Delivery also has client-side caching, which can be configured in the .NET Web application's Web.config file or in the file cd_client_conf.xml in a Java/JSP Web application - Dynamic Component Presentations
Components are combined with Component Templates during publishing to produce Component Presentations. A Component Presentation is a publishable piece of content. You can add static Component Presentations to a Web page manually in the Content Manager, or dynamically at runtime. This section describes how to create Dynamic Component Presentations. - Managing Web site code (TCDL)
SDL recommends that you manage your Web site code using SDL Web. When you use and create tags in a technology-neutral language called TCDL, Content Delivery can transform them into your Web site's language (actual code) at various stages of the delivery process. - Search
You can implement search as a free-form interface using a third-party search application; or you can use the filtering and querying capabilities of the Content Delivery API to create a query-type interface for searching. - Dynamic Link Resolving
You can create links to Components, Multimedia Components or Pages. On the published Web site, the links become links between published Web pages. You can configure how Content Delivery handles dead links, ambiguous links, and links to Components that were published but not embedded on a Page. - Navigation
You can implement Web site navigation in an SDL Web-based Web site using the organization of Structure Groups in the Content Manager, or you can use a taxonomy tree (Categories and Keywords) to create more sophisticated navigation (intelligent navigation). - Content Service
The Content Delivery Content Service, or Content Service for short, is the Web service that delivers content from the Content Delivery environment to the Presentation Server. It can also be used for integration with affiliate Web sites. - Ambient Data Framework
The Ambient Data Framework allows you to gather and transform Web site data, such as information about your visitor or about the current session and implement specific functionality by creating your own Claim Processors and organizing them into cartridges that plug into the framework. - Context Engine
Use Context Engine to retrieve, and respond to, information about the user visiting your Web site, as well as the hardware and software used to access the site. Device information is supplied by the SDL Mobile device database, which is a separately licensed offering from SDL. Without this database, Context Engine has no access to device information. Context Engine integrates with the Ambient Data Framework to make use of this context information. - Contextual Image Delivery
When developing a mobile version of your Web site, you may want to serve cropped, scaled-down or otherwise transformed versions of the images on your Web server. Contextual Image Delivery lets you construct URLs that transform images server-side at request time, and serve the transformed images to the client. - Profiling and personalization
Use profiling to track who visits your Web site, which content they access, and which links they click. Use personalization to use the information gathered through profiling to define types of Web visitors and to mark content as being only interesting to a specific type of Web visitor. Personalization and Profiling requires Dynamic Component Presentations and the Content Data Store must be a relational database (Microsoft SQL or Oracle). - Content Delivery security
This section describes the subsystems and services of Content Delivery System, the default user accounts used to access and run these subsystems, and the minimal rights, privileges and/or permissions required by an account to operate a subsystem. - Reference section
This section contains reference information for Content Delivery.