In March 2007, the effective dates of Daylight Savings Time (DST) in the U.S. and Canada will change. You need to take action to address issues related to Enterprise Content Management (ECM) products and features contained in this document.
Extended DST begins in March of 2007. Beginning in 2007, the DST start and end dates are as follows:
- Start date: Second Sunday of March
- End date: First Sunday of November
Because both the operating system and Java applications are affected by this change, you may need to take actions if you are using one of the ECM products or features listed in the first table, “ECM Products and Features DST impact”.
NOTE: When using this document to determine what path to take to update systems with these changes, it is important to note that this document does not cover operating system patches that must also be installed. Please contact your operating system vendor for specific patches.
Product List
The following products are covered by this notice:
- IBM DB2 Universal Database
- WebSphere Application Server
- IBM DB2 Content Manager
- IBM DB2 CommonStore
- IBM DB2 Records Manager
- IBM DB2 Document Manager
ECM Products
ECM Products and Features DST Impact
|
Product/Feature |
Impact |
Action required |
|
CM: Library Server |
No Impact on Library Server because it’s Server relies on operating system calls or SQL statements to obtain time, timestamps, and so on. Logging and timestamps are all GMT in CM 8.3. In CM 8.2, logs use timestamp in the local time zone.
|
None for CM 8.2 or CM 8.3. |
|
CM: Resource Manager |
No Impact for Resource Manager Database. No Impact for Resource Manager Application, which runs in WebSphere Application Server JVM |
To correct Minor possible display issues for DST for both CM 8.2 and CM 8.3 update Websphere per directions in WebSphere section. |
|
CM/II4C: System Administration Client |
No functional impact. Possible minor display issues. |
For CM 8.2 and CM 8.3 GA to CM 8.3 FP3 the private JRE might be patched using the Java Time Zone Update Tool.
In CM 8.3 FP4 or greater the DST is the updated version. |
|
eClient |
No functional impact for CM 8.2 and CM 8.3, possible minor display issues.
eClient use WebSphere Application Server JRE. (See WebSphere section later in document) |
Update WebSphere Application Server JRE for CM 8.2 and CM 8.3 eClient. |
|
Client for Windows |
No impact. Time determined by operating system. |
None |
|
Records Manager |
No functional impact to 4.1.2 or 4.1.3 for either Records Manager server or CM Records enabler.
Note that all use WebSphere Application Server JRE. Recommend DST update for WebSphere Application Server. (See WebSphere section later in the document.) |
Recommend WebSphere Application Server JRE updated for Records Manager and CM records enabler. |
|
Document Manager |
No functional impact. Time is provided through operating system. |
None |
DB2
DB2 Universal Database, Version 8
|
Operating system |
Action required |
|
AIX |
Take one of the following actions:
? Ensure the operating system JDK is DST compatible
or
? Apply the IBM Java SDK fix using the Java Time Zone Update tool.
* Use this method if you want to patch only the Java Time Zone data. It allows you to make minimum changes to address the DST change. |
|
Linux |
Take one of the following actions:
? Ensure the operating system JDK is DST compatible.
or
? Apply the IBM Java SDK fix using the Java Time Zone Update tool.
* Use this method if you want to patch only the Java Time Zone data. It allows you to make minimum changes to address the DST change. |
|
Windows |
Take one of the following actions:
? Apply DB2 UDB Version 8.1 FixPak 14 which includes Java fixes for the DST change
* If you apply the fix pack, you obtain more than just the fixes for the DST change. Refer to the fix pack APAR list to see the full list of APAR fixes included in the fix pack.
or
? Apply the IBM Java SDK fix using the Java Time Zone Update tool.
* Use this method if you want to patch only the Java Time Zone data. It allows you to make minimum changes to address the DST change. |
Wesphere
The following list shows the updates for WebSphere application Server
Java
In all cases, it is required that the Java software be updated using the IBM update tool.
The IBM Time Zone Update Utility for Java (JTZU) updates the time zone information in IBM supplied releases and service refreshes of the Java SDK and JRE. It provides a method of applying preventive service to IBM products that embed the Java SDK or JRE. It avoids the need to carry out a total replacement of the SDK or JRE and executes independently of any Fix Packs or Service Packs supplied by IBM products. It will update only the time zone information and apply no other fixes.
This fix can be located at:
http://www-128.ibm.com/developerworks/java/jdk/dst/index.html
Installation instructions and other information can be found at this location.
Conclusion
Integro is recommending that all clients using any of the ECM solutions listed above implement the Java Update from IBM along with any specific updates required.
For Content Manager solutions it is required that the Java update be done on all systems that are part of solution. In addition, the WebSphere patch should be applied and will be dependent on the level that is currently installed. The WebSphere level can be found by opening the administration console, logging in and taking note of the version in the upper right hand window.
It is also important that operating system vendors be contacted to ensure implementation of proper patches for the operating system.