Documentation Center

Installing the Content Deployer (other protocols) as a Windows service

To install the Content Deployer as a 64-bit Windows service, use the Content Delivery installer. You can only do this if your transport protocol is not HTTP or HTTPS.

Procedure

  1. Open a command prompt.
  2. Navigate to the Content Delivery\installer\ folder and run the file startCDinstaller.bat.
  3. Follow the instructions on the screen and select to install Content Deployer in a location you specify. Note that as a final step, you can save your installation settings to an XML file. This is useful if you want to reinstall Content Deployer again later on another machine.
  4. After the installer has finished, add the license file you received from Customer Support to the location you selected, giving it the name cd_licenses.xml. Your license must enable Content Deployer as a feature.
  5. Access the config\ subfolder of the location you specified.
  6. Open the file cd_deployer_conf.xml for editing.
  7. 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.
  8. If you intend to use SDL Tridion .NET Server Controls, ensure that your <TCDLEngine> contains a <Properties> section containing the following property:
    <Property Name="tcdl.dotnet.style" Value="controls" />
  9. Save and close cd_deployer_conf.xml.

Results

Content Deployer (other protocols) is now installed as Windows service. Note that this Windows service requires a 64-bit JVM.