|
AggreGate is a distributed system. In a large AggreGate installation, different components may be deployed in several countries or even on several continents. Thus, AggreGate Server, users, and Devices may be located in different time zones. You have to configure time zones properly when setting up the system. Once you do that, times will be automatically converted during system operation.
Here is a list of principles used by AggreGate when operating in multiple time zones:
| 4. | By default, the time zone for new users is undefined. |
| 5. | By default, the time zone for new Devices is undefined. |
| 6. | When the Device synchronizes its internal clocks with the Server, time is converted from Server's time zone to the Device's time zone. If Device's time zone is undefined, it's assumed to be located in owning user's time zone. If owning user's time zone is undefined too, no time conversion occurs. |
| 7. | When events are loaded from the Device and stored in the event history, the event's internal time is converted from the Device's time zone to the Server time zone. If Device's time zone is undefined, it's assumed to be located in owning user's time zone. If owning user's time zone is undefined too, no time conversion occurs. |
| 8. | Internally, AggreGate Server stores all date/time values in UTC. |
| 9. | When timestamps are shown to the user in AggreGate Client or Web Desktop, the local time in the User's time zone is used. If user's time zone is undefined all timestamps in Web Desktop are shown using Server Time Zone; all timestamps in AggreGate Client are shown using default time zone of the PC running AggreGate Client. |
| 10. | The Time zone defined in the operating system running AggreGate Server is used only once: to set a default time zone for the AggreGate Server. Once that's done, only the time zone defined in the server settings is used. |
|