Skip to main content

for questions that are related to Content Delivery (CD), including distribution, presentation, and storage APIs.

Content Delivery is the last part of the Publishing process where the content is being distributed to the Presentation Server. Content Distribution comprises the following sub processes:

Content Deployer
On the Content Delivery system, a Content Deployer receives the Transport Package. The Content Deployer uses one of its Processors to process the contents of the Transport Package. Each Processor contains a number of Modules which specify the steps in the deployment or undeployment process. The package is processed by the Content Deployer and the items in the package are sent on to the Storage Layer.
You can add your own custom processing (Processor and Module elements) to the Content Deployer.

Storage Layer
The Storage Layer handles the storing and retrieving of data to and from the Content Data Store. The Storage Layer is configurable so that you can store individual types of Content Manager items published from the Content Manager system to different databases.
You configure where to store content in the cd_storage_conf.xml configuration file.

You can implement object caching to store the most commonly used objects in the cache in order to speed up your Web site.

Content Delivery APIs
The Content Delivery APIs allow you to access published content (Pages, Component Presentations, and published metadata) from your Web pages using the ASP.NET APIs or the JSP APIs depending on the Web technology you use.

Presentation Server
The Presentation Server is the machine on which the Web Application Server is installed (which can be the same machine as the Content Delivery system).