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:BinaryVariantBinaryMetaComponentMetaComponentPresentationMetaItemMetaPageMetaPublicationReferenceSchemaLinkInfo
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
Metadatatype 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
Renderersection; 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.