Inside Apple's iCal Server

1 2 3 4 5 6 7 Page 3
Page 3 of 7

With directory services configured, you can begin setting up iCal Server. As with all services in Leopard Server, you will need to enable the iCal service in Server Admin. (Enabling services is done by selecting the server, selecting the Settings button from the contextual tool bar, selecting the Services tab and selecting the services you want to configure and run.)

You should also ensure that all users and groups who will use the server for calendars have access to the iCal service. This is done with the Access tab in the server's settings -- right next to the Services tab mentioned above. This is a particular concern if you move from standard or workgroup mode to advanced mode for your server, as Server Preferences will configure access to services and you will need to adjust those settings or all new users you create may be excluded.

Once the iCal service is enabled, select it in the Servers list; if need be, expand the selected server using the disclosure triangle. Then select the Settings button. As you can see in Figure 2, this gives you a series of options for iCal Server. The first option is the location of the calendar data store. This store contains a Documents directory that in turn contains two directories: calendars, which stores actual calendar data, and principals, which contains information about users for whom calendar services are configured.


Figure 2 -- iCal Server settings (Click for larger view.)

By default, the calendar store is located in the /Library directory of the server's start-up drive. If you are using a RAID array or SAN application, such as Apple's Xserve RAID or Xsan, or other higher-performance storage application, you will likely want to relocate the calendar store for performance and redundancy. As with most data, it is considered a best practice to store calendar data on a nonstart-up drive to reduce the risk of loss in the event of an unexpected failure.

As in Server Preferences, you can limit the space used by calendars and calendar items (in this case referred to as attachment size and user quota). You can also specify an authentication method. As CalDAV is based on WebDAV, you have a choice of Kerberos or Digest. You can choose to allow one or the other, or both (both is referred to as "any"). Digest is more widely supported and doesn't require CalDAV clients to be Kerberized, potentially offering a wider option for non-Leopard clients. Kerberos, however, offers single sign-on (users authenticate once for all Kerberized services) and is significantly more secure because user passwords are never transmitted over the network. If you select "any," Kerberos will be preferred.

1 2 3 4 5 6 7 Page 3
Page 3 of 7
7 inconvenient truths about the hybrid work trend
Shop Tech Products at Amazon