Adding new JARs to Server Roles

Add a number of new JAR files to your Content Delivery Web applications or file system directories for Windows services or Java processes.

Procedure

  1. Access the location of the JAR files of your Content Delivery Web application, Windows service or Java process.
  2. Access the SDL Tridion installation media and navigate to the folder Content Delivery\roles\<role>\java\lib\ where <role> is one of the following Content Delivery Server Roles contained in the Web application or directory you are upgrading:
    • API
    • Cache Channel Service
    • Content Deployer
    • HTTP Upload
    • Monitoring
  3. Alternatively, if you have the user interface update installed on top of SDL Tridion 2011 SP1, , SDL Tridion 2011 SP1 HR1 or SDL Tridion 2011 SP1 HR2, navigate to one of the following:
    • To upgrade the user interface Web service, navigate to Content Delivery\roles\preview\webservice\java\lib\
    • To upgrade the user interface Web site extension, navigate to Content Delivery\roles\preview\web\java\lib\
  4. Only if you are upgrading from SDL Tridion 2009 SP1, use the following tables to add new JARs to this location, depending on the Server Role:
    FilenameAPIContent DeployerHTTP Upload
    cd_ambient.jaryesnono
    cd_cache.jaryesyesyes
    cd_datalayer.jaryesyesyes
    cd_dynamic.jaryesnono
    cd_linking.jaryesnono
    cd_model.jaryesyesyes
    cd_tcdl.jaryesyesyes
    cd_undo.jarnoyesyes
    cd_upload.jarnonoyes
    cd_wrapper.jarnoyesyes
    activation.jaryesyesyes
    antlr.jaryesyesyes
    aopalliance.jaryesyesyes
    commons-collections.jaryesyesyes
    commons-fileupload.jarnonoyes
    commons-io.jarnonoyes
    dom4j.jaryesyesyes
    easylicense.jaryesyesyes
    hibernate-commons-annotations.jaryesyesyes
    hibernate-core.jaryesyesyes
    hibernate-entitymanager.jaryesyesyes
    javassist.jaryesyesyes
    jaxb-api.jaryesyesyes
    jaxb-impl.jaryesyesyes
    jcl-over-slf4j.jaryesyesyes
    jersey-servlet.jarnonono
    log4j-over-slf4j.jarnonono
    logback-classic.jaryesyesyes
    logback-core.jaryesyesyes
    serializer.jar (do not use if using JBoss)yesyesyes
    slf4j-api.jaryesyesyes
    spring-aop.jaryesyesyes
    spring-asm.jaryesyesyes
    spring-beans.jaryesyesyes
    spring-context-support.jaryesyesyes
    spring-context.jaryesyesyes
    spring-core.jaryesyesyes
    spring-expression.jaryesyesyes
    spring-jdbc.jaryesyesyes
    spring-orm.jaryesyesyes
    spring-tx.jaryesyesyes
    stax-api.jar (do not use if using JBoss or WebLogic)yesyesyes
    FilenameCache Channel ServiceMonitoring
    cd_cache.jaryesyes
    activation.jaryesyes
    axis-jaxrpc.jarnoyes
    axis.jarnoyes
    easylicense.jaryesyes
    commons-httpcore.jarnoyes
    jaxb-api.jaryesyes
    jaxb-impl.jaryesyes
    jcl-over-slf4j.jarnoyes
    logback-classic.jaryesyes
    logback-core.jaryesyes
    log4j-over-slf4j.jarnoyes
    serializer.jarnoyes
    sfl4j-api.jaryesyes
    stax-api.jar (do not use if using JBoss or WebLogic)yesyes

    If your Web application combines multiple Server Roles, copy the files marked 'yes' for any of those Server Roles.

  5. Only if you are running the user interface update on top of SDL Tridion 2011 SP1, use the following tables to add new JARs to this location, depending on the Server Role (the user interface update is now called Experience Manager):
    FilenameExperience Manager Web site extensionExperience Manager Web service
    cd_deployer.jarnoyes
    cd_odata.jaryesno
    cd_wrapper.jaryesyes

    If your Web application combines both Server Roles, copy the files marked 'yes' for any of those Server Roles.

  6. If you are upgrading either from SDL Tridion 2009 SP1 or SDL Tridion 2011 SP1, use the following tables to add new JARs to this location, depending on the Server Role:
    FilenameAPICache Channel ServiceContent DeployerHTTP Upload
    hibernate-jpa-2.0-api.jaryesnoyesyes
    jboss-logging.jaryesnoyesyes
    jboss-transaction-api_1.1_spec.jaryesnoyesyes
    json-smart.jaryesnonono
    FilenameMonitoringUGCContent Delivery Web service
    cd_odata.jarnoyesyes
    cd_odata_types.jarnonoyes
    hibernate-jpa-2.0-api.jaryesnoyes
    httpclient.jaryesnono
    httpcore.jaryesnono
    jackson-jaxis.jarnoyesyes
    jackson-mapper-asl.jarnoyesyes
    jackson-xc.jarnoyesyes
    jersey-servlet.jarnoyesyes
    jboss-logging.jaryesnoyes
    jboss-transaction-api_1.1_spec.jaryesnoyes
    json-smart.jarnoyesyes

    If your Web application combines multiple Server Roles, copy the files marked 'yes' for any of those Server Roles.

  7. If you are upgrading from SDL Tridion 2011 SP1, SDL Tridion 2011 SP1 HR1 or SDL Tridion 2011 SP1 HR2, and if you have the Context Engine Cartridge 1.1 for SDL Tridion 2011 SP1 installed, add the following JAR files from the \Context Engine Cartridge\java\lib\ folder on the installation media:
    • cwd_cartridge.jar
    • cwd_engine.jar
  8. Regardless of the version from which you are upgrading, and regardless of which Server Role you are upgrading, always add the following JAR file:
    • guava.jar