Using the Java Message Service (JMS) interface, you can develop event consumers that receive event notifications asynchronously from JMS queues or topics.
An event consumer can be implemented as a standard Java class or as a Message-Driven Bean (MDB).
By using the JMS interface, you can implement your event consumer using standard Java tools and programming models, and you can avoid the performance disadvantages of directly querying the event data store. Instead of interacting with the Common Event Infrastructure directly, your event consumer subscribes to JMS destinations (queues and topics) and receives event notifications in the form of JMS messages.
The Common Event Infrastructure organizes events in event groups, which are logical collections of events defined in the Common Event Infrastructure configuration. A particular event consumer typically needs to receive only events from specific event groups.
The configuration profile for each event group associates that event group with one or more JMS destinations through which notifications related to that event group are distributed. The relationships between event groups and JMS destinations are as follows:
In addition to the standard JMS interfaces, a JMS event consumer interacts with a facility called the Notification Helper. The Notification Helper translates between Common Event InfrastructureCommon Event Infrastructure entities (events and event groups) and equivalent JMS entities (messages and destinations). The Notification Helper provides the following functions:
permission java.util.PropertyPermission "*", "read"; permission java.io.FilePermission "${was.install.root}${/}java${/}jre${/}lib${/}jxpath.properties", "read";
Last updated: Thu Apr 27 15:02:41 2006
(c) Copyright IBM Corporation 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)