Sun Java logo     Previous      Contents      Index      Next     

Sun logo
Sun Java System Calendar Server 6 2005Q1 Administration Guide 

Chapter 20
Using Instant Messaging Pop-up Reminders

Calendar Server is integrated with Sun Java System Instant Messaging 6.0 (or later) to provide automatic pop-up reminders for both calendar events and tasks.

This chapter describes:


Pop-up Reminders Overview

This section contains the following topics:

Pop-up Reminders Operation

Users can receive Instant Messenger pop-up reminders for upcoming events and tasks on their calendars. To enable these pop-up reminders, two things must happen:

With pop-ups enabled, when an impending event or task nears, the alarm set in the Event Notification System causes Calendar Server to send an email notification and Instant Messaging to display a pop-up reminder.

A Calendar Server administrator can choose to configure either email notifications or pop-up reminders or both for end users. For example, to turn email reminders off, set the following parameter in the ics.conf file:

caldb.serveralarms.binary.enable= "no"

Pop-up Reminders Architectural Flow

If configured, Instant Messaging pop-up reminders follow this architectural flow:

  1. The Instant Messaging JMS subscriber subscribes to Calendar Server events and notifications in the Event Notification Service (ENS).
  2. Calendar Server publishes an event or task notification in text/xml or text/calendar format to ENS.
  3. The Instant Messaging JMS subscriber receives the calendar event or task notification and then generates a message in text/calendar format.
  4. The Instant Messaging server sends the message to the calendar owner, if the end user is online.
  5. If the recipient is available, Instant Messenger generates an HTML pop-up reminder on the end user’s desktop based on the message.
  6. If the recipient is not available, the Instant Messaging server discards the message.


Configuring Instant Messaging Pop-ups

This section includes the following configuration instructions:

To Configure Instant Messaging Server

The high level list of tasks necessary to configure Instant Messaging for Pop-ups that follows is for your convenience. To configure Instant Messaging, refer to the Instant Messaging documentation available at the docs.sun.com website.

  1. Install the new package SUNWiimag.
  2. Edit one or more of the parameters in the iim.conf file as shown in Table 20-1
  3. The parameter values shown assume you want pop-up reminders for both events and tasks. If these parameters do not already exist in your iim.conf file, add them.

    Table 20-1  iim.conf Parameters for Configuring Pop-ups  

    Parameter

    Description and Appropriate Value to Use

                                                                       JMS Consumers Section

    jms.consumers

    Name of alarm. Set the value to cal_reminder.

    jms.consumer.cal_reminder.destination

    Destination of the alarm. Set the value to enp:///ics/customalarm

    jms.consumer.cal_reminder.provider

    The name of the provider. Set to ens. This must be the same as the name in jms.providers in the JMS Providers section.

    jms.consumer.cal_reminder.type

    The type of alarm to set. Set the value to topic.

    jms.consumer.cal_reminder.param

    The alarm parameter. Set the value to "eventtype=calendar.alarm" (including the quotes)

    jms.consumer.cal_reminder.factory

    C++ factory name. Set the value to com.iplanet.im.server.JMSCalendarMessage
    Listener

                                                                     JMS Providers Section

    jms.providers

    The name of the provider. Set value to ens. This must be the same as the value listed in the JMS Consumers Section for jms.consumer.cal_reminder.provider.

    jms.provider.ens.broker=cal.example.com

    Port number that ENS listens on. Set to the port specified in the ics.conf file parameter service.ens.port. The default is 57997.

    jms.provider.ens.factory

    C++ factory to use. Set to com.iplanet.ens.jms.EnsTopicConnFactory

  4. Enable the following Instant Messaging agents using new boolean command line options in imadmin:
  5. im_agent.enable
    iim_agent.calendar.enable

  6. Be sure the calendar component is included in the stop, start and refresh commands.
  7. For example, imadmin has new switches to stop and start components. To start, stop, or refresh the calendar component, use the following command:

    imadmin stop|start|refresh agent:calendar

To Configure Calendar Server

  1. Confirm that the ics.conf parameters shown in Table 20-2 have the values shown. If they do not, perform the following steps to make them conform.
  2. Log in as an administrator with permission to change the configuration.
  3. Change to the /etc/opt/SUNWics5/cal/config directory.
  4. Save your old ics.conf file by copying and renaming it.
  5. Edit the parameters in Table 20-2 to the values shown.

    Table 20-2  ics.conf Parameters for Configuring Pop-ups 

    Parameter

    Description and Default Value

    caldb.serveralarms

    Enables calendar alarms to be queued. The default is “yes” (enabled).

    caldb.serveralarms.contenttype

    Output format for alarm content. The default is "text/xml".

    caldb.serveralarms.dispatch

    Enables calendar alarms to be dispatched. The default is “yes”.

    caldb.serveralarms.dispatchtype

    The type of server alarm to dispatch. The default is "ens".

    caldb.serveralarms.url

    This is the URL for alarm retrieving alarm contents. The default is "enp:///ics/customalarm".

  6. Save the file as ics.conf.
  7. Restart Calendar Server.
  8. cal_svr_base/SUNWics5/cal/sbin/start-cal

To Configure Instant Messenger

To receive pop-up reminders for Calendar Server events and tasks, end users must configure their Instant Messenger as follows:

  1. On the Main window, from the Tools menu, select Settings.
  2. On the Settings window, click the Alerts tab.
  3. Check the Show Calendar Reminders option.
  4. Click OK.

 



Previous      Contents      Index      Next     


Part No: 819-0024-10.   Copyright 2005 Sun Microsystems, Inc. All rights reserved.