Documentation Center

Content Delivery Role upgrade reference for upgrades from SDL Tridion 2013 SP1 HR1

As of SDL Web 8, you set up Content Delivery server-side software components as a set of microservices, with which you interact using client-side APIs and Web application extensions. The preferred upgrade plan (and the only option if you use .NET) is to replace all your existing Content Delivery Web applications with standalone microservices. You also always need to install a new Role (microservice): the Discovery Service. On the client side, an upgrade means continuing to use the deprecated in-process API.

Upgrading your Java/JSP Web application-based Content Delivery

If you currently run all your Content Delivery software as Java/JSP Web applications (and Windows services or Java processes), you can continue to use your in-process API Server Role and turn your server-side Java/JSP Web applications into standalone microservices.

Your upgrade operations per software component are as follows:
Current software componentTasks to perform
APIUpdate the resources of this software component (now known as API (in-process), a legacy Role)
Cache Channel ServiceUninstall this Role and reinstall it as a standalone microservice
Content Delivery Web serviceUninstall this Role and reinstall it as a standalone microservice called the Content Service
Content Deployer (HTTP or HTTPS)Uninstall this Role and install two standalone microservices: the Content Deployer endpoint and the Content Deployer worker.
Monitoring AgentUninstall this Role and reinstall it as a standalone microservice
Monitoring Agent Web serviceUninstall this Role and reinstall it as a standalone microservice
Session Preview Web serviceUninstall this Role and reinstall it as a standalone microservice called the Preview Service
Session Preview Web extensionUpdate the resources of this Role, which is now known as Preview Web extension
UGC Community ServiceUninstall this Role and reinstall it as a standalone microservice
UGC Moderation ServiceUninstall this Role and reinstall it as a standalone microservice
UGC Content Deployer extensionUpdate the resources of this Role
UGC Web site extensionUpdate the resources of this Role
Context Engine serviceUninstall this Role and reinstall it as a standalone microservice
Context Engine Web application extensionUpdate the resources of this Role

While the possibility to run microservices inside a Java/JSP Web application does exist, this kind of implementation is actively discouraged and not available in the product deliverable itself. If you do select this option, your Web application-based microservice must be a separate Web application from your own, and from a Web application that contains Content Delivery API/client software.

Upgrading your .NET Web application-based Content Delivery

If you currently run all your Content Delivery software as .NET Web applications (and Windows services or Java processes), you can continue to use your in-process API Role. The server-side software can no longer run as a .NET Web applications; you need to replace them with standalone microservices. Your existing API can call these microservices directly, or, if you have a pressing reason to keep using the same host and port in IIS, you can preserve your .NET Web applications by making them call the microservices using a reverse proxy. In that scenario, your server-side .NET Web applications continue to exist, but they no longer need their DLLs, JARs or configurations. Software components that already existed as services only (such as the Cache Channel Service, which existed as a Windows service or Java process only) are recast as standalone microservices. Your upgrade operations per software component are as follows:
Current Server Role software componentTasks to perform
APIUpdate the resources of this Role. Your API Server Role is now the legacy API (in-process) Role.
Cache Channel ServiceUninstall this Role and reinstall it as a standalone microservice
Content Delivery Web serviceUninstall this Role and install the new Content Service Role as a standalone microservice. If you want, use a reverse proxy to make your .NET Web application redirect to it.
Content Deployer (HTTP or HTTPS)Uninstall this Role and reinstall it as a standalone microservice. If you want, use a reverse proxy to make your .NET Web application redirect to it.
Monitoring AgentUninstall this Role and reinstall it as a standalone microservice
Monitoring Agent Web serviceUpdate the resources of this Role
Session Preview Web serviceUninstall this Role and reinstall it as the standalone Preview Service microservice. If you want, use a reverse proxy to make your .NET Web application redirect to it.
Session Preview Web extensionUpdate the resources of this Role, which is now called the Preview Web extension.
UGC Community ServiceUninstall this Role and reinstall it as a standalone microservice. If you want, use a reverse proxy to make your .NET Web application redirect to it.
UGC Moderation ServiceUninstall this Role and reinstall it as a standalone microservice. If you want, use a reverse proxy to make your .NET Web application redirect to it.
UGC Content Deployer extensionUpdate the resources of this Role
UGC Web site extensionUpdate the resources of this Role
Context Engine serviceUninstall this Role and reinstall it as a standalone microservice
Context Engine Web application extensionUpdate the resources of this Role