Upgrading Content Delivery
Content Delivery consists of various Server Roles that run as a Web application, Windows service or Java process. Upgrade your Server Roles by removing obsolete JAR files, updating JAR files, adding resources, downloading and (re)installing third-party libraries, updating configuration files and migrating Content Delivery functionality.
- Checking changes in prerequisites for Content Delivery
SDL Tridion 2013 SP1 Content Delivery has changed a number of prerequisites compared to SDL Tridion 2009 SP1, SDL Tridion 2011 SP1, SDL Tridion 2011 SP1 HR1, SDL Tridion 2011 SP1 HR2 or SDL Tridion 2013. The hotfix rollup 1 for SDL Tridion 2013 SP1 introduces some further changes. - Upgrading the Content Delivery Server Roles
Upgrade your Server Roles by removing obsolete JAR files, updating JAR files, adding resources and by downloading and (re)installing third-party libraries. - Upgrading the Context Engine Cartridge
In addition to updating your set of JAR files, perform a number of additional tasks to update your Context Engine Cartridge Server Role. - Upgrading the Content Delivery Web service configuration
If you use the Content Delivery Web service on its own, as part of the session preview feature, and/or as part of User Generated Content, some configuration changes are required to make it work with SDL Tridion 2013 SP1. - Upgrading the User Generated Content (UGC) Server Role configuration
Some configuration changes are required to make an existing UGC Server Role work in SDL Tridion 2013. - Upgrading Content Delivery .NET Server Roles
To upgrade a .NET Server Role, first follow the universal procedure for upgrading a Server Role. Next, depending on the SDL Tridion release from which you are upgrading, perform one or more additional steps to upgrade your .NET Server Roles. - Upgrading Content Delivery Server Roles running as Windows services
To upgrade Content Delivery Server Roles that run as Windows services (that is, Content Deployer, Monitoring, or the Cache Channel Service), stop the service you want to upgrade and run the installer. - Upgrading your Content Delivery configuration
Upgrade your Server Roles' configuration files to make your Server Roles work with SDL Tridion again. - Restarting Server Roles
Finalize the Content Delivery upgrade by restarting all Web applications, Windows services and Java processes that use Content Delivery functionality. - Migrating Content Delivery functionality
As of SDL Tridion 2011, a number of existing features has been deprecated and replaced with equivalent new features. Because the old feature was deprecated, you can continue using it. But because the feature may be dropped in the next release, you may want to migrate already to the new functionality. - Making custom code work with new Content Delivery .NET assemblies
If you created custom code that interacts with (parts of) Content Delivery running as a .NET Web application, then in order to work with Content Delivery 2013 SP1, your custom code requires policy files that resolve DLL versioning conflicts. Copy these policy files (and the new Content Delivery DLLs) to your Windows assembly on the machine that runs your custom code. - Making custom code work with the new Content Delivery Web service
As of SDL Tridion 2013, theComponentPresentationentity returned by the Content Delivery Web service contains a new property calledEncoding.