Documentation Center

Installing the Experience Manager Web service as a .NET Web application

As part of installing Experience Manager, install the Experience Manager Web service Server Role. Note that this Web application also contains the Content Delivery Web service Server Role. Note also that if you have a classic ASP Web site, you can skip this task.

Procedure

  1. Ensure that all the prerequisites for a Content Delivery Server Role are met on your target system.
  2. If you use Windows 2012 or Windows 2012 R2, do the following:
    1. Start up the Server Manager and Add Roles and Features Wizard. Step through the wizard until you reach the Features screen.
    2. 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.
    3. 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.
    4. Click Next and Install to install the feature.
  3. If you use Windows 2008 R2 SP1, do the following:
    1. Start up the Server Manager and under Features Summary, select Add Features.
    2. 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.
    3. Click Next and Install to install the feature.
  4. 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.
  5. Access the SDL Tridion installation media.
  6. Navigate to the Content Delivery\roles\ folder.
  7. Access the preview\webservice\dotNET\webapp\ subfolder.
  8. Unzip one of the following Zip files in this location to the location on your target system where you want to place the .NET Web application:
    • To install a 32-bit .NET Web application, unzip x86.zip.
    • To install a 64-bit .NET Web application, unzip x86_64.zip.
  9. 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:
  10. Navigate to the folder \Content Delivery\roles\preview\webservice\configuration\samples\.
  11. Copy logback.xml from that folder to the bin\config folder of your Web application.
  12. Copy each of the files that end in _sample.xml to the bin\config folder of your Web application, and rename them by removing the string _sample from each filename (for example, rename cd_storage_conf_sample.xml to cd_storage_conf.xml).
  13. From the location in which you installed the Content Deployer, copy cd_deployer_conf.xml from that Server Role into the bin\config subfolder of your new Web application.
  14. If you have SDL SmartTarget set up in one of your Content Delivery Server Roles, copy the following JAR files from that Server Role into the bin\lib subfolder of your new Web application:
    • smarttarget_core.jar
    • smarttarget_entitymodel.jar
    • All third-party library JAR files required by SmartTarget. You can find out what these files are by checking your SmartTarget installation media.
  15. 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.
  16. Optional: Configure logging.
  17. Configure the Storage Layer and optionally encrypt sensitive strings.
  18. Open Web.config for editing in the root folder of this Web application.
  19. 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" />
  20. Save and close Web.config.
  21. 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.
  22. Implement security for the new Web application by following the instructions about securing the Web service in the SDL Tridion platform documentation. If you do not wish to secure the Web application (it is strongly recommended that you do), remove the <Security> section from cd_ambient_conf.xml.
  23. Restart the Web application.