Troubleshooting Diameter Configurations Oracle Fusion Middleware Online Documentation Library

11-2 Oracle Fusion Middleware Administrator’s Guide for Oracle SOA Suite – Integration with Oracle BPEL—Oracle JDeveloper includes pre-built BPEL activities that enable messaging operations. Developers can add messaging capability to a SOA composite application by dragging and dropping the desired activity into any workflow. – Integration with Oracle Human Workflow—UMS enables the Human Workflow engine to send actionable messages to and receive replies from users over email. – Integration with Oracle BAM—Oracle BAM uses UMS to send email alerts in response to monitoring events. – Integration with Oracle WebCenter—UMS APIs are available to developers building applications for Oracle WebCenter Spaces. The API is a realization of Parlay X Web Services for Multimedia Messaging, version 2.1, a standard web service interface for rich messaging.

11.1.1 Components

There are three types of components that make up Oracle User Messaging Service. These components are standard Java EE applications, making it easy to deploy and manage them using the standard tools provided with Oracle WebLogic Server. ■ UMS Server: The UMS Server orchestrates message flows between applications and users. The server routes outbound messages from a client application to the appropriate driver, and routes inbound messages to the correct client application. The server also maintains a repository of previously sent messages in a persistent store, and correlates delivery status information with previously sent messages. ■ UMS Drivers: UMS Drivers connect UMS to the messaging gateways, adapting content to the various protocols supported by UMS. Drivers can be deployed or undeployed independently of one another depending on what messaging channels are available in a given installation. ■ UMS Client applications: UMS client applications implement the business logic of sending and receiving messages. A UMS client application might be a SOA application that sends messages as one step of a BPEL workflow, or a WebCenter Spaces application that can send messages from a web interface. In addition to the components that make up UMS itself, the other key entities in a messaging environment are the external gateways required for each messaging channel. These gateways are not a part of UMS or Oracle WebLogic Server. Since UMS Drivers support widely-adopted messaging protocols, UMS can be integrated with existing infrastructures such as a corporate email servers or XMPP Jabber servers. Alternatively, UMS can connect to outside providers of SMS or text-to-speech services that support SMPP or VoiceXML, respectively.

11.1.2 Architecture

The system architecture of Oracle User Messaging Service is shown in Figure 11–1 . For maximum flexibility, the components of UMS are separate Java EE applications. This allows them to be deployed and managed independently of one another. For example, a particular driver can be stopped and reconfigured without affecting message delivery on all other channels. Exchanges between UMS client applications and the UMS Server occur as SOAPHTTP web service requests for web service clients, or through Remote EJB and JMS calls for BPEL messaging activities. Exchanges between the UMS Server and UMS Drivers occur through JMS queues. Configuring Oracle User Messaging Service 11-3 Oracle UMS server and drivers are installed alongside SOA or BAM in their respective WebLogic Server instances. A WebCenter installation will include the necessary libraries to act as a UMS client application, invoking a server deployed in a SOA instance. Figure 11–1 UMS architecture

11.2 Introduction to Oracle User Messaging Service Configuration

Oracle User Messaging Service enables users to receive notifications sent from SOA applications that are developed and deployed to the Oracle WebLogic Server using Oracle JDeveloper. At the application level, there is notification activity for a specific delivery channel such as SMS or E-Mail. For example, when you build a SOA application that sends e-mail notification, you drag and drop an Email Activity component from the JDeveloper Component Palette to the appropriate location within a workflow. The application connects then sends notifications. For more information about Oracle JDeveloper, see your JDeveloper documentation. Figure 11–2 shows a user adding an Email Activity to the BPEL process of a SOA composite application. 11-4 Oracle Fusion Middleware Administrator’s Guide for Oracle SOA Suite Figure 11–2 Setting the Notification Activity in the BPEL Workflow To enable the workflow participants to receive and forward notifications, use Oracle 11g Enterprise Manager to set the Oracle User Messaging Service environment by configuring the appropriate driver instances that reside on the same Oracle WebLogic Server on which you deploy the workflow application Figure 11–3 . Oracle User Messaging Service includes drivers that support messaging through E-Mail, IM, SMS and voice channels. For more information, see Section 11.4, Configuring User Messaging Service Drivers . Figure 11–3 Oracle Enterprise Manager 11g Fusion Middleware Control In order for workflow participants to actually receive the notifications, they must register the devices that they use to access messages through User Messaging Preferences Figure 11–4 . Configuring Oracle User Messaging Service 11-5 Figure 11–4 User Messaging Preferences

11.3 Accessing User Messaging Service Configuration Pages

You configure User Messaging Service through Oracle Enterprise Manager Fusion Middleware Control. For more information on Oracle Enterprise Manager, see your Oracle Enterprise Manager documentation.

11.3.1 How to Set the Storage Method

Use the Basic Configuration page to set deployment type for the Messaging Server that is, select the storage method for run time and management data and add or remove the User Messaging Preference Business Terms that are used for creating message filters. Select Persistent the default to enable entries and the Messaging Store to persist when the server has been restarted. In the Transient mode which is recommended for lightweight deployments, the Messaging Server does not maintain any data stored in the Messaging Store after a restart.

11.3.2 How to Add or Remove User Messaging Preferences Business Terms

The Basic Configuration page enables you to add or remove the business terms used to construct the message filters in User Message Preferences. For more information about building messaging filters with business terms, refer to Adding Business Terms .

11.3.2.1 Adding Business Terms

To add a business term to User Messaging Preferences:

1. Click Add.

Note: Business Terms are stored per server instance. If there are multiple instances as in a cluster, then new business terms must be added to each instance individually.