Documentation Center

Installing the Content Deployer (other protocols) as a standalone Java process

To install the Content Deployer (other protocols) as a standalone Java process (on a Windows or non-Windows machine), copy resources and configuration files. On a Windows machine, you can also install this Server Role as a Windows service.

Procedure

  1. Open a command prompt.
  2. Create a directory on your machine for the Content Deployer.
  3. Create subdirectories lib/ and config/ in this directory.
  4. Access the SDL Tridion installation media.
  5. Navigate to the deployer\java\ subfolder.
  6. Access the lib\ subfolder and copy all the JAR files into the lib/ directory.
  7. Access the third-party-lib\ subfolder and copy all the JAR files into the lib/ directory.
  8. 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 WEB-INF/lib directory 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:
  9. Navigate to \Content Delivery\resources\configurations\.
  10. Copy logback.xml from that folder to the config/ directory.
  11. Copy the Content Delivery license file you received from SDL Tridion Customer Support in the config/ subdirectory as cd_licenses.xml. This license must include a Content Deployer license.
  12. Copy the following configuration files to the config/ subdirectory you created, and rename them:
    Original configuration fileRenamed configuration file
    cd_ambient_conf_sample.xml (if using the Ambient Data Framework)cd_ambient_conf.xml
    cd_deployer_conf_sample.xmlcd_deployer_conf.xml
    cd_storage_conf_sample.xmlcd_storage_conf.xml
    cd_link_conf_sample.xmlcd_link_conf.xml
  13. Access the config/ subfolder and open the file cd_deployer_conf.xml in a plain-text or XML editor.
  14. In the <Queue> section, add a Location element for each protocol over which you publish content to this Content Deployer, for example:
    <Location Path="MYPATH" WindowSize="20" Workers="10" Cleanup="true" Interval="2s" />
    For each Location element, specify the Path and optionally other attributes to optimize the publishing process:
    Path
    The absolute path to a location specified in a Publication Target as a relative path:
    ProtocolPublication Target Property (relative path)
    FTPLocation
    SFTP (FTP over SSH)Path on the FTP server
    SSHFTP (SSH2 using an FTP subsystem)Location
    Local file copyLocation
    For example, if the Location property specifies /dest/ for an FTP publishing destination, set Path to the absolute path to this location: c:\inetpub\ftproot\dest.
    WindowSize
    Sets the maximum number of Transport Package that can be "in flight" (publishing or deploying) at any one time. It represents the number of publish actions the Content Deployer should be able to handle. The default value for this attribute is 20.
    Workers
    Sets the maximum number of deployment threads that can be running at any time. If WindowSize is bigger than Workers, items to publish may enter a deployment queue, which in turn may cause a publish action to time out and fail. The default value for this attribute is 10.
    Interval
    The amount of time, in milliseconds (ms), seconds (s), hours (h) and so on, that the Content Deployer waits before checking for new content in this location. The default value for this attribute is 2s; that is, two seconds.
  15. If you use SDL Tridion JSP Custom Tags on your Web site:
    1. Open cd_deployer_conf.xml.
    2. Ensure that your <TCDLEngine> contains a <Properties> section containing the following property:
      <Property Name="tcdl.jsp.style" Value="tags" />
    3. Save and close cd_deployer_conf.xml.
  16. Configure the Storage Layer and optionally encrypt sensitive strings.
  17. In the directory you created, create a shell script file that places the config/ subdirectory, as well as all the JAR files, in the classpath and then runs the Java Content Deployer class:
    Linux/UNIX operating systems:
    #!/bin/sh
    TRIDION_CLASSPATH=./config
    for i in ./lib/*.jar ; do
    	TRIDION_CLASSPATH=${TRIDION_CLASSPATH}:$i
    done
    java -cp $TRIDION_CLASSPATH com.tridion.deployer.Deployer
    Windows operating system:
    java -cp "./config;./lib/*" com.tridion.deployer.Deployer
  18. Run this shell script to run the Content Deployer.