Reference section
This section contains reference information for Content Delivery.
- Content Delivery microservices, their relative endpoint URLs and their default port numbers
Every microservice has a relative endpoint URL. Also, by default. every Content Delivery microservice runs on a specific port number. This topic tells you the endpoint URL and default port number for each microservice. If the port number is somehow unavailable to you, you can change the microservice installation script to run on a different port number. - Content Delivery JAR file reference
A list of JAR files for Content Delivery Server Roles and the Transport Service on the Content Manager. These are not prerequisites; SDL Tridion Sites includes them in its installation media. Note that some of these JARs are contained in WAR files. - Content Delivery third-party JAR file reference
A list of third-party JAR files for Content Delivery Server Roles and the Transport Service on the Content Manager. These are not prerequisites; SDL Tridion Sites includes them in its installation media. Note that some of these JARs are contained in WAR files. - Content Delivery configuration file reference
This section contains reference documentation for the configuration files used by basic Content Delivery Server Roles, and links to other Content Delivery configuration file reference documentation. In some configuration files, including cd_storage_conf.xml, we use parameters instead of hardcoded or literal strings for some configuration values. - Metadata reference
Metadata reference contains information and samples of system and custom metadata. - Reference for Server Controls, Custom Tags and TCDL tags
To access Content Delivery functionality from your web application, use the Server Controls if you produce ASP.NET content, Custom Tags if you produce JSP content, and TCDL tags if you produce TCDL in your output (if you publish to the target language Render Engine Language, or REL for short). - System classpath generation
On Windows systems, the Java Virtual Machine (JVM) uses the system classpath to locate libraries and other resources such as configuration files.