Documentation Center

Upgrading timestamps in the Archive Manager database

From your Content Deployer Web application, run a Java tool included with the installation media to update the timestamps in your Archive Manager database. Perform this task only after you have upgraded your Archive Manager database.

Before you begin

To run the Java tool that upgrades these timestamps, the following must be true:
  • Your JAVA_HOME variable must be set.

  • The tool must be able to connect to a database through a JDBC connection (that is, a JDBC driver must be installed and a JDBC connection must be configured). If you use only a JNDI connection to your database, the tool does not work. To configure your Storage Layer for a JDBC connection, back up your existing JNDI storage settings and add the following JDBC settings:

    <Storage Type="persistence" Id="defaultdb" dialect="MSSQL" Class="com.tridion.storage.persistence.JPADAOFactory">
      <Pool Type="jdbc" Size="5" MonitorInterval="60" IdleTimeout="120" CheckoutTimeout="120" />
      <DataSource Class="com.microsoft.sqlserver.jdbc.SQLServerDataSource">
        <Property Name="serverName" Value="SERVER_NAME" />
        <Property Name="portNumber" Value="1433" />
        <Property Name="databaseName" Value="DATABASE_NAME" />
        <Property Name="user" Value="USER_NAME" />
        <Property Name="password" Value="PASSWORD" />
      </DataSource>
    </Storage>

    where SERVER_NAME, DATABASE_NAME, USER_NAME and PASSWORD identify your database and the credentials to access it. After running the database update tool, you can remove these settings and reinstate your JNDI settings.

About this task

Timestamps in your Archive Manager database were stored in local time (that is, local to the server on which the Content Deployer runs). As of Archive Manager 1.0 SP3, timestamps are stored as UTC timestamps. To ensure that your existing database records have the right timestamps, run a Java tool.

Procedure

  1. On the server on which your Content Deployer runs, navigate to your Content Deployer root location.
  2. On your SDL Archive Manager installation media, navigate to the folder Content Delivery\resources\db_update_10sp3\.
  3. Copy the file db_update_10sp3.bat (when copying to a Windows system) or db_update_10sp3.sh (when copying to a non-Windows system) to your Content Deployer machine.
  4. Copy the file cd_archiveupdate_10sp3.jar to your Content Deployer library location (typically, the subdirectory called lib/ of your root location).
  5. Open a command prompt, navigate to the Content Deployer root location and enter one of the following commands:
    • On a Windows system with the Content Deployer running as a .NET Web application or Windows service, type:

      db_update_10sp3.bat bin lib
    • On a Windows system with the Content Deployer running as a Java Web application or Java process, type:

      db_update_10sp3.bat classes lib
    • On a non-Windows system with the Content Deployer running as a Java Web application or Java process, type:

      sh db_update_10sp3.sh classes lib

      or

      bash db_update_10sp3.sh classes lib

    The tool updates your timestamps, using the timezone of the system on which the tool is running. To explicitly set the timezone to another value, add it as a parameter. For example:

    db_update_10sp3.bat classes lib GMT-8

    This command ignores the timezone on the system where the tool is running and instead assumes the timezone of the database to be GMT-8. It then converts the timestamps in the database to UTC based on that assumption.

  6. Now remove the batch file and JAR file from your Content Deployer machine; you no longer need them.