Configuring NEOSYS to display local time

From NEOSYS Technical Support Wiki
Revision as of 11:57, 15 April 2015 by Ruku (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search

Before you setup the Timezone in NEOSYS, you should have an idea about how Time works on the NEOSYS server/client locations.

Neosys Servers are set to GMT. All historical/new Server related events e.g messages like "Database not available" have the server time. In case of Client servers, their server time depending upon the server location is displayed.

All historical/new User related events have the local time of the Client Office location i.e when a report is generated, the time displaying when the report was generated is the local Time of that place. This local time has to be configured in the system configuration file.

All times which are the result of User data entry in a document/file e.g "broadcast time of an ad" are saved exactly the same. This means if in future we change the timezone in system configuration file, these times entered will always remain the same.

User display timezone can be configured in the System Configuration File as follows:

  1. Login to NEOSYS
  2. Go to Menu > Support > System Configuration File
  3. Enter the time difference with reference to the GMT in the User Timezone section. For Example - If the client is based in Dubai then it belongs to the UAE/OMAN timezone which is 4 hours ahead of the GMT. Hence we set the user timezone section to +4 to indicate the UAE/Oman timezone as follows:
    Timezoncfg.jpg


Note -

  1. If the server administrator timezone is not set to GMT/UTC then any timezone configuration is ignored
  2. Many dates and times in NEOSYS are stored as local date or time without timezone information and are not affected by timezone configuration
  3. Generally, NEOSYS stores date+time in conjunction then it always saves them in the database server administrator timezone as the server LOCAL system administrator timezone. This means that databases are NOT fully portable to servers configured with different timezones.