Installing a server role as a .NET Web application—universal procedure
To install a server role as a .NET Web application, you need to set up the correct Web application directory structure then copy over the necessary JAR files, .NET libraries, configuration files and other resources. You then need to perform configuration, remove recycling of the IIS worker process, set up .NET server controls, and install a license.
Before you begin
Procedure
- Create a new .NET Web application.
- Create the Web application directory structure:
- In the root folder, create a
bin\subfolder. - In the
bin\folder, create subfolders config\ and lib\.
The Web application should have the following folder structure:root\ +--bin\ +--config\ +--lib\ - In the root folder, create a
- Access the SDL Tridion installation media.
- Navigate to the Content Delivery\ folder.
- Access the
dotNet\subfolder for the specific role you are installing:Folder Server role roles\api\dotNet\ API roles\deployer\dotNet\ Content Deployer roles\upload\dotNet\ HTTP Upload roles\webservice\dotNet\dll\ Content Delivery Web service - Depending on the system architecture of your target system, go to the x86\ (x86 architecture) or x86_64\ (x64 architecture) subfolder.
- Copy all assemblies from this folder to the bin\ folder of your Web application.
- Navigate to the Content Delivery\ directory and access the
java\Java subfolder for the specific role you are installing:Folder Server role roles\api\java\ API roles\deployer\java\ Content Deployer roles\upload\java\ HTTP Upload roles\webservice\java\ Content Delivery Web service - Access the lib\ subfolder and copy all the JAR files into the lib\ folder of your Web application.
- Access the third-party-lib\ subfolder and copy all the JAR files into the lib\ folder of your Web application.
- If you intend to use the Ambient Data Framework with this Server Role, and your lib folder does not yet contain cd_ambient.jar, copy this file from Content Delivery\roles\api\java\lib\ to your lib folder.
- 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:
Database vendor JDBC Driver File to download when using Java 5 File to download when using Java 6 Microsoft SQL Server Microsoft SQL Server JDBC Driver 3.0 sqljdbc.jar sqljdbc4.jar Oracle Oracle JDBC driver 11.2.0.2.0 or
Oracle JDBC driver 11.2.0.1.0 (deprecated)
ojdbc5.jar ojdbc6.jar IBM DB2 IBM Data Server Driver for JDBC and SQLJ db2jcc.jar db2jcc.jar Note: IBM DB2 is not supported for certain add-on products, for example Audience Manager, Outbound E-mail and Online Marketing Explorer. - Navigate to resources\configurations\.
- Copy logback.xml from that folder to the config folder.
- Check the JAR files in your Web application's lib subfolder that begin with cd_. You need to copy the corresponding configuration files to the config (.NET) or classes (Java) directory of your Web application and rename them as follows:
JAR file Corresponding configuration file Renamed configuration file cd_ambient.jar cd_ambient_conf_sample.xml cd_ambient_conf.xml cd_deployer.jar cd_deployer_conf_sample.xml cd_deployer_conf.xml cd_datalayer.jar cd_storage_conf_sample.xml cd_storage_conf.xml cd_dynamic.jar cd_dynamic_conf_sample.xml cd_dynamic_conf.xml cd_linking.jar cd_link_conf_sample.xml cd_link_conf.xml cd_monitor.jar cd_monitor_conf_sample.xml cd_monitor_conf.xml cd_wai.jar cd_wai_conf_sample.xml cd_wai_conf.xml cd_webservice.jar cd_webservice_conf_sample.xml cd_webservice_conf.xml - Open cd_ambient_conf.xml (if using) in a plain-text or XML editor.
- Find the
<Security>section and enclose it in comments. This element is only needed if you intend to set up OAuth authentication. - Save and close cd_ambient_conf.xml.
- 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
Licenseelement in your configuration files. - Configure logging.
- If your configuration files include a cd_storage_conf.xml, configure the Storage Layer and optionally encrypt sensitive strings.
- Open IIS Manager, navigate to Application Pools > DefaultAppPool and open the Properties window. Deselect Recycle worker process (in minutes) and all other recycle options, commit your changes and restart IIS.