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.
- Content Delivery .NET upgrade impact overview
This topic shows, for each release from which you are upgrading, the impact of upgrading to SDL Tridion 2013 SP1. - Making your 32-bit .NET Web application using Java 6 work
To make your 32-bit .NET Web applications that uses Java 6 work in SDL Tridion 2013 SP1, ensure the presence of the bin\ subdirectory of your Java instance in yourPATHvariable. - Turning on HTTP Activation
Switch on Windows HTTP Activation for each Server Role you have installed that runs as a .NET Web service or a .NET Web application. - Upgrading the .NET API Server Role
If your Web application interacts with the Content Delivery .NET API, remove old DLLs, update existing DLLs, and add new DLLs. - Upgrading the .NET HTTP Upload Server Role
If your HTTP Upload Server Role runs as a .NET Web application, you must also upgrade the Web page HTTPUpload.aspx and a number of DLLs in the HTTP Upload Server Role (now called the Content Deployer (HTTP or HTTPS) Server Role). - Upgrading the .NET Content Delivery Web service Server Role
To update your Content Delivery Web service Server Role running as a .NET Web application, you must also update existing DLLs. - Upgrading the .NET UGC Web site extension Server Role
You need to upgrade the DLLs required for the Web site extension for User Generated Content. - Upgrading the .NET UGC Moderator and Visitor Web service Server Roles
To update your UGC Moderator and Visitor Web service Server Roles running as .NET Web applications, you must also update existing DLLs. - Upgrading the .NET session preview Web service Server Role
To update your session preview Web service Server Role running as a .NET Web application (now called the Experience Manager Web service Server Role), you must also update existing DLLs. - Upgrading the .NET session preview Web site extension Server Role
To update your session preview Web site extension Server Role running as a .NET Web application (now called the Experience Manager Web site extension Server Role), you must also update existing DLLs. - Updating namespaces
- Installing new versions of deprecated Windows services
Only if you intend to keep using the classic ASP API or the 5.3 ASP.NET API, copy and install the deprecated Windows services for the Broker, Linking and the WAI.