Fix (APAR): JR43099 Status: Fix Product: IBM Business Process Manager Release: 7.5.1.0 Operating System: All operating systems Supersedes Fixes: JR41966 Pre-requisite Fixes: JR42280 Exclusive-requisite Fixes: Defect: JR43099 Byte size of APAR: 237076 Date: 2012-06-28 Abstract: Time-elapsed UCAs should be executed at the specified process server times Description/symptom of problem: Time-elapsed UCA are rescheduled incorrectly if Process Server and Database are in different time zones. If you design a UCA for repeated execution, you might experience the case that the first execution happens on the defined time, while all subsequent executions are moved by one or more hours. This situation can happen, if the Process Server and the Database are running on different time zones. This fix solves this situation so that the UCA execution takes place always on the scheduled Process Server time. Hint: if the Process Server runs on Linux, the UCA's schedules are meant without daylight savings time. Additional Information: http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r5m1/index.jsp?topic=%2Fcom.ibm.wbpm.wle.editor.doc%2Fmodeling%2Ftopic%2Fusing_undercover_agents_B.html describes how to define an UnderCover Agent for a scheduled event. In bullet 10, the sample shows how to define the schedule to fire at midnight. The time specification "midnight" is interpreted as the point in time, where the process server machine's clock reaches 24:00 local time. This means, that the local timezone setting of the process server machine is used. In case of clustered process servers, the process servers must be set to the same time zone, and their clocks should be synchronized. For scheduled Undercover Agents, the clocks' times must not differ for more than 2.5 minutes. The process server's databases may reside on a remote machine, and this machine may have different timezone and time setting. Changes to timezone or time setting on process server or database machines may cause already scheduled Undercover Agents to run at an unexpected time. However, all subsequent executions of the Undercover Agents are performed according to the specification, interpreted as usual: according to the current time zone and time setting of the systems. Directions to apply fix: 1) Shutdown WebSphere. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix. 2) Extract the .zip file to a directory. For example, extract to C:\temp. 3) Add the fix pack repository location in IBM Installation Manager: a. Start IBM Installation Manager. b. In Installation Manager, click File > Preferences > Repositories. c. Click Add Repository. d. Browse to or enter the file path to the repository.config file. The repository.config file is located in the directory where you extracted the compressed files. For example, enter C:\temp\repository.config, and then click OK. 4) On the main page of the Installation Manager, click Update. 5) Restart WebSphere Directions to remove fix: NOTE: FIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED. DO NOT REMOVE A FIX UNLESS ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED. YOU MAY REAPPLY ANY REMOVED FIX. Example: If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be removed, fix3 must be removed first, then fix2 may be removed 1) Shutdown WebSphere. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix. 2) Start IBM Installation Manager. 3) On the main page of the Installation Manager, click Unistall. 4) Select the package to uninstall and follow the prompts on screen. 5) Restart WebSphere Directions to re-apply fix: 1) Shutdown WebSphere. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix. 2) Extract the .zip file to a directory. For example, extract to C:\temp. 3) Add the fix pack repository location in IBM Installation Manager: a. Start IBM Installation Manager. b. In Installation Manager, click File > Preferences > Repositories. c. Click Add Repository. d. Browse to or enter the file path to the repository.config file. The repository.config file is located in the directory where you extracted the compressed files. For example, enter C:\temp\repository.config, and then click OK. 4) On the main page of the Installation Manager, click Update. 5) Restart WebSphere. Additional Information: