This chapter describes issues associated with Oracle WebCenter Content. It includes the following topics:
This section describes general issues and workarounds. It includes the following topics:
Oracle Site Studio does not support multibyte characters in any value that will be used in URLs, including site IDs, directory names, and page names.
Oracle Site Studio Publisher does not support multibyte characters.
The Inbound Refinery component WinNativeConverter requires the .NET Framework, but it can be either 3.5 or 4.x. The Microsoft .NET Framework 4 (Standalone Installer) is available at:
For the Oracle E-Business Suite and PeopleSoft managed attachment function in WebCenter Content, users are not granted access to managed attachment pages if their user locale does not match the server locale, which means they cannot view these pages.
If the Records Management feature is installed in an Oracle WebCenter Content product, xdoruntime.ear library needs to be added manually from the Oracle WebLogic administration console after a domain is created. A reference to the library must be added to the weblogic-application.xml file of the Oracle WebCenter Content EAR file before the managed server is started for the first time.
To add xdoruntime.ear to the WebLogic WebCenter Content domain, follow these steps:
After a domain is created, start the Admin Server only. If a managed WebCenter Content server has already been started, then the administrator will have to perform additional steps to add reference to the deployed WebCenter Content server instance later.
Open WebLogic console in browser. Click on Deployments in the left pane. Browse the pages to check if there is already a xdoruntime.ear file in the WebLogic administration console. If it is already present, then no more steps need to be performed.
If no xdoruntime.ear file is present, click Install on the Deployments display. A file selection dialog opens. Browse the available file system and select xdoruntime.ear in the following path:
Click Next. The option page to select the file as library opens. Select "Install this deployment as a library" and click Next.
The Target Selection Screen opens. Select all targets and click Next.
The Deployment Name screen opens. In the Security section, select "DD Only: Use only roles and policies that are defined in the deployment descriptors." In the Source accessibility section, select "Copy this application onto every target for me" and click Next.
In the Additional Configuration section, select "Yes, Take me to the deployment's configuration screen" and click Finish. The library is now deployed in the environment.
To reference the deployed library from the WebCenter Content Enterprise Application library, follow these steps:
Extract the cs.ear file from the following path:
In the extracted directory modify META-INF/weblogic-application.xml and add the following line for library reference:
<library-ref> <library-name>oracle.xdo.runtime</library-name> </library-ref>
Create an archive file named cs.ear from the extracted modified directory and replace the file by the same name in the path it was retrieved from. This change will take for all undeployed WebCenter Content server instances.
Start the managed server.
If the managed server has been started at least once after the domain has been created, complete the following:
Locate the weblogic-application.xml of the Oracle WebCenter Content enterprise application in the deployed WebCenter Content domain at a path similar to the following example:
/FMW_HOME/domain path/servers/UCM_server1/servers/UCM_server1/tmp/_WL_user/Oracle Universal Content Management - Content Server/k6ggd/META-INF/weblogic-application.xml
Modify the META-INF/weblogic-application.xml and add the following line for library reference:
<library-ref> <library-name>oracle.xdo.runtime</library-name> </library-ref>
If the UCM_server1 is not available in /FMW_HOME/domain path/servers/, then this step is not needed, as the managed server has not been started, which would have deployed the UCM_server1 at this location.
When backing up a Site Studio website using Chrome, and manage the archive and download as a ZIP file, the name of the ZIP file might not be as expected.
The name of an archive downloaded as a ZIP file should be in this format: server_DDMMYYYY_HHMMSS.zip. But when using Chrome, the name may be idcplg.zip.
When using the Trays view with Site Studio on the Content Server, some screens viewed with the Firefox browser may not correctly fill the browser window.
Kofax 9 does not install VB6 components required for many of the Export Connectors. Install and register the required VB6 components to use the Export Connectors.
On Windows XP, Oracle WebCenter Content: Desktop shows a special icon overlay for offline content servers in the Oracle Content Servers tree in Windows Explorer (a red circle with a red diagonal line). This icon overlay is not displayed on Windows Vista and Windows 7. You can see if a server is offline in its details pane.
The Microsoft Office integration provided by Oracle WebCenter Content: Desktop allows you to open an older revision of a managed file in the Office application. However, this feature is not available in Microsoft Excel. Please note this is not a bug in Desktop, but rather a limitation in Excel, which does not allow two files with the same file name to be opened simultaneously.
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:
Note the '.' have been escaped with '\'
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:
Note:The Folders_g component is available and supported in release12.2.1 and also in release12.2.2. However, it will be removed in a future release and customers should make plans to migrate to FrameworkFolders.
On a Windows 7 or Vista system, Microsoft Office documents may become corrupted if you drag and drop them from an Oracle WebCenter Content: Desktop content folder in Windows Explorer to a location outside Content Server, particularly documents in native Office 2007/2010 format (
If you want to edit a document, you should use the Check Out or Available Offline (previously the Make Available Offline) item on the context menu.
If you have administration privileges, you can disable the DesktopTag component before performing a drag and drop operation, to avoid document corruption.
Once UCM managed server is started, errors of the kind
!csSchemaUnableToPublishView can sometimes be seen. These errors happen only when UCM is in EBR mode.
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
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
immediately after the start.
When using the WebCenter Content user interface (as opposed to the native interface) to work with a multi-level folder tree and doing a right-click on a sub-folder to display the "Show on Top" context menu option, the option is not always immediately displayed. Also, when the option does display, it does not always immediately function when clicked.
A workaround is always select the folder first (by doing a left-click), then do a right-click to invoke the context menu.
When using the WebCenter Content user interface (as opposed to the native interface) and Internet Explorer version 11 to select multiple files to upload, clicking on the row does not expand the metadata window. This is inconsistent with behavior in Firefox version 31 or newer, and in Chrome version 43 or newer.
A workaround is to click a file name to expand the metadata window.
When using the WebCenter Content user interface (as opposed to the native interface) and Chrome, the presence of the Ask.com toolbar disables dropdown menu functionality. A workaround is to remove the Ask.com toolbar.
By default the AutoSuggest index engine splits a term into grams and stores them in the index. For better performance the minimum gram length is set to a default of 2. Because the minimum gram length is 2, users cannot select user and role names that are only one character in length. Avoid creating documents, folders, libraries, users, and roles with a single character name.
New revisions of documents are not searchable in both the CS Native UI and ADFUI, when the Oracle Database 11g Enterprise Edition Release 22.214.171.124.0 is used. To fix this issue, apply DB patch 16892262 against the ORA DB 126.96.36.199.0 for the new revisions of documents to be searchable and displayed in both CS Native UI and ADFUI.
The 12.2.1 release includes an Imaging Migration Tool that helps in migrating imaging documents to the latest version of WebCenter Content. This is accessed from the Administration tray, Imaging Migration Administration, then Migration Admin Control.
The Imaging Migration Tool does not work when German (de) is selected as the user locale. It works in all other languages.
The Microsoft Edge browser on Windows 10 does not support JAVA PlugIns.
When using workflow in WebCenter Content User Interface (as opposed to the native interface), make sure that you have enabled Access Control List in the Content Server configuration.
To enable Access Control List in Content Server, open the
config.cfg file and set the following configuration value:
This section describes configuration issues and their workarounds. It includes the following topics:
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:
When integrating WebCenter Content with Oracle Access Manager 11g, add the following to the Logout URL setting for the WebGate:
JpsUserProvider should be up for WebCenter Content to be able to fetch users' roles/groups from the LDAP server. The JPS layer does not automatically pick up the SSL truststore configuration from WLS. Since a custom truststore is being used in the WLS configuration, the problem is that the JPS connection to ActiveDirectory is not using this custom truststore.
Therefore, set the following Java properties when starting UCM_server1:
Djavax.net.ssl.trustStore=<location of custom truststore> Djavax.net.ssl.trustStorePassword=<truststore password>
If you start the server from the command line using startManagedWeblogic.sh you can set the environment variable
EXTRA_JAVA_PROPERTIES before invoking
If you start the server using the NodeManager, these can be set using the WLS Admin console by setting the Arguments in the Server Start tab for the Configuration of UCM_server1.
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:
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,
, and set it to
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
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
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.
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"/>
Modify your cell's
jps-config.xml file with a text editor:
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.
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.
The electronic signature authentication process has been redesigned to include changes to the ESIG_GET_SIGN_CONTENT_FORM and ESIG_SIGN_CONTENT services in order to redirect users to the Oracle WebLogic Server login page before they can sign content items.
The Sign Content Item page has a time limit cookie (the default is 2 minutes) for re-authenticating users before signing content items. The cookie timeout can be reconfigured by setting the
ESigCookieTimeOut property (with the value in seconds) in the
electronicsignatures_environment.cfg file. For example, to set the cookie timeout value to 30 seconds, specify the following:
For systems using the WebCenter Content user interface instead of the native interface, the administrator must set the application configuration property
temporaryDirectory to a safe location that does not automatically get cleaned up by the operating system or other scheduled jobs.
For example, if the temporaryDirectory property is not set, on the Linux operating system it defaults to
/tmp. Many Linux distributions include
cron jobs that automatically clean up the
/tmp directory. If this happens, the application cannot recover from this unexpected error and it needs to be restarted.
For systems using the WebCenter Content user interface instead of the native interface, the configuration parameter
maximumWindowsPerSession is used to limit the number of active Doc Properties windows. The default is set to 7. If the WebCenter Content instance is experiencing higher than desired memory consumption, the setting can be changed to 4 to reduce the required heap size.
The AutoSuggestConfig component is a new feature that is valid only with the WebCenter Content user interface, not with the native interface. When using the WebCenter Content user interface the AutoSuggestConfig components is required and must be enabled. When using the native interface, the AutoSuggestConfig component must be disabled.
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
In Release 12c (12.2.1)
SHA1 usage was deprecated and replaced with
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
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.
This section describes documentation errata. It includes the following topics:
Update component configuration information included in the 188.8.131.52.0 documentation set is not included in the 184.108.40.206.0, 220.127.116.11.0, and 18.104.22.168.0 documentation sets. The information in section A.3.7 "Update Component Configuration Interface" in the 22.214.171.124.0 Oracle WebCenter Content System Administrator's Guide for Content Server is valid and can be viewed on the Oracle online documentation library at
The Need to Know (NTK) component is documented in Appendix B of the Administering Oracle WebCenter Content guide. The following note is to be included:
Note:Only users with an Admin role can download the file from the search results. Other users can see the file in the search results but cannot download the file or see its document information.
The following information is missing in Section B.5.3 Search Results Configuration Information Page for the Script element:
|Script (continued)||getNativeFile: enabled: Set to 0 to disable the
While checking in a document the user needs to be given Admin privileges Read, Write, Delete, and Admin (RWDA), so that the user can later change the ACLs when he/she updates it.