Database Reference
In-Depth Information
Administering
User
Messaging
Service
Oracle
User Messaging Service (UMS)
enables two-way communication
between actors in processes such as human users, automatic activities, and de-
ployed applications. UMS has support for a variety of messaging channels, such
as e-mail, IM, SMS, and text-to-voice messages. Any process components, such
as BPEL/BPMN, Human Workflow, or BAM can leverage UMS to send notifica-
tions and alerts to user mailboxes. The Oracle SOA Suite 11g UMS infrastructure
provides a range of features such as:
•
Support for multiple messaging channels such as e-mail,
instant messaging
(IM)
,
Extensible Messaging and Presence Protocol (XMPP)
,
short mes-
sage service (SMS)
, and voice. Actionable e-mail messages can also be de-
livered to a process user's inbox.
•
Two-way messaging allows sending messages from applications to users (re-
ferred to as outbound messaging) who can then initiate messaging interac-
tions (inbound messaging).
•
User messaging preferences provide process users with a web interface to
define preferences for how and when they can receive messaging notifica-
tions allowing applications to become immediately more flexible. Rather than
deciding whether to send to a user's e-mail address or IM client, the applica-
tion can simply send the message to the user, and let UMS route the message
according to the user's preferences.
Describing UMS architecture and components
UMS in Oracle SOA Suite 11g is made up of a layer of clients, servers, and
drivers.
The following diagram shows a typical architecture of UMS. The UMS server con-
sists of EJB interfaces, standard web services, and a stateless session bean to
provide business logic to client applications. The UMS architecture heavily re-
lies on JMS queues used to buffer content between clients, servers, and drivers.
