Administering a Calendar server

Administering a Calendar server

The Calendar client, scocal, uses a client-server architecture to access data. When a user accesses the Calendar application to request or update calendar data, a request is sent to a Calendar server, which may be on the local computer or may be on a networked server computer.

The use of the client-server architecture gives you great power and flexibility in maintaining the calendar database. For example, consider the following system setup:

Four heavily used end-user computers, each with 10 users running the Calendar.
One administrative computer (for example, a print spooler or database handler) that has excess disk space and a low load average.
A local area network (LAN) tying each of these computers together with SCO TCP/IP.

Given this sample setup, you would want to place the calendar data on the administrative computer. In doing so, you see the following benefits:

All 40 users have access to each other's calendars (within the limitations of individual calendar permissions).
The system's load is concentrated on a computer that has excess capacity, allowing end-users to work more efficiently.
The calendar data is maintained in a central location, allowing for single-point backup and maintenance.