This document will be updated as new
information becomes available.
Last Updated: March 95,
2007
Change Log
|
Date |
Change |
|
03/09/07 |
·
Adds information Sun Alert 102836 and a backward
compatibility issue ·
Adds information about using the Sun tzupdater
tool with JRE 1.3.x ·
Updates to patch status |
|
03/05/07 |
·
Updates to patch status |
|
03/01/07 |
·
Format changes ·
Updates to patch status |
|
02/28/07 |
·
Fixes note regarding the use of P8AE-3.5.1-006.001 ·
Updates patch status |
|
02/15/07 |
·
Updated link to Microsoft’s tzedit tool ·
Updated link to HP update tool ·
Updated patch status ·
Provided additional information on Process Engine Changes |
|
02/01/07 |
·
Added information on the HP tool for updating JREs in place ·
Updated patch status ·
Updated JRE level information |
|
01/17/07 |
·
Updated patch status |
|
01/12/07 |
·
Adding Windows 2000-specific information. ·
Fixed the JRE level for HP ·
Added high-level overview information on the steps required to upgrade
any environment because of the DST changes ·
Added the location of the JREs installed by FileNet products |
|
01/09/07 |
·
Added a generic warning regarding third party products and DST updates ·
Added information about a Sun tool for updated calendar information in
the Sun JREs |
|
12/22/06
AM |
·
Added an IM Process Analyzer line item. No JRE changes are required on
IM Process Analyzers. |
|
12/22/06
PM |
·
Updated the information for CFS-CS and CFS-TPR. ·
Updated status information on the Application Engine patches. |
The
JRE vendors have released alerts identifying a 2007 DST change issue that
affects backward compatibility with a number of time zones. Customers who have
made their systems DST compliant by applying FileNet-supplied patches or by
updating their JREs with the vendor-supplied tools must take corrective action. FileNet recommends
that the corrective action be completed prior to Sunday, March 11, 2007 2:00 AM. Detailed
information on this issue is available at:
http://java.sun.com/developer/technicalArticles/Intl/alert.html
http://www-1.ibm.com/support/docview.wss?rs=3068&uid=swg21250247
http://h18012.www1.hp.com/java/alpha/DST-Alert.html
To
ensure you have the latest version of the appropriate Sun, IBM or HP tool that
fixes the backward compatibility issue, please re-download the tool from the
appropriate web site.
To resolve the issue with
Sun JREs, you must run the
tzupdater tool supplied by Sun with the –f and –bc
options.
To resolve the issue
with HP JREs, you must run the tzupdater tool supplied by HP with the –f and
–bc options.
To resolve the
issue with IBM JREs, you must use Version 1.4.7.c
of the IBM JTZU
tool.
Several countries, the
Several FileNet products rely on the time conversion functions
provided in a JDK or a JRE. The updated JDKs and JREs also contain DST rules
for other countries, so even though only a few countries are changing their use
of DST, the updates will affect JDK and JRE usage globally.
At a high-level to update an environment because of the DST
changes, the following steps are required:
1. Update Operating Systems per
manufacturer’s instructions
2. Update any installed applications
per the manufacture’s instructions, this includes, but is not limited to
Application Server software, JDKs and JREs
3. Update FileNet products as indicated
in the DST document.
In some cases, as an alternative to applying a
FileNet-supplied hot fix, if the changes required are to update the JREs
installed by FileNet (and this can be on the client as well as on server
machines), it is possible to run a utility to update the calendar information
used by the JRE. If you choose to use the utility instead of applying a
FileNet-supplied hot fix pack, be aware that:
·
The
utility must be run against each installed instance of the JRE (this includes
copies installed on client and server machines)
·
You
must use the correct utility for each JRE. Separate utilities are available for
updating IBM, Sun, and HP JREs
·
Using
the utility rather than updating the installed versions of the JREs is a
short-term solution
In the
·
Clocks go forward on the second Sunday in March
·
Clocks revert to standard time on the first Sunday in November
Previously, the clocks changed on the first Sunday in April and
the last Sunday in October.
IBM Customers are being directed to the following website to
ascertain the impact of the change:
http://www.ibm.com/support/alerts/daylightsavingstimealert.html
The information in this document is directed at the impact to the
FileNet-suite of products because of the DST changes. Please review the web
sites for all third-party products installed in your environments to determine
if additional updates are required because of the DST changes.
The following table identifies the minimum levels of JDK/JRE that
support the new rules.
Note: A security vulnerability that affects downloaded applets has
recently been detected. The issue does not affect the JREs installed on
servers. The issue has been resolved in JRE 1.5.0_10 and above, and in JRE
1.4.2_13 and above.
|
JDK 1.3.x Level |
JDK 1.4.x Level |
JDK 1.5.x Level |
Notes |
|
|
Sun |
1.3.1_18 |
1.4.2_11 |
1.5.0_06 |
|
|
JRockit |
Not available yet |
1.4.2_11 R26.4 |
1.5.0_06 R26.3 |
The JRockit JDK relies on the Sun JDK for fixes for the
DST change; therefore, if a fix is in the Sun JDK version 1.4.2_11, then the
fix will also be in JRockit JDK 1.4.2_11 |
|
IBM |
·
1.3.1 SR10 ·
1.3.1 SR10a (US & |
·
1.4.2 SR5 (US only) ·
1.4.2 SR6 (US & ·
1.4.2 SR-7 (adds support for Bermuda & Brazil) due to release
November 30. |
1.5.0 SR1 (US only) 1.5.0 SR3 (US & |
Update also includes
new Xalan 2.7 files: ·
serializer.jar -- 185 KB, modified 8/6/2005 ·
xalan.jar – 3007 KB, modified 8/6/2005 ·
xercesImpl.jar – 1176 KB modified 8/6/2005 ·
xml-apis.jar – 190 KB, modified 8/6/2005 IBM JDK Update for
WebSphere The IBM JDK update overwrites the unlimited strength JCE
files (if your P8 environment uses Symmetric encryption). As a result, users may observe this problem
when logging on: Problem initializing
encryption/decryption with keyId 83dfe9f1, size 448 bits.
java.home=C:\Program Files\IBM\WebSphere\AppServer\java\jre. Cause:
java.lang.SecurityException: Unsupported keysize or algorithm parameters To avoid this issue, the unlimited strength IBM JCE files
need to be reapplied after applying the JDK. |
|
HP |
1.3.1.18 (US only) 1.3.1.19 (Adds Canadian support) |
1.4.2_11 |
5.0.3 (US only) |
Information for Canadian support not available yet. |
FileNet will support
issues occurring as a result of using a vendor’s tool for updating the JRE
calendar information in the event that only FileNet’s software is
non-functional as a result of running the tool. If, on the other hand, the general
stability of the JRE environment is affected as a result of using the tool,
then the vendor will be responsible for the issue. FileNet will give full
support for issues that result from installing our hot fix packs. A list of the
hot fix packs being provided is available later in this document.
IBM, HP, and Sun have
provided tools for updating calendar information.
IBM has created a tool that can update the static date information
used by IBM JDKs. The tool is called the Java Time Zone Utility (JTZU). This
tool is directed at customers who would find updating to a new IBM JRE/JDK
level onerous. For FileNet products, such as Process Engine which are
particularly sensitive to JRE/JDK levels, directing our customers who run our
products on AIX servers, this would be viable alternative to generating a patch
to update the private JRE. The utility has been updated for the Western
Australia DST changes.
Information on the JTZU is available at the following location:
http://www-128.ibm.com/developerworks/java/jdk/dst/index.html
Sun has provided a similar utility to IBM for updating the
calendar information in their JREs. The utility is called tzupdater. The tool
updates calendar information for the US DST changes. Sun still recommends using
the newer JREs, but if making the change is not viable, the utility can be used
in stead. Also, the utility does not at this time support the other time zone
changes. Information about this tool is available at the following URL:
http://java.sun.com/javase/tzupdater_README.html
NOTE:
If
you are running JDK or JRE
version 1.3.1, the standard tzupdater
tool will not work, because of compatibility issues. However, a specialized
version of tzupdater
is available for 1.3.1 customers who have subscribed to a support contract.
Customers with support contracts can download the version of tzupdater
for JDK/JRE version 1.3.1 from the Sun Solve Support Solutions
site.
HP has provided a similar utility to IBM for updating the calendar
information in their JREs. The utility is called tzupdater. The tool updates
calendar information for the US DST changes. HP still recommends using the
newer JREs, but if making the change is not viable, the utility can be used
instead. Information about Daylight Savings Time changes for HP products and
for the JDK/JRE update tool are available at the following URLs:
General Information
Java update tool
http://www.hp.com/products1/unix/java/DST-US.html
Please refer to the Oracle Metalink home page for information
on DST changes for Oracle products. Metalink Note 397281.2 is very informative.
Note that while your use of Oracle might require you to pick up
patches in support of the Daylight Savings Time changes, the following FileNet
products that communicate directly with a database do not utilize any of the updated
Oracle facilities:
·
Image Services
·
Content Engine
·
Process Engine
·
eProcess
·
Business Process Framework
For each platform, the following table indicates the minimum patch levels that support the new DST rules.
|
Platform |
Patches |
|
IBM |
AIX 4.3: APAR IY91593 AIX 5.1: APAR IY75214 AIX 5.2: APAR IY75213 AIX 5.3: APAR IY75211 |
|
HP-UX |
HP-UX 11.0: PHCO_34673 HP-UX 11.11i v1: PHCO_34668 HP-UX 11.11i v2: PHCO_34669 |
|
Solaris |
Solaris 8 with patches 109809-02 or
later and 108993-52 or later Solaris 9 with patches 113225-03 or
later and 112874-33 or later Solaris 10 with patches 122032-01 or
later and 119689-07 or later |
|
Windows |
Refer to the 2007 Global Time Zone update patch (KB924840)
information available at the following locations: http://support.microsoft.com/kb/928388 http://www.microsoft.com/windows/timezone/dst2007.mspx There is no DST patch for Windows 2000 operating systems,
instead customers are being directed to a utility called tzedit utility at: http://support.microsoft.com/kb/914387 for DST adjustments on Windows 2000 Servers. |
More information on the impact of the DST changes is
provided at the following links
·
WebLogic
Patch for 2007 Daylight Savings Time Changes
·
CRN
Java's Daylight Savings Problem Brings Back A Bad Memory
·
IBM Daylight
Savings Time Alert
The following table identifies which FileNet products are affected
by the DST changes and if changes are needed, what the carrier will be for
those changes. As changes are released, the table will be updated. The products
are listed in alphabetical order.
To determine if there are any dependencies between the hot fixes
listed in the table and other FileNet products installed in your environment,
refer to the patch dependency matrix which is published on the CSS FTP site in
the same folder as the hot fixes.
Notes
·
At this time, the Process Engine hot fix packs are addressing the
Daylight Savings Time change being introduced in March. A further change is
required in the Process Engine code to support the daylight savings time change
that will take affect in the November. This additional Process Engine update
will be introduced in a hot fix pack later in the year.
·
In the Process Simulator there is one unresolved issue that affects
any Daylight Savings Time event, and that is, the clock time displayed in all
Process Simulator windows is incorrect for the one hour when the clocks are
changed. This issue will be resolved in a future hot fix pack.
|
Product |
Release |
Patch Needed? |
Patch Name |
Status |
Expected Availability |
|
Acenza |
All
releases |
N |
|
|
|
|
Application
Engine/Workplace |
3.0.0 |
Y |
P8AE-3.0.0-012 |
Released
on 2/13/07 |
Released |
|
|
|
|
P8AE-3.0.0-012.001 |
Updated
JRE to address security vulnerability In QA
review |
March |
|
|
3.5.1 |
Y |
P8AE-3.5.1-004.003 |
Contains
updated Xalan files for compatibility with WebSphere changes. These
updates are also available in P8AE-3.5.1-007. Released
on 10/30/06 |
Released |
|
|
|
|
P8AE-3.5.1-006.001 |
Contains
the older Xalan files for compatibility with deployments that use Sun Java
App Server. These
updates can also be applied on top of in P8AE-3.5.1-007. Released
on 12/22/06 |
Released |
|
|
|
|
P8AE-3.5.1-007 |
Contains
updated JRE and updated Xalan files for compatibility with WebSphere changes. Released
on 2/13/07 |
Released |
|
|
|
|
P8AE-3.5.1-007.002 |
Updated
JRE to address security vulnerability In development
review |
March |
|
|
4.0.0 |
N |
|
|
|
|
Business
Activity Monitor (BAM) |
All
releases |
N |
|
|
|
|
Business
Process Framework |
3.5.2 |
Y |
BPF 3.5.2-005.001 |
Released
on 1/15/2007 |
Released |
|
|
3.6.0 |
N |
Is in
base release |
Released
in December 2006 |
Released |
|
|
4.0.0
FCS |
N |
Is in
base release |
Released
in January 2007 |
Released |
|
|
4.0.0
GA |
N |
Will
be in base release |
In
test |
May |
|
Capture |
All
releases |
N |
|
|
|
|
CFS-CS/TPR[1] |
3.5.1 |
N |
|
|
|
|
Content
Engine |
3.0.0 |
Y |
P8CE-3.0.0-010 |
Released
on 1/15/2007 |
Released |
|
|
3.5.2 |
Y |
P8CE-3.5.2-003.001 |
Released
on 2/5/2007 |
Released |
|
|
4.0.0 |
N |
|
|
|
|
Content
Services |
All
releases |
N |
|
|
|
|
Email
Manager |
All
releases |
N[2] |
|
|
|
|
eForms |
All
releases |
N |
|
|
|
|
eProcess |
5.0.0 |
N |
Manual
process required on top of eProcess-5.0.0-018 |
Does
not use a private JRE. Requalified released patch with DST-compatible JREs Documented called 2007 Daylight Savings Time - Patching the JRE -doc (added_02_28_2007) posted
3/2/07 to CSS web site in the following locations: /Product Info/1)
Products/Business Process Manager (BPM)/Technical Bulletins/3.5.2x /Product Info/1)
Products/Business Process Manager (BPM)/Technical Bulletins/3.5.1x /Product Info/1)
Products/Business Process Manager (BPM)/Technical Bulletins/3.5.0x /Product Info/1)
Products/Business Process Manager (BPM)/Technical Bulletins/3.0.0x /Product Info/1)
Products/Image Manager (IM)/eProcess Services/Technical Bulletins |
Released |
|
|
5.1.0 |
Y |
eProcess-5.1.0-006 |
Released
3/2/2007 |
Released |
|
IDM
Desktop and Web Services |
All
releases |
N |
|
|
|
|
Image
Services |
3.6 |
N |
|
|
|
|
|
4.0 |
N |
|
|
|
|
IM
Process Analyzer |
3.0.0 |
Y |
IMPA-3.0.0-004 |
Released
3/2/2007 |
Released |
|
|
All
other releases |
N |
|
|
|
|
ISRA |
All
releases |
N |
|
|
|
|
Print
Services |
All
releases |
N |
|
|
|
|
Process
Analyzer |
3.0.0 |
Y |
P8PA-3.0.0-005 |
Released
on 2/20/07 |
Released |
|
|
3.5.1 |
Y |
P8PA-3.5.1-002 |
Released
on 2/27/07 |
Released |
|
|
4.0.0 |
N |
|
|
|
|
Process
Engine[3] |
3.0.0 |
Y |
P8PE-3.0.0-005 |
Released
on 2/20/07 |
Released |
|
|
3.5.2 |
Y |
P8PE-3.5.2-002 |
Released
on 2/27/07 |
Released |
|
|
4.0.0
GA |
Y |
P8PE-4.0.1
for AIX No
changes required for other platforms |
In
development |
March |
|
Process
Simulator |
3.0.0 |
Y |
P8PS-3.0.0-005 |
Released
on 2/20/07 |
Released |
|
|
3.5.2 |
Y |
P8PS-3.5.2-002 |
Released
on 2/27/07 |
Released |
|
|
4.0.0
FCS |
Y |
P8PS-4.0.0-001 |
Released
on 2/21/07 |
Released |
|
|
4.0.0
GA |
Y |
PS
4.0 GA |
In
development |
March |
|
Records
Crawler |
3.5 |
N |
|
|
|
|
Records
Manager[4] |
3.0.0 |
Y |
Manually
apply Xalan updates. Xalan files available in P8AE-3.5.1-004.003 and in
P8AE-3.5.1-007. |
Manual
application of files. No hotfix pack planned. |
|
|
|
3.5.1 |
Y |
Manually
apply Xalan updates. Xalan files available in P8AE-3.5.1-004.003 and in
P8AE-3.5.1-007. Will
also be provided in P8RM-3.5.1-004 |
|
Manual workaround
available. Hotfix pack |
|
|
3.7.0 |
N |
|
|
|
|
Remote
Capture Services |
All
releases |
N |
|
|
|
|
Rendition
Engine |
All
releases |
N |
|
|
|
|
Report
Manager |
All
releases |
N |
|
|
|
|
SAP
Connector |
All
releases |
N |
|
|
|
|
Siebel
Connector |
All
releases |
N |
|
|
|
|
System
Monitor |
3.7.0 |
N |
|
Documentation
only Included
in FSM-3.7.0-001 readme. Released
in February. |
Released |
|
|
4.0.0 |
N |
|
|
|
|
Team
Collaboration Manager |
3.5.0 |
Y |
P8TCM-3.5.0-004.001 |
Xalan
changes. Released 2/6/07 |
Released |
|
Visual
Workflow |
|
N |
|
No
changes needed |
|
|
Web
Site Manager |
4.0.1 |
N |
|
|
|
|
|
4.1.1 |
N |
|
|
|
The
following table identifies the default location for the JREs that are installed
by FileNet software on to server machines. The table also indicates if using
the product could cause a JRE to be installed on the client machine.
Note: If using the vendor-supplied tool
for updating JREs in place, then use the vendor tools as indicated in the
following table.
|
For FileNet products installed on
operating system… |
|
|
Windows |
Sun |
|
Solaris |
Sun |
|
Linux |
Sun |
|
HP-UX |
HP |
|
AIX |
IBM |
|
Product |
JRE Location |
Client Download |
|
Application Engine |
..\FileNet\Router\JRE |
No |
|
..\FileNet\_jvm |
No |
|
|
..\FileNet\Workplace\download |
Yes |
|
|
Business Process
Framework (BPF) |
..\FileNet\BPF\_jvm |
Yes |
|
Content Engine |
..\FileNet\Content Engine\_jvm |
No |
|
Content Federated
Services for CS |
..\FielNet\_cfs\jvm |
No |
|
..\FileNet\CFS\FedJRE |
No |
|
|
eProcess 5.0.0 |
|
|
|
On the Process Engine |
..\FNSW\jre |
No |
|
On the WebWorkflo IDM
Web Server |
..\FileNet\IDM\Web\IDMWS\Redist\Download |
Yes |
|
C:\Program Files\JavaSoft\JRE |
No |
|
|
On the Open Client
Server |
..\FileNet\IDM\Web\FNOpenClient\eprocess\ download |
Yes |
|
eProcess 5.1.0 |
|
|
|
On the Process Engine |
..\FNSW\jre |
No |
|
On the IDM Web Server |
..\FileNet\IDM\Web\IDMWS\Redist\Download |
Yes |
|
..\FileNet\IDM\PWBin\jre |
No |
|
|
On the Open Client
Server |
..\FileNet\IDM\Web\FNOpenClient\eprocess\ download |
Yes |
|
|
|
|
|
Process Analyzer |
..\FileNet\Process Analyzer Engine\jre |
No |
|
Process Engine |
..\FNSW\jre |
No |
|
|
|
|
|
|
|
|
|
Process Simulator |
..\FileNet\ProcessSimulator\jre |
No |
|
Records Manager |
..\Filenet\_rmjvm |
No |
|
Team Collaboration
Manager |
..\FileNet\Collaboration\_jvm |
No |
Several P8 applications, including Workplace and Records Manager,
utilize Xalan. The WebSphere patches that provide updated JREs also update the
level of the Xalan used by the application server to 2.7. If you install an
application server patch and subsequently discover that any of the P8
applications no longer function correctly, then update the Xalan files used by
the P8 application to version 2.7. Hot fix P8AE-3.5.1-004.003 contains the 2.7
Xalan files and installation instructions. The files provided in this hot fix
can be applied to other P8 applications, such as Records Manager and Team
Collaboration Manger.
If you are using the Sun Java Application Server, then you must
use the older (2.5) version of Xalan. These files are provided in hot fix
P8AE-3.5.1-006.001.
The JRE/JDK used by System Monitor is configurable. For the 3.7
System Monitor special instructions will be provided telling customers how to
make the required changes. In addition, the Installation Guide and the Release
Notes will be updated with the appropriate instructions.
For the 4.0 release, the changes will be incorporated prior to the
release.
Basic instructions are as follows:
Install the JRE provided by Sun or the appropriate hardware vendor
that includes support for the new DST rules.
Update some System Monitor files on both the server and the
client. Details on this step will be forthcoming shortly.
The Windows FSM 3.7 CD already contains a JRE that has the DST
changes: 1.4.2_12.
FSM 3.7 Unix customers will be advised not to use the JRE provided
on the FSM 3.7 media.
[1] The JREs installed with CFS are used by
InstallShield and for WAR file generation and therefore do not need to be
updated.
[2] No code changes needed.
However, if EM is in “run once” mode and scheduled to start running between
2:01am and 2:59am on the day the clocks move forward, then the run will not
occur because the time will not occur.
[3] The Process Engine hot fix packs being released at
this time provide support for the March 2007 daylight savings time change,
however an additional hot fix pack will be provided at a later date to provide
support for the November, 2007 change.
[4] The JRE installed with Records Manager is for use by
InstallShield only and therefore does not need to be updated.