Upgrading the Content Delivery Roles
Upgrading Content Delivery Roles consists of updating your resources.
- Upgrading Content Delivery server-side software components
The majority of your Content Delivery server-side software components run as a microservice, either as a standalone microservice or (if you are upgrading from SDL Web 8.5) as a Java/JSP Web application-based microservice (a discontinued option as of SDL Tridion Sites 9). There are also a few server-side software components that are extensions of other microservices. Regardless of your setup, you must install the new search feature, before installing or upgrading the (Session-enabled) Content Service. - Upgrading client-side Content Delivery software components
Upgrade the client-side Content Delivery software components to a version compatible with this product release. Client-side Content Delivery software components can be upgraded in their original in-process form (a deprecated setup); or they can be replaced with their new RESTful equivalents. The RESTful clients are different from the in-process clients in two ways: one, they are more lightweight and have much fewer dependencies; two, the .NET versions of the clients no longer require JuggerNET and Java; they are pure .NET-only clients. - Upgrading a Content Delivery Server Role to a new environment
Depending on your specific upgrade path, you may need to (or want to) upgrade not only your Content Delivery software, but also your web application server (release and/or vendor), your operating system (release and/or vendor) or even your hardware. If so, this task explains what to do before performing the other upgrade steps.