In this release, there are two notification services for event notifications and alarms: Sun Java System Message Queue (JMQ) and the Event Notification System (ENS). In a future release, the Communications Service products will use JMQ exclusively, and ENS will be removed. However, for this release, the Communications Services products (Messaging Server, Calendar Server, and Instant Messaging) still have internal dependencies on ENS, and you can continue to use ENS for notifications and alarms.
To use JMQ, rather than ENS, you must have Sun Java System Message Queue installed and configured. In addition you must write your own notifications, as no notifications provided by Calendar Server 6.3.
Install the product using the Sun Java Enterprise System installer. For information about configuring Message Queue, see theMessage Queue Documentation.
To configure Calendar Server for JMQ, you must add the following lines to the ics.conf file:
local.server.csmfagent.enable = "yes"
caldb.serveralarms.jmqlib = "/opt/SUNWics5/cal/lib/libmqcrt.so" (for Solaris)
Or,
caldb.serveralarms.jmqlib = "/opt/sun/calendar/lib/libmqcrt.so" (for Linux)
caldb.serveralarms.dispatchtype = "jmq"
caldb.serveralarms.jmqhost = "localhost"
caldb.serveralarms.jmqport = "7676"
caldb.serveralarms.jmqUser = "guest"
caldb.serveralarms.jmqPWD = "guest"
caldb.serveralarms.jmqTopic = "JES-CS"
Each notification must have the following property: MQ_MESSAGE_TYPE_HEADER_PROPERTY . This property identifies what kind of notification it is.
In addition, notifications can have other properties as shown in the following table:
A string property that indicates the type of action this notification produces. This property can have the following values: "EMAIL", "AUDIO", "DISPLAY", "PROCEDURE", "FLASHING".
A string property containing the alarm ID.
A string property containing the calendar ID.
A string property indicating the type of component. The value is either "event" or "todo".
An integer property containing the recurrence ID.
A string property containing the component ID, that is either the event ID or the todo ID (task ID).
Notifications can be of two types: alarm notifications and update notifications for events and todos.
For alarm notifications, the value of MQ_MESSAGE_TYPE_HEADER_PROPERTY is simply "alarm".
For update notifications, the value of MQ_MESSAGE_TYPE_HEADER_PROPERTY depends on the type of action that triggered the notification. Table 2–2 lists the trigger actions and the corresponding values for this property.
Table 2–2 Update Notifications Values
Trigger |
Update Notification Value |
---|---|
Deleting a calendar |
DELETECAL |
Modifying an event |
MODIFYEVENT |
Modifying a todo (task) |
MODIFYTODO |
Creating an event |
CREATEEVENT |
Creating a todo (task) |
CREATETODO |
Refreshing an event |
REFRESHEVENT |
Refreshing a todo (task) |
REFRESHTODO |
Replying to an event |
REPLYEVENT |
Replying to a todo |
REPLYTODO |