Setting up Content Delivery Web services for UGC_ running as .NET Web applications

Install the UGC server role twice as a .NET Web application that contains the Content Delivery Web service, with Ambient Data Framework enabled. If you already have such a Web application, you can add UGC to it and build the second one from scratch; if you do not have Content Delivery Web service setup at all, build both .NET Web applications from scratch.

Procedure

  1. Do one of the following:
    • To add UGC Content Delivery Web service installed as (part of) a .NET Web application, start by going to the root directory of that Web application.
    • To create a new .NET Web application, start by creating a bin\ subfolder in it. In that folder, create subfolders called lib\ and config\.
  2. Access the SDL Tridion installation media.
  3. If this is a new Web application, go to the folder Content Delivery\roles\ugc\dotNet\x86 (for a 32-bit system) or the folder Content Delivery\roles\ugc\dotNet\x86_64 (for a 64-bit system), and copy all DLL files in that folder to the bin folder of your Web application.
  4. If this is a new Web application, from the root folder, go to the folder Content Delivery\roles\webservice\dotNet\x86 (for a 32-bit system) or the folder Content Delivery\roles\webservice\dotNet\x86_64 (for a 64-bit system), and copy the file Tridion.ContentDelivery.Webservice.dll in that folder to the bin folder of your Web application.
  5. If this is a new Web application, navigate one folder up to Content Delivery\roles\webservice\dotNET and copy the following files to the root location of your new .NET Web application:
    • Global.asax
    • Web.config
    • access_token.svc
    • linking.svc
    • odata.svc
    The Web.config file is set up for use with .NET 4.0. If your version of the .NET framework is 2.0 SP2 or 3.5 SP1, open the file in a plain-text or XML editor, search for ".NET 3.5" and uncomment the two sections indicated.
  6. To enable the Ambient Data Framework, do one of the following:
    IIS 6, or IIS 7.x (Application Pool in Classic Mode)

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

    <add type="Tridion.ContentDelivery.AmbientData.HttpModule" name="AmbientFrameworkModule" />
    IIS 7.x (Application Pool in Integrated Mode)

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

    <add type="Tridion.ContentDelivery.AmbientData.HttpModule" name="AmbientFrameworkModule" preCondition="managedHandler" />
  7. Access the Content Delivery\roles\ugc\java\ directory.
  8. Copy all the JAR files from the lib\ subdirectory into the bin\lib\ subdirectory of your Web application. Overwrite any existing files.
  9. Access the third-party-lib\ subfolder and copy all the JAR files into the bin\lib\ subdirectory of your Web application. Overwrite any existing files.
  10. If this is a new Web application, download the JDBC driver (JAR file) required for your specific database vendor and Java version, and copy it into the bin\lib\ subdirectory of your Web application:
    Database vendorJDBC DriverFile to download when using Java 5File to download when using Java 6
    Microsoft SQL ServerMicrosoft SQL Server JDBC Driver 3.0sqljdbc.jarsqljdbc4.jar
    Oracle

    Oracle JDBC driver 11.2.0.2 or

    Oracle JDBC driver 11.2.0.1.0 (deprecated)

    ojdbc5.jarojdbc6.jar
  11. Go to the root of the SDL Tridion installation media and navigate to resources\configurations\.
  12. If this is a new Web application, copy logback.xml from that folder to the bin\config\.
  13. If this is a new Web application, copy and rename the following configuration files to the bin\config\ subdirectory:
    Copy this configuration file......and rename it to this:
    cd_ambient_conf_sample.xmlcd_ambient_conf.xml
    cd_storage_conf_sample.xmlcd_storage_conf.xml
    cd_dynamic_conf_sample.xmlcd_dynamic_conf.xml
    cd_wai_conf_sample.xmlcd_wai_conf.xml
    cd_webservice_conf_sample.xmlcd_webservice_conf.xml
  14. Copy the configuration file cd_ugc_conf_sample.xml to the bin\config\ subdirectory and rename it to cd_ugc_conf.xml.
  15. Open cd_ambient_conf.xml in a plain-text or XML editor.
  16. Find the <Security> section and enclose it in comments. This element is only needed if you intend to set up OAuth authentication.
  17. Save and close cd_ambient_conf.xml.
  18. Copy cd_licenses.xml, your Content Delivery license file available from SDL Tridion Customer Support, to the config (.NET) or classes (Java) 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.
  19. Configure logging.
  20. If your configuration files include a cd_storage_conf.xml, configure the Storage Layer and optionally encrypt sensitive strings.
  21. Start your Web application.
  22. Open IIS Manager, navigate to Application Pools > DefaultAppPool and open the Properties window. Deselect Recycle worker process (in minutes) and all other recycle options, and commit your changes.
  23. If you are using IIS 6, still in IIS Manager, navigate to the current machine, then open the Web sites folder and right-click the Web application that runs your Content Delivery Web service for UGC. From the context menu that opens, select Properties to open the properties for this Web application, and select the Home Directory tab. Ensure that in the Application settings area, Execute permissions is set to the value Scripts and Executables.
  24. If you are using IIS 6, also select the Directory Security tab and in the area called Authentication and access control, click the Edit button. The Authentication Methods dialog opens, showing a value for User name in the Enable anonymous access area. Copy the name of this user (typically IUSR_<machinename>, where <machinename> is the name of your machine) to your clipboard or note it down. Then close the Authentication Methods dialog and the properties dialog.
  25. Alternatively, if you are using IIS 7.0 or IIS 7.5, still 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.
  26. Close IIS Manager.
  27. If you are using IIS 6, in Windows Explorer, navigate to the root folder of the Web application, right-click odata.svc and from the context menu that opens, select Properties to open the file's properties. Access the Security tab and in the Group or User names area, click Add to add a new user. Find and add the user you noted down in step 20, and give this user Write permissions.
  28. Restart IIS.
  29. Now repeat all the steps above to create your second .NET Web application.