Documentation Center

Upgrading Archive Manager 1.0 SP1 Core on Content Delivery

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

Procedure

  1. Update the set of JAR files of Archive Manager 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
  2. 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.

  3. 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.
  4. Open your Content Deployer configuration file cd_deployer_conf.xml, by default located in your SDL Tridion Installation \config directory, for editing:
    1. Remove the Processor section with the following attribute-value pairs:
      • Action="Deploy"
      • Class="com.tridion.archiving.processors.TransactionalProcessor"
      • Phase="processing"
    2. Add the following Processor section as the first element inside Processors:
      <Processor Action="Deploy" Class="com.tridion.deployer.Processor" Phase="pre-processing">
        <Module Type="DeploymentPipelineModule" Class="com.tridion.archiving.modules.DeploymentPipelineModule">
          <Pipeline Name="archiving-pipeline-initial" InitialState="" FinalState="current-urls" />
        </Module>
      </Processor>
    3. Locate the Processor element with its Action attribute set to Deploy and its Class attribute set to com.tridion.archiving.processors.TransactionalProcessor.
    4. 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"/>
    5. Locate the Processor element with its Action attribute set to Undeploy and its Class attribute set to com.tridion.archiving.processors.TransactionalProcessor.
    6. 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"/>  		  
    7. Save and close cd_deployer_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.