Oracle® Fusion Middleware

Oracle User Messaging Service Release Notes

12c (12.2.1.3.0)

E81290-01

August 2017

This document describes all the known issues for this release of Oracle User Messaging Service.

Oracle Fusion Middleware Oracle User Messaging Service Release Notes, 12c (12.2.1.3.0)

E81290-01

Copyright © 2015, 2017, Oracle and/or its affiliates. All rights reserved.

Primary Author: Vinodini Shashikumar

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Contents

Preface

- Audience

- Documentation Accessibility

- Conventions

1 Introduction

- Latest Release Information

- Purpose of this Document

- System Requirements and Specifications

- Certification Information

- Product Documentation

- Oracle Support

- Licensing Information

2 What’s New in this Release

- New Features

- Deprecated Features

3 Known Issues and Workaround

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

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

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

- User Messaging Service URLs Unavailable After Restart

- User Messaging Service Upgrade from 11g to 12c may Fail

- Duplicate Messages Rendered in Twitter Driver

- Exceptions Occur while Registering Multiple Drivers and Access Points

- User Messaging Service schema does not have connect button in the Upgrade Assistant

- Message resend from EM Message Status page failed

- WLST command manageUserCommunicationPrefs has changed

- Invalid Objects from ORASDPM Schema Appear on BPM Upgrade

- Configuration Issues and Workarounds

- Use Correct SSL Trust Store When Configuring Drivers

- WebLogic Administrator cannot update UMS configuration in Enterprise Manager

4 Documentation Changes

Preface

Oracle User Messaging Service 12c (12.2.1.3.0) release notes summarize release information related to new features or enhancements, resolved issues, general issues and workarounds, deprecated and removed functionality, and more.

Audience

This document is intended for users of Oracle User Messaging Service 12c.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Accessible Access to Oracle Support

Oracle customers who have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Conventions

The following text conventions are used in this document:

Convention

Meaning

boldface

Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.

italic

Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.

monospace

Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

1 Introduction

This chapter introduces the Release Notes for Oracle User Messaging Service.

- Latest Release Information

- Purpose of this Document

- System Requirements and Specifications

- Certification Information

- Product Documentation

- Oracle Support

- Licensing Information

Latest Release Information

This document is accurate at the time of publication. Oracle will update the release notes periodically after the software release. You can access the latest information and additions to these release notes on the Oracle Technology Network at:

http://www.oracle.com/technetwork/indexes/documentation/index.html

Purpose of this Document

This document contains the release information for Oracle Fusion Middleware Release for Oracle User Messaging Service. It describes differences between Oracle Fusion Middleware and its documented functionality.

Oracle recommends you review its contents before installing, or working with the product.

System Requirements and Specifications

Oracle User Messaging Service installation and configuration will not complete successfully unless users meet the hardware and software pre-requisite requirements before installation. See Installing User Messaging Service in Oracle Fusion Middleware Administering Oracle User Messaging Service.

Certification Information

To see versions of platforms and related software for which Oracle User Messaging Service is certified and supported, go to http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html.

Product Documentation

For complete documentation on Oracle User Messaging Service, go to http://docs.oracle.com/en/middleware/.

Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support at https://support.oracle.com.

Licensing Information

For the latest information on Oracle Fusion Middleware Licensing, see Licensing Information User Manual.

Detailed information regarding license compliance for Oracle Fusion Middleware is available at:

http://www.oracle.com/technetwork/middleware/ias/overview/index.html

2 What’s New in this Release

This chapter describes the features and improvements in Oracle User Messaging Service (UMS). The following topics introduce the new and changed features of UMS and other significant changes in the guides, and provides pointers to additional information.

- New Features

- Deprecated Features

New Features

There are no new features in the current release.

Deprecated Features

Oracle User Messaging Service is deprecated in Release 12.2.1.

3 Known Issues and Workaround

This chapter describes the issues associated with Oracle Platform Security Services:

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

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

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

- User Messaging Service URLs Unavailable After Restart

- User Messaging Service Upgrade from 11g to 12c may Fail

- Duplicate Messages Rendered in Twitter Driver

- Exceptions Occur while Registering Multiple Drivers and Access Points

- User Messaging Service schema does not have connect button in the Upgrade Assistant

- Message resend from EM Message Status page failed

- WLST command manageUserCommunicationPrefs has changed

- Invalid Objects from ORASDPM Schema Appear on BPM Upgrade

- Configuration Issues and Workarounds

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

Issue

Impacted Platform: Generic

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.

Workaround

No workaround available.

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

Issue

Impacted Platform: Generic

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.

Workaround

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).

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

Issue

Impacted Platform: Generic

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. The UMS server home page may also display the message counts (in Statistics section) as Unavailable.

Workaround

No workaround available.

User Messaging Service URLs Unavailable After Restart

Issue

Impacted Platform: Generic

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).

Workaround

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.

User Messaging Service Upgrade from 11g to 12c may Fail

Issue

Impacted Platform: Generic

In some scenarios, while upgrading UMS from 11g to 12c, the upgrade may fail with the following error:

[2014-04-10T20:38:14.915-07:00] [UCSUMS] [ERROR] [] [upgrade.UCSUMS.UCSUMS_CONFIGURATION_PLUGIN] [tid: 70] [ecid:435559f9-7615-48f8-8e80-950a7f10e152-00000001,0] [[com.jcraft.jsch.JSchException: verify: false

Workaround

The com.jcraft.jsch.JSchException: verify: false exception is intermittent. As a workaround, try to upgrade again.

Duplicate Messages Rendered in Twitter Driver

Issue

Impacted Platform: Generic

Each time the Twitter driver is restarted, the last 20 tweets are fetched for the configured user. This means, that the first receive attempt after restarting the application might return some messages that have already been seen previously.

Workaround

As a workaround, if you want to handle every tweet only once, you can use the header containing the Twitter Id.

Exceptions Occur while Registering Multiple Drivers and Access Points

Issue

Impacted Platform: Generic

Access Points are registered in a new transaction meaning that if the client application registers Access Points in a transaction that is roll-backed, the Access Points are still stored.

Workaround

If the Access Points must be removed, deregister the Application as described in 5.1.2 Deregistering Messaging Client Applications at https://docs.oracle.com/middleware/1213/ums/administer/ns_monitor.htm#UMSAG37181.

User Messaging Service schema does not have connect button in the Upgrade Assistant

Issue

Impacted Platform: Generic

While upgrading the UMS schema using Oracle Fusion Middleware Upgrade Assistant, if the Individually Selected Schemas option is chosen, the connect button that is used to obtain connection to the database, and the drop-down list that is used to populate the available UMS schema names will not be present.

Workaround

The workaround is to manually enter the value for schema name.

Message resend from EM Message Status page failed

Issue – Resend for deployment with unclustered managed servers

Impacted Platform: Generic

In a domain with UMS deployed in multiple unclustered managed servers, the Message Status page in EM for one UMS server can display messages sent through another server in the domain. Resending a message that was originally sent from another server will result in a resend failure. A resend operation must be attempted from the same server through which the message was originally intended to be sent.

Workaround

To resend the message through another server, navigate to the Message Status page of the right UMS server target in the domain and resend. For example, in a domain with two managed servers (a_ums_server and b_ums_server), perform the following steps for a proper resend:

1. Select target "usermessagingserver (a_ums_server)" from the left navigation tree, and click on the Message Status menu item. The page displays all messages in the message status table, based on the default search criteria.

2. Click on a message in the table, and view the Message Details of the message to determine the UMS server used for the original send of the message.
For instance, if the value of the Engine parameter for the selected message is "/unclustered_base_domain/base_domain/b_ums_server/usermessagingserver", the current target server (a_ums_server) does not match the server in the Engine parameter (b_ums_server). Clicking on Resend button for this selected message will result in the following error: Invalid server selected for resend message operation.

3. To resend this message, navigate to the "usermessagingserver(b_ums_server)" in the left navigation tree, click on the message, verify that the target name and server name in the Engine details match, and click on Resend.

Issue – Resend for deployment with multiple clusters

Impacted Platforms: N/A

In a domain with UMS deployed in multiple clusters, the Message Status page in EM for one UMS server (belonging to a cluster) can display messages sent through another server in the domain. Resending a message that was originally sent from another server (belonging to a different cluster) will result in a resend failure. A resend operation must be attempted from the same cluster through which the message was originally intended to be sent. To resend the message through another cluster, navigate to the Message Status page of the right UMS server target (one of the UMS servers in the right cluster) in the domain and resend.

Workaround

For example, in a domain with two clusters (a_ums_cluster and b_ums_cluster) with each cluster containing two managed servers (a_ums_cluster with a_ums_server1 and a_ums_server2, b_ums_cluster with b_ums_server1 and b_ums_server2), perform the following steps for a proper resend:

1. Select target "usermessagingserver (a_ums_server1)" from the left navigation tree, and click on the Message Status menu item. The page displays all messages in the message status table, based on the default search criteria.

2. Click on a message in the table, and view the Message Details section of the message to determine the UMS server used for the original send of the message.
As seen in the sample, the value of the Engine parameter for the selected message is "/cluster_base_domain/base_domain/b_ums_server1/usermessagingserver".

Since the target server (a_ums_server1) and the server in the Engine parameter (b_ums_server1) do not belong to the same cluster, clicking on Resend button for this selected message will result in the following error: Invalid server selected for resend message operation.

3. To resend this message, navigate to the "usermessagingserver (b_ums_server1)" in the left navigation tree, click on the message, verify that the target name and server name in the Engine details match (or are in the same cluster), and click on Resend.

WLST command manageUserCommunicationPrefs has changed

Issue

Impacted Platform: Generic

The function of WebLogic Scripting Tool (WLST) command manageUserCommunicationPrefs has changed. The WLST command no longer connects to the managed server during command execution. Instead, the WLST command now reuses the MBeanServer connection to connect to the managed server. Due to this, the connecting URL, username, and password are deleted from all variants of the manageUserCommunicationPrefs command.

Workaround

No workaround available.

Invalid Objects from ORASDPM Schema Appear on BPM Upgrade

Issue

Impacted Platform: Generic

When upgrading Business Process Management (BPM) projects from Oracle 11g to 12c, invalid objects from Oracle Service Delivery Platform Messaging (ORASDPM) schema appear in the database.

Workaround

No workaround available.

Configuration Issues and Workarounds

This section describes the configuration issues and their workarounds.

- Use Correct SSL Trust Store When Configuring Drivers

- WebLogic Administrator cannot update UMS configuration in Enterprise Manager

Use Correct SSL Trust Store When Configuring Drivers

Issue

Impacted Platform: Generic

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), if 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.

Workaround

To resolve this issue, follow the instructions for using the correct SSL trust store. Replacing the DemoTrustkeystore 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.

WebLogic Administrator cannot update UMS configuration in Enterprise Manager

Issue

Impacted Platform: Generic

The WebLogic administrator does not have the permission to edit the User Messaging Service (UMS) configuration in the Enterprise Manager for multi-tenancy. Therefore, the add, edit, and delete buttons for the driver configuration page as well as the user preference configuration page are disabled for the WebLogic administrator.

Workaround

To edit the UMS configuration, you need to log in as a partition administrator.

4 Documentation Changes

Documentation Updates to Oracle User Messaging Service Guides

All documentation updates to the following guides will be included in the release notes:

- Administering Oracle User Messaging Service

- Administering User Communication Preferences

- Developing Applications with Oracle User Messaging Service

- User Messaging Service Java API Reference

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2018, Oracle and/or its affiliates. All rights reserved.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Hazardous Applications Notice

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Trademark Notice

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Pre-General Availability Draft Documentation Notice

If this document is in public or private pre-General Availability status:

This documentation is in pre-General Availability status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.

Private Pre-General Availability Draft Documentation Notice

If this document is in private pre-General Availability status:

The information contained in this document is for informational sharing purposes only and should be considered in your capacity as a customer advisory board member or pursuant to your pre-General Availability trial agreement only. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described in this document remains at the sole discretion of Oracle.

This document in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle Master Agreement, Oracle License and Services Agreement, Oracle PartnerNetwork Agreement, Oracle distribution agreement, or other license agreement which has been executed by you and Oracle and with which you agree to comply. This document and information contained herein may not be disclosed, copied, reproduced, or distributed to anyone outside Oracle without prior written consent of Oracle. This document is not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.