Installing the Content Deployer (HTTP or HTTPS) as a .NET Web application
Install the Content Deployer (HTTP or HTTPS) Server Role, to enable transport over the HTTP(s) protocol.
Before you begin
Procedure
- Ensure that all the prerequisites for a Content Delivery Server Role are met on your target system.
- If you use Windows 2012 or Windows 2012 R2, do the following:
- Start up the Server Manager and Add Roles and Features Wizard. Step through the wizard until you reach the Features screen.
- If you use .NET 4.5, expand the item .NET Framework 4.5 Features and the subitem WCF Services. If the option HTTP Activation is not listed as installed, select it.
- Alternatively, if you use .NET 3.5, expand the item .NET Framework 3.5 Features. If the option HTTP Activation is not listed as installed, select it.
- Click Next and Install to install the feature.
- If you use Windows 2008 R2 SP1, do the following:
- Start up the Server Manager and under Features Summary, select Add Features.
- In the Add Features dialog that opens, expand the item .NET Framework 3.5.1 Features and the subitem WCF Activation. If the option HTTP Activation is not listed as installed, select it.
- Click Next and Install to install the feature.
- Access the SDL Tridion installation media.
- Navigate to the Content Delivery\roles\ folder.
- Access the upload\dotNET\webapp subfolder.
- Do one of the following:
- To install a 32-bit .NET Web application, access the x86\ subfolder.
- To install a 64-bit .NET Web application, access the x86_64\ subfolder.
- Unzip the Zip file in this location to the location on your target system where you want to place the .NET Web application.
- In IIS Manager, create or select a Web site that will contain your Content Deployer (HTTP or HTTPS) .NET Web application.
- Select the Web site and in the IIS area on the right, select Authentication. In the list of properties that appears, set Anonymous Authentication to Disabled and Basic Authentication to Enabled.
- If this is a 32-bit .NET Web application running in combination with Java 6, then in the advanced system properties of your machine, select Environment Variables to see and edit your environment variables, and ensure that your
PATHvariable contains the bin\ subfolder of the Java instance you are using. This location contains the file MSVCR71.DLL. - Configure the IIS user who will be executing the HTTP upload Web page to have modify access to the Content Deployer location for incoming content. By default, the IIS user is the identity running the SDL Tridion Application Pool (which typically is the Network Service user).
- If you store published content in a database, download the JDBC driver (JAR file) required for your specific database vendor and copy it into the bin\lib folder of your Web application:
Vendor JDBC Driver Required JAR Microsoft SQL Server Microsoft SQL Server JDBC Driver 4.0 sqljdbc42.jar for Java 8
sqljdbc4.jar for Java 6 or Java 7
Oracle Oracle JDBC driver 11.2.0.3 (deprecated) ojdbc6.jar for Java 6 or Java 7
Oracle Oracle JDBC driver 12.1.0.1 ojdbc7-12.1.0.1.jar for Java 8
ojdbc7.jar for Java 7
ojdbc6.jar for Java 6
IBM DB2 IBM Data Server Driver for JDBC and SQLJ (9.7 GA) (deprecated) Not supported with Java 8
db2jcc.jar for Java 6 or Java 7
You can download JDBC drivers from the following locations:- Oracle: download the JDBC Driver 12.1.0.1 from this location: http://www.oracle.com/technetwork/database/features/jdbc/index-091264.html
- SQL Server: download the JDBC Driver 4.0 from this location: http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=11774
- DB2: the JDBC driver is included with your DB2 installation.
- Navigate to \Content Delivery\resources\configurations\.
- Copy logback.xml from that folder to the bin\config folder of your Web application.
- Copy and rename the following configuration files to the bin\config folder of your Web application:
Corresponding configuration file Renamed configuration file cd_deployer_conf_sample.xml cd_deployer_conf.xml cd_storage_conf_sample.xml cd_storage_conf.xml - Open the file cd_deployer_conf.xml for editing.
- In the
<Queue>section, add aLocationelement, for example:<Location Path="MYPATH" WindowSize="20" Workers="10" Cleanup="true" Interval="2s" />Specify thePathand optionally other attributes to optimize the publishing process:Path- The absolute path to the pickup location.
WindowSize- The maximum number of Transport Package that can be "in flight" (publishing or deploying) at any one time. It represents the number of publish actions the Content Deployer should be able to handle. The default value for this attribute is 20.
Workers-
The maximum number of deployment threads that can be running at any time. If
WindowSizeis bigger thanWorkers, items to publish may enter a deployment queue, which in turn may cause a publish action to time out and fail. The default value for this attribute is10.Note: If you store metadata on the file system rather than in a database, you cannot configure multiple workers. Interval-
The amount of time, in milliseconds (
ms), seconds (s), hours (h) and so on, that the Content Deployer waits before checking for new content in this location. The default value for this attribute is2s; that is, two seconds.
- Directly below the
<Queue>section, add the following element:<HTTPSReceiver MaxSize="10000000" Location="MYPATH" InProcessDeploy="true" />Configure the attributes as follows:
MaxSize- The maximum size (in bytes) of a Transport Package sent to the location.
Location-
The same value as the MYPATH you specified in the
Locationelement earlier. InProcessDeploy-
If you set this attribute to
true(this is the case by default), publishing and deployment is contained within the Web application. If you set it tofalse, you must have your Content Manager publish content over HTTP or HTTPS to a location outside the Web application, and run the Content Deployer as a standalone Windows service or Java process. In this setup, the entire publishing transaction bypasses your Web application, which can improve your publishing performance. Refer to Scaling Content Delivery for a more detailed explanation of this implementation plan.
- Save and close cd_deployer_conf.xml.
- Open cd_ambient_conf.xml for editing (if using).
- Find the
<Security>section and enclose it in comments. This element is only needed if you intend to set up OAuth authentication. - Save and close cd_ambient_conf.xml.
- Copy cd_licenses.xml, your Content Delivery license file available from SDL Tridion Customer Support, to the bin\config directory of your Web application.
If you want to name the file differently or put it in a different location, you need to update the
Licenseelement in your configuration files. - Optional: Configure logging.
- Configure the Storage Layer and optionally encrypt sensitive strings.
- Disable recycling of the Application Pool of this Web application by doing the following:
- Open IIS Manager.
- From the tree on the left, select the current machine and navigate to the Web application you just created.
- Click Advanced settings to open a dialog with the application's properties, and note down the value of Application Pool.
- Close the dialog.
- From the tree on the left, under the current machine, now select the Application Pools node.
- From the list on the right, select the Application Pool you just noted down.
- Select Recycling in the Edit Application Pool area on the right.
- In the dialog that opes, deselect Regular time intervals, then click Next and Finish to commit your change.
- Restart IIS.
- Restart the Web application.
- Test the installation by accessing the ASPX page HTTPUpload.aspx from a Web browser. The browser should display the following:
SDL Tridion ASPX Upload Page
Related concepts