Installing the new .Net Content Delivery Service in SDL Tridion Service Pack 1 is incredibly easy. This post assumes that you have already updated your Content Manager and Content Delivery environments to Service Pack 1.
- The first step is to create a new folder to hold the .Net web application:
- Next, go to your SP1 installation files and navigate to the folder Content Deliveryroleswebservice and depending on your target machine's architecture, open the correct subfolder (x86 or x64). Extract the files inside the webservice.zip file to the location created in step 1:
- If you store published content in a database, download the JDBC driver (JAR file) required for your specific database vendor and Java version, and copy it into the lib folder:
- Going back into your installation files, navigate to Content Deliveryresourcesconfigurations. Copy logback.xml from that folder to the binconfig folder of the new web application:
- Open the logback.xml file in a text editor and configure it to log to your required location:
- Save and close the logback.xml file
- Copy your cd_licenses.xml to the binconfig folder of the web application:
- If your Content Deployer has been installed as a Windows Service then you DO NOT need to follow step 8.1 or 8.2 as your Tridion installation is already set up to look at the TRIDION_HOME Environment Variable directory for the storage and ambient configuration files.
- Copy your cd_storage_conf.xml to the binconfig folder of the web application:
- If you have already implemented your own Ambient Data Framework Cartridge then copy your cd_ambient_conf.xml file into the binconfig folder.
- If you have NOT implemented a Cartridge then open up the Web.config file of the content delivery service in a text editor and comment out the Ambient Data Http Module:
- Create a new website in Microsoft IIS:
- Point the new website to the location created earlier:
- Set the Application Pool for the website to run under .Net 4.0:
- In IIS7, open up the Advanced Settings of the Application Pool and in the Recycling section, change the “Regular Time Interval (minutes)” setting to “0”.
- In IIS6, open the Properties of the Application Pool and deselect Recycle worker process (in minutes) and all other recycle options.
- Ensure your DNS is set up to resolve from the host name you have given the web service.
That is it, now you can open up the web service in a web browser e.g. http://dotnetcontentdeliveryservice/odata.svc :