Installing core Content Delivery standalone microservices
The microservices, also called Content Interaction Services, are the server-side components of Content Delivery.
- Content Delivery prerequisites
This topic lists the required and supported software for installing Content Delivery Roles. There are different prerequisites for microservices on the one hand, and for client APIs and Web application extensions on the other hand. - 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 Tridion Sites to work. - Installing the Content Delivery Search feature
The Search feature enables the indexing and querying of searchable content from the Content Delivery-based website. The feature requires a microservice, the IQ Index Service, for indexing. Querying is performed using the Public Content API, and queries are handled by the (Session-enabled) Content Service. Although RWS considers Content Delivery Search to be a core feature, you may not want to install it, perhaps because you already have your own search solution, or intend to use one. In that case, you can skip this section and follow the instructions in the Content Deployer documentation about how to disable search. - Installing the Content Service
The Content Service is a core Content Delivery Server Role. The Content Service must be installed in order for Tridion Sites to work. - Installing the Session-enabled Content Service
The Session-enabled Content Service in an 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. When the Session-enabled Content Service is installed, the Content Service does not need to be installed. - 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 Tridion Sites, to work. Specifically, it connects to Content Manager to update resources based on modifications to published items on the presentation side. - Installing the Content Deployer
The Content Deployer takes care of receiving incoming content published from Content Manager, and processing and storing that content. - 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