Summary
This tutorial explains how to configure a Tridion Content Delivery instance with the oData Web Service.
It is meant as a guide, and it may be applicable only to the "GA" release of SDL Tridion 2011.
Tutorial Sections
- Part 1 - Creating the Content Delivery Database
- Part 2 - Configuring an application server
- Part 3 - Configuring the Tridion Deployer using Eclipse IDE
- Part 4 - Configuring the oData Web Service
- Part 5 - Testing and publishing to the web service
Configuring the Tridion Deployer using Eclipse IDE
In this chapter will cover the steps required to configure a Tridion (HTTPS) deployer application running on Tomcat. If you have not installed Eclipse yet, download it from here.
Configuring Eclipse
Open Eclipse, select File -> New -> Other
Select "Server" from the wizard list
Select Apache -> Tomcat v6.0 Server from the list
Specify the location where Tomcat is installed, and click on Installed JREs…
Click Add…
Select Standard VM
Point your JRE Home setting to the folder containing the JDK. Click Finish
Set the JDK as default JRE. Click OK, then Click Finish
You have now configured Tomcat as a server in Eclipse.
Configuring the deployer Web Application
In Eclipse, select "File -> Import"
Select WAR file from the list
Enter the path to the cd_upload.war file: [Tridion_Install]\Content Delivery\java\httpupload\cd_upload.war, enter a name for the web application (TridionUpload in our case) and Select Tomcat from the "Target runtime" dropdown. Click Finish
Right click "TridionUpload" and select New -> Folder
Select the "src" folder as the parent, click on "Advanced", select "Link to alternate location (Linked Folder)" and specify the path to [Tridion_Install]\Content Delivery\configuration\schemas.
Click Finish
Select File -> Import from the main menu
Select File System, click Next
In the "From directory" field, fill in the path to [Tridion_Install]\Content Delivery\configuration\samples
Select the deployer, dynamic, link, storage, wai and logback configuration samples.
Import into TridionUpload/src folder
Overwrite resources.
Click Finish
Rename the imported files, removing _sample from their names
Double-click cd_deployer_conf.xml and switch to the source view
Uncomment the license node, and make sure it points to an existing (and valid) license file.
Repeat this step for cd_link_conf.xml
Edit logback.xml and configure the log location and log level.
(Optional) Encrypt your database password
Create a SQL Server storage in cd_storage_conf.xml. In this example we are setting the ID of this storage to "sqlserver"
Change the default ItemTypes storage to the SQL Server storage we created
Make sure the Page mapping is commented out (it is set to the file system by default)
Add a Binary mapping to the tomcatFS storage
Enable the license node, and make sure it points to a valid license file. (note: you may receive an error because the storage XSD does not allow the license node, but you DO need it)
Export the deployer web application to Tomcat
Select File -> Export
Select WAR file
Select the TridionUpload project, and choose the destination for your WAR file. In this case, we're exporting it directly into the webapps folder of Tomcat, which will cause it to deploy automatically
Verify the deployment by opening an explorer window in c:\tomcat\webapps. You should see a new folder named "TridionUpload"
Try the Upload servlet by opening a browser and going to http://localhost:8080/TridionUpload/httpupload
You have now configured the Tridion HTTP Upload Servlet.
Next section: Configuring the oData Web Service
Proceed to the next step in this Tutorial, Configuring the oData Web Service .