prim29451:Is Primavera Evolve compatible with the Daylight Savings Time (DST) changes effective 2007?

Daylight Savings Time (DST) Changes Effective 2007

Effective in 2007, Daylight Savings Time (DST) will begin three weeks earlier and end one week later in the United States, Canada, and several other locations. In summary:

?SPAN style=”FONT: 7pt ‘Times New Roman’”>          The US Energy Policy Act of 2005 changed the dates for Daylight Saving Time in the US starting in 2007

?SPAN style=”FONT: 7pt ‘Times New Roman’”>          Prior to 2007, US DST started on the first Sunday in April and ended the last Sunday in October.

?SPAN style=”FONT: 7pt ‘Times New Roman’”>          Starting 2007, US DST starts on the second Sunday in March and ends the first Sunday in November, i.e. March 11 through November 4 for 2007

This bulletin includes the following sections:

?SPAN style=”FONT: 7pt ‘Times New Roman’”>          Impact of DST Changes to Primavera Evolve

?SPAN style=”FONT: 7pt ‘Times New Roman’”>          Recommended DST Updates – WINDOWS

?SPAN style=”FONT: 7pt ‘Times New Roman’”>          Recommended DST Updates – SOLARIS

?SPAN style=”FONT: 7pt ‘Times New Roman’”>          Actuate Management Console and DST Changes

Impact of DST Changes to Primavera Evolve

The new changes to Daylight Savings Time (DST) impact Primavera Evolve application servers. This section outlines the known impacts if no updates are made to the server environments.

The impacts will occur during the new DST periods only (three weeks in March/April and one week in October/November) and only in the countries affected.

?SPAN style=”FONT: 7pt ‘Times New Roman’”>          Database timestamps will be incorrect and be an hour later than actual time.

?SPAN style=”FONT: 7pt ‘Times New Roman’”>          Message and request timestamps listed in the application will be an hour later than actual time.

?SPAN style=”FONT: 7pt ‘Times New Roman’”>          Staffing workflows will expire an hour later than expected.

?SPAN style=”FONT: 7pt ‘Times New Roman’”>          Scheduled Primavera Evolve tasks (such as notifications) will be off by one hour

?SPAN style=”FONT: 7pt ‘Times New Roman’”>          Scheduled Windows tasks may be off by one hour (such as Data Mart)

?SPAN style=”FONT: 7pt ‘Times New Roman’”>          If you run scheduled Actuate reports through the Actuate Management Console, these may not trigger at the correct time (off by one hour)

Note that timestamps are permanently recorded in the database. Therefore, time stamps created during the new DST period (for 2007, March 11 – April 1) will still remain incorrect when the prior DST start date is reached on April 1, 2007. This is true even if updates are applied afterwards.

Recommended DST Updates – WINDOWS

Primavera recommends the following steps to mitigate the impact of the new DST changes to Microsoft Windows server environments.This includes servers used for Primavera Evolve, Collaboration, Actuate, and database hosts.

1.Update the Windows OS clock using the following information depending on the OS version (Windows 2003 or Windows 2000):

WINDOWS 2003: Install the Microsoft Windows Critical Update to add the new DST effective dates.

This update was released as part of Microsoft抯 February monthly security update. This update should be installed on any Windows 2003 server hosting a Primavera Evolve-related application.

For information on this specific update, see http://support.microsoft.com/kb/931836.

WINDOWS 2000: To update Windows 2000, download the Microsoft Time Zone Editor (Tzedit.exe).

For information on downloading and running the Time Zone Editor, see http://support.microsoft.com/kb/914387.

On this link, refer to 慚ethod 2: Change the time zone settings on a single computer?and the sub-header, 慚anually configure daylight saving time dates by modifying an existing time zone?/I>.

Follow the four steps to update the Windows 2000 OS clock. These instructions require changes to the registry.

2.The following Primavera Evolve servers require a java virtual machine (JVM) update:

?SPAN style=”FONT: 7pt ‘Times New Roman’”>          Primavera Evolve application server

?SPAN style=”FONT: 7pt ‘Times New Roman’”>          PM/BI server

?SPAN style=”FONT: 7pt ‘Times New Roman’”>          Connector server

Each server must be stopped before applying the JVM update. If any connector is running to import or export data, allow it to complete first on the machine being updated.

To update the JVM on each server, use the Sun Java SE Platform TZupdater Tool. For information on TZupdater, see http://java.sun.com/javase/tzupdater_README.html

To download TZupdater, go to the Sun downloads page: http://java.sun.com/javase/downloads/index.jsp

Select the 慗DK US DST Timezone Update Tool – 1.0.1?download link to download the 憈zupdater-1_0_1.zip?file. If required, create a Sun Online Account in order to access the download file.

After downloading the zip file, extract the file locally and read the instructions in the README.It is recommended to view the README in WordPad.

NOTE: You must set the correct BEA path PRIOR to updating the JVM. The syntax to run in a DOS prompt is:

set PATH=<BEA WebLogic directory>\jdk142_05\jre\bin;%PATH%

Where <BEA WebLogic directory> is the directory where Weblogic is installed.For example, C:\bea.

After updating the PATH statement, use the same DOS window to update the JVM per the README by running:

java -jar tzupdater.jar -u

The prompt should return with no messages. Repeat this for each server.

This completes the Primavera Evolve updates and the Primavera servers can be restarted.

No updates are required on the database host (unless running an Evolve application listed at the beginning of step 2).

NOTE: End-user client machines should also be updated with the appropriate Microsoft Critical Update to update the Windows OS clock. This is not required.

Recommended DST Updates – SOLARIS

This section applies if your application server is running on Solaris. For an overview on the required DST updates, refer to http://www.sun.com/bigadmin/hubs/dst/software/.

For each Primavera application server (Core server, Collaboration, and Connector server), Solaris 10 and the BEA JVM must be updated.

To update Solaris 10:

1.In a web browser, go to the following URL referenced by Sun Alert 102775:

http://sunsolve.sun.com/search/document.do?assetkey=1-26-102775

2.Scroll down to section 5, 慠esolution?Under 慡PARC Platform? you will see the following:

Solaris 10 with timezone patch 122032-04 or later and libc patch 119689-07 or later

3.Click on “122032-04″ to apply the timezone patch.Follow the instructions to apply the patch.

4.Return to the URL in step 1 and scroll to where you see the text in step 2.

5.Click on “119689-07″ to apply the libc patch.Follow the instructions to apply the patch.

NOTE: The libc patch in step 5 is now listed as 慜BSOLETE?on Sun抯 website and has been accumulated in patch 118833-36 ( http://sunsolve.sun.com/search/document.do?assetkey=urn:cds:docid:1-21-118833-36-1 ).

You have the option of applying this patch instead.

This completes the update of Solaris 10.

To update the BEA Weblogic JVM:

1.In a web browser, go to the following URL:

http://java.sun.com/javase/downloads/index.jsp

Scroll down to “JDK US DST Timezone Update Tool – 1.0.1″.Click the Download button next to this.

2.You will be prompted by the Sun website to login.Please login (if you do not have a user login, register for one).

3.Accept the license agreement and select “JDK US DST Timezone Update Tool – 1.0.1″ to download the update.Save the file to your computer and then copy it to the server machine running Primavera applications.

4.If updating a server machine running Primavera applications, stop all Primavera applications.If any connector is running to import or export data, allow it to complete first on the machine being updated.

5.Unzip the file tzupdater-1_0_1.zip that was downloaded in step 3.Unzipping should have copied 3 files including a file called tzupdater.jar.

6.Navigate to the directory where tzupdater.jar was unzipped in step 5; it should be in a subdirectory called “tzupdater2007a”.

7.If updating a machine running Primavera applications, continue to step 8.Otherwise, go to step 10.

8.Type the following:

set PATH=<Sun AS directory>/jdk142_05/jre/bin:$PATH

where <Sun AS directory> is the directory where Sun Application Server is installed.

9.Type “java -jar tzupdater.jar -u”.Make sure there are no error messages.If the update is successful, there should be no output to the command line.Verify that the previous timezone information was backed up into a folder that looks like

<Sun AS directory>/jdk142_05/jre/lib/zi.XXXX

where XXXX is a label like tzdata2003a.

If not running connectors on this machine, go to step 12.

10.If you are not running Connectors with your Primavera Application, go to step 12.If you are running Connectors with your Primavera Application type the following:

set PATH=<Primavera connectors directory>/_JVM/bin:$PATH

where <Primavera connectors directory> is the directory where the Primavera connectors tool is installed.

If you are running Connectors from a different Solaris host please update this Solaris machine with the Solaris 10 with timezone patch as outlined in steps 1 through 5 in the section 揟o update Solaris 10?

11.Type “java -jar tzupdater.jar -u”.Make sure there are no error messages.If the update is successful, there should be no output to the command line.Verify that the previous timezone information was backed up into a folder that looks like

<Primavera connectors directory>/_JVM/lib/zi.XXXX

where XXXX is a label like tzdata2003a.

12.Restart the Sun Application.

No updates are required on the database host (unless running an Evolve application listed at the beginning of step 2).

Actuate Management Console and DST Changes

Actuate抯 Management Console and scheduling tools are impacted by the new DST changes and Actuate has released a fix to address these issues.Actuate has released ’8.1sp1 Fix 10′ to address JVM calculations used by Actuate itself, primarily around scheduling within the Actuate Management Console

Before considering implementing this Fix please note the following:

?SPAN style=”FONT: 7pt ‘Times New Roman’”>          Actuate抯 8.1sp1 Fix 10 contains a significant number of defect fixes and Primavera has not tested to see the impact of these other fixes yet. Thus there could be impacts to the standard delivered reports and your custom reports.

?SPAN style=”FONT: 7pt ‘Times New Roman’”>          If deciding to move forward with this Actuate抯 8.1sp1 Fix 10, Primavera recommends testing thoroughly in a test Primavera environment before applying to a Primavera production environment(s).

?SPAN style=”FONT: 7pt ‘Times New Roman’”>          If any problems are found after applying Actuate抯 8.1sp1 Fix 10, Primavera will provide best effort support.

?SPAN style=”FONT: 7pt ‘Times New Roman’”>          If your company is interested in obtaining Actuate抯 8.1sp1 Fix 10, please log a POINT incident with Primavera Support who will work to deliver the appropriate files to you.

Primavera will test Actuate抯 8.1sp1 Fix 10 in conjunction with the release of 8.6.0sp1, tentatively scheduled for the end of April 2007.In the meantime, during the period of the new DST changes (between March 11, 2007 and April 1, 2007 for example), scheduled reports set up within the Actuate Management Console may execute one hour differently than expected.