Configuring iProcess Engine Time Zone
An iProcess Engine that is installed on a server operating in one time zone may be accessed by TIBCO iProcess Workspace users who are operating in different time zones. For example, a company’s office in California (Pacific Standard Time, GMT‑08:00) may want to run cases of procedures that are hosted on a server running in the company’s administrative center in Washington D.C. (Eastern Standard Time, GMT‑05:00).
This will lead to a disparity between timestamps created by the server (which will use its local time) and their subsequent interpretation by the computers hosting the TIBCO iProcess Workspaces. This disparity will affect:
|
•
|
audit trail time stamps |
|
•
|
deadline time stamps and processing |
|
•
|
priority escalation of work items |
|
•
|
date/time settings for participation and redirection. |
To avoid this disparity, you can configure the iProcess Engine processes to operate in the same time zone as the clients.
Note:
|
•
|
The time zone is set for ALL processes generated by iProcess Engine. Different processes on the same iProcess Engine cannot use different time zones, even if they are running on different servers. To continue the example above, if iProcess Engine is configured to run in Pacific Standard Time it can only administer sites in that time zone without discrepancy. |
|
•
|
If multiple iProcess Engines are running on the same physical hardware (which can be either a single node or a node cluster), each iProcess Engine can operate in its own designated time zone. |