Complete Contents |
Chapter 1 Installation and Deployment
Chapter 2 Configuring Calendar Server
Chapter 3 Admininistering Calendar Server
Chapter 4 Monitoring the Calendar Server
Appendix A Commnand Line Utilities
Appendix B Monitoring Tools
Appendix C Time Zones
Appendix D Calendar Server LDAP Schema
Appendix C Time Zones The file data/timezones _libnls.ics shown (see Calendar Server Time Zones Table) contains the representation of the time zones supported by Calendar Server. This file is located in the server-root/cal/bin/data directory (for example, opt/SUNWicsrv/cal/bin/data). The 91 time zones that this file contains are based off the time zone list defined in libnls3.0.At startup, the Calendar Server reads the file timezones _libnls, then generates 91 in-memory time zones and stores them in an array (cal_array). Therefore, all the time zones are kept in memory while the server is running. If a WCAP command includes a time zone ID (tzid), it should reference a time zone in the cal_array. For more information on WCAP, refer to the iPlanet Calendar Server Programmer's Guide. For example, if a command such as storeevents or fetchcomponents_by_range specifies a tzid parameter, the parameter value must be a tzid that is defined in the list of 91 time zones. The server will return data in that time zone and all data will have dates applied to that time zone. If the command specifies an unrecognized tzid, the server will return a GMT time zone by default. All data returned on that command will have its dates applied in GMT. For example, suppose the following WCAP command is sent to the server: fetchcomponents_by_range.wcap?id=12345&calid=JSmithcal&dtstart=0&dtend=0&tzid=America/New_York&brief=1
The above command asks the server to return all data in the CALID JSmithcal with all dates returned in the time zone defined in America/New_York. Since this time zone is recognized by the server, the data will be returned successfully as follows:HTTP/1.1 200
|Time Zone Administration|
This section diatribes how to:
To modify the Calendar Server time zone list, an administrator must edit the file timezones_libnls.ics located in the server-root/cal/db/data directory. This file contains the Calendar Server format of 91 time zones. (See iCalendar Specification for more details about VTIMEZONE format).
Timezones are identified by the property TZID. For example, Calendar Server recognizes the Pacific Standard Time Zone (PST/PDT) as the TZID "America/Los_Angeles". The following time zone defines the "America/Los_Angeles" time zone.
The "RRULE" property defines the pattern of the STANDARD and DAYLIGHT rules. The "TZOFFSETFROM" and "TZOFFSETTO" properties define the offset from GMT before and after the DAYLIGHT to STANDARD or STANDARD to DAYLIGHT change occurs.
The "TZNAME" property is an abbreviated representation of the time zone. (The iCalendar Specification provides additional information about the representation of VTIMEZONE.)
Adding a New Time zone
The X-NSCP-TZCROSS property contains a large list of dates that indicate when the time zone crosses over from DAYLIGHT to STANDARD and STANDARD to DAYLIGHTT:
To modify an existing time zone:
The Calendar Server time zone table is defined in a plain text file called timezones _libnls.ics located in the server-root/cal/bin/data directory (for example, /opt/SUNWicsrv/cal/bin/data). It includes 91 time zones based on JDK1.1. The following example shows the first few sections of the time zone table. BEGIN:VCALENDAR