6 Oracle User Messaging Service

This chapter describes issues associated with Oracle User Messaging Service (UMS).

It includes the following topics:

6.1 General Issues and Workarounds

This section describes general issue and workarounds. It includes the following topics:

6.1.1 Extension Driver has Different Target Types for 11g and 12c

In Oracle Enterprise Manager Fusion Middleware Control 12c, the User Messaging Service Extension driver will be displayed under the User Messaging Service folder, instead of the Application Deployments folder in the left navigation pane. The driver performance data is also available for the extension driver. This is an expected behavior.

6.1.2 Node Manager Fails to Start After Configuring Oracle User Messaging Service and Oracle HTTP Server

In a cluster environment, the node manager may fail to start if you have configured Oracle User Messaging Service (UMS) and Oracle HTTP Server in a domain with Oracle Real Application Clusters (RAC) multi data sources.


UMS uses about 100 connections per data source if all UMS drivers are deployed and running. Therefore, in a clustered environment with RAC setup, you may have to increase the maximum number of connections allowed on the database server. Set this value to the sum of maximum number of connections per data source for each WebLogic Server. For example, when Oracle RAC is used with three nodes, that is two WebLogic Servers with three Oracle RAC data sources, set the maximum number of connections to 600 (2 x 3 x 100).

6.1.3 UMS Schema Purge Script is Available for Download

A UMS schema purge script is available for your download and use. You can access the script and instructions for its use by contacting Oracle Support.


The purge script is available as part of the UMS 12c component for Oracle Database users.

6.1.4 Messages Metrics Rendered as Unavailable in the Performance Page for User Messaging Server

When no metric data is found (for example when no messages have been sent or received after server setup), the Metrics Performance page will display Unavailable. This is not a problem with the software, and the Performance reporting is operating properly. As soon as Send and Receive traffic exists, the Performance page will display results normally.

6.1.5 User Messaging Service URLs Unavailable After Restart

Upon restarting the User Messaging Service server (usermessagingserver) from Oracle Enterprise Manager Fusion Middleware Control or through Oracle WebLogic Console, you may get an error: Error 503--Service Unavailable when attempting to access any URLs served by the User Messaging Service server, such as the User Preferences UI (/sdpmessaging/userprefs-ui) or the various Web Services endpoints. This error occurs intermittently in cases when the Oracle WebLogic Server is heavily loaded (such as with a SOA instance). To work around this issue:

  • Restart the User Messaging Service server again (two or more restarts may be required).

  • If multiple User Messaging Service server restarts are not sufficient, then restart the entire Oracle WebLogic Server instance.

6.2 Configuration Issues and Workarounds

This section describes configuration issues and their workarounds. It includes the following topics:

6.2.1 Pre-seeded Channel for Worklist and Pop-up Drivers Cannot be Removed

If you deinstall the Worklist or Pop-up driver, the pre-seeded channel for these drivers cannot be removed. The pre-seeded channel will remain available in your preference list.

6.2.2 Use Correct SSL Trust Store When Configuring Drivers

Before configuring any User Messaging Service Driver (such as the Email Driver), to connect to a remote gateway using SSL, ensure that the SSL Trust Store is properly configured as described in "Configure Keystores" in Oracle WebLogic Server Administration Console Online Help.

Ensure that the value of the JVM system property (javax.net.ssl.trustStore) set in $DOMAIN_HOME/bin/setDomainEnv.sh (or Windows equivalent file) points to the correct trust store that you want to use.The Java Standard Trust Store is located at:

$JAVA_HOME/jre/lib/security/cacerts or $BEA_JAVA_HOME/jre/lib/security/cacerts

With the default out-of-the-box configuration of SSL trust store, that is with the Java Standard Trust Store, the UMS driver will be able to connect to the Oracle Beehive Email Server over SSL. Note that in some installations, for example, when you have SOA installed, the Java Standard Trust Store is replaced by a Demo Trust Store. In such situations, the Trust Store may not contain the valid root certificate needed by Oracle Beehive Email Server. To resolve this issue, follow the instructions for using the correct SSL trust store. Replacing the DemoTrust keystore in the setDomainEnv.sh file (or Windows equivalent file) with the Java Standard SSL trust store will enable UMS email driver to connect successfully over SSL to the Oracle Beehive Email Server.

6.2.3 Worklist Driver Configuration

While following the Worklist Driver configuration instructions, you may see that Oracle User Messaging Service for SOA in the Configuration Wizard is not selected, leading you to think that it is not configured and that you must select and configure it. This is not the case. The basic Oracle User Messaging Service is already configured, along with a few UMS drivers.

Continue to follow the documented instructions, and disregard the fact that the Oracle User Messaging Service for SOA option is not selected.