Documentation Center

Upgrading your Content Delivery configuration

Upgrade your Server Roles' configuration files to make your Server Roles work with SDL Tridion again.

About this task

Reconfiguring logging
Before SDL Tridion 2011, Content Delivery logging was configured in the individual configuration files of the various software components, such as cd_transport_conf.xml, cd_deployer_conf.xml, and so on. SDL Tridion 2013 SP1 Content Delivery arranges logging using the Logback framework and lets you configure logging settings in a separate configuration file called logback.xml.
Upgrading Content Deployer Modules
The Content Deployer configuration requires additional Modules.
Storage Layer

If you are upgrading from a release before SDL Tridion 2011, content storage is now arranged through the Storage Layer (previously using the Content Broker configuration). SDL Tridion 2013 SP1 ships with an XSLT stylesheet that transforms the old Content Broker to a new Storage Layer configuration, but it is recommended to upgrade the configuration yourself by hand. For more information, refer to Deprecation of old storage framework.

If you are upgrading from SDL Tridion 2011, metadata (including binary variants and link information) must now all be stored in the same data repository (either a database or the file system). This means that the following type mapping values are replaced with a single, new type mapping called Metadata:

  • BinaryVariant
  • BinaryMeta
  • ComponentMeta
  • ComponentPresentationMeta
  • ItemMeta
  • PageMeta
  • Publication
  • Reference
  • Schema
  • LinkInfo

If your Storage Layer contains type mappings for these values, Content Delivery will accept the settings but log a warning that you should replace them with a Metadata type mapping. If you do not do this, and if you store the various item types in multiple content repositories, your database may experience inconsistencies.

Content Deployer configuration file
The Content Deployer configuration file contains a new element Queue, used for the configuration of the new feature: scalable deployment. This element replaces the Receivers element in the old configuration. SDL Tridion 2013 SP1 ships with an XSLT stylesheet that transforms the old Content Deployer configuration to a new one. You can also apply the XSLT stylesheet yourself by hand. The file is located on the SDL Tridion installation media in the folder Content Delivery\resources\xslt and is called cd_deployer_conf.xsl.
Dynamic configuration file
  • If you are upgrading from SDL Tridion 2009 SP1, this new release introduces a new configuration file, cd_dynamic_conf.xml, which you need to add if you want to upgrade.
  • If you are upgrading from SDL Tridion 2011 or SDL Tridion 2011 SP1, the file cd_dynamic_conf.xml no longer has a Renderer section; you need to remove it.
New weblogic.xml file for HTTP upload in Java
If your Web application server is WebLogic, add a weblogic.xml file if you use HTTP upload.

Procedure

  1. If you upgrade from a release earlier than SDL Tridion 2011, reconfigure logging by manually reapplying the settings specified in the various configuration files in a single configuration file called logback.xml. Refer to the installation documentation for more information on how to configure logging.
  2. After you have moved your logging settings into the logback.xml file, you can remove the <Logging> sections from all of your XML configuration files. This is not required: Content Delivery ignores any logging settings in your existing configuration files.
  3. If you upgrade from SDL Tridion 2009 SP1, then in you Content Deployer Web application, Windows service file location or Java process file location, locate your Content Deployer configuration file and open it in a plain-text or XML editor. Now upgrade your Modules by doing the following:
    • In the <Processors> section, find the Processor element with its Action attribute set to the value Deploy and its Class set to com.tridion.deployer.Processor. You see a number of Module elements in this element. Add the following at the bottom of this list:
      <Module Type="PublicationDeploy" Class="com.tridion.deployer.modules.PublicationDeploy" />
      <Module Type="StructureGroupDeploy" Class="com.tridion.deployer.modules.StructureGroupDeploy" />
    • Next, find the Processor element with its Action attribute set to the value Undeploy and its Class set to com.tridion.deployer.Processor. You again see a number of Module elements in this element. Add the following at the bottom of this list:
      <Module Type="StructureGroupUndeploy" Class="com.tridion.deployer.modules.StructureGroupUndeploy" />
  4. Save and close the Content Deployer configuration file.
  5. If you are upgrading from SDL Tridion 2009 SP1, on the SDL Tridion installation media, access the folder Content Delivery\resources\configurations\ and copy the file cd_dynamic_conf_sample.xml to the location where your existing configuration files are stored. Then rename the file to cd_dynamic_conf.xml.
  6. Alternatively, if you are upgrading from SDL Tridion 2011 or SDL Tridion 2011 SP1, open your existing cd_dynamic_conf.xml file, find the section called Renderer, and remove it. You no longer need this section.
  7. If your Web application server is WebLogic, ensure that the WEB-INF folder of all of your Web applications contains a file called weblogic.xml with the following contents:
    <weblogic-web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    	xsi:schemaLocation="http://www.bea.com/ns/weblogic/weblogic-web-app http://www.bea.com/ns/weblogic/weblogic-web-app/1.0/weblogic-web-app.xsd"
    	xmlns="http://www.bea.com/ns/weblogic/weblogic-web-app">
    	<container-descriptor>
    		<prefer-application-packages>
    			<package-name>javax.persistence.**</package-name>
    			<package-name>antlr.*</package-name>
    			<package-name>org.slf4j.**</package-name>
    			<package-name>org.apache.log4j.**</package-name>
    			<package-name>org.apache.xml.serializer.**</package-name>
    		</prefer-application-packages>
    	</container-descriptor>
    </weblogic-web-app>
  8. Finally, do one of the following:
    • If your Content Deployer runs as a Windows service, access your Windows Services and restart the service called Tridion Content Deployer.
    • If your Content Deployer runs as a Java Web application, restart the Web application as per the instructions of your Web application server.