Known Issues for Oracle WebCenter Content
12c (12.2.1.2.0)
E77882-01
October 2016
Learn about the issues you may encounter when using Oracle WebCenter Content and how to workaround them.
12c (12.2.1.2.0) — October 2016
There are no known issues for 12c (12.2.1.2.0).
12c (12.2.1.1.0) — June 2016
General Issues and Workarounds
Using URLs With SSP Include and Exclude Filters
If URLs are used in the Include or Exclude Filters list then any periods ('.') will need to be escaped, otherwise the filter will fail. For example:
http://www\.oracle\.com/information/about\.html
Note that each '.' is escaped with '\'
Disabling the Folders_g Deprecation Alert
As there is an intent to deprecate Folders_g in a future release, an alert appears when Folders_g is enabled.
To prevent this alert from displaying, open the config.cfg file and set the following configuration value:
DisableFoldersgDeprecationMesssage=1
Note:
The Folders_g component is available and is supported in releases 12.2.1, 12.2.1.1.0, and 12.2.1.2.0. However, it will be removed in a future release and customers should make plans to migrate to FrameworkFolders.
Propagating the cwallet.sso Changes to Deployment Manager
The updates to the cwallet.sso file, in some cases, are not propagated from the UCM server to the Deployment Manager. In these cases, you must propagate the change manually.
The Oracle UCM server updates the cwallet.sso file located in
WAS_PROFILES/UCM_SERVER_NAME/config/cells/UCM_CELL_NAME/fmwconfig/
when it starts after completing configuration on the Post Install Configuration Page or after enabling PdfWatermark or BpelIntegration components. In these instances, propagate this change back to the Deployment Manager.
To do this, copy the cwallet.sso file to
WAS_PROFILES/DEPLOYMENT_MANAGER_NAME/config/cells/UCM_CELL_NAME/fmwconfig/
immediately after the start.
Configuration Issues and Workarounds
Setting Security Privileges for Modifying Contribution Folders
By default, users only need RW privileges to modify contribution folders (Folders_g), where before the default was that RWD or owner was required unless collaboration was enabled.
Users explicitly relying on RWD privileges must set the environment variable to allow for this. WebCenter users and those with no upgrade issues are not affected.
For those who require RWD rather than RW, set the variable as:
FoldersModifyWithRW=false
Windows: Using WebDAV on a Windows 7 Client <Include?>
If you use WebDAV on a Windows 7 client, consider the following issues:
Registry changes are necessary for WebDAV use.
Windows 7 will not connect to a WebDAV server running over HTTP and using HTTP basic authentication. To fix this, set these registry entries:
Set HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\ Services\WebClient\Parameters\BasicAuthLevel to 2.
Set HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\ Services\WebClient\Parameters\UseBasicAuth to 2.
By default, Office 2010 will not open documents over WebDAV using basic authentication over a non-SSL connection.
To get around this problem, you need to create a registry entry, HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Common\ Internet\BasicAuthLevel, and set it to 2.
The WebDAV implementation used by Windows 7 (Mini-Redirector) does not implement the WebDAV locking protocol correctly (still the case as of WebDAV version 6.1.7601.17514). This means that on a drag and drop using Explorer, you will get an error. The file will likely be checked in correctly, though.
To avoid the error, you can turn off the locking protocol through a registry setting. Set HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\ Services\WebClient\Parameters\SupportLocking to 0.
Drag and drop creates an empty first revision.
The WebDAV implementation used by Windows 7 (Mini-Redirector) creates an empty file for an initial revision on a drag and drop using Explorer. This just means that you will get two revisions for your first drag and drop of a file, and the first revision will be zero bytes.
The Network Location shortcut to WebDAV in Windows Explorer stops working.
The typical method for accessing and browsing the WebDAV share for Oracle WebCenter Content Server is through creating a network location in Explorer, as follows:
Select Computer in the Explorer navigation tree on the left, and select Add a network location on the right.
Enter the WebDAV URL to Content Server (http://..../_dav/cs/idcplg/webdav/).
Log in.
After you log in, a shortcut to the Content Server WebDAV URL will be displayed in Explorer under the list of drives for the client computer.
You will initially be able to access the WebDAV share for Content Server through this shortcut, as expected. However, once your session expires (typically after 2 hours of inactivity, as configured), you will not be able to access the WebDAV share through this shortcut again. The reason this occurs seems to be the way the shortcut data is stored and used for reconnecting.
If you delete the shortcut and re-create it the same way, it should work correctly.
Deleting a folder may cause a performance issue. The Windows 7 (Mini-Redirector) client will navigate the entire folder tree, deleting each item in the tree recursively. Microsoft's previous WebDAV client sent a single DELETE command to the server and relied on the server to perform the delete folder action. The new behavior may have performance and network traffic repercussions for large folder trees.
Deleting a folder shortcut will delete the contents of the entire tree. The base WebDAV protocol does not distinguish between shortcuts to folders and normal folders. That means deleting a folder shortcut will cause all the items contained in the target folder of the shortcut to be deleted. This will not typically happen with other WebDAV clients, like the Microsoft XP Web Folders implementation. The reason for this is the behavior described in item 4 above.
Setting the Connection Pool for an External LDAP ID Store on IBM WebSphere Application Servers
An LDAP server is not automatically installed and configured when you install Oracle WebCenter Content on IBM WebSphere Application Server - Network Deployment (ND) or IBM WebSphere Application Server. Before you can configure WebCenter Content, you must install and configure an external LDAP identity store for your WebCenter Content applications. For information about how to set up external LDAP identity stores, such as Oracle Internet Directory, see the "IBM WebSphere Identity Stores" section of the "Managing Oracle Fusion Middleware Security on IBM WebSphere" chapter of the Oracle Fusion Middleware Third-Party Application Server Guide.
After the LDAP identity store is set up for a cell, you must set the CONNECTION_POOL_CLASS property in the cell's jps-config.xml file to avoid excessive LDAP connections. You need to add the following property to the <serviceInstance> entry in the file:
<property name="CONNECTION_POOL_CLASS" value="oracle.security.idm.providers.stdldap.JNDIPool"/>
To set the connection pool for an external LDAP ID store on IBM WebSphere application servers:
Modify your cell's jps-config.xml file with a text editor:
Open the WAS_HOME/profiles/profile_name/config/cells/cell_name/fmwconfig/jps-config.xml file.
WAS_HOME is the location where the WebSphere application server is installed, DISK/IBM/WebSphere/Application Server by default, profile_name is the name of the WebSphere Deployment Manager profile for the cell, and cell_name is the name of the cell.
Specify the CONNECTION_POOL_CLASS property in the <serviceInstance> entry as follows:
<serviceInstance name="idstore.ldap.0" provider="idstore.ldap.provider">
<property name="subscriber.name" value="dc=us,dc=oracle,dc=com"/>
<property name="CONNECTION_POOL_CLASS" value="oracle.security.idm.providers.stdldap.JNDIPool"/>
<property name="bootstrap.security.principal.key" value="bootstrap_idstore"/>
<property name="idstore.type" value="OID"/>
<property name="ldap.url" value="ldap://example.com:3060"/>
<property name="bootstrap.security.principal.map" value="BOOTSTRAP_JPS"/>
<property name="user.login.attr" value="mail"/>
<property name="username.attr" value="mail"/>
<extendedProperty>
<name>user.search.bases</name>
<values>
<value>cn=Users,dc=us,dc=oracle,dc=com</value>
</values>
</extendedProperty>
<extendedProperty>
<name>group.search.bases</name>
<values>
<value>cn=Groups,dc=us,dc=oracle,dc=com</value>
</values>
</extendedProperty>
</serviceInstance>
Synchronize all managed nodes.
Restart all the servers.
For more information about installing and configuring Oracle WebCenter Content on WebSphere application servers, see the "Managing Oracle WebCenter Content on IBM WebSphere Application Servers" chapter of the Oracle Fusion Middleware Third-Party Application Server Guide.
Content Server Localization and Verbose Tracing
Enabling Content Server localization tracing with Verbose also enables strict error detection. As a result, Content Server throws an exception when it tries to localize a key that is not valid. When Content Server gets in this state, the only solution is to restart the server. To disable strict error detection for localization, set the parameter EnableLocalizationAssertions=false in the config.cfg file.
Limitation of httpoutgoing Provider in 12.2.1
In Release 12c (12.2.1) SHA1 usage was deprecated and replaced with SHA2 (SHA256) as part of a security bug. As a result, source and target both needs to be on 12.2.1. If one is trying to do 11g and 12.2.1 mixed testing it will not work as 11g is using SHA-1 whereas 12.2.1 is using SHA-2.
Note:
Any connection passwords created earlier to this fix needs to be recreated. Also, the corresponding providers making use of those connection passwords needs to be recreated.
Learn about the issues you may encounter when using Oracle WebCenter Content and how to workaround them.
12c (12.2.1.2.0) — October 2016
There are no known issues for 12c (12.2.1.2.0).
12c (12.2.1.1.0) — June 2016
General Issues and Workarounds
Using Firefox to Configure the Dashboard
"Drag and drop" functionality to move dashboard panels is not available when using the Firefox browser. Instead, you should remove the panel and re-insert a new panel in the proper location.
Learn about the issues you may encounter when using Oracle WebCenter Enterprise Capture and how to workaround them.
12c (12.2.1.2.0) — October 2016
There are no known issues for 12c (12.2.1.2.0).
12c (12.2.1.1.0) — June 2016
There are no known issues for 12c (12.2.1.1.0).
Oracle® Fusion Middleware Known Issues for Oracle WebCenter Content, 12c (12.2.1.2.0)
E77882-01
Copyright © 2016, Oracle and/or its affiliates. All rights reserved.
Documentation for administrators and developers that lists known issues for this release for Oracle WebCenter Content.
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, 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.