Whether you intend to perform a minimal upgrade for the time being and migrate later, or you intend to migrate to the new Content Delivery setup immediately, this topic provides you with a broad outline of how the deprecated setup with in-process APIs should be migrated to a new setup using the RESTful APIs.
Procedure
- Check the list of Content Delivery known issues to ensure that none of the items mentioned applies to your implementation.
- Ensure that you have installed the Discovery Service. (The minimal upgrade procedure already instructs you to do so.) It has OAuth authentication enabled automatically, but you can switch off this feature.
- Ensure that the Preview Service is configured correctly, and register it with the Discovery Service.
- If you have configured any storage medium using JNDI, change your Storage Layer configuration to no longer use JNDI: it is not supported with standalone microservices.
- if you have server-side Content Delivery .NET Web applications, remove all SDL Web .NET DLLs (which start with Tridion.) and Java JARs (both Content Delivery's own JARs, which start with cd_ or ugc_, and third-party libraries not in use by others) from all of them. Also remove the following configuration files from bin\config\, which are no longer needed:
- jvm.xml
- logback.xml
- cd_storage_conf.xml
- cd_licenses_conf.xml
- if you have Java/JSP Web applications, remove all SDL Web Java JARs (which start with cd_ or ugc_) (including third-party libraries not in use by others) from all of them. Also remove the following configuration files from bin\config\, which are no longer needed:
- cd_storage_conf.xml
- cd_licenses_conf.xml
- On the client side (that is, in your own Web sites and Web applications), install the API (RESTful) Server Role and the Preview Web site extension.
- Refer to the installation documentation to configure these software components, merging any existing client file changes you may have made with the new defaults.