Message queues publish notifications about selected data events to interested subscribers.
For example, when student grades are posted, SIS could push out a notice to all subscribers. A student-facing system receiving that event could thus procede with its own grade-based functions without having to constantly ask SIS, “have the grades been posted yet?”
Event-based messaging is a valuable but complicated tool in the integration toolbox. We operate a robust messaging platform (based on Apache ActiveMQ and RedHat JBoss Fuse) to make it easier, and share our expertise to shorten your learning curve.
Publishing
Publishers can configure the event message in a number of ways to determine how and to whom it's delivered using the Common > System Event EDO found on bMeta.berkeley.edu. Payload content can be added based on the event triggered by the reference system, and a list of multiple events can be included in a single post to the queue.
To get started, contact us at eis-support@berkeley.edu and include:
- The name of the campus system triggering the event
- A description of the triggering event
- Functional and technical contacts
(this information will be used for future notifications about service changes, upgrades, and outages)
We'll follow-up with you to set-up your access to the message broker and create the namespace for your topic or queue.
Subscribing
Clients can receive messages using JMS by subscribing to specific queues and topics. Open source client libraries are available for most popular languages and environments.
To get started, contact us at eis-support@berkeley.edu and include:
- The name and description of the campus system that will listen for events
- The system and action/s that trigger the events you're interested in
- Functional and technical contacts
(this information will be used for future notifications about service changes, upgrades, and outages)
We'll set-up your access to the appropriate topic or queue and help you set-up your client.