MCLG: How will the new USA 2007 Daylight Saving Time rules impact Collage?

ID:    A15
Published:    06 February 2007
Updated:    24 April 2008

Operating System(s)

  • All Windows
  • Linux
  • Solaris
  • Unix
  • Windows 2000
  • Windows 2003
  • Windows 98
  • Windows NT
  • Windows XP


  • Collage


Beginning in 2007, the start and end date of Daylight Savings Time (DST) will change in the United States (see Daylight Savings Time will begin March 11, 2007 (the second Sunday in March) instead of April 1 (the first Sunday of April). Daylight Savings Time will end November 4, 2007 (the first Sunday of November) instead of October 28 (the last Sunday in October).

Collage uses Java technology on the server as well as on the clients. To successfully support the 2007 DST changes, the Java software will need to be upgraded on the clients and the server. For complete details on how to upgrade the Collage server and client machines, see KB #A12.

IMPORTANT: There may also be operating system patches that need to be applied to both the client and the server. Check with the appropriate vendors for details. Also, a large number of the dates in Collage are retrieved using function calls to the database. Because of this, make sure the appropriate operating system patches are also applied to the server hosting the Collage database.

This document is designed to describe the behavior of Collage, if the DST changes described in KB #A12 are not made. 

No Changes Made

If the operating system's patches (client and server) and the Collage patches (client and server) are not installed, you will notice the following problems:

  • All of the date and time stamps within Collage will be wrong by one hour.
  • Daily scheduled deploys, backups, imports, and tasks will start an hour early.
  • The audit logs, deploy logs, import logs, Tomcat logs, etc will have time stamps off by one hour.

Where does Collage get the dates and times?

Most of the date-time stamps within Collage come from the database server. Collage uses Java to call the database date function, the database gets the date and time from the operating system, and the database returns the value to Java. Because of this, it is very important that the Collage server and the database server are both up to date. This includes any operating system patches on both servers and the Java patch for Collage. If any of these are out of sync, you will see unexpected results. The date-time stamps that are controlled by the server include: asset last update, asset approved, check out/in, deploy start/end times, log timestamps (deploy, import, backup, Tomcat, audit log, etc), task transitions, deploy and task emails.

A few of the date-time stamps come from the client machines. These include the file create date, modify date, the default date and time used by the Collage calendar. The dates are determined by the client operating system and by the JVM installed on the client machine. If these are not updated, you will see unexpected results.

Special Note About Scheduled Activites:

After the DST time change, you should review all of your scheduled activites to make sure there are not any new conflicts. As an example, let's say that you have a deploy that runs every 4 hours at 11:00, 3:00, and 7:00. The night before the DST time change, the 11:00pm deploy will run. Then, 4 hours later, the next deploy will run.  However, 4 hours after 11:00pm will be 4:00am because the 2:00-3:00 hour is skipped. So, now the deploys will run at 4:00, 8:00, and 12:00. Depending on your environment, this may not be important. This is simply a reminder to review backup proccess or other process that may conflict with the shifted time.

Migration ID


Find Answers

Type a question or describe what you are looking for below

My Recent Searches

Welcome kb sso

Additional Assistance

  • Submit a Case Online
  • FAQs