Sun Java logo     Previous      Contents      Index      Next     

Sun logo
Sun Java System Calendar Server 6 2004Q2 Deployment Planning Guide 

Chapter 1
Understanding Calendar Server

This chapter provides an overview of Sun Java™ System Calendar Server 6 2004Q2, the business reasoning behind deploying Calendar Server, and the deployment process itself.

This chapter contains the following sections:

Calendar Server Overview

Sun Java System Calendar Server 6 2004Q2 (formerly Sun™ ONE Calendar Server) is a high- performance, Internet standards-based calendar server designed with the scalability to meet the needs of customers ranging from medium-and large-sized enterprises to even the largest Internet, telecommunication, and enterprise service provider. Through a native Web browser interface or connectors to other calendar clients, including Microsoft Outlook, Calendar Server provides group scheduling and personal calendaring to consumers at home or at work, while enabling them to share calendar information with others over the Internet. The user interface (UI) can be customized to include Web links for e-commerce, banner ads, logo, or brand of the calendar server customer, and more.

Calendar Server provides one of the industry’s most open, interoperable, and high-performance time and resource management solutions. Through its scalability, performance, and reliability, it provides the features you require at a lower total cost of ownership than alternative solutions. Native support for iCalendar standards enables users to schedule events in a format that is easily shared across the Internet. The Java System Calendar Server employs standards and protocols such as:

The Calendar Server architecture is flexible, extensible, and scalable both vertically (by increasing the number of CPUs per system) and horizontally (by introducing additional servers into the network). As a result, Calendar Server can be thought of as a system of servers that can be configured to fit a variety of needs. It can remain in isolation as a standalone calendar server, or it can be configured with many instances, having the various services duplicated or split between them.

Calendar Server makes use of plugins to obtain external services. It also supports both LDAP-and identity-based deployments, and integrates with the Sun Java™ System Identity Server (formerly Sun™ ONE Identity Server), Sun Java™ System Portal Server (formerly Sun™ ONE Portal Server), and Sun Java™ System Instant Messaging (formerly Sun™ ONE Instant Messaging) to provide additional functionality.

Calendar Server provides the following benefits:

For more information on Calendar Server concepts, see the Sun Java System Calendar Server Administration Guide:

How Calendar Server Satisfies Business Needs

Calendar Server provides one of the industry’s most open, interoperable, and high-performance time and resource management solutions. Calendar Server provides the features you need at a lower total cost of ownership than alternative solutions. Through its flexible and extensible architecture, Calendar Server scales both vertically (by increasing the number of CPUs per system) and horizontally (by adding more servers to the network).

The following table summarizes the benefits to the enterprise provided by Calendar Server.

Table 1-1  How Calendar Server Benefit the Enterprise  

Key Feature

Benefit to the Enterprise

High performance and scalability

Enables efficient communications and improves quality of service for both enterprises and ISPs.

Extensive security features

Protects the integrity of communications and data and the privacy of employees, customers and partners, and enables compliance with industry regulations.

Scalable, robust and extensible components

Enables deployment of unified communication services, bringing together telephone services with email notification, faxing, paging, and other technologies.

Extensible collaboration platform for scheduling events, managing tasks and resources

Calendar Server improves time and resource management, and enhances user productivity.

Group scheduling for meetings and events

Calendar Server improves team collaboration and communication across the enterprise.

Information sharing through hyperlinks in events or tasks

Calendar Server facilitates collaboration through exchange of information relevant to tasks or events.

Open, modular, and standards-based architecture

Enables customers to deploy customized and personalized solutions.

Making the Calendar Server Deployment Highly Available

Calendar Server provides high-availability options that supports the Sun™ Cluster services. With this option, a secondary Calendar Server host provides services to users if the primary system is taken offline for maintenance or is down due to a problem.

Additionally, you can deploy Calendar Server in a highly available configuration through use of redundant components. This kind of deployment gives services a high level of uptime. A highly available deployment of this sort requires the redundancy of every component in the service architecture. These components include a duplicate data store server, duplicate network interface cards, and duplicate system storage.


This guide does not discuss the details of using Sun Cluster in highly available deployments for Calendar Server. See the Sun Cluster and Calendar Server documentation for more information on this topic.

Using Portal Server with Calendar Server

You can install Calendar Server with Portal Server to provide access to a calendar portlet in a portal page. This portlet provides a calendar schedules and address book information. The integration of Portal Server includes single sign-on capabilities between Portal Server and Calendar Express web client (as well as other Messenger Express and Communications Express clients).

The following two components of Portal Server provide additional functionality to a basic Calendar Server deployment:

Understanding the Deployment Process

The Calendar Server deployment process consists of the following general phases:

The deployment phases are not rigid: the deployment process is iterative in nature. Nevertheless, the following subsections discuss each of the deployment phases independently.

Designing the Deployment and Architecture

In general, during the deployment design phase, you construct a deployment architecture based on the deployment scenario specified in the requirements analysis phase. The objective is to map the logical building blocks (the logical architecture) to a physical environment (a physical topology) in a way that meets the system requirements specified in the deployment scenario.

One aspect of this design is sizing the physical environment to meet load, availability, and performance requirements. The deployment architecture takes into account details of the physical topology, such as the capabilities of different computing nodes and network bandwidth, in assigning system servers and application components to the computing nodes in the environment.

Objectives of Your Deployment

Before you begin your deployment planning, a good question to ask is:

Several reasons to consider are:

Calendar Server Deployment Team

Deploying Calendar Server usually involves a number of people, each with different roles and responsibilities. In a small organization, one person might perform several roles. Some of the roles to consider are:

Support Specialists support both the trial and production deployments.

Calendar Server End Users

End users can connect to Calendar Server by using the Calendar Express Web client, Communications Express web client, or Sun Java™ System Connector for Microsoft Outlook.

Questions about end users at your site include:

Expected End User Performance

What are your specific performance requirements for your end users? For example:

What configuration do you plan to use for your deployment? Calendar Server configuration scenarios include:

If you plan to configure multiple front-end servers, how do you plan to distribute your end users?

If you plan to configure multiple back-end database servers, how do you plan to distribute your database? For example, geographically.

What plans to you have for growth? For both front-end and back-end servers?

Development and Customization

The logical architecture specified in the requirements analysis stage of the life cycle determines the scope of the development work needed to implement a solution.

Additional work might be necessary, either in extending services through the use of APIs, or in customizing look and feel, for example, introducing a corporate branding.

For some solutions, development and customization might be quite extensive, requiring you to develop new business and presentation services. In other cases, it might be sufficient to customize existing graphical user interfaces, such as the Portal Server desktop, to achieve the functionality required.

For more information on using product APIs and customizing product functionality, see the appropriate component product documentation, including:

Prototyping and Testing

In the prototyping phase, you prototype your deployment design by implementing the deployment architecture in a test environment. You use new application logic and server customizations from the development effort, as described above (see Development and Customization), to perform proof-of-concept deployment testing. This phase involves installing, configuring, and starting up distributed applications and any required infrastructure services in your test environment.

If prototype testing reveals shortcomings in your deployment architecture, you modify the architecture, prototype again, and test again. This iterative process should eventually result in a deployment architecture that is ready for deployment in a production environment.

Your trial deployment should include a rollback plan, in case the deployment fails or runs into serious problems. As part of this plan, consider:

Rolling Out the Production System

In the production rollout phase, you implement your deployment architecture in a production environment. This phase involves installing, configuring, and starting up distributed applications and any required infrastructure services in a production environment. You normally start with a limited deployment and move to organization-wide implementation. In this process, you perform trial runs, in which you apply increasing loads and stress test the system.

As part of the rollout phase you might need to perform administrative tasks such as provisioning users, implementing single sign-on, and tuning the system to meet performance objectives. Verifying the deployment and performing capacity planning are also part of this phase. Capacity planning, of which monitoring the system plays an important role, is necessary for meeting the long-term needs of system growth.

Previous      Contents      Index      Next     

Copyright 2004 Sun Microsystems, Inc. All rights reserved.