Nuno Linhares has a great article on Setting up the Deployer and the new 2011 Content Delivery Service here but I feel it has too many steps to follow for most of our Building Blocks scenarios.
Most of our scenarios are when the Content Manager and Content Delivery server has already been installed and set to publish using FTP, HTTPS or Local File System but then we (developers) will need to go in and set up the Content Delivery Service to serve up dynamic content if it is required.
As the Application Server that is in use by most of our clients is Microsoft IIS 6/7.5 on Microsoft Windows Server 2003/2008, this blog post will cover the steps to follow to install and configure the Content Delivery Service by extracting all the unwanted steps from Nuno's post that are relevant to our standard Microsoft set up.
Install Tomcat 6
Download Tomcat 6.x from http://tomcat.apache.org/download-60.cgi
Start the installation and make sure you place a tick in the Host Manager on the features screen
Specify a user name and password
Specify the JRE location
Specify your installation directory. It may be good to change the install location to C:Tomcat, since it's easier to remember and access than C:Program FilesApache Software FoundationTomcat 6.0
Click Finish with the Run Apache Tomcat box ticked
The Tomcat server will now start
Right-click the Tomcat Monitor icon in the system tray and click "Configure..."
Set the service to start automatically and click "OK"
You will now be able to access the Tomcat Web Application Manager at http://localhost:8080/manager/html
As most of our clients use Microsoft SQL, copy the sqljdbc4.jar from [Tridion_Install_Directory]lib and copy it to C:Tomcatlib
Configure the Tridion configuration files
Create a temporary folder to hold your configuration files
Locate the sample cd_dynamic_conf_sample file in the [Tridion_Install_Files]Content Deliveryconfigurationsamples directory and copy it to your temporary folder
Rename it to cd_dynamic_conf
Locate your current configuration files in [Tridion_Install_Directory]Tridionconfig and copy the cd_link_conf, cd_storage_conf, cd_wai_conf and logback files into your temporary folder.
Open the cd_link_conf.xml file and uncomment the license node, and make sure it points to an existing (and valid) license file then Save & Close the file
And again for cd_wai_conf.xml then Save & Close the file
And again for cd_storage_conf.xml then Save & Close the file
Edit logback.xml and configure the log location and log level then Save & Close the file
Install the Web Service
Locate the cd_webservice.war file at [Tridion_Install_Files]Content Deliveryjavawebservice and copy it to your temporary location and rename it to cd_webservice.zip
Open the zip file (using Explorer) and navigate to WEB-INFclasses
Copy the configuration files from your temporary location into the WEB-INFclasses folder
Now, in the zip file, navigate back to WEB-INFlib
On a different explorer window, navigate to [Tridion_Install_Files]Content Deliveryjavathird-party-lib1.5, and copy both jar files to the zip file's WEB-INFlib folder
Rename the cd_webservice.zip file back to cd_webservice.war
Make sure you can set the extension correctly. By default windows will hide the .zip extension. You can change this by selecting Organize -> Folder and search options from the Windows Explorer menu
Copy the war file in Tomcat (by copying it to C:TomcatWebapps) and Tomcat will automatically install the application
Restart the Tomcat Service
Test it in a browser by opening http://localhost:8080/cd_webservice/odata.svc
Browse to http://localhost:8080/cd_webservice/odata.svc/Pages and you should have the list of pages that are published.
Note: In order to display the feed correctly in Internet Explorer, you will need to change the settings. To do this, in Internet Explorer -> Options, Content Tab, and clicking on Settings under "Feeds and Web Slices" and unchecking the box "Turn on feed reading view". You need to restart IE for this change to be active
You now have an active oData WebService endpoint which you can now use LINQ to query against the Tridion Broker.
There are more blog posts to follow that explain how this is done. A basic example of this can be found on SDL Tridion World here