Publishing diagram
The following diagram shows the various stages of a publish action, from the moment a user pushes the Publish button to the moment the visitor sees the published content.
The publishing process works as follows:
- Publish—a user publishes content to a Target Type.
- Target Type—a Target Type specifies a user-friendly name for one or more Publication Targets.
- Publication Target—a Publication Target defines the information required to publish content using a specific protocol.
- Publisher Engine—the Publisher Engine generates Publish Transactions and puts them in the Publisher Queue.
- Publisher Queue—the Publisher Queue holds Publish Transactions waiting to be picked up by the Publisher Service.
- Publisher Service—the Publisher Service picks up Publish Transactions in the Publisher Queue, resolves and renders the items and passes the resulting Transport Package to the Transport Service.
- Transport Service—the Transport Service sends Transport Packages to the Content Deployer Queue over a specific protocol, or throttles the service if it calculates that the Content Deployer is overloaded. Throttling occurs based on a calculation of the following information:
- the number of Transport Packages the Content Deployer can process at a time
- the number of Transport Packages the Content Deployer is currently processing
- Content Deployer Queue—the Content Deployer Queue is the file system location where Content Deployer can pick up Transport Packages.
- Content Deployer—the Content Deployer picks up and processes Transport Package and passes the content to the Storage Layer.
- Storage Layer—the Storage Layer stores content in the Content Data Store (a file system, relational database, or both).
The publishing process is completed when the content arrives at the Storage Layer as the content is then available for Web site visitors. When a visitor requests a URL of the Web site, the Presentation Server—the server on which your SDL Tridion-driven Web site is hosted—retrieves content from the cache, if configured and if the content is fresh, otherwise from the database and/or file system.