New Content Delivery Roles for upgrades from SDL Tridion 2013 SP1 HR1
This product release introduces a number of new Roles if you are upgrading from SDL Tridion 2013 SP1 HR1
- Discovery Service
-
Without this core Role, a (RESTful, service-based) Content Delivery installation will not work, so it is required to install this Role if you want to use the new architecture. You can install this Role as a standalone microservice (preferred) or as a Web application-based microservice (deprecated).
- Content Service
-
In a Content Delivery environment in which Preview is not set up, a (RESTful, service-based) Content Delivery installation without this core Role will not work, so it is required to install this Role if you want to use the new architecture and do not have Preview set up. You can install this Role as a standalone microservice (preferred) or as a Web application-based microservice (deprecated).
Depending on your current setup, you may need to upgrade or install from scratch:- If you have the Content Delivery Web service set up, upgrade it to become the Content Service. In this case, it can run as (part of) a Web application; you will then have a Web application-based microservice (a deprecated setup). Alternatively, you can migrate completely to Content Service as a standalone microservice.
- If you do not have the Content Delivery Web service set up, install the Content Service, either as a Web application-based microservice (a deprecated setup) or as a standalone microservice.
- Session-enabled Content Service
-
In a Content Delivery environment in which Preview is set up, a (RESTful, service-based) Content Delivery installation without this core Role will not work, so it is required to install this Role if you want to use the new architecture and have Preview set up. You can install this Role as a standalone microservice (preferred) or as a Web application-based microservice (deprecated).
- API (RESTful)
-
Replacing the Role called "API" (now renamed to "API (in-process)" and categorized as a legacy Role), the API (RESTful) Role contains a large number of Content Delivery APIs, including the Content Service API, Linking API, Audience Manager API, UGC API and so on). You install this Role as (part of) a Java/JSP Web application (and you can interact with it from .NET using a reverse proxy).
- Contextual Image Delivery
-
This nonessential Role previously shipped as a separate add-on, but is now a part of the SDL Web 8 product itself. Refer to the installation section to learn whether and how to install this Role.
- Content Deployer endpoint, Content Deployer worker
-
This release splits up the existing Content Deployer (HTTP or HTTPS) Role into two new Roles (microservices):
- The Content Deployer endpoint is the microservice that accepts incoming content published from Content Manager
- The Content Deployer worker is the microservice that takes care of the actual processing and storage of the incoming content.