Documentation Center

Upgrading Archive Manager 1.0 Core on Content Delivery

Follow these steps to update the Archive Manager Core if you are upgrading from Archive Manager 1.0.

Procedure

  1. Back up the following files:
    • cd_deployer_conf.xml
    • cd_archivemanager_conf.xml
  2. Update the set of JAR files to become JAR files of Archive Manager 1.0 SP3:
    1. From the installation media, copy the following files from the \Content Delivery\roles\am_modules\java\third-party-lib directory into your Web application library location, overwriting any files by the same name:
      • commons-codec.jar
      • commons-httpclient.jar
      • jackson-core-asl.jar
      • jackson-mapper-asl.jar
      • xmlpull.jar
      • xpp3_min.jar
      • xstream.jar
    2. From the installation media, copy the following new files from the \Content Delivery\roles\am_modules\java\lib directory into your library location, overwriting any files by the same name:
      • cd_archivedeploy.jar
      • cd_archivemanager.jar
      • cd_archivepipeline.jar
      • cd_archivequeue.jar
      • cd_archivestorage.jar
    3. Delete the following JAR files, if present in your library location, as these are no longer needed by Content Delivery or Archive Manager:
      • ezlicrun.jar
      • xercesImpl.jar
  3. If your Archiver database uses a different DBMS than your Content Data Store (for example, your Content Data Store is a DB2 database, but your Archiver database is a SQL Server database), download the JDBC driver (JAR file) required for your specific database vendor, Java version and SDL Tridion release, and copy it into the Web application \lib subdirectory:
    • If your Archiver database is a SQL Server database, download the Microsoft SQL Server JDBC Driver 4.0, specifically the file sqljdbc4.jar.

    • If your Archiver database is an Oracle database, download Oracle JDBC driver 11.2.0.3, specifically the file ojdbc6.jar.

  4. If your Archiver database is a SQL Server database and you wish to set up integrated authentication for it, also copy the file sqljdbc_auth.dll, which is included in the same deliverable that contains the JDBC driver JAR.
  5. Open your Content Deployer configuration file cd_deployer_conf.xml, by default located in your SDL Tridion Installation \config directory, for editing and do the following:
    1. Replace your existing <Processor> elements for Archive Manager with the <Processor> elements described in Configuring Content Deployer.
    2. Locate the Processor element with its Action attribute set to Deploy and its Class attribute set to com.tridion.deployer.Processor.
    3. Inside this Processor element, remove the following Modules:
      <Module Type="PageDeploy"
      		  Class="com.tridion.archiving.modules.PageLinkCollector"/> 
      <Module Type="ComponentPresentationDeploy"
      		  Class="com.tridion.archiving.modules.ComponentPresentationLinkCollector"/>
    4. Locate the Processor element with its Action attribute set to Undeploy and its Class attribute set to com.tridion.deployer.Processor.
    5. Inside this Processor element, remove the following Modules:
      <Module Type="PageUndeploy"
      		  Class="com.tridion.archiving.modules.LinkCollectorUndeployModule"/>
      <Module Type="ComponentPresentationUndeploy"
      		  Class="com.tridion.archiving.modules.LinkCollectorUndeployModule"/>  		  
    6. Save and close cd_deployer_conf.xml.
  6. Open the Archive Manager cd_archivemanager_conf.xml configuration file you backed up and make the following changes:
    1. Remove the <Storage> section then reconfigure storage in the Content Delivery cd_storage_conf.xml configuration file—for more information, see Configuring the Storage Layer
    2. Remove the <Logging> section then reconfigure logging in the logback.xml configuration file—for more information, see Configuring Archive Manager logging
    3. Save and close cd_archivemanager_conf.xml.

Results

Your Archive Manager core is now upgraded. Most likely, your archiving performance will improve (because archiving is now asynchronous and multi-threaded), while your CPU load may increase. If you find that your CPU load is unacceptably high, consider scaling up or scaling out your implementation.