Installing core Content Delivery standalone microservices
The microservices, also called Content Interaction Services, are the server-side components of Content Delivery.
- Performing an express installation of Content Delivery microservices
For fast installation, configuration, deployment and automatic registration of multiple Content Delivery microservices, use the express installation scripts found in the Content Delivery\resources\quickinstall\ folder of the SDL Tridion Sites 9.1 installation media. - Configuring Content Delivery environments for the Add-ons Service
For Extensions to Content Delivery, the Add-ons Service requires that you add a cdenvironment environment variable to each Content Delivery environment. - Containerizing Content Delivery microservices using Docker
Using the third-party enterprise container platform Docker (website at http://www.docker.com), you can containerize the Content Delivery microservices, that is, you can build and run the microservices as a collection of independent, self-contained applications. The only Content Delivery microservice that you cannot containerize is the Cache Channel Service, which is a deprecated feature. - Installing the Discovery Service
The Discovery Service is a core Content Delivery Server Role that must be installed in order for SDL Tridion Sites to work. - Installing the Content Service
The Content Service is a core Content Delivery Server Role. The Content Service must be installed in order for SDL Tridion Sites to work. - Installing the Session-enabled Content Service
The Session-enabled Content Service was the alternative for the regular Content Service, to be used in a Content Delivery environment that enables inline editing of its content using the Experience Manager user interface. It is no longer necessary to install this feature; instead, you can enable session management in the normal Content Service. Only install this deprecated microservice if you have a pressing reason to do so. When the deprecated Session-enabled Content Service is installed, the Content Service does not need to be installed. - Installing the Content Deployer feature
Content Deployer takes care of receiving incoming content published from Content Manager at the Content Deployer endpoint, and processing and storing the content using a Content Deployer worker. You can combine endpoint and worker in one microservice, the combined Content Deployer. Such a setup is recommended on a single-machine installation. If you want to (be able to) scale out Content Deployer, install the endpoint and worker separately. - Installing the Preview Service
The Preview Service is a core Content Delivery Server Role software component that must be installed in order for Experience Manager, one of the main user interfaces of SDL Tridion Sites, to work. Specifically, it connects to Content Manager to update resources based on modifications to published items on the presentation side. - Checking the health of the Content Delivery microservices
To check the health of each of your Content Delivery microservices, visit the microservice health URL. You can create this URL by assembling its component parts. - Configuring JVM memory settings in the microservice installation scripts
The easiest way to allocate less or more memory than the default for your standalone microservice is by editing the contents of the startup scripts, installService.ps1, start.ps1 or start.sh.
Related concepts