Copyright © Cloud Software Group, Inc. All Rights Reserved
Copyright © Cloud Software Group, Inc. All Rights Reserved


Chapter 1 Controlling the iProcess Engine : Configuring iProcess Engine Time Zone

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 centre in Washington D.C. (Eastern Standard Time, GMT‑05:00).
This will lead to a disparity between time stamps 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:
To avoid this disparity, you can configure the iProcess Engine processes to operate in the same time zone as the clients. Note that:
Setting the Time Zone
The time zone used by iProcess Engine is stored using the TIMEZONE process attribute. Its value must be a valid time zone recognized by the operating system. See TIMEZONE on page 172.
By default, the TIMEZONE attribute is not set, and iProcess Engine uses the host server’s local time.
You can set the value of TIMEZONE using the SWDIR\util\swadm utility. If you want to:
Using the SWDIR\util\swadm utility to change the time zone triggers an event informing the server processes that the time zone has changed. iProcess Engine does not need to be restarted for the change to take effect.

Copyright © Cloud Software Group, Inc. All Rights Reserved
Copyright © Cloud Software Group, Inc. All Rights Reserved