|
AggreGate is a distributed system. In a large AggreGate installation, different components may be deployed in several countries or even on several continents. Thus, LinkServer, users, Device Servers 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 timezones:
| 4. | By default, the time zone for new users is the same as the Server time zone. |
| 5. | By default, the time zone for new Device Servers is the same as the Server's time zone, unless a different time zone has been specified for the user owning the Device Server. |
| 6. | The time zone for new Devices is the same as the time zone for the Device Server they're connected to. This makes sense, because they're connected via a "short" link (a serial cable or a local wireless link, etc). You can't change this time zone manually - it is wholly dependant on the time zone set for the Device Server connected to the Device. |
| 7. | When the Device synchronizes clocks with the Server, time is converted from Server's time zone to the Device Server's time zone. |
| 8. | When events are loaded from the Device and stored in the event history, the event's internal time is converted from the Device Server's time zone to the Server time zone. |
| 9. | Internally, LinkServer stores all date/time values in UTC. |
| 11. | The Time zone defined in the operating system running LinkServer is used only once: to set a default time zone for the LinkServer. Once that's done, only the time zone defined in the server settings is used. |
| 12. | The Time zone defined in the operating system running AggreGate Client or from which the user logs in to the Web Admin is never used. |
|