Sun Java System Calendar Server 6.3

FAQs for Sun Java System Calendar Server 6.3

Get answers to the questions most frequently asked about Sun Java System Calendar Server 6.3.

Table Of Contents
General Questions
  1. What is the Sun Java System Calendar Server 6.3?
  2. How is the Calendar Server priced?
  3. What languages are supported in Sun Java System Calendar Server 6.3?
  4. What APIs are supplied with the product?
  5. Is Microsoft Outlook supported? What versions are supported?
  6. Are tasks or to-dos supported?
  7. Can I schedule group meetings?
  8. Can someone else schedule appointments on my calendar?
  9. What type of access control is provided?
  10. Can Calendar Server be used to schedule resources such as conference rooms and A/V equipment?
  11. Can the Calendar Server 6.3 user interface be customized?
  12. What is horizontal scalability? How is it achieved with the Calendar Server 6.3?
  13. Does Calendar Server offer offline support? If a user is disconnected from the network/internet, can they access their calendar?
  14. What type of notification service does Sun Java System Calendar Server 6.3 support?
  15. Does the Calendar Server 6.3 support customization?
  16. What are the features of Sun Java System Calendar Server and how do they compare to the features of Calendar Server 5.X?
Technical Questions
  1. What Internet standards does Calendar Server 6.3 support?
  2. What is iCalendar?
  3. What are iMIP and iTIP?
  4. What is WCAP?
  5. What administrative tools are provided for the Calendar Server 6.3?
  6. Where can the Calendar Server 6.3 be deployed?
  7. On what platforms can I run the Calendar Server 6.3?
  8. What Web Browsers are supported?
  9. Is there a list of supported Calendar 6.3 clients?
  10. What security features are in Sun Java System Calendar Server 6.3?
  11. How is authentication performed?
  12. What directory servers are supported?
  13. What LDAP schemas are supported?
  14. How are users provisioned?
  15. What are the minimum system requirements to install and run the Calendar Server 6.3?
  16. Can Calendar Server 6.3 run on any Linux OS?
  17. Can you install Calendar Server 6.3 on the same machine that contains the messaging, directory and instant messaging servers?
  18. How are invitees notified of newly scheduled appointments? Can they be notified via email?
  19. What migration tools are available for migrating to the current version of Sun Java System Calendar Server?
  20. How do I run Calendar Server 6.3 with the portal server through the secure gateway? Do I need additional URL rewriting rules?
  21. What devices and/or applications does Calendar Server sync with?
  22. Does Sun Java System Communications Sync provide one-way or two-way sync?
  23. Can I run the Communications Sync over SSL?
  24. Can Blackberry Devices work with Calendar Server? What solutions are available?
  25. Can Sun Java System Calendar Server and Netscape Calendar Server coexist on the same machine? Can NCS data be migrated to Java System Calendar Server?
  26. At what levels does Calendar Server interoperate with Outlook?
  27. What are calendar event feeds?
  28. How are event feeds implemented?
  29. Does Calendar Server support HTML links within a calendar event?
 
 

General Questions


Q:
What is the Sun Java System Calendar Server 6.3?
A:
The Sun Java System Calendar Server is a high performance, Internet standards-based calendar server for service providers and large enterprises. Through a rich integrated AJAX web UI or connectors to other clients including Microsoft Outlook and Mozilla Thunderbird/Lightning, it provides personal calendaring and group scheduling to consumers at home or at work and integrates with mail and address book functionality. The user interface can be customized to include Web links, banner ads, or logos.

Back to Top


Q:
How is the Calendar Server priced?
A:
Calendar Server is available with both subscription based licensing and perpetual licensing on a per user basis, with volume discounts. It is also available as part of the Sun Java Communications Suite with annual subscription-based pricing; this Suite also includes Sun Java System Messaging Server, Sun Java System Instant Messaging, and support, as well as limited licenses for Sun Java System Access Manager, Sun Java System Directory Server, Sun Java System Web Server and Sun Java System Application Server.

Back to Top


Q:
What languages are supported in Sun Java System Calendar Server 6.3?
A:
Sun Java System Calendar Server has been localized in the standard Java Communications Suite languages: English, French, Spanish, German, Simplified Chinese, Traditional Chinese, Korean, and Japanese. Note that these are the languages that are shipped. The software has the capability of supporting nearly any language and character set.

Back to Top


Q:
What APIs are supplied with the product?
A:
Several APIs are supplied with the latest release of Calendar Server.
  • The CSAPI is the Calendar Server API. This API allows the developer to replace one of the pluggable modules with one of their own, thereby modifying or enhancing the feature set of Calendar Server.
  • The Event Notification Service API enables a developer to publish events and register applications which may have an interest in certain events or categories of events.
  • The Proxy Authentication SDK enables programmers to integrate the authentication mechanisms of separate applications into a single authentication so users don't have to authenticate twice. This is ideal for portal users since the portal will authenticate the user and allow access to the Calendar services.
  • WCAP is the Web Calendar Access Protocol. It allows programmers to retrieve calendar content data and write calendar content to the server. This permits the integration of virtually any type of client to Calendar Server in order to create or retrieve calendar event or to-do information.

Back to Top


Q:
Is Microsoft Outlook supported? What versions are supported?
A:
Yes. Outlook 2007 and Outlook 2003 are supported through the Java System Connector for Microsoft Outlook.

Back to Top


Q:
Are tasks or to-dos supported?
A:
Yes. Sun Java System Calendar Server supports tasks. Tasks can be repeating or non-repeating and public or private.

Back to Top


Q:
Can I schedule group meetings?
A:
Yes, Calendar Server fully supports group scheduling and free/busy lookup. Calendar Server also supports the notion of personal calendar groups that enable a user to layer the personal calendars of people in the group. This creates a single virtual group calendar comprised of the individual calendars of the members in the group. Alternatively, a group may create a calendar with shared ownership by everyone on the team, enabling all group members to post meetings that can be viewed by all members in the group. Finally, the Sun Convergence client supports a dynamic calendar picklist that enables users to view events from multiple calendars within a single calendar view. The user simply checks off the calendars of interest and the composite calendar is created dynamically.

Back to Top


Q:
Can someone else schedule appointments on my calendar?
A:
Yes. By default everyone has invite access on your calendar. If this is not desired, you can modify your calendar access permissions.

Back to Top


Q:
What type of access control is provided?
A:
Calendar Server access control is based on Access Control Lists and includes the following privileges: Availability, Schedule, Read, Modify and Delete. Availability and Schedule allow for availability checking and group scheduling. Read, Modify and Delete allow for other users to see the events, modify the events, or even delete the events in given user's calendar. As a result of these privileges, a calendar owner can decide whether or not to give certain users access to read the event details within a calendar or access to simply observe when free time is available.

Calendar Server supports the concept of "owners" or "delegated owners" who may be granted permissions to act on behalf of a calendar's primary owner.

Finally, Calendar Server supports the notion of public, private, and confidential events. Individual event access control enables users to create private events within an otherwise public calendar. Events can be designated public, private, or time and date only.

Back to Top


Q:
Can Calendar Server be used to schedule resources such as conference rooms and A/V equipment?
A:
Yes. Resources can be managed and scheduled using the Calendar Server. Each resource is associated with its own calendar. The calendar can be configured to enable or disable the double-book option. By default, a calendar for a resource such as a conference room will have this option disabled so that resources will not be double booked.

Back to Top


Q:
Can the Calendar Server 6.3 user interface be customized?
A:
Yes. Calendar Server currently supports two native web interfaces. The new UI, Sun Convergence is AJAX-based and can be customized globally or by domain. The older Communications Express interface is JSP-based and can be customized by modifying the JSP pages. Although the Calendar Server supports both web UIs today, new customizations should be performed on Sun Convergence, not Communications Express, as the latter UI will soon be retired.

Back to Top


Q:
What is horizontal scalability? How is it achieved with the Calendar Server 6.3?
A:
Horizontal scalability means that server components such as the daemons can now be distributed over several machines, to allow greater flexibility and scalability.

It also means multiple calendar servers can communicate with each other and the administrator can distribute calendar users over several calendar servers.

Back to Top


Q:
Does Calendar Server offer offline support? If a user is disconnected from the network/internet, can they access their calendar?
A:
Yes, depending on the client being used. If Outlook is the client, full disconnected mode is supported. Calendar users can view their existing appointments, modify their appointments, and create new appointments. When the user connects Outlook to Calendar Server, the local changes are transferred to the server.

Similarly, if a PDA is used as the client, calendar data can be manipulated and later resynched to the calendar server.

For the Sun Convergence and Communications Express user interfaces, a user must have access to the network to access their calendar since the calendar is not saved or stored on the desktop or PC.

Back to Top


Q:
What type of notification service does Sun Java System Calendar Server 6.3 support?
A:
Sun Java System Calendar Server includes a flexible notification service that includes support for Java System Message Queue and the Event Notification Service. As a result, event reminders and calendar database change alerts are dispatched via email or other means such as pager or wireless device. Enhancements to the developer APIs (both C and the Java Message Service API) enable customers to extend this notification to end users through a variety of additional delivery mechanisms such as XML, Short Message Service (SMS), or instant messaging. In the case of Instant Messaging, a calendar agent subscribes to Calendar Server events and generates an alert to the Instant Messaging Server, which manifests itself as a pop-up notification or calendar reminder on the client desktop.

Back to Top


Q:
Does the Calendar Server 6.3 support customization?
A:
Calendar Server supports extensive customization. There is a customization guide for Convergence that explains customization capabilities in detail. Note that customizations to the older Communications Express UI do not carry forward to the new Convergence UI.

Back to Top


Q:
What are the features of Sun Java System Calendar Server and how do they compare to the features of Calendar Server 5.X?
A:
Sun Java System Calendar Server provides:
  • Connectors for Microsoft Outlook and Evolution
  • Support for Sun Convergence, a rich AJAX Web Client
  • Support for Unified Communications Web Client
  • Integrated personal address book and corporate address book
  • Automatic archive backup and hot backup capabilities for database recovery
  • Full disconnected mode support via Outlook Connector
  • Attachment support for events and tasks
  • Support for Hosted Domains
  • Support for LDAP Groups and group calendars
  • Pop-up reminders for calendar events
  • SSL encryption for login, or both login and data (entire session encryption)
  • Integration with Access Manager to provide Identity-enabled single sign-on and provisioning
  • Supports event categories
  • Supports GUI administration through the Delegated Administrator Console
  • Watcher Service and Monitoring Framework support
  • Support for Java System Message Queue for event notifications
  • Supports Linux and Solaris OS (SPARC and x86 platforms)
... And all of this is in addition to the Calendar Server 5.X features, which include:
  • Web-based personal calendaring
  • Group and resource scheduling
  • Conference room scheduling
  • Free/busy search
  • Text search
  • Conflict notification
  • Single sign-on support
  • Horizontal and vertical scalability
  • Moderate access control
  • Public and private calendars, public and private events
  • Enhanced performance and scalability
  • Sun Cluster support
  • Synchronization tools
  • Global and Domain level Customization
  • Multiple calendars per user
  • Composite calendar views
  • Calendar publishing and subscription
  • Rich content in events and tasks
  • Event feeds
  • Personal customization
  • Client and server APIs
  • Command line administration
  • Standards-based
  • Supports an LDAP Calendar Lookup Database (CLD) plug-in in addition to an algorithmic CLD

Back to Top

Technical Questions


Q:
What Internet standards does Calendar Server 6.3 support?
A:
Calendar Server was designed from the ground up to support Internet Engineering Task Force (IETF) calendar standards. The relevant IETF calendar standards are:
  • iCalendar (RFC2445)
  • iTIP (RFC2446 iCalendar Transport-Independent Interoperability Protocol)
  • iMIP (RFC2447 iCalendar Message-Based Interoperability Protocol)
Calendar Server uses HTTP (RFC 2616) as its primary transport mechanism. Commands and replies can be in several data formats: iCalendar, or XML.

Back to Top


Q:
What is iCalendar?
A:
iCalendar is the standard calendar schema definition. It defines the properties and parameters associated with events, to-dos, journals, alarms, and time zones. iCalendar is defined by the IETF in RFC 2445.

Back to Top


Q:
What are iMIP and iTIP?
A:
iTIP (RFC 2446) is the Transport-independent Interoperability Protocol. This is a simple application-level protocol for performing common scheduling tasks such as publishing events or to-dos, inviting people to meetings, replying to invitations, etc.

iMIP (RFC 2447) is the iCalendar Message-based Interoperability Protocol. It is an email binding for iTIP. In other words, the iMIP standard describes how the iTIP scheduling operations can be performed over email.

Back to Top


Q:
What is WCAP?
A:
WCAP is the Web Calendar Access Protocol. It is an open application protocol that uses HTTP as its transport.

Back to Top


Q:
What administrative tools are provided for the Calendar Server 6.3?
A:
Calendar Server ships with many command-line tools to handle the configuration and management of your calendaring system. Command-line administration interfaces, a key requirement for ISPs, give administrators the flexibility to create customized scripts. The provided tool set includes utilities for adding and deleting users, adding and deleting calendars, back up and restoration of calendars, and server management and control. These tools are described in detail in the administration guide that accompanies the product. In addition, there is a graphical user interface delegated administrator tool that enables administrators to create domains, groups, users, and calendar resources.

Back to Top


Q:
Where can the Calendar Server 6.3 be deployed?
A:
Calendar Server can be deployed in virtually any network. The only requirement for it to work out-of-the-box is that you should deploy LDAP for user authentication and user preferences. If you choose not to use LDAP, you can replace the authentication model with one of your own using the CSAPI. You can also deploy the calendar server in an identity-based environment where the access manager provides authentication and provisioning.

Back to Top


Q:
On what platforms can I run the Calendar Server 6.3?
A:
Currently Calendar Server supports the following platforms:
  • Solaris 9 and 10 Operating Systems (SPARC platform) with recommended patches
  • Solaris 9 and 10 Operating Systems (x86 platform)
  • Red Hat Enterprise Linux 5 (64-bit version)
  • Red Hat Enterprise Linux 3 and 4

Back to Top


Q:
What Web Browsers are supported?
A:
Calendar Server includes two native user interfaces: Sun Convergence and Java System Communications Express. Sun Convergence is a state-of-the-art AJAX Web Client whereas Communications Express is a more traditional Web Client. Both provide unified, Web-based access to calendaring, email, and a common address book. Both provide the interface for all end-user functionality of the calendar server, including multiple calendar views, task management, and administration such as reminder options, time zones, and privacy controls. Both require a JavaScript-enabled browser. However, each user interface has its own browser requirements. It is recommended that you consult the Java Communications Suite 7 Release Notes for up-to-date information.

Back to Top


Q:
Is there a list of supported Calendar 6.3 clients?
A:
Sun Convergence is a rich AJAX Web client that provides thick client functionality from a Web browser. It combines a state-of-the-art design with an intuitive user interface that integrates e-mail, calendaring, address book, chat, and instant messaging presence. Because this client is browser based, the enterprise or service provider avoids the time and cost issues involved in installing a specific application on each client in the organization and can facilitate the application being available from almost any machine/location.

Communications Express is the older, more traditional unified communications web client that combines messaging, calendar, and address book in a unified user interface. The Communications Express UI is still supported but is no longer provided with Java Communications Suite. Support for it will eventually be retired at a later date.

Evolution is the fat client available with the Java Desktop System. The Evolution client looks very much like Outlook but it runs on Solaris OS and Linux -- not on Windows.

Outlook 2007 and Outlook 2003 are supported through the Java System Connector for Microsoft Outlook.

The Sun Java System Communications Sync product synchronizes the Calendar Server with many popular programs (such as Outlook) and devices (such as Palm and WinCE/Pocket PC devices).

Back to Top


Q:
What security features are in Sun Java System Calendar Server 6.3?
A:
Calendar Server provides a number of security features:
  • Encryption: SSL encryption for login, or both login and data. This ensures that the entire session, including the login, may be encrypted from the Web client to the server.
  • Encryption and Obfuscation: SSL encryption through a proxy gateway via the Java System Portal Server, Secure Remote Access product. URL rewriting obfuscates the true URL of Calendar Server.
  • Authentication: Secure authentication through LDAP or through the Sun Java System Access Manager. Calendar Server also supports the use of an authentication plug-in for cases where an alternate means of authentication is desired. Sun Java System Access Manager also provides a single sign-on capability.
  • Authorization and Access Control: Calendar Server provides an access control layer which grants or denies user access to calendars or calendar components. For instance, a calendar may grant permission for other users to view the availability of a user and may even grant permission for other users to schedule events in this calendar, but it may deny other users permission to view the actual events or appointments scheduled into this calendar. Access control also enables a user to select who can act on his behalf to respond to invitations, schedule or modify events, and delete events. Finally, access control can be used to span domains of users, thus preventing (or enabling) users in one domain from scheduling events with users of another domain.
  • Database protocol level security: Database Wire Protocol (DWP) authentication utilizes a name/password pair to authenticate a DWP connection when the calendar front end is separate from the database back end.
  • Password security. Calendar Server Administrator passwords are stored in a separate file and are obfuscated to prevent others from seeing the passwords accidentally.

Back to Top


Q:
How is authentication performed?
A:
The default authentication is through LDAP. It is possible to change this authentication model through the CSAPI. This allows a developer or deployer to replace LDAP authentication with some other form of authentication. The developer can write a plugin that will allow the Calendar Server to talk to something other than a directory server. Since the Calendar Server is also identity-enabled, it can take advantage of the Access Manager single sign-on mechanism.

Back to Top


Q:
What directory servers are supported?
A:
Sun Java System Directory Server Enterprise Edition 6.3 is officially tested and supported.

Back to Top


Q:
What LDAP schemas are supported?
A:
Calendar Server supports both LDAP Schema v.1 and LDAP Schema v.2.

Back to Top


Q:
How are users provisioned?
A:
Users are provisioned through LDAP; no special provisioning is needed for the Calendar Server. It uses the same users that were provisioned for the backend messaging server. Only the calendar schemas must be incorporated into the directory server, and this is performed by the installation program if Sun Java System Directory Server is used.

Back to Top


Q:
What are the minimum system requirements to install and run the Calendar Server 6.3?
A:
The minimum system requirements for a Solaris system are:
  • Solaris 9 and 10 Operating Systems (either SPARC or x86 platforms)
  • 128 MB memory (for production systems, 256MB to 1GB recommended)
  • 500 MB disk space for standard installation (for production systems, at least 1GB)
  • RAID storage for fast access (recommended for large databases)
The same memory and disk requirements apply for Red Hat Enterprise Linux as shown for Solaris OS.

Back to Top


Q:
Can Calendar Server 6.3 run on any Linux OS?
A:
No, only Red Hat supported.

Back to Top


Q:
Can you install Calendar Server 6.3 on the same machine that contains the messaging, directory and instant messaging servers?
A:
Yes, you can install Calendar Server on the same machine as your directory, messaging, or instant messaging servers. However, you may want to install Calendar Server on a separate machine for performance reasons.

Back to Top


Q:
How are invitees notified of newly scheduled appointments? Can they be notified via email?
A:
When a user is invited to an event, it will show up on the user's calendar. The user can also receive an automatic notification via email if the "Event Notifications" checkbox is checked and an email address is entered in the Calendar Options for Communications Express or Sun Convergence. In addition, if the event organizer wants to send an email notification of the event to every attendee, the organizer should add a "mailto" line (followed by an email address) in the Invitee List for each attendee he or she wishes to notify.

Back to Top


Q:
What migration tools are available for migrating to the current version of Sun Java System Calendar Server?
A:
A variety of migration tools are available, including:
  • csmigrate - Migrates Calendar Server 6.0, 6.1, and 6.2 databases to Calendar Server 6.3 version.
  • cs5migrate - Migrates Calendar Server 5.x database and LDAP schema to Calendar Server 6 and upgrades the calendar database from Berkeley DB version 2.6 to version 4.2. If the customer is currently running Calendar Server 6.0, the migration to the current Berkeley DB version is seamless and occurs during the installation. Available with Calendar Server 6.2 patch 116577-35 and later.
  • ncs4migrate - Migrates data from Netscape Calendar Server 4.x. Only available through technical support. This tool migrates data to Calendar Server 5.x. You must then migrate from CS 5.0 to CS 6 2005Q1 using other tools already mentioned.
  • csmig - Assigns an owner to each calendar in the Calendar Server 6.x database and maps each calendar ID to an owner. This is needed for hosted domains and LDAP CLD.
  • csvdmig - Upgrades Calendar Server 6.x site to use hosted domains by adding the calendar's domain (@domainname) to each calid. Run this utility after cs5migrate and csmig.
  • commdirmig - Migrates LDAP data from schema 1 to schema 2 in preparation for use with Access Manager 6.1 or higher. This utility is packaged with Access Manager.
Sun also provides a migration service to ensure a successful migration from Exchange to the Java System Calendar Server. Please contact your Sun Professional Services representative for more information.

Back to Top


Q:
How do I run Calendar Server 6.3 with the portal server through the secure gateway? Do I need additional URL rewriting rules?
A:
It is possible to use the Sun Java System Portal Server and its associated gateway to provide a secure SSL connection to Calendar Server. The gateway will rewrite all the calendar server URLs so that all access to the calendar server must be performed through the gateway.

Back to Top


Q:
What devices and/or applications does Calendar Server sync with?
A:
Calendar Server syncs with Microsoft Outlook for Calendar, Palm handheld devices, Palm Desktop, and Windows CE handheld devices (including Windows Mobile 5.0 devices). The synchronization software is included with the Java Communications Suite for no additional charge to customers.

Please consult the release notes for a complete list of devices.

Back to Top


Q:
Does Sun Java System Communications Sync provide one-way or two-way sync?
A:
Sun Java System Communications Sync supports bidirectional sync to or from the Sun ONE Calendar Server 5.X or Calendar Server 6.X. This sync allows the customer to synchronize CS to popular desktop applications and PDAs. The software does not allow the customer to sync between two non-Sun sources, such as syncing between Microsoft Outlook and a Palm device.

Back to Top


Q:
Can I run the Communications Sync over SSL?
A:
Yes.

Back to Top


Q:
Can Blackberry Devices work with Calendar Server? What solutions are available?
A:
Yes. Blackberry Devices work with Calendar Server through a third-party product called NotifyLink from the company Notify Technology. Their solution provides access to your calendar through the calendar application on the Blackberry Device. It also provides notifications whenever your calendar is updated. This same solution also enables you to sync your mail and contacts with mail and contacts on the Sun Java Communications Suite servers.

Back to Top


Q:
Can Sun Java System Calendar Server and Netscape Calendar Server coexist on the same machine? Can NCS data be migrated to Java System Calendar Server?
A:
Yes, both calendar servers can coexist on the same machine. Sun Java System Calendar Server provides migration tools to migrate NCS 4.0 data to Sun Java System Calendar Server.

Back to Top


Q:
At what levels does Calendar Server interoperate with Outlook?
A:
MAPI level Outlook interoperability is available in Sun Java System Calendar Server; you can use the Outlook client to access calendar information.

Currently, we integrate with Outlook through the following capabilities:
  1. MAPI level interoperability. This is the preferred level of interoperability. This level includes free/busy integration with Outlook where Outlook users can schedule events with users on Calendar Server and view the availability information for those users. Outlook interoperability provides full fidelity offline support. In the current version, you can view the events and can also modify them and expect the server to reflect the changes when you reconnect. This level of interoperability is not limited to calendar information. Outlook can also be used for mail and contacts if the Java Communications Suite is deployed as the backend server for email, calendar, and contacts.
  2. iTIP/iMIP e-mail integration where Calendar Server can send events to Outlook users as e-mail attachments that can be dragged and dropped into Outlook. Outlook users can send events to Calendar Server users as e-mail attachments that can be imported into Calendar Server.
  3. Outlook Synchronization with Calendar Server. The Sun Java System Communications Sync software enables bi-directional sync with Calendar Server and Outlook. The sync tool does not map the Outlook attendees field to the Calendar Server attendees field because Outlook users are not represented the same way as Calendar Server users are represented. For instance, Calendar Server users are represented by their calids, whereas Outlook users may be represented by first name, last name or some other identification. The user should map the Outlook attendees to the Calendar Server Description field so as not to lose the data.
  4. Use the Outlook control panel to start Sun Java System Calendar Server. This form of integration is lightweight and simply allows Calender Server to start up when the user clicks on the Outlook calendar icon.

Back to Top


Q:
What are calendar event feeds?
A:
Calendar event feeds are collections of time-based events presented in a calendar format. They can be searched, browsed, and incorporated into user calendars by a user if they subscribe to the event calendar. Service providers and enterprises can create their own customized calendar event feeds that meet the needs and requirements of their calendar users. As well, Web site and e-commerce links can easily be integrated with the content calendar.

Back to Top


Q:
How are event feeds implemented?
A:
The content must be in either the iCalendar format or the XMLized version of iCalendar. Customers may create their own event feeds or convert existing content feeds into iCalendar or XML/iCalendar formats.

Back to Top


Q:
Does Calendar Server support HTML links within a calendar event?
A:
Yes, Calendar Server does support HTML links within the event. This allows event information to contain GIF images and links that point to other Web pages. However, not all calender user interfaces currently support this feature. For instance, Communications Express supports it, but Sun Convergence does not.

Back to Top