Documentation Center

Installing the Community Web Service as a .NET Web application

User Generated Content requires you to install and configure two Web applications, one of which is used for adding comments (the Community Web Service). Note that this Web application also contains the Content Delivery Web service Server Role.

Procedure

  1. Ensure that all the prerequisites for a Content Delivery Server Role are met on your target system.
  2. 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 PATH variable contains the bin\ subfolder of the Java instance you are using. This location contains the file MSVCR71.DLL.
  3. On your Windows machine, start up the Server Manager and do one of the following:
    • If this Web application runs under Windows 2012 or Windows 2012 R2, start up the Add Roles and Features Wizard. Step through the wizard until you reach the Features screen. Now do one of the following:

      • If you use .NET 4.5, expand the item .NET Framework 4.5 Features and the subitem WCF Services.
      • Alternatively, if you use .NET 3.5, expand the item .NET Framework 3.5 Features.
    • Alternatively, if this Web application runs under Windows 2008 R2 SP1, 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. Then click Next and Install to install the feature.
  4. Create the following Web application directory structure:
    1. In the root folder, create a bin\ subfolder.
    2. In the bin\ folder, create subfolders config\ and lib\.
  5. Access the SDL Tridion installation media.
  6. Navigate to the Content Delivery\roles\ folder.
  7. Navigate to the ugc\dotNET subfolder.
  8. Copy all DLLs in this folder to the bin\ folder of your Web application.
  9. 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.
  10. Copy all DLLs in this folder to the bin\ folder of your Web application.
  11. Navigate to the Content Delivery\roles\ugc\java\ folder.
  12. Copy all the JAR files from the lib\ subfolder, and all the JAR files from the third-party-lib\ subfolder, to the bin\lib\ folder of your Web application.
  13. 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:
    VendorJDBC DriverRequired JAR
    Microsoft SQL ServerMicrosoft SQL Server JDBC Driver 4.0

    sqljdbc42.jar for Java 8

    sqljdbc4.jar for Java 6 or Java 7

    OracleOracle JDBC driver 11.2.0.3 (deprecated)

    ojdbc6.jar for Java 6 or Java 7

    OracleOracle 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 DB2IBM 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:
  14. Navigate to \Content Delivery\resources\configurations\.
  15. Copy logback.xml from that folder to the bin\config folder of your Web application.
  16. Copy and rename the following configuration files to the bin\config folder of your Web application:
    Corresponding configuration fileRenamed configuration file
    cd_ambient_conf_sample.xmlcd_ambient_conf.xml
    cd_dynamic_conf_sample.xmlcd_dynamic_conf.xml
    cd_storage_conf_sample.xmlcd_storage_conf.xml
    cd_link_conf_sample.xmlcd_link_conf.xml
    cd_ugc_conf_sample.xmlcd_ugc_conf.xml
    cd_webservice_conf_sample.xmlcd_webservice_conf.xml
  17. Open cd_ambient_conf.xml for editing.
  18. Remove the comment tags around the following elements:
    WhiteList
    This element contains an IPAddresses subelement which contains one or more Ip elements. Ensure that IPAddresses contains only one Ip subelement, and set its value to the IP address of your Presentation Server.
    GloballyAcceptedClaims
    Uncomment this element and its subelement Claim with its Uri set to the value taf:tracking:id.

    These elements specify which forwarded Claims, coming from which IP address, are accepted by the Community Web service.

  19. Save and close cd_ambient_conf.xml.
  20. 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 License element in your configuration files.
  21. Optional: Configure logging.
  22. Configure the Storage Layer and optionally encrypt sensitive strings.
  23. Open Web.config for editing in the root folder of this Web application.
  24. To enable the Ambient Data Framework, do the following:
    Application Pool in Classic Mode

    Ensure the presence of the following inside the <httpModules> section inside the <system.web> section (create an <httpModules> element if it does not yet exist):

    <add type="Tridion.ContentDelivery.AmbientData.HttpModule" 
    	name="Tridion.ContentDelivery.AmbientData.HttpModule" />

    To enable the Ambient Data Framework for static Web pages, also do the following:

    • Ensure the presence of the following inside the <handlers> section inside the <system.webServer> section (create a <handlers> section if it does not yet exist):

      <remove name="StaticFile" />
      <add name="StaticFile" path="" verb="" modules="IsapiModule,StaticFileModule,DefaultDocumentModule,DirectoryListingModule"
        scriptProcessor="c:\PATH\TO\DOTNET\aspnet_isapi.dll" resourceType="Either" requireAccess="Read" preCondition="bitness64" />

      where c:\PATH\TO\DOTNET\ is the path to your .NET Framework root folder, for example, C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.

      If you run 32-bit .NET, remove the preCondition attribute.

    • Ensure the presence of the following inside the <httpHandlers> section inside the <system.web> section (create an <httpHandlers> section if it does not yet exist):

      <add verb="GET" path="*" type="System.Web.StaticFileHandler" />
    Application Pool in Integrated Mode

    Add the following inside the <modules> section inside the <system.webServer> section (create a <modules> element if it does not yet exist):

    <add type="Tridion.ContentDelivery.AmbientData.HttpModule" 
    	name="Tridion.ContentDelivery.AmbientData.HttpModule" />
  25. Save and close Web.config.
  26. Disable recycling of the Application Pool of this Web application by doing the following:
    1. Open IIS Manager.
    2. From the tree on the left, select the current machine and navigate to the Web application you just created.
    3. Click Advanced settings to open a dialog with the application's properties, and note down the value of Application Pool.
    4. Close the dialog.
    5. From the tree on the left, under the current machine, now select the Application Pools node.
    6. From the list on the right, select the Application Pool you just noted down.
    7. Select Recycling in the Edit Application Pool area on the right.
    8. In the dialog that opes, deselect Regular time intervals, then click Next and Finish to commit your change.
    9. Restart IIS.
  27. In IIS Manager, navigate to the Content Delivery Web service .NET Web application and select it. In the IIS area in the content area, double-click Modules to see a list of installed Managed Modules. If you see an item in this list called WebDAVModule, select it and click Remove on the right hand side of the screen to remove it.
  28. Close IIS Manager.
  29. Restart IIS.