Oracle® Fusion Middleware

Release Notes for Oracle Fusion Middleware Infrastructure

12c (12.2.1)

E58102-04

March 2017

This document describes all known issues for this release of Oracle Fusion Middleware Infrastructure.

Oracle Fusion Middleware Release Notes for Oracle Fusion Middleware Infrastructure, 12c (12.2.1)

E58102-04

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

Primary Author: Phil Stubbs

Contributing Authors: Christine Ford, Lisa Jamen, Helen Grembowicz, Peter LaQuerre, Vinaye Misra, Devanshi Mohan, Megha Sharma

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

- Related Documents

- Conventions

1 Install and Configure

- 1.1 Issues Pertaining to Product Installation

- 1.1.1 Applying a Mandatory Patch for Oracle Business Activity Monitoring

- 1.1.2 Checking for Available Software Patches

- 1.2 Issues Pertaining to Product Configuration

- 1.2.1 Node Manager with Type Set to Plain Cannot be Modified Using Fusion Middleware Control in Non-English Environments

- 1.2.2 Applications will not Start After WebLogic Server is Upgraded

- 1.3 Issues Pertaining to Product Installation and Configuration Documentation

- 1.3.1 Registering Node Manager as a Windows Service

- 1.3.2 Incorrect Step Displayed on the Installation Complete Screen

- 1.3.3 Error Message Displayed When Incorrect Version of JDK Used for Installation

- 1.3.4 Incorrect Error Message Displayed if JDK not Compatible with Operating System

- 1.3.5 Warning Messages in make.log File

- 1.3.6 Simple Security Mode Does Not Function with OAM Server

- 1.3.7 Domain Creation Fails if Correct Server Groups are not Selected While Configuring OSB and SOA

- 1.3.8 Incorrect config.xml File Generated While Extending a SOA Cluster with OSB

- 1.3.9 install<time-stamp>.out File not Created in the MFT Installation Log Directory

- 1.3.10 Error Message Displayed in oblog.log File After Configuring OHS WebGate

- 1.3.11 Configuring Oracle WebLogic Server to Access Oracle Internet Directory over SSL

- 1.4 Documentation Errata

2 Patching and Upgrade

- 2.1 Issues Pertaining to Product Upgrade

- 2.1.1 Upgrade Assistant Fails to Load All Schemas Used by a Domain for Audit Schema Users

- 2.1.2 BPM Composites are Not Compiled Post Upgrade

- 2.1.3 OWSM Data Source Connection Failure During 12.1.3 to 12.2.1 Domain Upgrade

- 2.1.4 Standard Workspace Dashboards Missing Participant Information After Upgrade

- 2.1.5 SAXParseException May Occur During Reconfiguration

- 2.1.6 Oracle SOA Suite 12c Does Not Support Non-Oracle Databases and Third-Party Application Servers

- 2.1.7 MissingResourceException May Occur During Reconfiguration

- 2.1.8 Analytics Data for 11g (11.1.1.7) Composites Created Without Roles Will Not Be Migrated to 12c

- 2.1.9 MDS Schema Data Not Populated During Configuration After Upgrade

- 2.1.10 Notification Queue Cannot Be Selected After Upgrade

- 2.1.11 Business Process Composer Appears to Freeze After Migration

- 2.1.12 Oracle HTTP Server Upgrade Overwrites Node Manager Configuration

- 2.1.13 EDN-JMS Backlogged Events Do Not Migrate During Upgrade

- 2.2 Issues Pertaining to Product Patching

- 2.2.1 OPatch Does Not Restore Regenerated Libraries Even After User Quits the Patching Process

3 Oracle Fusion Middleware Administration

- 3.1 General Issues and Workarounds

- 3.1.1 Problems Using Oracle Database 12.2 with This Release

- 3.1.2 Limitations in Moving from Test to Production

- 3.1.3 MDS purgeMetadata Command Can Take a Long Time

- 3.1.4 SSL Certificate Chain Required on Certain Browsers

- 3.2 Configuration Issues and Workarounds

- 3.2.1 Fusion Middleware Control Incorrectly Refers to Shared Service Tables

- 3.3 Documentation Errata for Administering Oracle Fusion Middleware

4 High Availability

- 4.1 Issues Pertaining to Automatic Service Migration

- 4.1.1 Oracle User Messaging Service 12c (12.1.3) Does Not Support Automatic Service Migration

- 4.2 Issues Pertaining to Oracle BAM

- 4.2.1 Configuring Oracle BAM After Scale Up

5 Platform Security Services

- 5.1 Configuration Issues and Workarounds

- 5.1.1 libOVD Move Plan Does Not Support Obfuscated Password

- 5.1.2 libovdconfig.bat script Does Not Support a Space in File Path

- 5.1.3 Property maxDirSize not used in Audit Service

- 5.2 Documentation Errata

6 Oracle User Messaging Service

- 6.1 Deprecation Notice

- 6.2 General Issues and Workarounds

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

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

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

- 6.2.4 User Messaging Service URLs Unavailable After Restart

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

- 6.2.6 Duplicate Messages Rendered in Twitter Driver

- 6.2.7 Exceptions Occur while Registering Multiple Drivers and Access Points

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

- 6.2.9 Message resend from EM Message Status page failed

- 6.2.9.1 Resend for deployment with unclustered managed servers

- 6.2.9.2 Resend for deployment with multiple clusters

- 6.3 Configuration Issues and Workarounds

- 6.3.1 Use Correct SSL Trust Store When Configuring Drivers

7 Web Services

- 7.1 Upgrade Fails When OWSM Data Source is Configured as Multi Data Source

- 7.2 Using a Repository Backed by a Hardened Oracle Database

- 7.3 Using Multibyte User Credentials with wss_http_token_* Policy

- 7.4 Performing a Bulk Upload of Policies

- 7.5 Removing Post-deployment Customizations

- 7.6 Reviewing Localization Limitations

- 7.7 Fusion Middleware Control Does Not List Policies When Two Servers Are SSL Enabled (Two-way SSL)

- 7.8 Web Service Test Page Cannot Test Input Arguments Bound to SOAP Headers

- 7.9 Possible Limitation When Using Custom Exactly-one Policies

- 7.10 Security Policies Do Not Work on Subscriber Mediator Component

- 7.11 Policy Table Might Not Show Attached Policies for Some Locales

- 7.12 Restart Applications to Get an Accurate Policy Usage Count

- 7.13 Performance Improvements In Web Services Policy Pages

- 7.14 Bulk Attachment of Policies Is not Supported In the Current Release

- 7.15 Enterprise Manager Returns You to the OWSM Policies Page After Editing a Client Policy

- 7.16 JKS Configuration Screen Displays Incorrect Values

- 7.17 Domain Configuration Is Not Supported in Classpath Mode

- 7.18 Apply/Revert Buttons Are Not Activated After Editing SAML Trust on Authentication Tab of OWSM Domain Configuration Page

- 7.19 Query by Example Feature is Not Working

- 7.20 Avoiding XML Encryption Attacks

- 7.21 OWSM Introspection Plug-in Fails When Proxy Is Configured Incorrectly

- 7.22 Cross-Domain Policy Manager Configuration Is Not Supported In this Release

- 7.23 USERNAME_ID_PROPAGATION Policies Deprecated

- 7.24 Deprecated Commands for Oracle Infrastructure Web Services

- 7.25 Test Web Service Page Does Not Generate the Correct Date/Date Time Patterns When Importing a Locally Saved Payload

- 7.26 Test Web Service Page Does Not Save Loaded Payloads In the Correct Format

- 7.27 Using the Automatic Policy Configuration for STS May Not Result in a Compatible Policy for a Web Service Client

- 7.28 Incompatible Policies Listed for Web Services and Clients Using SOAP Over JMS Transport

- 7.29 Unsupported Make Connection Policy/ Assertion Template Category Shown In Fusion Middleware Control

- 7.30 NoSuchObjectException when Server Hosting WSM-PM is Shut Down

- 7.31 Harmless Warning Message when Creating Policy Sets

- 7.32 Difference between Installed and Upgraded Configuration Files

- 7.33 Oracle Infrastructure Web Service Applications Built in 11g Containing WebServiceRef Annotation Will Fail

- 7.34 WADL for OPSS and OWSM REST APIs not Generated from Browser

Preface

This document describes known issues with Oracle Fusion Middleware 12c.

Audience

This document is intended for users of Oracle Fusion Middleware 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.

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.

Related Documents

For more information, see the following resources:

- Oracle Fusion Middleware 12c Documentation Library
This contains all documentation for all Oracle Fusion Middleware 12c products.

- Oracle Technology Network
This site contains additional documentation that is not included as part of the documentation libraries.

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 Install and Configure

This chapter describes issues pertaining to Oracle Fusion Middleware product installation and configuration.

The following topics are covered in this chapter:

- Issues Pertaining to Product Installation

- Issues Pertaining to Product Configuration

- Issues Pertaining to Product Installation and Configuration Documentation

- Documentation Errata

1.1 Issues Pertaining to Product Installation

This section contains the following topics:

- Section 1.1.1, "Applying a Mandatory Patch for Oracle Business Activity Monitoring"

- Section 1.1.2, "Checking for Available Software Patches"

1.1.1 Applying a Mandatory Patch for Oracle Business Activity Monitoring

Before installing Oracle Business Activity Monitoring (Oracle BAM) 12c, be sure to review the My Oracle Support Document ID 1682371.1, which is available from My Oracle Support.

This Support Note provides important information about a mandatory patch that must be applied to Oracle BAM 12c immediately after installation.

1.1.2 Checking for Available Software Patches

Before installing any Oracle Fusion Middleware product, it is good practice to review the product information available on My Oracle Support:

http://support.oracle.com/

When you register for My Oracle Support, you have easy access to important information about available patches and other important Oracle Fusion Middleware product information.

1.2 Issues Pertaining to Product Configuration

This section contains the following topics:

- Section 1.2.1, "Node Manager with Type Set to Plain Cannot be Modified Using Fusion Middleware Control in Non-English Environments"

- Section 1.2.2, "Applications will not Start After WebLogic Server is Upgraded"

1.2.1 Node Manager with Type Set to Plain Cannot be Modified Using Fusion Middleware Control in Non-English Environments

If you are using Fusion Middleware Control in a non-English environment, you might experience problems when you attempt to edit the Node Manager settings for an existing machine with Type set to Plain.

For example, if you navigate to the Configuration > Node Manager page to edit the Node Manager for an existing machine, the Type field appears blank. If you manually set the Type field to Plain, then an error message appears when trying to save your settings.

If you encounter this issue, perform one of the following workarounds:

- Use the WebLogic Server Administration Console to edit the Node Manager settings.
For more information, see "Configure Node Manager" in the Oracle WebLogic Server Administration Console Online Help.

- Use Fusion Middleware Control in an English browser to edit the Node Manager settings.
For more information, see "Configure Node Manager settings" in Administering Oracle WebLogic Server with Fusion Middleware Control.

1.2.2 Applications will not Start After WebLogic Server is Upgraded

After applying the latest patches to Oracle WebLogic Server, the ORACLE_HOME/wlserver/server/lib/weblogic.policy file must be edited to include the following entry in order for Middleware services such as Discoverer, Access Manager, and Identity Manager to start:

grant codeBase "file:ORACLE_HOME/WLS/patch_jars/-" {
permission java.lang.RuntimePermission "oracle.*","read";
};

Replace ORACLE_HOME with the location of your Oracle home directory.

Replace WLS with one of the following:

- patch_wls1035 for WebLogic Server version 10.3.5

- patch_wls1036 for WebLogic Server version 10.3.6

- patch_wls1212 for Weblogic Server version 12.1.2

1.3 Issues Pertaining to Product Installation and Configuration Documentation

This section contains the following topics:

- Section 1.3.1, "Registering Node Manager as a Windows Service"

- Section 1.3.2, "Incorrect Step Displayed on the Installation Complete Screen"

- Section 1.3.3, "Error Message Displayed When Incorrect Version of JDK Used for Installation"

- Section 1.3.4, "Incorrect Error Message Displayed if JDK not Compatible with Operating System"

- Section 1.3.5, "Warning Messages in make.log File"

- Section 1.3.6, "Simple Security Mode Does Not Function with OAM Server"

- Section 1.3.7, "Domain Creation Fails if Correct Server Groups are not Selected While Configuring OSB and SOA"

- Section 1.3.8, "Incorrect config.xml File Generated While Extending a SOA Cluster with OSB"

- Section 1.3.9, "install<time-stamp>.out File not Created in the MFT Installation Log Directory"

- Section 1.3.10, "Error Message Displayed in oblog.log File After Configuring OHS WebGate"

- Section 1.3.11, "Configuring Oracle WebLogic Server to Access Oracle Internet Directory over SSL"

1.3.1 Registering Node Manager as a Windows Service

To register Node Manager as a Windows Service serving either one of the following:

- a standalone OHS domain

- a domain with a collocated ODI agent

Do the following after you have created the domain:

1. Set the JAVA_OPTIONS environment variable so that it points to the proper Oracle home and Domain home directories.

set JAVA_OPTIONS=-Dohs.product.home=ORACLE_HOME -Dweblogic.RootDirectory=DOMAIN_HOME

For example:

set JAVA_OPTIONS=-Dohs.product.home=C:\Oracle\product\OHS\OracleHome -Dweblogic.RootDirectory=C:\Oracle\config\domains\OHSDomain

2. Go to the Domain home directory and run the following command:

installNodeMgrSvc.cmd

1.3.2 Incorrect Step Displayed on the Installation Complete Screen

On completing a standalone OHS installation, the step 'Start Node Manager and Domain Servers' is displayed as one of the next steps you should take after installation.

This information is incorrect, as there are no domain servers configured during the standalone installation.

1.3.3 Error Message Displayed When Incorrect Version of JDK Used for Installation

When you attempt to install a Fusion Middleware product on a 64-bit system, using a JDK for a 32-bit system, an error message is displayed before the installation begins.

Refer to the Oracle Fusion Middleware System Requirements and Specifications document for your product, and download a suitable JDK from the following location, before installing the Fusion Middleware software:

http://www.oracle.com/technetwork/java/javase/downloads/index.html

1.3.4 Incorrect Error Message Displayed if JDK not Compatible with Operating System

If you run the installer jar file from a 32-bit JDK7 JVM on a 64-bit machine, the installer displays an incorrect message that the version of the JVM is correct and the version of the operating system on which the software is installed is incorrect.

Refer to the System Requirements and Specifications document for your product, and download a suitable JDK from the following location, before installing the Fusion Middleware software:

http://www.oracle.com/technetwork/java/javase/downloads/index.html

1.3.5 Warning Messages in make.log File

While installing Oracle Web Tier 12c on AIX operating systems, warning messages may appear in the ORACLE_HOME/install/make.log file.

These messages can be safely ignored.

1.3.6 Simple Security Mode Does Not Function with OAM Server

On the AIX Platform, Simple Security Mode is not functioning with OAM Server.

While registering new Webgate Agent for artifacts generation, select Open or Cert Security Mode in OAM Server Console.

1.3.7 Domain Creation Fails if Correct Server Groups are not Selected While Configuring OSB and SOA

If you configure an OSB and SOA cluster without selecting the correct server groups, then the domain creation fails with the following notice:

Preparing...
Extracting Domain Contents...
Creating Domain Security Information...
Starting OPSS Security Configuration Data Processing...
The OPSS Security Configuration Data Processing Completed...
Domain Creation Failed!

To avoid this error, select OSB-MGD-SVRS-COMBINED and SOA-MGD-SVRS server groups for all managed servers on the Managed Servers screen.

1.3.8 Incorrect config.xml File Generated While Extending a SOA Cluster with OSB

While extending your SOA cluster domain with OSB, if you delete the existing Managed Server and create a new Managed Server, an incorrect config.xml file is generated. For example, if you delete the existing soa_server1 and replaced it with osb_server1 you will get an incorrect config.xml file. Specifically, the following SAF tags are missing from config.xml:

<saf-agent>
<name>ReliableWseeSAFAgent_auto_1</name>
<target>osb_server1 (migratable)</target>
<store>WseeFileStore_auto_1</store>
</saf-agent>
<saf-agent>
<name>ReliableWseeSAFAgent_auto_2</name>
<target>ms2 (migratable)</target>
<store>WseeFileStore_auto_2</store>
</saf-agent>

To avoid this issue, while extending, create new Managed Servers for OSB.

1.3.9 install<time-stamp>.out File not Created in the MFT Installation Log Directory

In Managed File Transfer, install<timestamp>.out file is not created in the log inventory.

This is not an error.

1.3.10 Error Message Displayed in oblog.log File After Configuring OHS WebGate

After configuring OHS WebGate and restarting the servers, the following error message is displayed in oblog.log file in the Domain_Home/server/ohs1/logs/oblog.log directory:

2014/06/10@05:56:29.81679       14314   27      INIT    ERROR
0x000003B6      ../oblistrwutil.cpp:225 "Could not read file"
filename^/scratch/aime/1213FMW/ASCORE/RC4BColocated/MW_HOME/webgate/ohs/config
/oblog_config.xml
2014/06/10@05:56:43.14915       14313   9       INIT    ERROR
0x000003B6      ../oblistrwutil.cpp:225 "Could not read file"
filename^/scratch/aime/1213FMW/ASCORE/RC4BColocated/MW_HOME/webgate/ohs/config
/oblog_config.xml

To work around, do the following:

1. Run:
cp Oracle_Home/webgate/ohs/config/oblog_config_wg.xml $Oracle_Home/webgate/ohs/config/oblog_config.xml

2. Restart all the servers.

1.3.11 Configuring Oracle WebLogic Server to Access Oracle Internet Directory over SSL

If you want to configure Oracle WebLogic Server to access Oracle Internet Directory (OID) over SSL, then you need to obtain and add an OID server certificate to the WebLogic domain. The OID certificate is necessary for a successful SSL handshake and for successfully setting up a connection from Oracle WebLogic Server to Oracle Internet Directory.

For information on obtaining the required certificate and adding it to the WebLogic Server store, see "Enabling SSL Communication Between the Middle Tier and the Hardware Load Balancer" in Enterprise Deployment Guide for Oracle SOA Suite.

1.4 Documentation Errata

There are no known issues at this time.

2 Patching and Upgrade

This chapter describes issues related to the Infrastructure upgrade.

The following topics are covered in this chapter:

- Issues Pertaining to Product Upgrade

- Issues Pertaining to Product Patching

2.1 Issues Pertaining to Product Upgrade

This section contains the following topics:

- Section 2.1.1, "Upgrade Assistant Fails to Load All Schemas Used by a Domain for Audit Schema Users"

- Section 2.1.2, "BPM Composites are Not Compiled Post Upgrade"

- Section 2.1.3, "OWSM Data Source Connection Failure During 12.1.3 to 12.2.1 Domain Upgrade"

- Section 2.1.4, "Standard Workspace Dashboards Missing Participant Information After Upgrade"

- Section 2.1.5, "SAXParseException May Occur During Reconfiguration"

- Section 2.1.6, "Oracle SOA Suite 12c Does Not Support Non-Oracle Databases and Third-Party Application Servers"

- Section 2.1.7, "MissingResourceException May Occur During Reconfiguration"

- Section 2.1.8, "Analytics Data for 11g (11.1.1.7) Composites Created Without Roles Will Not Be Migrated to 12c"

- Section 2.1.9, "MDS Schema Data Not Populated During Configuration After Upgrade"

- Section 2.1.10, "Notification Queue Cannot Be Selected After Upgrade"

- Section 2.1.11, "Business Process Composer Appears to Freeze After Migration"

- Section 2.1.12, "Oracle HTTP Server Upgrade Overwrites Node Manager Configuration"

- Section 2.1.13, "EDN-JMS Backlogged Events Do Not Migrate During Upgrade"

2.1.1 Upgrade Assistant Fails to Load All Schemas Used by a Domain for Audit Schema Users

When upgrading from 11g (11.1.1.7 or 11.1.1.9) to 12.2.1, the Upgrade Assistant fails to load schemas associated with the domain when All schemas used by a Domain is selected when using the Upgrade Assistant.

The following exception is logged:

Exception
-------------
UPGAST- 00214 - Unable to connect to database as schema user <prefix>_IAU.
Listener refused the connection with the following error :
.
ORA-12504, TNS : Listener was not given the SID in CONNECT_DATA
.
Cause : The database connection failed for the specified reason.
Action : Correct the problem using information provided in the log file; then
retry the operation. In particular if the indicated reason is "Login has
timed out" verify that the host and port are correct and make sure the
database is up and is configured for network access.

To work around this issue:

Restart the Upgrade Assistant, enter the 11g domain location, select Individually Selected Schemas, and select the correct _IAU. _SOAINFRA, and _OPSS schemas.

Selecting the SOA and OPSS schemas will ensure that Audit Services, User Messaging Service and MDS schemas are selected automatically.

2.1.2 BPM Composites are Not Compiled Post Upgrade

When upgrading from 11.1.1.9 to 12.2.1, Oracle Business Process Management (BPM) composites are not compiled post upgrade.

To compile the BPM composites after the upgrade, simply restart the Oracle SOA Server.

The following example shows the error that is received:

[soa_server1] [ERROR] []
Exception while loading process
[[
ORABPEL-01005

Failed to compile bpel generated classes.
failure to compile the generated BPEL classes for BPEL process
The class path setting is incorrect.
Ensure that the class path is set correctly. If this happens on the server
side, verify that the custom classes or jars which this BPEL process is
depending on are deployed correctly. Also verify that the run time is using
the same release/version.

2.1.3 OWSM Data Source Connection Failure During 12.1.3 to 12.2.1 Domain Upgrade

When you select All configurations used by the domain when running the Upgrade Assistant, the upgrade fails at the examination phase with the following error:

[2015-09-22T10:46:54.552-07:00] [WSM] [INCIDENT_ERROR]
[upgrade.WSM.WSMPLUGIN]
oracle.ias.update.exception.UpgradeException: WSMERROR-00015: Failed to read the Oracle WSM datasource connection details.
at
oracle.wsm.lifecycle.upgrade.impl.WSMUpgradePlugin.initializePluginData(WSMUpgradePlugin.java:396)

This error occurs because the 12.1.3 domain is created with Multi-DataSource connection. When upgrading to 12.2.1, the Upgrade Assistant expects a generic datasource connection.

To perform the upgrade, complete the following steps:

Change the "mds-owsm" data source to be a generic data source.

Restart the Upgrade Assistant and, when prompted, select All configurations used by the domain.

After a successful upgrade, you can change the "mds-owsm" data source back to a multi-DS.

2.1.4 Standard Workspace Dashboards Missing Participant Information After Upgrade

After an upgrade to 12c, the Performance Per Participant graph that is displayed on standard Workspace dashboards will only be available for new 12c instances and will not be available for in-flight, hybrid, or completed (closed) 11g instances. However, custom 12c Workspace dashboards will continue to display the participant information.

2.1.5 SAXParseException May Occur During Reconfiguration

The following exception appears in the reconfig.log file after invoking the Reconfiguration Wizard with -log_priority=ALL:

[org.xml.sax.SAXParseException; lineNumber: 3; columnNumber: 77; cvc-elt.1:
Cannot find the declaration of element 'stringSubsInfo'.]

You can ignore this exception.

2.1.6 Oracle SOA Suite 12c Does Not Support Non-Oracle Databases and Third-Party Application Servers

Instances that were created using a non-Oracle database cannot be migrated to Oracle Fusion Middleware 12c.

To migrate the closed instances from Oracle Fusion Middleware 11g to Oracle Fusion Middleware 12c, you must create a new 12c SOA domain using a supported Oracle database. Active 11g instances must be completed using the existing 11g server.

2.1.7 MissingResourceException May Occur During Reconfiguration

The following exception appears in the reconfig.log file after invoking the Reconfiguration Wizard with -log_priority=ALL:

java.util.MissingResourceException: No bundle found for base name
config-template

You can ignore this exception.

2.1.8 Analytics Data for 11g (11.1.1.7) Composites Created Without Roles Will Not Be Migrated to 12c

Analytics data for 11g (11.1.1.7) composites without any roles defined in them will not be migrated to 12c.

2.1.9 MDS Schema Data Not Populated During Configuration After Upgrade

When you run the Configuration Wizard after upgrading your Oracle Fusion Middleware products from Release 11g (11.1.1.6) to Release 12c, the MDS schema data might not be populated in the schema table on the JDBC Component Schema screen.

You must manually enter MDS schema data into the schema table on the JDBC Component Schema screen before continuing.

2.1.10 Notification Queue Cannot Be Selected After Upgrade

After you upgrade Oracle SOA Suite from Release 11g (11.1.1.6) MLR to Release 12c, you should be able to select a Notification Queue from the Oracle SOA Suite for Healthcare Integration Runtime Settings.

However, Oracle SOA Suite for Healthcare Integration does not display the JMS Send to Internal channels in the Notification Queue drop-down list after you upgrade.

To work around this issue, change or update other Oracle SOA Suite for Healthcare Integration runtime settings and save the changes. Then, Oracle SOA Suite for Healthcare Integration should display the JMS Send to Internal channels in the Notification Queue list.

2.1.11 Business Process Composer Appears to Freeze After Migration

When you log into Oracle Business Process Composer after upgrading your environment from Release 11g (11.1.1.7) to Release 12c, process migration is launched. After migration finishes, a default space is created and projects are migrated. However, the composer appears to freeze.

As a workaround, log out of the composer, close the browser, and clear the browser cache. You can then log in again to continue working in the composer.

2.1.12 Oracle HTTP Server Upgrade Overwrites Node Manager Configuration

While upgrading your Oracle HTTP Server from Release 11g (11.1.1.7) to 12c when you have a Managed Server being upgraded in the same domain as your HTTP Server and when you have a customized port value for the Node Manager, the Reconfiguration Wizard upgrades the Node Manager and the Managed Server successfully. However, when you run the Upgrade Assistant to upgrade the component configurations, the Upgrade Assistant overwrites the customized Node Manager configuration with the default values for the Node Manager host and port. As a result, a new machine entry is created in the WebLogic Server Administration Console. And, the Managed Server is assigned to this new, non-working machine set by the Reconfiguration Wizard.

After running Upgrade Assistant, if config.xml has any Oracle HTTP Server instances referring to the duplicate Node Manager, then follow the steps below to correct these instances:

1. Modify the nodemanager.properties file to set the Listen Port to the appropriate value.
This value should contain the same port value used in the previous version and should match the value in config.xml for the Node Manager instance.

2. Restart the Node Manager.

3. Modify the configuration via the WebLogic Administration Server to remove the duplicate NodeManagerMBean and MachineMBean.

4. Alter any references to the deleted MachineMBean to point to the valid MachineMBean.

5. Restart the WebLogic Administration Server.

2.1.13 EDN-JMS Backlogged Events Do Not Migrate During Upgrade

Backlogged events in the EDN-JMS queue do not migrate when you upgrade from Oracle Fusion Middleware 11g to Oracle Fusion Middleware 12c.

Before you upgrade, check if there are any backlogged events in the JMS queue. After you finish upgrading, verify that these backlogged events are not in the queue.

You can verify if there are any backlogged events in the JMS queue via the Oracle WebLogic Server Administration Console:

1. From the Domain Structure, select soainfra, then Services, Messaging, JMS Modules, SOAJMSModule, and EDNQueue.

2. Select Monitoring tab.

3. Select SOAJMSModule and EDNQueue, and then click Show Messages.

2.2 Issues Pertaining to Product Patching

This section contains the following topic:

- OPatch Does Not Restore Regenerated Libraries Even After User Quits the Patching Process

2.2.1 OPatch Does Not Restore Regenerated Libraries Even After User Quits the Patching Process

If the OPatch postscript fails and users choose not to proceed with the patching process and quit, OPatch does not restore regenerated libraries correctly.

Check the OPatch log to determine whether or not library regeneration has occurred. If the library regeneration has occurred, apply the patch again. If the OPatch postscript fails again, choose y to proceed with the patching process. OPatch will not roll back the patch automatically this time; the user needs to roll back OPatch manually to restore the pre-patch environment.

For information on how to roll back a patch, see "Using OPatch to Patch Oracle Fusion Middleware" in Patching with OPatch.

3 Oracle Fusion Middleware Administration

This chapter describes issues associated with Oracle Fusion Middleware administration. It includes the following topics:

- General Issues and Workarounds

- Configuration Issues and Workarounds

- Documentation Errata for Administering Oracle Fusion Middleware

3.1 General Issues and Workarounds

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

- Section 3.1.1, "Problems Using Oracle Database 12.2 with This Release"

- Section 3.1.2, "Limitations in Moving from Test to Production"

- Section 3.1.3, "MDS purgeMetadata Command Can Take a Long Time"

- Section 3.1.4, "SSL Certificate Chain Required on Certain Browsers"

3.1.1 Problems Using Oracle Database 12.2 with This Release

When you use Oracle Database 12.2. or higher, you may run into the following issues:

- When you create a Metadata Services (MDS) database schema using Repository Creation Utility (RCU) or upgrade the MDS database schema using Upgrade Assistant against Oracle Database 12.2, the operation may fail.
You may receive the error ORA-28104: input value for statement_types is not valid. This is because, as part of a security fix beginning with Oracle Database 12.2, for the DBMS_RLS.ADD_POLICY procedure, statement types of INSERT and UPDATE_CHECK with a value of FALSE (the default value) are no longer allowed. The security fix results in an ORA-28104 error while registering Virtual Private Database policies.

This error is returned to avoid giving the impression that Virtual Private Database policies are enforced for INSERT statements, which is not the case.

To work around this error, configure the system with "_allow_inserts_with_UPDATE_CHECK" set to True, by executing the following SQL command:

ALTER SYSTEM SET "_allow_insert_with_update_check"=TRUE scope=spfile

Then, restart the database and re-run RCU or the Upgrade Assistant to create or upgrade the MDS database schema.

- When you use Oracle Fusion Middleware with Oracle Database 12.2 or higher, you may encounter the following error:

ORA-00932: inconsistent datatypes: expected SYS.AQ$_JMS_MESSAGE gotSYS.AQ$_JMS_MESSAGE

The error occurs because during enqueue and dequeue of AQ$_JMS_MESSAGE type, the version number sent to the database server may be inconsistent. This happens when TOID (the type's unique identifier) for AQ$_JMS_MESSAGE type in type$ is a user-defined TOID and not a fixed SYSTEM defined TOID.

To work around this error, install the following patch, which replaces the ojdbc6.jar file used by Oracle Fusion Middleware:

https://updates.oracle.com/download/21663638.html

For Oracle Fusion Middleware 12.1.3, select Release 12.1.0.2.0.

3.1.2 Limitations in Moving from Test to Production

Note the following limitations in moving from test to production:

- On Windows, with Oracle Data Integrator in your source environment, before you run the pasteConfig script, you must set HOSTNAME as a system variable

- If you are using Oracle Data Integrator on Windows, after you run the pasteConfig script, update the config.properties file with the following:

odi.shared.config.dir.path=%DOMAIN_HOME%/config/oracledi

- When you are moving Oracle Platform Security Services and the data is moving from LDAP to LDAP, the source and target LDAP domain component hierarchy must be same. If it is not, the Oracle Platform Security Services data movement will fail. For example, if the source is hierarchy is configured as dc=us,dc=com, the target LDAP must have the same domain component hierarchy.

- On Windows, Node Manager and any configured system components must be shut down before you run the copyConfig script.

- The movement scripts do not support environments where multitenancy is enabled.

- On Windows, the pasteConfig operation fails if the SSL-only mode is enabled in configurations that include both WebCenter Content and Capture. This is not an issue on Linux.
To work around this issue, before executing the movement scripts, enable non-SSL ports in addition to SSL ports. Then, run the copyBinary, paste Binary, copyConfig and pasteConfig scripts. After the scripts complete successfully, disable non-SSL ports on the target environment so that you have an SSL-only environment.

- When you execute pasteConfig and the archive contains Oracle Platform Security Services, the script may return the following errors:

oracle.security.audit.util.StrictValidationEventHandler handleEvent
WARNING: Failed to validate the xml content. Reason: cvc-complex-type.2.4.b:
The content of element '' is not complete. One of
'{"http://xmlns.oracle.com/ias/audit/audit-2.0.xsd":source}' is expected..
Apr 24, 2013 6:28:29 AM
oracle.security.audit.util.StrictValidationEventHandler handleEvent
WARNING: Failed to validate the xml content. Reason: cvc-complex-type.2.4.b:
The content of element '' is not complete. One of
'{"http://xmlns.oracle.com/ias/audit/audit-2.0.xsd":source}' is expected..

You can ignore these errors.

- When your environment includes Oracle Business Activity Monitoring, the bamcommand.log.0 log file may contain the following benign error message after you execute the pasteConfig script:

oracle.beam.impexp.commandline.util.ImportExportClient.main: Exception
occurred in method
Import/Export(-dbusername,DEFAULT,-dburl,DEFAULT,-dbdriver,DEFAULT,-cmd,import,
-file,/scratch/aime/t2pprodsoa/soa/bam/bin/BAMT2PEMSArtifacts.zip,-mode,append)
Exception: java.io.FileNotFoundException:
/scratch/oracle/t2pprodsoa/soa/bam/bin/BAMT2PEMSArtifacts.zip (No such file or directory)

You can ignore this message.

- When your environment includes Oracle Business Activity Monitoring, the log file may contain the following benign error message after you execute the copyConfig or pasteConfig scripts:

<Apr 29, 2014 1:04:39 AM MDT> <Warning> <JNDI> <BEA-050001>
<WLContext.close() was called in a different thread than the one in which it
was created.>

You can ignore this message.

- When you move any environment which contains a Web Tier component, such as Oracle HTTP Server, the copyBinary script may return the following message:

Warning Message  :1
Nov 20, 2014 10:47:57 - WARNING - CLONE-20266   Unable to archive a file.
Nov 20, 2014 10:47:57 - CAUSE - CLONE-20266   The file
"/scratch/oracle/webtier6400/network/log/cgisock.9465" did not have
sufficient permission to access.
Nov 20, 2014 10:47:57 - ACTION - CLONE-20266   Correct the permission of
above file and run copyBinary again.

You can safely ignore this message.

3.1.3 MDS purgeMetadata Command Can Take a Long Time

When autopurge is not enabled or manual purge is not frequently executed, the MDS database repository could have a lot of older (non-tip) versions accumulated. This can result in the next purge operation to take a very long time (possibly hours). In such a case, the purge operation may need to be terminated to avoid affecting the system performance. Currently, it is not possible to terminate the purge operation using Oracle Fusion Middleware tools. Instead, you need to do this at the database level.

To terminate the purge operation, contact the DBA. The DBA can identify the database session where the purgeMetadata operation is executing and kill the session to stop the purge. Note that MDS purges 300 documents in each iteration, commits the change, and repeats until all purgeable documents are processed. As a result, killing the database session will not affect already committed purge iterations.

3.1.4 SSL Certificate Chain Required on Certain Browsers

When you configure SSL for Oracle HTTP Server, you may need to import the entire certificate chain (rootCA, Intermediate CAs and so on).

Certain browsers, for example Internet Explorer, require that the entire certificate chain be imported to the browsers for SSL handshake to work. If your certificate was issued by an intermediate CA, you will need to ensure that the complete chain of certificates is available on the browser or the handshake will fail. If an intermediate certificate in the chain expires, it must be renewed along with all the certificates (such as OHS server) in the chain.

3.2 Configuration Issues and Workarounds

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

- Section 3.2.1, "Fusion Middleware Control Incorrectly Refers to Shared Service Tables"

3.2.1 Fusion Middleware Control Incorrectly Refers to Shared Service Tables

The Service table page of Fusion Middleware Control contains a mention of shared service tables. Shared service tables are not supported.

3.3 Documentation Errata for Administering Oracle Fusion Middleware

There are no documentation errata at this time.

4 High Availability

This chapter describes the issues related to Oracle Fusion Middleware high availability.

The following topics are covered in this chapter:

- Section 4.1, "Issues Pertaining to Automatic Service Migration"

- Section 4.2, "Issues Pertaining to Oracle BAM"

4.1 Issues Pertaining to Automatic Service Migration

This section contains the following topic:

- Section 4.1.1, "Oracle User Messaging Service 12c (12.1.3) Does Not Support Automatic Service Migration"

4.1.1 Oracle User Messaging Service 12c (12.1.3) Does Not Support Automatic Service Migration

In enterprise deployments that take advantage of high availability, Oracle recommends that you configure Oracle BAM to use Automatic Service Migration, which migrates specific services to a different Managed Server in the cluster when a server fails.

However, in some scenarios where Oracle BAM is producing constant and intensive User Messaging Service (UMS) messages, a Managed Server failure might leave some alert messages stuck in the UMS queues. This is because UMS 12c (12.1.3) does not currently support Automatic Service Migration.

To workaround this issue, you can recover messages in the UMS queues by restarting the failed Oracle BAM Managed Server. To resume the appropriate capacity and load sustainability after a BAM server failure, you must do two things:

- Restart the failed Managed Server.

- Fail back the migrated services to the original Managed Server.

For more information, see "Failing Back Oracle BAM Services After Automatic Service Migration Occurs" in Enterprise Deployment Guide for Oracle SOA Suite.

If a BAM server restart is not compatible with your system's recovery time objectives (RTO), then you can configure UMS with Advanced Queuing (AQ) JMS instead of the default JMS provider. For more information, see Appendix B, "Configuring User Messaging Service with AQ JMS," in Administering Oracle User Messaging Service.

4.2 Issues Pertaining to Oracle BAM

This section contains the following topic:

- Section 4.2.1, "Configuring Oracle BAM After Scale Up"

4.2.1 Configuring Oracle BAM After Scale Up

Oracle BAM requires additional configuration steps after you configure the domain. See the topic "Configuring BAM for High Availability" in the 12.1.3 version of the Oracle Fusion Middleware High Availability Guide.

5 Platform Security Services

This is chapter describes issues associated with Oracle Platform Security Services and Oracle Security Developer Tools. It includes the following topics:

- Configuration Issues and Workarounds

- Documentation Errata

5.1 Configuration Issues and Workarounds

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

- Section 5.1.1, "libOVD Move Plan Does Not Support Obfuscated Password"

- Section 5.1.2, "libovdconfig.bat script Does Not Support a Space in File Path"

- Section 5.1.3, "Property maxDirSize not used in Audit Service"

5.1.1 libOVD Move Plan Does Not Support Obfuscated Password

When you move from the Test to Production environment using pasteConfig, the move plan contains the configuration property Password File, which is a path to a file containing the back end LDAP server password for the adapter. In case of libOVD, obfuscated passwords are not supported for this configuration property.

The workaround is to use clear text password.

5.1.2 libovdconfig.bat script Does Not Support a Space in File Path

On the Microsoft Windows platform, the libovdconfig.bat script does not work if the path to your Java installation in the -jreLoc option includes a space character. For example, C:\Program Files\Java\jdk1.7.0_21.

The workaround is to provide the path to your Java installation in DOS 8.3 format.

For example:

-jreloc C:\Progra~1\Java\jdk1.7.0_21

5.1.3 Property maxDirSize not used in Audit Service

The configuration property maxDirSize has been deprecated in Release 12c. It is no longer used in the OPSS audit service.

5.2 Documentation Errata

There are no documentation errata.

6 Oracle User Messaging Service

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

It includes the following topics:

- Section 6.1, "Deprecation Notice"

- Section 6.2, "General Issues and Workarounds"

- Section 6.3, "Configuration Issues and Workarounds"

6.1 Deprecation Notice

Oracle User Messaging Service is deprecated in Release 12.2.1.

6.2 General Issues and Workarounds

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

- Section 6.2.1, "Extension Driver has Different Target Types for 11g and 12c"

- Section 6.2.2, "Node Manager Fails to Start After Configuring Oracle User Messaging Service and Oracle HTTP Server"

- Section 6.2.3, "Messages Metrics Rendered as Unavailable in the Performance Page for User Messaging Server"

- Section 6.2.4, "User Messaging Service URLs Unavailable After Restart"

- Section 6.2.5, "User Messaging Service Upgrade from 11g to 12c may Fail"

- Section 6.2.6, "Duplicate Messages Rendered in Twitter Driver"

- Section 6.2.7, "Exceptions Occur while Registering Multiple Drivers and Access Points"

- Section 6.2.8, "User Messaging Service schema does not have connect button in the Upgrade Assistant"

- Section 6.2.9, "Message resend from EM Message Status page failed"

6.2.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.2.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.

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

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

6.2.4 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.5 User Messaging Service Upgrade from 11g to 12c may Fail

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

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

6.2.6 Duplicate Messages Rendered in Twitter Driver

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. As a workaround, if you want to handle every tweet only once, you can use the header containing the Twitter Id.

6.2.7 Exceptions Occur while Registering Multiple Drivers and Access Points

Issue and Workaround

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

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

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. The workaround is to manually enter the value for schema name.

6.2.9 Message resend from EM Message Status page failed

- Section 6.2.9.1, "Resend for deployment with unclustered managed servers"

- Section 6.2.9.2, "Resend for deployment with multiple clusters"

6.2.9.1 Resend for deployment with unclustered managed servers

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

6.2.9.2 Resend for deployment with multiple clusters

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.

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.

6.3 Configuration Issues and Workarounds

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

- Section 6.3.1, "Use Correct SSL Trust Store When Configuring Drivers"

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

7 Web Services

This chapter describes issues associated with Web services development, security, and administration, including Oracle Web Services Manager.

It includes the following topics:

- Upgrade Fails When OWSM Data Source is Configured as Multi Data Source

- Using a Repository Backed by a Hardened Oracle Database

- Using Multibyte User Credentials with wss_http_token_* Policy

- Performing a Bulk Upload of Policies

- Removing Post-deployment Customizations

- Reviewing Localization Limitations

- Fusion Middleware Control Does Not List Policies When Two Servers Are SSL Enabled (Two-way SSL)

- Web Service Test Page Cannot Test Input Arguments Bound to SOAP Headers

- Possible Limitation When Using Custom Exactly-one Policies

- Security Policies Do Not Work on Subscriber Mediator Component

- Policy Table Might Not Show Attached Policies for Some Locales

- Restart Applications to Get an Accurate Policy Usage Count

- Performance Improvements In Web Services Policy Pages

- Bulk Attachment of Policies Is not Supported In the Current Release

- Enterprise Manager Returns You to the OWSM Policies Page After Editing a Client Policy

- JKS Configuration Screen Displays Incorrect Values

- Domain Configuration Is Not Supported in Classpath Mode

- Apply/Revert Buttons Are Not Activated After Editing SAML Trust on Authentication Tab of OWSM Domain Configuration Page

- Query by Example Feature is Not Working

- Avoiding XML Encryption Attacks

- OWSM Introspection Plug-in Fails When Proxy Is Configured Incorrectly

- Cross-Domain Policy Manager Configuration Is Not Supported In this Release

- USERNAME_ID_PROPAGATION Policies Deprecated

- Deprecated Commands for Oracle Infrastructure Web Services

- Test Web Service Page Does Not Generate the Correct Date/Date Time Patterns When Importing a Locally Saved Payload

- Test Web Service Page Does Not Save Loaded Payloads In the Correct Format

- Using the Automatic Policy Configuration for STS May Not Result in a Compatible Policy for a Web Service Client

- Incompatible Policies Listed for Web Services and Clients Using SOAP Over JMS Transport

- Unsupported Make Connection Policy/ Assertion Template Category Shown In Fusion Middleware Control

- NoSuchObjectException when Server Hosting WSM-PM is Shut Down

- Harmless Warning Message when Creating Policy Sets

- Difference between Installed and Upgraded Configuration Files

- Oracle Infrastructure Web Service Applications Built in 11g Containing WebServiceRef Annotation Will Fail

- WADL for OPSS and OWSM REST APIs not Generated from Browser

Note:
For WebLogic Web Services, see "Web Services and XML Issues and Workarounds" in the Oracle Fusion Middleware Release Notes for Oracle WebLogic Server.

7.1 Upgrade Fails When OWSM Data Source is Configured as Multi Data Source

When attempting to upgrade Weblogic and Oracle SOA Suite from 11g to 12c Release 12.13 and later, when the 11g instance uses a mds-owsm datasource that is configured to be a multi data source, the Upgrade Assistant is failing with the following error:

WSM] [INCIDENT_ERROR] [] [upgrade.WSM.WSMPLUGIN] [tid: 63] [ecid: 235be93f-e646-47fb-b960-34947fed8f86-00000001,0] [[
oracle.ias.update.exception.UpgradeException: WSMERROR-00015: Failed to read the Oracle WSM datasource connection details.
at oracle.wsm.lifecycle.upgrade.impl.WSMUpgradePlugin.initializePluginData(WSMUpgradePlugin.java:227)
at oracle.wsm.lifecycle.upgrade.impl.WSMUpgradePlugin.upgrade(WSMUpgradePlugin.java:263)
at oracle.ias.update.plugin.Plugin.upgrade(Plugin.java:576)
at oracle.ias.update.plan.PlanStep.upgrade(PlanStep.java:377)
at oracle.ias.update.UpgradeDriver.doUpgrades(UpgradeDriver.java:947)
at oracle.ias.update.gui.UAUpgradeThread.run(UAUpgradeThread.java:41)

Note:
This error occurs even after applying patch 19865550 to prevent "AN UNSUPPORTED MULTIDATASOURCE" message.

To work around this issue, perform the following steps:

1. Modify the mds-owsm data source, changing it from a multi data source to a generic data source.

2. Run the Upgrade Assistant.

3. Once the upgrade completes successfully, if necessary, modify the data source back to it's original configuration.

7.2 Using a Repository Backed by a Hardened Oracle Database

Oracle Web Services Manager uses an MDS repository to store metadata such as policies, assertion templates, and policy usage data.

Oracle Web Services Manager 12c (12.2.1) is certified to work with a repository backed by a hardened Oracle Database.

For more information about the repository, see "Managing the OWSM Repository" in Securing Web Services and Managing Policies with Oracle Web Services Manager

7.3 Using Multibyte User Credentials with wss_http_token_* Policy

In this release, multibyte user credentials are not supported for the wss_http_token_* policies. If multibyte user credentials are required, use a different policy, such as wss_username_token_* policy. For more information about the available policies, see "Predefined Policies" in Securing Web Services and Managing Policies with Oracle Web Services Manager.

7.4 Performing a Bulk Upload of Policies

When performing a bulk import of policies to the MDS repository, if the operation does not succeed initially, retry the operation until the bulk import succeeds.

For the most part, this can occur for an Oracle RAC database when the database is switched during the metadata upload. If there are n databases in the Oracle RAC database, then you may need to retry this operation n times.

For more information about bulk import of policies, see "Migrating Policies" in the Administering Web Services.

7.5 Removing Post-deployment Customizations

When the connections.xml file is changed after deployment using the AdfConnection MBean, the complete connection is saved as a customization. This means that changes to the connection in a redeployed application are overwritten by the customization.

When you use Fusion Middleware Control to make changes to an application's connections.xml file after deployment, a new connections.xml file is created as a customization and stored in the MDS repository. This customization persists for the life of the application. Therefore, if you redeploy the application, the customized connections.xml file continues to be applied as a customization on the application.

To allow the redeployed application's connections.xml file to be applied without the prior customization (from Fusion Middleware Control), you must explicitly remove the connections.xml customizations from the MDS repository.

For example, if you deploy an application with a Web services data control, then use Fusion Middleware Control to attach the username_token_client_policy, and subsequently detach the policy. Then, you return to JDeveloper to edit the application and attach the http_token_client_policy, and redeploy the application. When you view the application using Fusion Middleware Control, you see that it is not using the http_token_client_policy that you attached. That is because it is using the customized connections.xml file that you previously created using Fusion Middleware Control.

If you remove the connections.xml customizations from the MDS repository, the application will use the its own connections.xml file.

7.6 Reviewing Localization Limitations

The following information is supported in English only in this release of Oracle Enterprise Manager:

- All fields in the policy and assertion template except the orawsp:displayName field.

- If using the ?orawsdl browser address, the orawsp:description field.

7.7 Fusion Middleware Control Does Not List Policies When Two Servers Are SSL Enabled (Two-way SSL)

When a Managed Server is Two-way enabled SSL (for example, a SOA server hosting OWSM Policy Manager over Two-way SSL) and the Administration Server hosting Fusion Middleware Control is correctly configured to access the Two-way SSL-enabled Managed Server, Fusion Middleware Control still does not list the OWSM policies.

7.8 Web Service Test Page Cannot Test Input Arguments Bound to SOAP Headers

For Web services that have any input arguments bound to SOAP headers, the Test Web Service page in the Fusion Middleware Control console cannot show the message. Therefore, such operations cannot be tested with the Test Web Service page.

For example, if the input for a multi-part WSDL is viewed through Fusion Middleware Control, and one input argument is bound to a SOAP header, the composite instance fails with the following exception because the other part of the message was missing in the input:

ORAMED-01203:[No Part]No part exist with name "request1" in source message

To resolve such an issue, select XML View for Input Arguments and edit the payload to pass input for both parts of the WSDL.

7.9 Possible Limitation When Using Custom Exactly-one Policies

In some cases, there can be a limitation when using custom Exactly-one policies. For a set of assertions within the exactly-one policy, if a request message satisfies the first assertion, then the first assertion gets executed and a response is sent accordingly. However, this may not be the desired behavior in some cases because the request may be intended for the subsequent assertions.

For example, you may have a client policy that has Timestamp=ON and a service exactly-one policy that has a wss11 username token with message protection assertions: the first has Timestamp=OFF; the second has Timestamp=ON. Therefore, the first assertion in the service exactly-one policy is not expecting the Timestamp in the request, yet the second assertion does expect it. In this case, the first assertion gets executed and the response is sent with no Timestamp. However, the client-side processing then fails because it expects the Timestamp that was sent in the request.

This limitation can exist with any cases where a client policy expects a greater number of elements to be signed and a service policy does not.

7.10 Security Policies Do Not Work on Subscriber Mediator Component

Component Authorization denyall policy does not work at subscriber mediator component. Authorization policy works for other normal mediator component cases.

7.11 Policy Table Might Not Show Attached Policies for Some Locales

Select the Web service application in Fusion Middleware Control and navigate to the Web service endpoint. Attach a policy to the endpoint in the Attach/Detach page. Sometimes the Directly Attached Polices table might not display the attached policies for the following locales: zh-cn, zh-tw, ja, pt-br, es, fr, ko.

As a workaround, enlarge the columns.

7.12 Restart Applications to Get an Accurate Policy Usage Count

If a policy that is being referred to by a Web Service is deleted and then re-imported, then its usage count will not be correct and application(s) must be restarted to obtain an accurate usage count.

7.13 Performance Improvements In Web Services Policy Pages

Performance improvements have been made to the Web Services Policy pages in Fusion Middleware Control by removing the unnecessary role query.

7.14 Bulk Attachment of Policies Is not Supported In the Current Release

Attaching one or more policies to one or more Web services using the bulk attachment feature is not supported in the current release. Please use the Policy Set feature instead. For more information on Policy Sets, see "Attaching Policies Globally Using Policy Sets Using WLST" and "Schema Reference for Policy Sets" in Securing Web Services and Managing Policies with Oracle Web Services Manager.

7.15 Enterprise Manager Returns You to the OWSM Policies Page After Editing a Client Policy

When you generate client policies in Enterprise Manager, the Generate Client Policies page is displayed and the generated policies are shown as Not saved. Once you save the policies, and then edit one of them, you are returned to the OWSM Policies page. This is an error in Enterprise Manager. You should be returned to the Generate Client Policies page.

To edit additional policies, use the search feature in the OWSM Policies page to locate the client policy you wish to edit.

For more information, see "Generating Client Policies from a WSDL" in Securing Web Services and Managing Policies with Oracle Web Services Manager.

7.16 JKS Configuration Screen Displays Incorrect Values

If you configure the OWSM keystore for KSS and then attempt to configure the JKS keystore, the Path field and the Key menus in the JKS configuration screen are populated with the values for the KSS keystore.

Workaround: Clear the Path and Key fields in the JKS configuration screen before configuring the JKS keystore. For information on configuring JKS keystore in OWSM, see "Configuring OWSM to Use the JKS Keystore" in Securing Web Services and Managing Policies with Oracle Web Services Manager

7.17 Domain Configuration Is Not Supported in Classpath Mode

If the Policy Manager URL is configured as a classpath, then domain-level configuration is not supported. All domain-level configuration information is stored in the OWSM repository, and not the JAR file that is included in the classpath. For information about configuring the Policy Manager URL, see the following sections in Securing Web Services and Managing Policies with Oracle Web Services Manager:

- "Configuring the Policy Manager Connection Using Fusion Middleware Control"

- "Configuring the Policy Manager Connection Using WLST"

If you wish to manage domain-level configuration, configure the Policy Manager URL to specify a remote domain or use auto mode. Once you have configured the new Policy Manager URL mode, you must restart the server for it to take effect.

7.18 Apply/Revert Buttons Are Not Activated After Editing SAML Trust on Authentication Tab of OWSM Domain Configuration Page

When editing the SAML trusted issuers and DN lists on the Authentication tab of the OWSM Domain Configuration page, as described in "Configuring SAML Trusted Issuers and DN Lists Using FMC" in Securing Web Services and Managing Policies with Oracle Web Services Manager, the Apply and Revert buttons are not activated until you edit another field on the page. If necessary, make "dummy" edits in another field to activate the buttons.

7.19 Query by Example Feature is Not Working

"Using the Query by Example Filter" (for Web Service policies) and "Using the Query by Example Filter" (for assertion templates) in Securing Web Services and Managing Policies with Oracle Web Services Manager describe how to search for policies and assertion templates by querying on a specific field. This feature is not working in the current release.

Workaround: To work around this issue, use the advanced search utility as described in "Using Advanced Search" (for Web Service policies) and in "Using Advanced Search" (for assertion templates) in Securing Web Services and Managing Policies with Oracle Web Services Manager.

7.20 Avoiding XML Encryption Attacks

In past releases, OWSM sent different fault codes (for example, FailedAuthentication, InvalidSecurityToken, FailedCheck, and so on) for different error cases In the current release, this default behavior has been changed. OWSM now sends the InvalidSecurity fault code for all error cases. This has been done to avoid XML encryption attacks. An encryption attack is possible if the service sends different fault codes for different types of errors (for example, FailedAuthentication, InvalidSecurityToken, FailedCheck, and so on).This default behavior can be changed by setting the domain-wide agent property use.unified.fault.code to false. However, this is not recommended, because it might allow XML encryption attacks. The default value for this property, "true", will cause OWSM to send the InvalidSecurity fault code for all error cases. For more information on the use.unified.fault.code property, see "Configuring Security Policy Enforcement Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.

7.21 OWSM Introspection Plug-in Fails When Proxy Is Configured Incorrectly

OWSM provides an introspection plug-in for Oracle Virtual Assembly Builder, which is a tool for virtualizing installed Oracle components, modifying those components, and then deploying them into an Oracle VM environment. For more information, see "OWSM Introspection Plug-in for Oracle Virtual Assembly Builder" in Securing Web Services and Managing Policies with Oracle Web Services Manager.

The OWSM introspection plug-in executes when you introspect a WebLogic domain using the abctl introspectWLS12 command or Oracle Virtual Assembly Builder Studio (abstudio.sh). This introspection may fail in the following conditions:

- When the Administration Server listen address is configured to listen on a particular address that is different than localhost.
Workaround:

Clear the Administration Server listen address in the Administration Console to enable the local address to be in effect, as described in "Configure listen address" in Oracle WebLogic Server Administration Console Online Help.

Then, set the Administration Server listen address to localhost.

- When proxy setting is performed during introspection. This introspection may fail when a proxy server is required in your networking environment and no proxy configuration is available to the tool being used to perform the introspection (for example, abctl or abstudio.sh).
Workaround:

If you are introspecting using abstudio.sh, you must bypass the proxy setting for localhost. Please consult the Release Notes for Oracle Virtual Assembly Builder for information about configuring the proxy.

If you are introspecting with abctl, use the standard proxy configuration properties for Java applications. Before issuing the abctl command, set the properties in your environment using the SYSPROPS environment variable to bypass the proxy setting for localhost. For example, use one of the following commands, based on your shell:

csh: setenv SYSPROPS '-Dhttp.proxyHost=myProxyHost -Dhttp.proxyPort=NN -Dhttp.nonProxyHosts=localhost|n.n.n.n

sh/bash/ksh: export SYSPROPS '-Dhttp.proxyHost=myProxyHost -Dhttp.proxyPort=NN -Dhttp.nonProxyHosts=localhost|n.n.n.n

Note:
The actual proxy settings will be specific to your environment.

7.22 Cross-Domain Policy Manager Configuration Is Not Supported In this Release

In this release, configuration to a Policy Manager in a remote domain is not supported.

7.23 USERNAME_ID_PROPAGATION Policies Deprecated

The following USERNAME_ID_PROPAGATION policies are deprecated in Release 12c (12.2.1):

wss10_username_id_propagation_with_msg_protection_client_policy
wss10_username_id_propagation_with_msg_protection_service_policy

For details about these policies, see "Oracle Web Services Manager Predefined Policies" in Securing Web Services and Managing Policies with Oracle Web Services Manager.

7.24 Deprecated Commands for Oracle Infrastructure Web Services

Table 7-1 lists the WLST commands for Oracle Infrastructure Web Services (or clients) that were available in Oracle Fusion Middleware 11g release and which have been deprecated in 12c (12.1.2). In addition, the table lists the new WLST command equivalent and provides an example of how you can update your code use the new command.

For more information about the WLST commands, see "Web Services Custom WLST Commands" in WLST Command Reference for Infrastructure Components.

Table 7-1 Deprecated Commands for Oracle Infrastructure Web Services

Deprecated Command (11g)

Recommended Command (12c)

Updating Your Code

abortRespositorySession

abortWSMSession

11g Release (for Repository operations):

wls:/jrfServer_domain/serverConfig> abortRepositorySession()

12c Release (for both Repository and PolicySubject operations):

wls:/jrfServer_domain/serverConfig> abortWSMSession()

attachPolicySet

setWSMPolicySetScope

11g Release:

wls:/jrfServer_domain/serverConfig> attachPolicySet ('Domain("base_domain")')

12c Release:

wls:/jrfServer_domain/serverConfig> setWSMPolicySetScope ('Domain("base_domain")')

attachPolicySetPolicy

attachWSMPolicy

attachWSMPolicies

11g Release (for both Repository and PolicySubject operation on policy set):

wls:/jrfServer_domain/serverConfig> attachPolicySetPolicy ('oracle/wss_username_token_service_policy')

12c Release:

wls:/jrfServer_domain/serverConfig> attachWSMPolicy('oracle/wss_username_token_service_policy')

wls:/wls-domain/serverConfig>attachWSMPolicies(["oracle/wss_username_token_client_policy","oracle/log_policy"])

beginRespositorySession

beginWSMSession

11g Release (for Repository operations):

wls:/jrfServer_domain/serverConfig> beginRepositorySession()

12c Release (for both Repository and PolicySubject operations):

wls:/jrfServer_domain/serverConfig> beginWSMSession()

clonePolicySet

cloneWSMPolicySet

11g Release:

wls:/jrfServer_domain/serverConfig> clonePolicySet ('myNewPolicySet', 'myPolicySet')

12c Release:

wls:/jrfServer_domain/serverConfig> cloneWSMPolicySet ('myNewPolicySet', 'myPolicySet')

commitRespositorySession

commitWSMSession

11g Release (for Repository operations):

wls:/jrfServer_domain/serverConfig> commitRepositorySession()

12c Release (for both Repository and PolicySubject operations):

wls:/jrfServer_domain/serverConfig> commitWSMSession()

createPolicySet

createWSMPolicySet

11g Release:

wls:/jrfServer_domain/serverConfig> createPolicySet('myPolicySet', 'ws-service', 'Domain("base_domain")')

12c Release:

wls:/jrfServer_domain/serverConfig> createWSMPolicySet ('myPolicySet', 'ws-service', 'Domain("base_domain")')

deletePolicySet

deleteWSMPolicySet

11g Release:

wls:/jrfServer_domain/serverConfig> deletePolicySet('myPolicySet')

12c Release:

wls:/jrfServer_domain/serverConfig> deleteWSMPolicySet ('myPolicySet')

describeRespositorySession

describeWSMSession

11g Release (for Repository operations):

wls:/jrfServer_domain/serverConfig> describeRepositorySession()

11g Release (for PolicySubject operations):

N/A

12c Release (for both Repository and PolicySubject operations):

wls:/jrfServer_domain/serverConfig> describeWSMSession()

detachPolicySet

detachWSMPolicy

detachWSMPolicies

11g Release (for both Repository and PolicySubject operation on policy set):

wls:/jrfServer_domain/serverConfig> detachPolicySet ('oracle/wss_username_token_service_policy')

12c Release:

wls:/jrfServer_domain/serverConfig> detachWSMPolicy('oracle/wss_username_token_service_policy')

wls:/wls-domain/serverConfig>detachWSMPolicies(["oracle/log_policy","oracle/wss_username_token_client_policy"])

displayPolicySet

displayWSMPolicySet

11g Release:

wls:/jrfServer_domain/serverConfig> displayPolicySet('myPolicySet')

12c Release:

wls:/jrfServer_domain/serverConfig> displayWSMPolicySet ('myPolicySet')

enablePolicySet

enableWSMPolicySet

11g Release:

wls:/jrfServer_domain/serverConfig> enablePolicySet(true)

12c Release:

wls:/jrfServer_domain/serverConfig> enableWSMPolicySet(true)

enablePolicySetPolicy

enableWSMPolicy

enableWSMPolicies

11g Release:

wls:/wls-domain/serverConfig>enablePolicySetPolicy('/oracle/log_policy',false)

12c Release:

wls:/wls-domain/serverConfig>enableWSMPolicy('/oracle/log_policy',false)

wls:/wls-domain/serverConfig>enableWSMPolicies(["oracle/log_policy", "oracle/wss_username_token_client_policy"], true )

exportRepository

exportWSMRepository

11g Release:

wls:/jrfServer_domain/serverConfig> exportRepository ("/tmp/repo.zip")

12c Release:

wls:/jrfServer_domain/serverConfig> exportWSMRepository ("/tmp/repo.zip")

importRepository

importWSMArchive

11g Release (for repository documents):

wls:/jrfServer_domain/serverConfig> importRepository ("/tmp/repo.zip")

12c Release (for repository documents):

wls:/jrfServer_domain/serverConfig> importWSMArchive ("/tmp/repo.zip")

listPolicySets

listWSMPolicySets

11g Release:

wls:/wls-domain/serverConfig>listPolicySets('sca-reference')

12c Release:

wls:/wls-domain/serverConfig>listWSMPolicySets('sca-reference')

migrateAttachments

migrateWSMAttachments

11g Release:

wls:/jrfServer_domain/serverConfig> migrateAttachments()

12c Release:

wls:/jrfServer_domain/serverConfig> migrateWSMAttachments()

modifyPolicySet

selectWSMPolicySet

11g Release:

wls:/jrfServer_domain/serverConfig> modifyPolicySet('myPolicySet')

12c Release:

wls:/jrfServer_domain/serverConfig> selectWSMPolicySet ('myPolicySet')

resetWSMPolicyRepository

restWSMRepository

11g Release:

wls:/jrfServer_domain/serverConfig> resetWSMPolicyRepository()

12c Release:

wls:/jrfServer_domain/serverConfig> resetWSMRepository()

setConfiguration

setWSMConfiguration

11g Release

wls:/jrfServer_domain/serverConfig> setConfiguration('/WLS/myDomain')

12c Release

wls:/jrfServer_domain/serverConfig> displayWSMConfiguration('WLS/base_domain')

setPolicySetConstraint

setWSMPolicySetConstraint

11g Release:

wls:/jrfServer_domain/serverConfig> setPolicySetConstraint ('HTTPHeader("VIRTUAL_HOST_TYPE","external")')

12c Release:

wls:/jrfServer_domain/serverConfig> setWSMPolicySetConstraint ('HTTPHeader("VIRTUAL_HOST_TYPE","external")')

setPolicySetDescription

setWSMPolicySetDescription

11g Release:

wls:/jrfServer_domain/serverConfig> setPolicySetDescription ('Global policy set for web service endpoint.')

12c Release:

wls:/jrfServer_domain/serverConfig> setWSMPolicySetDescription ('Global policy set for web service endpoint.')

setWebServicePolicyOverride

setWSMPolicyOverride

11g Release:

wls:/jrfServer_domain/serverConfig> setWebServicePolicyOverride ('/base_domain/server1/HelloWorld#1_0','j2wbasicPolicy', 'web', '{http://namespace/}WssUsernameService','JRFWssUsernamePort', 'oracle/wss_username_token_service_policy', 'reference.priority', '10')

12c Release:

wls:/jrfServer_domain/serverConfig> setWSMPolicyOverride ('oracle/wss_username_token_service_policy', 'reference.priority', '10')

setPolicySetPolicyOverride

setWSMPolicyOverride

11g Release (for both Repository and PolicySubject operation on policy set):

wls:/jrfServer_domain/serverConfig> setPolicySetPolicyOverride ('oracle/wss_username_token_service_policy', 'reference.priority', '10')

12c Release:

wls:/jrfServer_domain/serverConfig> setWSMPolicyOverride ('oracle/wss_username_token_service_policy', 'reference.priority', '10')

upgradeWSMPolicyRepository

upgradeWSMRepository

11g Release:

wls:/jrfServer_domain/serverConfig> upgradeWSMPolicyRepository()

12c Release:

wls:/jrfServer_domain/serverConfig> upgradeWSMRepository()

validatePolicySet

validateWSMPolicySet

11g Release:

wls:/jrfServer_domain/serverConfig> validatePolicySet ('myPolicySet')

12c Release:

wls:/jrfServer_domain/serverConfig> validateWSMPolicySet ('myPolicySet')

7.25 Test Web Service Page Does Not Generate the Correct Date/Date Time Patterns When Importing a Locally Saved Payload

In Fusion Middleware Control, when testing a SOAP web service on the Test Web Service page, the Import Payload option does not generate the correct date/date time type patterns when importing a payload XML file, as follows:

- Tree View – The date time value is always formatted to a US pattern, such as Tue Dec 30 00:00:00 PST 2014, when the correct pattern should be YYYY-MM-ddTHH:mm:ss or YYYY-MM-dd.

- XML View – The server time zone is always incorrectly appended to the date, such as 2014-12-30-08:00, which is not part of the imported value.

Workaround:

Clear the imported date and date time values, and then manually enter the correct values before submitting the payload.

7.26 Test Web Service Page Does Not Save Loaded Payloads In the Correct Format

In Fusion Middleware Control, when testing a SOAP web service on the Test Web Service page, the Save Payload option incorrectly saves the loaded payload in Server Locale format (ISO-8859-1) instead of in UTF-8 format.

7.27 Using the Automatic Policy Configuration for STS May Not Result in a Compatible Policy for a Web Service Client

Using the automatic policy configuration for STS (Security Token Service) in OWSM may not result in a compatible policy.

Workaround:

You should manually configure the STS config policy from a web service client, as described in "Manually Configuring the STS Config Policy From the Web Service Client: Main Steps" in Securing Web Services and Managing Policies with Oracle Web Services Manager.

7.28 Incompatible Policies Listed for Web Services and Clients Using SOAP Over JMS Transport

In Fusion Middleware Control, when attaching OWSM policies to web services and clients that use SOAP over JMS transport, the list of available policies includes those that are not compatible.

For a list of compatible policies, refer to "Which OWSM Policies Are Supported for Web Services and Clients That Use SOAP Over JMS Transport" in Securing Web Services and Managing Policies with Oracle Web Services Manager.

7.29 Unsupported Make Connection Policy/ Assertion Template Category Shown In Fusion Middleware Control

In Fusion Middleware Control, the Make Connection category for OWSM policies and Assertion templates is included in the search drop-down menus on the WSM Policies and Assertion Template page. However, this category is not supported and should not be displayed.

7.30 NoSuchObjectException when Server Hosting WSM-PM is Shut Down

When the server on which the wsm-pm is running in a WebLogic domain is shut down before servers on other domains are shut down, you will see an exception as follows:

<Error> <oracle.wsm.resources.policymanager>
<WSM-02313> <The documents used by a policy subject cannot be recorded due to
underlying error "Exception during invoke."
java.rmi.NoSuchObjectException: Exception during invoke.

This error occurs as agents on other domains try to continue to talk to wsm-pm and are unable to do so since that WebLogic server has shut down.

This is expected behavior when wsm-pm is not available due to shutdown of the WebLogic server where it is deployed. No user action is needed.

7.31 Harmless Warning Message when Creating Policy Sets

When you create policy sets for resource type of "SOAP Web Service" or "SOAP Web Service Client", with non-security policy references attached, you will see a warning message:

"Non-Security policies do not apply to Java EE Web Services."

This is a harmless warning message which can be ignored.

7.32 Difference between Installed and Upgraded Configuration Files

These domain configuration files appear different in a new 12.2.1 install compared to an upgraded WebCenter Portal:

config/fmwconfig/audit-store.xml
config/fmwconfig/jps-config.xml
config/fmwconfig/jps-config-jse.xml

This occurs because, during upgrade, the configuration is moved to wsm-config.xml but not removed from the original files including jps-config.xml. There is no impact to functionality and the variation can be safely ignored.

7.33 Oracle Infrastructure Web Service Applications Built in 11g Containing WebServiceRef Annotation Will Fail

Oracle Infrastructure Web Services do not support the WebServiceRef annotation. In Release 11g, generated example code included this annotation. If you included this generated example code in your applications, they built and ran successfully because the annotation was ignored. In the CDI implementation in Java EE 7 in 12c (12.2.1), all annotations are processed. As a result, any applications built in Release 11g that contain these generated example classes ([Service]PortClient.java) will fail.

Note that Oracle Infrastructure Web Service applications built in 12c do not contain this annotation and do not exhibit this problem.

Workaround

Use one of the following solutions:

- Remove the offending WebServiceRef annotation from the generated source code in the application or library.
In the 11g Oracle Infrastructure Web Service WSA generated example client classes, the class name is always <Port Name>Client.java. You can remove the annotation by:

- Searching within your source code to find terms such as "*Client.java", or

- Writing a helper class to search the JAR/WAR/EAR code. For example:

private final static Class DefaultAnnotationTypeClass =
javax.xml.ws.WebServiceRef.class;
private void findAnnotation(Class targetClass, Class annotationTypeClass)
throws Exception {
if (targetClass == null || annotationTypeClass == null) {
return;
}
if (targetClass.getAnnotation(annotationTypeClass) != null) {
throw new Exception("Found " + annotationTypeClass + " in class "
+ targetClass.getName());
}
for (Field field : targetClass.getDeclaredFields()) {
if (field != null && field.getAnnotation(annotationTypeClass) !=
null) {
throw new Exception("Found " + annotationTypeClass + " in
class " + targetClass.getName());
}
}
}
...
findAnnotation( userPortClientClass , DefaultAnnotationTypeClass );
.

or

- For each WAR /JAR file, provide a beans.xml that disables CDI annotation scanning for the application. The necessary beans.xml snippet to turn off CDI annotation scanning is as follows:

<beans xmlns="http://xmlns.jcp.org/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee
http://xmlns.jcp.org/xml/ns/javaee/beans_1_1.xsd"
bean-discovery-mode="none">
</beans>

7.34 WADL for OPSS and OWSM REST APIs not Generated from Browser

WADL for OPSS REST APIs and OWSM REST APIs is not getting generated from the browser due to loading of XSL stylesheet.

Workaround

Instead of generating WADL from the browser by hitting URLs like:

http://myhost.mydomain.com:7001/idaas/platform/admin/v1/application.wadl
http://myhost.mydomain.com:7001/idaas/webservice/admin/v1/application.wadl

Use the Mozilla REST client to hit these URLs. The response will give the XML contents of WADL.

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2017, 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.