Guest

Cisco Web Collaboration Option

Field Notice: FN - 62938 - Daylight Saving Time Policy Changes Effective September 2007 - For Cisco Web Interaction Manager and Email Interaction Manager


Revised September 26, 2007

September 11, 2007

NOTICE:

THIS FIELD NOTICE IS PROVIDED ON AN "AS IS" BASIS AND DOES NOT IMPLY ANY KIND OF GUARANTEE OR WARRANTY, INCLUDING THE WARRANTY OF MERCHANTABILITY. YOUR USE OF THE INFORMATION ON THE FIELD NOTICE OR MATERIALS LINKED FROM THE FIELD NOTICE IS AT YOUR OWN RISK. CISCO RESERVES THE RIGHT TO CHANGE OR UPDATE THIS FIELD NOTICE AT ANY TIME.


Products Affected

Products Affected

EIM - 4.2(X)

WIM - 4.2(X)

Problem Description

In compliance with the Energy Policy Act of 2005, the switchover dates to and from Daylight Savings Time (DST) will shift in the United States in calendar year 2007. DST will commence three weeks earlier (the second Sunday in March) and will end one week later (the first Sunday in November), each occurring at 2:00 A.M.

Background

On August 8, 2005, the Energy Policy Act of 2005 (H.R.6.ENR) was signed into law. Section 110 of this Act modified the time change dates for Daylight Saving Time (DST) in the US. Beginning in March of 2007 and beyond, DST will begin on the second Sunday of March at 2:00 A.M. and end the first Sunday of November at 2:00 A.M.

For more information, see the Energy Policy Act of 2005 (Section 110).

The old DST policy dictated the start of DST was the first Sunday of April and ended on the last Sunday of October.

Problem Symptoms

SLA for email activities would be set incorrectly.

Timestamps on UI consoles would be displayed incorrectly.

SLA-based reports would display inaccurate data.

Any alarm workflows that are setup that have a condition which is time-based, would not execute at correct intervals.

Workaround/Solution

Stopping Servers

  1. Stop Cisco Interaction Manager service on all the servers.

  2. Make backups of all the files that are being edited in the steps below.

Applying the Operating System Patches

Use the following procedure to configure the application. Use JDK 1.4.2.13 for NZ DST.

Sun Download Page

Single or Split Server Configuration

  1. Create a folder called jdk1.4.2.13 under the folder (BEA_HOME)

  2. Install JDK 1.4.2.13 under the folder (BEA_HOME)\jdk1.4.2.13.

    After the installation, this folder should contain sub-folders - bin, demo, include, an so on.

  3. Verify the JDK version. See instuctions in the "Verify the JDK Version" section.

  4. Make a backup of the following file:

    CIM_Home\bin\platform\setenv_(APP_SERVER_NAME).bat

  5. Edit the following file and set the value of the JAVA_HOME environment variable to point to the path of the JDK 1.4.2.13 installation directory.

    CIM_Home\bin\platform\setenv_(APP_SERVER_NAME).bat

    For example,

    SET JAVA_HOME=(BEA_HOME)\jdk1.4.2.13

Distributed Configuration

Application Server(s) under the folder BEA_HOME.

2. Install JDK 1.4.2.13 under the folder (BEA_HOME)\jdk1.4.2.13. After the installation, this folder should contain sub-folders - bin, demo, include, and so on.

3. Verify the JDK version. See instuctions in "Verify the JDK Version" section.

4. Make a backup of the following file:

CIM_Home\bin\platform\setenv_(APP_SERVER_NAME).bat

Edit the following file and set the value of the JAVA_HOME environment variable to point to the path of the JDK 1.4.2.13 installation directory.

CIM_Home\bin\platform\setenv_APP_SERVER_NAME).bat

For example,

SET JAVA_HOME=BEA_HOME\jdk1.4.2.13

Services Server

  1. Install JRE 1.4.2_15 on the Services Server in a folder, D:\jre1.4.2.13 for example.

  2. Verify the JDK version. See instuctions in "Verify the JDK Version" section.

  3. Take a backup of the following file:

    CIM_Home\bin\platform\setenv.bat

  4. Edit the following file and set the value of the JAVA_HOME environment variable to point to the path of the JRE 1.4.2.13 installation directory.

    CIM_Home\bin\platform\setenv.bat

    For example,

    SET JAVA_HOME=D:\jre1.4.2.13

Notes:

  1. If File System is installed on a server other than the Application server, then the above changes need to be done on the File server, in case of Single/Split Server configuration.

  2. If there are multiple application-web servers configured, make similar changes in the setenv_(APP_SERVER_NAME).bat files for each application server.

  3. In case of a Distributed server configuration, the setenv.bat file will always reside under CIM_Home folder of the Services server and not on the File Server.

Starting Servers

Start Cisco Interaction Manager service on all the servers.

Verifying JDK/JRE Version

Change directory to BEA_HOME/JDK/JRE_VERSION/bin and open DOS command.

Execute following command to verify JDK version:

java -version

For JDK/JRE 1.4.2.13

java version "1.4.2.13"

Revision History

Revision

Date

Comment

1.1

26-SEP-2007

Added three additional symptoms in Problem Symptoms section. Added workaround steps and details to the Workaround/Solution section.

1.0

11-SEP-2007

Initial Public Release

For More Information

If you require further assistance, or if you have any further questions regarding this field notice, please contact the Cisco Systems Technical Assistance Center (TAC) by one of the following methods:

Receive Email Notification For New Field Notices

Product Alert Tool - Set up a profile to receive email updates about reliability, safety, network security, and end-of-sale issues for the Cisco products you specify.