| Sun ONE Calendar Server 6.0 Programmer's Manual |
Glossary
ACE (access control entry) A string that provides access control for calendars, calendar properties, and calendar components such as events and todos (tasks). An example of an ACE is jsmith^c^wd^g.
ACL (access control list) A set of access control entry (ACE) strings that collectively provide access control for calendars, calendar properties, and calendar components such as events and todos (tasks). An example of an ACL with three ACEs, with each ACE separated by a semi-colon is @@o^a^r^g;@@o^c^wdeic^g;@^a^sf^g.
alarm event An event generated and sent by the Sun™ ONE Calendar Server Event Notification Service (ENS). When an alarm event occurs, a message reminder is sent to specific recipients.
authentication The verification of a user ordinarily done using a user ID and a corresponding password. Knowledge of the password is assumed to guarantee that the user is authentic. The Calendar Server requires a directory service such as an LDAP server for user authentication.
base DN The distinguished name (DN) that identifies the starting point of a search in an LDAP directory. Also known as a search base. For example, ou=people,o=sesta.com.
Berkeley DB A transactional database intended for high-concurrency read-write workloads and for applications that require transactions and recoverability. The Calendar Server uses the Berkeley DB from Sleepycat Software Inc. for storing calendar data.
Calendar Express A Web-based calendar client program that provides access to the Calendar Server for end users.
calendar group A collection of several calendars that can help a user manage more than one calendar.
calendar ID (calid) A unique identifier associated with a calendar in the Calendar Server database. The format for a calendar ID is userid[:calendar] where userid is the user ID and calendar is the calendar name.
Calendar Lookup Database (CLD) (CLD) A mechanism (distributed as a plug-in) that determines the physical location of a calendar when the calendar database is distributed over several servers. The Database Wire Protocol (DWP) uses the CLD mechanism to fully qualify a calendar ID (calid). DWP can use the returned URL to determine the location of the calendar, along with its access protocol.
Calendar Server Application Programming Interface CSAPI A programmatic interface that provides the capability to modify or enhance the feature set of the Calendar Server. CSAPI modules are plug-ins that are loaded from the cal/bin/plugins directory when the Calendar Server is started.
Calendar Access Protocol (CAP) A standard Internet protocol for calendaring based on requirements identified by the Internet Engineering Task Force (IETF).
cal_svr_base A directory location relative to other files on a server. For example, the default Calendar Server installation on Solaris systems uses the path /opt/SUNWics5/ as the server root.
common name (cn) An attribute that identifies the person or object defined by the entry in an LDAP directory.
component state A set of attributes that describe a calendar event such as a meeting. In WCAP, the compstate parameter allows fetch commands to return events by component state. For example, compstate might be REPLY-DECLINED (attendee has declined a meeting) or REQUEST_NEEDS-ACTION (attendee has not taken action on a meeting yet).
Calendar User Agent (CUA) An application that a calendar client uses to access the Calendar Server.
default calendar The calendar a user first sees after logging into Calendar Express. Usually, the calendar ID of a default calendar is the same as the user’s user ID. For example, wchang@sesta.com would have a default calendar named wchang.
directory service A centralized repository of directory information for use by other servers. The Calendar Server requires that a calendar user be stored in a directory server such as an LDAP server. The Calendar Server then uses the directory server for user authentication and for the storage and retrieval of user preferences. See also LDAP (Lightweight Directory Access Protocol).
distinguished name (DN) A string representation that uniquely identifies a user, system, or organization. A DN identifies an entry in an LDAP directory from which searches will occur. Also known as a search base. For example, ou=people,o=sesta.com.
Database Wire Protocol (DWP) A Calendar Server proprietary protocol that allows multiple servers to be linked together within the same Calendar Server system to form a distributed calendar store. The Calendar Servers uses DWP to retrieve remote data stored in the calendar database.
event A entry with an associated date and time in a calendar. For example, an event might be a new meeting or appointment on a calendar.
Event Notification Service (ENS) A generic service that accepts reports of server-level events that can be categorized and then notifies other servers that have registered interest in certain categories of events.
Extensible Markup Language (XML) A flexible programming language developed by the World Wide Web Consortium (W3C) to create common information formats and share both the format and the data on the Web, intranets, and elsewhere. XML is extensible because, unlike HTML, the markup symbols are unlimited and self-defining. The Calendar Server uses XML and XSL to generate the Calendar Express user interface.
Extensible Style Language (XSL) A language used to create style sheets for XML. XSL describes how data sent over the Web using the XML is to be presented to the user. The Calendar Server uses XSL and XML to generate the Calendar Express user interface.
Group ID (GID) On UNIX systems, the group for Calendar Server files such as counters and logs. The GID is stored in the ics.conf file in the local.servergid parameter.
GMT (Greenwich Mean Time) The mean solar time of the meridian of Greenwich, England, and the time standard against which all other time zones in the world are referred. GMT is not affected by Daylight Savings Time or Summer Time.
Group Scheduling Engine (GSE) The Calendar Server process that handles group scheduling. The GSE enables a user to schedule events with other calendar users on the same server or on a different server. The other user can then modify, cancel, or reply to the event.
High Availability (HA) A configuration that enables two Solaris servers to run a single instance of Calendar Server that remains continuously available after any single point of failure in hardware (disk, server, or network) or software has occurred in either of the servers.
horizontal scalability The Calendar Server’s capability to run on a single server or as a group of processes that are spread across multiple server with a wide variety of possible configuration options.
Hypertext Transfer Protocol (HTTP) A standard protocol that allows the transfer of hypertext documents over the Web. The Calendar Server uses HTTP as its primary transport.
instance A Calendar Server configuration of one or more server processes. Multiple Calendar Server instances can be configured per server.
ISO 8601 An ISO (International Organization for Standardization) standard that specifies the numeric representation of date and time. The Calendar Server uses ISO 8601 standard notations to represent date, time, and duration strings.
LDAP (Lightweight Directory Access Protocol) A directory service protocol defined by the Internet Engineering Task Force (IETF) used for the storage, retrieval, and distribution of information, including user profiles, distribution lists, and configuration data.
LDAP server A software server that maintains an LDAP directory and services queries to the directory. The Calendar Server uses the Sun ONE Directory Server, which is an implementation of an LDAP server.
notification A message describing an event occurrence. An example of a notification in Calendar Server is a reminder for an upcoming meeting.
notification service A service that receives subscriptions and notifications from other servers and then relays notifications to specific subscribers. The Calendar Server csnotifyd service sends notifications of events and todos (tasks) using the Event Notification Service (ENS) as the broker for the events.
permissions The settings that control the access to a calendar. For example, in Calendar Express, permissions include Availability, Invite, Read, Delete, and Modify. Calendar Server administrators set permissions as access control entry (ACE) strings using command-line utilities. See also ACE (access control entry) and ACL (access control list).
plug-in An accessory program that can be loaded and then used as part of the overall system. For example, the Calendar Server can use a plug-in to access a non-LDAP directory service.
resource calendar A calendar associated with a resource such as a meeting room or equipment such as a notebook computer or overhead projector.
RFC (Request For Comments) A series of numbered international documents (such as RFC 2445, RFC 2446, and RFC 2447) that set standards that are voluntarily followed by Internet software developers. RFC standards are written informally by experts based on their technical experience and not by formal committees.
server root A directory location relative to other files on a server. For example, the default Calendar Server installation on Solaris systems uses the /opt/SUNWics5/path as the server root. In syntax and examples, cal_svr_base is used to represent the server root for Calendar Server.
service A component of an overall system. The Calendar Server has the following services: Administration Service (csadmind). HTTP Service (cshttpd), Notification Service (csnotifyd), Event Notification Service (enpd), and Distributed Database Service (csdwpd).
SHTML (Server-side Include Hypertext Markup Language) An HTML file that includes embedded server-side includes (SSIs).
Single Sign-on (SSO) An authentication mechanism that enables a user to log in once and then access multiple applications. These applications form a circle of trust that use each other’s cookies as verification of authority so that the user does not have to login to each application separately.
task In Calendar Express on the client side, a component of a calendar that specifies something to be done. On the server side, a task is called a todo.
time zone A geographical region that uses the same time. There are 25 hourly time zones from -12 through +12 (GMT is 0). Each time zone is measured relative to GMT. Most time zones have localized designations in three-letter abbreviations. The Calendar Server also identifies time zones using a time zone ID (TZID) such as America/Los_Angeles or Asia/Calcutta.
todo On the server side, a a component of a calendar that specifies something to be done. In Calendar Express on the client side, a todo is called a task.
user ID (uid) A unique string identifying a user to a system. The Calendar Server identifies each user by a user ID.
Universal Principle Name (UPN)
The value for a logged-in user that includes the login name combined with the domain to which the user belongs. For example, user bill in domain sesta.com has the UPN bill@sesta.com.
WCAP (Web Calendar Access Protocol) A high-level, command-based protocol used by clients to communicate with the Calendar Server.
Zulu time A military designation for GMT and UTC (Coordinated Universal Time).
