This chapter describes the features and improvements in Oracle User Messaging Service (UMS). The following topics introduce the new and changed features of Oracle User Messaging Service and other significant changes in this guide, and provides pointers to additional information.
Oracle User Messaging Service 12c (12.1.2) includes the following new and changed features for this document:
Rebundling of User Messaging services (UMS): User Messaging Services (UMS) is now available as a part of JRF instead of SOA suite. This enables easier upper stack integration. For more information about the architecture and packaging of UMS, see Section 1.1, "Introduction to User Messaging Service".
Introduction of Twitter Driver: In addition to the other drivers that were supported in 11g, UMS now supports Twitter driver. Twitter driver provides a bi-directional messaging service, thus enabling the application users to publish their Twitter feed and receive response for the same. For more information about Twitter driver, see Section 2.3.1.9, "Configuring the Twitter Driver".
Support for Group Messaging: In addition to supporting bi-directional mutli-channel messaging through a variety of channels, UMS now supports group messaging. For more information about group messaging support, see Section 2.5, "Using Oracle User Messaging Service for Group Messaging".
Support for Domain and Cluster Level Configuration: In 11g, UMS server and most types of drivers supported configuration only at the application level. In 12c, the configuration is defined at the domain level with the possibility of overriding this configuration at the cluster level. For more information about domain and cluster level configuration, see Section 2.2, "Configuring User Messaging Server".
Support for Automatic Retry Feature: This feature automates resending of messages in case of delivery failure. For more information about this feature, see Section 2.6, "Configuring Automatic Message Resend".
Enhanced User Communication Preference (UCP) Services: User Communication Preferences (UCP) is no longer packaged with User Messaging Service. Multiple applications may consume a single instance of UCP services. To meet various requirements of different applications, UCP features are virtualized into profiles. This enable each application to target to a specific profile that encapsulates a subset of UCP features. For more information, see chapter "User Communication Preferences" in Developing Applications with Oracle User Messaging Service.
XA Transaction Support for Outbound and Inbound Messages: UMS provides support for XA enabled transactions (distributed transactions) for outbound and inbound messages. The XA support enables UMS to send messages from within a transaction boundary only when the transaction is committed. If the transaction is rolled back, then the sending of the message fails. For more information about this feature, see the section "Using UMS Client API for XA Transactions" in Developing Applications with Oracle User Messaging Service.
For Release 12c (12.1.2), this guide has been updated in several ways:
This document was delivered through Oracle Fusion Middleware Administrator's Guide for Oracle SOA Suite and Oracle Business Process Management Suite in 11g. It is now delivered as a standalone document titled, Oracle Fusion Middleware Administering Oracle User Messaging Service.