Software > WebSphere >

Daylight Saving Time (DST) information for IBM WebSphere Everyplace Deployment (WED) for Windows and Linux

Flash (Alert)

Abstract

The Energy Policy Act of 2005 changes the effective dates of Daylight Saving Time for the United States beginning in 2007 and other countries have also revised their Daylight Saving Time rules. Actions will be required to address this issue in many software applications, including operating systems and IBM® WebSphere® Deployment for Windows® and Linux®.

Content

The WebSphere Everyplace Deployment (WED) for Windows and Linux product will use a tool called the Java™ Time Zone Updater (JTZU) to resolve the impact of the Daylight Savings Time (DST) changes for the installed JVM.
TOOLKIT INSTRUCTIONS:

To install this update directly on machine that has toolkit installed, the following JTZU utility may be used:
http://www-128.ibm.com/developerworks/java/jdk/dst/index.html

CLIENT INSTRUCTIONS:
To install this update directly on each client, the following JTZU utility may be used:
http://www-128.ibm.com/developerworks/java/jdk/dst/index.html

OR

If you wish to distribute the DST update to multiple clients, then Device Management Server (DMS) may be used following these instructions:

For Linux:
1. Download the JTZU Utility using the following link:
http://www-128.ibm.com/developerworks/java/jdk/dst/index.html
2. For applying the fix on Linux based WED client, copy the file onto a Linux machine.
3. Extract the zip file to a temporary folder
Example:
On Linux: /tmp/jtzu
On Windows: C:\jtzu
4. Edit file runjtzuenv, on Windows - C:\jtzu\runjtzuenv.bat, on Linux - /tmp/jtzu/runjtzuenv.sh
a. Modify JAVA_HOME variable to point to a Java home directory (the location in the client
machine where a SDK/JRE is installed)
For example,
On Linux: JAVA_HOME=/usr/ibm/websphere/appserver/java/jre
On Windows: set JAVA_HOME=c:\program files\ibm\java142\jre
b. Modify NOGUI variable.
For example,
On Linux: NOGUI=false
On Windows: set NOGUI=false
5. For Linux based WED client, edit file /tmp/jtzu/runjtzu.sh
Insert the "cd /jtzu" in a new line before the following lines:
chmod -R 755 1.3.1
chmod -R 755 1.4.2
chmod -R 755 1.5.0
6. Save and close the edited files. Zip the jtzu folder and copy it onto the machine that has
NativeAppBundle tool.
7. On machine that has NativeAppBundle tool, extract the zip file to a temporary folder like
C:\temp\jtzu-linuxia32-1.1.7a
8. Run the NativeAppBundle command.
a. For Lotus Expeditor 6.1 NABT tool is located on the Expeditor Client CD under
utils\NativeAppBundle\.
Example of the command:
NativeAppBundle.bat -BundleSymbolicName=JTZU -InputDirectory=C:\temp\jtzu-linuxia32-1.1.7a -InstallDirectory=/jtzu -BundleVersion=1.0.0 -Install=/jtzu/runjtzu.sh
b. For WebSphere Everyplace Deployment 6.0 NABT tool is located by default under C:\Program Files\IBM\WebSphere\DMS18\bin.
Example of the command:
NativeAppBundle.bat -BundleName=JTZU -InputDirectory=C:\temp\jtzu-linuxia32-1.1.7a -InstallDirectory=/jtzu -BundleVersion=1.0.0 -Install=/jtzu/runjtzu.sh
This creates the file JTZU+1_0_0.jar.
9. On the DM Server machine, copy file JTZU+1_0_0.jar to C:\Program Files\IBM HTTP Server\htdocs\en_US
10. In Device Manager Console,
a. Right click on 'Softwares' and select 'New Software'
b. Select 'Software type' as 'Native Win32 OSGI bundle'
c. Enter http://<wedservername>/JTZU+1_0_0.jar in 'URL' field and click on 'Fetch'.
d. Click on 'Next'.
e. Click on 'OK'.
f. Select 'Device' in the right panel
g. Right click on a device and select 'Submit Job'
h. Click on 'Next'.
i. Select 'Native Bundle Software Distribution' as the 'Job type'.
j. Click on 'Next'.
k. Click on 'Add Group'.
l. Select 'JTZU (version 1.0.0) NativeWin32OSGIBundle' as Software and click on 'Next'.
m. Click on 'OK'.

11. On the WED Client machine: -
a. Wait for client to check for updates. 'IBM Time Zone Update Utility for Java' window is displayed.
b. Select 'Interactive mode' and press 'Start'.
c. Type in path or choose using the 'Browse' button, the directory which contains the WED Client JRE
For example, C:\Program Files\IBM\WED\rcp\eclipse\plugins\com.ibm.rcp.j2se.win32.x86_1.4.2.SR2\jre
d. Press the 'Update' button.
e. A warning message is popped up. Press 'OK'.
f. Message is popped up telling that the Java installation is updated with the new timezone information. Press 'OK'.
g. Press 'Exit'.

On the DMS Server machine:
1. Download the JTZU Utility from:

http://www-128.ibm.com/developerworks/java/jdk/dst/index.html

2. Extract the zip file to a temporary folder.

For Example: C:\jtzu
3. Edit file C:\jtzu\runjtzuenv.bat

4. Run the NativeAppBundle command:

-BundleVersion=1.0.0–Install=C:\jtzu\runjtzu.bat

5. Copy file JTZU+1_0_0.jar from:

6. In Device Manager Console:

http:\\

and click on 'Next'.

On the WED Client machines:
1. Restart WED Client.
2. ‘IBM Time Zone Update Utility for Java’ window is displayed.
3. Select ‘Interactive mode’ and press ‘Start’.
4. Enter or choose using the ‘Browse’ button, the directory which contains the

5. Press the ‘Update’ button.
6. If a warning message appears. Press ‘OK’.
7. Message is displayed telling that the Java installation is updated with the

new timezone information. Press ‘OK’. 8. Press ‘Exit’.

IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.

Document information


Product categories:

	Software

	Mobile, Speech and Enterprise Access

	Mobile and Enterprise Access

	WebSphere Everyplace Deployment

	WebSphere Everyplace Deployment for Windows and Linux


Operating system(s):
	Linux Red Hat - xSeries, Windows

Software version:
	6.0

Software edition:
	Enterprise, Starter

Reference #:
	1249063

IBM Group:
	Software Group

Modified date:
	2007-01-02

Translate My Page

Rate this page

Help us improve this page. Your response will be used to improve our document content. Requests for assistance, if applicable, should be submitted through your normal support channel as we cannot respond from this site.