38 Oracle WebCenter Content

This chapter describes issues associated with Oracle WebCenter Content. It includes the following topics:

38.1 General Issues and Workarounds

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

38.1.1 Standalone Inbound Refinery Application Executables on Windows 7

On Windows 7, the standalone Oracle WebCenter Content: Inbound Refinery application executables are not automatically copied to the bin directory (Domain_Dir/ucm/ibr/bin). If you need to use standalone applications, you can copy and rename them from Idc_Home/bin. For example, to use System Properties, you should copy Idc_Home/bin/Installer.exe to Domain_Dir/ucm/ibr/bin/SystemProperties.exe.

Please note that Inbound Refinery is supported on Windows 7 in development environments only.

38.1.2 Folio Items With Content IDs Containing Multibyte Characters Do Not Display Correctly in Safari

If you use the Safari web browser to download content into a simple folio where one or more content IDs include multibyte characters, then these multibyte content IDs are displayed as '------'. To avoid this, you can either use Internet Explorer or Firefox, or avoid using multibyte characters in content IDs.

38.1.3 Site Studio Does Not Support Multibyte Characters in Site IDs, Directory Names, and Page Names

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.

38.1.4 Site Studio Publisher Does Not Support Multibyte Characters

Oracle Site Studio Publisher does not support multibyte characters.

38.1.5 Transferring Folder Archives Between Content Servers Fails If Server System Locales Do Not Match

If you transfer folder archives between two Oracle Content Server instances using the Archiver utility, then this will fail if these servers have different system locales. No folder will be created on the target server, and no items under that folder will be imported. To avoid this, make sure that the system locales of both content servers match.

38.1.6 Importing Folder Archives Fails If User Locale Did Not Match Server System Locale During Export

If you export a folder archive from the Folder Configuration page in Oracle Content Server and the user locale during export does not match the server system locale, then you will not be able to import that folder archive to the same or a different content server, even if the user and system locales on that server do match. To avoid this, make sure that the user and system locales match during the folder archive export.

38.1.7 New Folio Page Does Not Work in French and Italian Languages

If both the Folios and AppAdapterCore features are enabled, and the user language is set to either French or Italian, the New Folio page does not allow you to select a template and create a new folio.

38.1.8 Oracle WebCenter Content Servers and IPv6 Support

Oracle WebCenter Content servers are supported on IPv4/IPv6 dual-stack hosts, but not on"IPv6-only" hosts. The following topologies are supported:

  • Oracle Database on IPv4 hosts

  • Oracle WebCenter Content, Oracle WebCenter Content: Records, Oracle WebCenter Content: Inbound Refinery on IPv4/IPv6 dual-stack hosts

  • Client (browser) on either IPv4 or IPv6 hosts

38.1.9 Large File Check-ins May Cause Timeouts

Large file check-ins often time out due to the amount of I/O that occurs. Database locks are held while the large file is written and this blocks subsequent check-ins. The IdcServerThreadQueryTimeout configuration setting can be used to lengthen the checkout time. The setting is expressed in seconds; to make the timeout 5 minutes, set IdcServerThreadQueryTimeout=300.

38.1.10 Content Categorizer Trace Log Settings Discontinued

The Content Categorizer-specific execution trace log settings are discontinued. Use the Content Server System Audit Information facility instead. To enable Content Categorizer execution trace, enter contentcategorizer in the Active Sections control of the Tracing Sections Information section of the Admin System Audit Information page.

38.1.11 Using WebCenter Content with OAM Server Under Single Sign-on

When WebCenter Content is used with Oracle Access Manager in a single sign-on environment, an entry to the config.cfg file must have the following lines added:


38.1.12 Extra Lines Displayed Viewing Contribution Folders in Internet Explorer 8

When using Folders in Internet Explorer 8 with default settings, IE8 adds extra lines. This is solved by opening the Compatibility View Settings dialog and unselecting the Display intranet sites in Compatibility View checkbox.

38.1.13 WebDAV Connection Fails After Logout or Restart

In Windows 7 and Windows Vista clients, after logging out and logging back in or after restarting, the Network Place used to access WebCenter Content over WebDAV may no longer work. This is solved by deleting and recreating the connection.

38.1.14 LDAP Users Not Receiving Some Administrator Privileges

WebCenter Content inspects for the group "Administrators" on each user's login to grant WebCenter Content roles. If a user should have access to the WebCenter Content admin server, the WebCenter Content server requires that the user be a member in a group named "Administrators."

38.1.15 WinNativeConverter Requires .NET Framework

The Inbound Refinery component WinNativeConverter requires the vb.Net libraries included in the Microsoft .NET Framework 3.5 Service Pack 1 Redistributable Package for a Windows operating system. This package is available from the Microsoft Download Center at:


Search for "Microsoft .NET Framework 3.5 Service Pack 1" and download and install the dotnetfx35setup.exe on your Windows operating system.

38.1.16 Detailed Oracle OpenOffice Configuration Settings

When configuring Inbound Refinery to convert content using Oracle OpenOffice, additional configuration details can be found in the Oracle 10g release of the PDF Converter Installation and Administration Guide. The complete guide is available for download in either PDF or HTML format from Oracle Technology Network at the following URL:


Oracle OpenOffice configuration is detailed in the "OpenOffice" section of "Installing Third-Party Applications" in Chapter 4, "Installing PDF Converter" and can be accessed directly at the following URL:


Oracle OpenOffice configuration is detailed in the "OpenOffice" section of "Installing Third-Party Applications" in Chapter 4, "Installing PDF Converter" and can be accessed directly at the following URL:


38.1.17 Clarification When Setting Classpath to OpenOffice Class Files

In the Oracle Digital Asset Manager and Conversion Administration guide, chapter 2 "Managing Conversions" under the section "Configuring Content Server and Refinery Communication," step 2 asks you to enter:


Note that the true value for <OfficePath> is likely to include spaces and care must be taken when setting this in a Microsoft Windows environment.

Ensure that the paths are not enclosed in quotes, that slashes (/) are used for path separators and not backslashes (\), and that any space in the path is escaped using a backslash (\). For example, a properly formed classpath in a Windows environment could look like this:

JAVA_CLASSPATH_openoffice_jars=C:/Program\Files/OpenOffice.org\3/Basis/program/classes/unoil.jar:C:/Program\Files/OpenOffice.org\3/URE/java/ridl.jar:C:/Program\ Files/OpenOffice.org\3/URE/java/jurt.jar:C:/Program\ Files/OpenOffice.org\ 3/URE/java/juh.jar

38.1.18 Inbound Refinery PDF Conversion May Differ Visually from the Original Content

Oracle WebCenter Content: Inbound Refinery makes every effort to maintain the visual integrity and formatting of content being converted from its native format to PDF, but Oracle cannot guarantee that the resulting PDF will be an exact visual replication.

38.1.19 Mismatching User and Server Locales Prevent Access to Oracle E-Business Suite and PeopleSoft Managed Attachment Pages in WebCenter Content

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.

38.1.20 Connection Issues with Windows to WebDAV

Supported Windows operating systems may have difficulty connecting to a WebDAV server running over HTTP and using HTTP Basic authentication in some situations. To correct for this, you must edit the registry of the client computer to enable Basic authentication. For detailed information, see Microsoft Knowledge Base Article 841215 at http://support.microsoft.com/kb/841215.

38.1.21 Manual Addition of xdoruntime.ear Library for Records Management

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:

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

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

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

  4. Click Next. The option page to select the file as library opens. Select "Install this deployment as a library" and click Next.

  5. The Target Selection Screen opens. Select all targets and click Next.

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

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

  1. Extract the cs.ear file from the following path:

  2. In the extracted directory modify META-INF/weblogic-application.xml and add the following line for library reference:

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

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


    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.

38.1.22 Using HCSP Custom Elements with SSXA

When a new custom element form is created from scratch (rather than copying an existing form to build an element from), it may have issues lading properly in SSXA.

To use HCSP custom elements within SSXA, you must include the following in the SSXA application's web.xml file:


This will allow the files related to the custom element to be executed rather than downloaded.

38.1.23 Using Link Wizard with FCKEditor and Chrome

If the defined editor for Site Studio Contributor is FCK Editor, in some cases the Link Wizard may not launch properly when using Contributor via Chrome 9.0.

This is an issue with the FCK editor. You should either use CK editor for Site Studio, or use one of the recommended browsers for Site Studio (IE, Firefox, Safari) when using Site Studio Contributor.

38.1.24 Link Wizard Display Errors When Using Chrome

When making a link in the Link Wizard while using Chrome, in some cases JavaScript code is displayed rather than the link. The code continues to display even when looking at the web site outside of Contributor. This only happens when using Chrome, and not IE, Firefox, or Safari.

38.1.25 Backing Up Site Studio Websites Using Chrome

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.

38.1.26 DAM Video Storyboard Errors With Chrome and Safari

The storyboard links on the Rendition Info page for a video item (which should make the video start playing at a specific spot) are not working in Chrome or Safari browsers with Windows Media or QuickTime player plug-ins. Nothing happens when you click on the links. They do work in Chrome and Safari with the flash player, and they work with all plugins in Firefox and IE.

38.1.27 Issues Applying Table Styles When Using FireFox and FCK Editor

When using FCK editor and FireFox with Site Studio Contributor, it is difficult to apply available table styles to a table. This is a functionality missing from FCK editor, and not a limitation of FireFox or Site Studio.

38.1.28 Content Integration Suite Is Not Supported for 11g

Oracle Content Integration Suite (CIS) is not supported for WebCenter Content 11g connections in any formats.

38.1.29 Window Size Using Trays with FireFox

When using the Trays view with Site Studio on the Content Server, some screens viewed in FireFox may not correctly fill the browser window.

38.1.30 Content Item Icon for Basket Item Appears Broken in Chrome

When using Chrome with WebCenter Content, the icon for content items in the user's active basket appears broken. This only happens when using the Chrome browser.

38.1.31 VB6 Component Dependency for Kofax 9

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.

38.1.32 Offline Server Status Icon Overlay Not Displayed on Windows Vista and Windows 7

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.

38.1.33 Opening an Older Managed File Revision Not Available in Microsoft Excel

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.

38.1.34 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:


Note the '.' have been escaped with '\'

38.1.35 Disabling the Folders_g Deprecation Alert

There is an alert displayed when Folders_g is enabled that says, "The Folders_g component is in use but is now deprecated. Folders_g is replaced with the FrameworkFolders component, which implements the Folders feature. Folders_g data can be migrated to the new Folders feature."

To prevent this alert from displaying, open the config.cfg file and set the following configuration value:


38.1.36 Dragging and Dropping Microsoft Office Documents in Windows Explorer

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 (.docx, .xlsx, or .pptx extension).

If you want to edit a document, you should use the Check Out or 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.

38.1.37 Accessing ZipRenditionStaticAccess Scheduled Job Information

The ZipRenditionManagement component automatically creates a scheduled job to aid in the creation of static renditions. This job is sometimes created at the wrong time during the setup or configuration process, which causes an error when an administrator accesses the Administration > Scheduled Jobs Administration > Active Scheduled Jobs page. If the administrator deletes the job and restarts Content Server, the job will be recreated, and the Active Scheduled Jobs page will not throw an error.

38.1.38 Using Only Page 1 for Thumbnail Images of Documents

Both Oracle WebCenter Content: Inbound Refinery and Oracle WebCenter Content Server can generate thumbnail images of documents, and there is an option to set which page number of a document will be used for the thumbnail image. The default page number is 1, and this works, but using any other number does not work.

38.1.39 Check-in and Search Forms Pop Up Error Messages when UCM is in EBR Mode

When UCM is run in EBR more, the following errors pop up when opening check-in or search forms.

"Unable to generate data for the view websiteobjecttypelist. Unable to build where clause for for view WebsiteObjectTypeList. The field dKey does not exist in table OptionsList"

"Unable to generate data for the view pachagedconversionslist. Unable to build where clause for for view PachagedConversionsList. The field dKey does not exist in table OptionsList"

"Unable to generate data for the view pdfwtemplatetypelist. Unable to build where clause for for view PdfwTemplateTypeList. The field dKey does not exist in table OptionsList"

"Unable to generate data for the view videorenditionslist. Unable to build where clause for for view VideoRenditionsList. The field dKey does not exist in table OptionsList"

As a result, some dropdowns in the forms are not populated with data.

38.1.40 View Publishing Errors Are Observed in Logs When UCM is in EBR Mode

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.

38.1.41 Optimization Errors with External OracleTextSearch

When using OracleTextSearch using an Oracle database as an external search provider, optimization errors may appear in the logs. It is an issue with the database, not UCM. This issuse is resolved in the database.

38.1.42 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


when it starts after completing configuration on the Post Install Configuation 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.

38.1.43 UCM in EBR Mode Fails to Start when Dynamic Converter Component is Enabled

When the UCM is in EBR mode, and Dynamic Converter is enabled, UCM managed server will not start due to an error with creating the HtmlConversions object. An ORA-00955 error will be referenced in this exception:

!csDbUnableToPerformAction_create,HtmlConversions!$ORA-00955: name is already used by an existing object

A possible workaround is to disable DynamicConverter component using ComponentWizard.

38.2 Configuration Issues and Workarounds

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

38.2.1 Minimum JDBC Driver Version Required for Oracle Text Search Component

The Oracle Text Search component that is part of WebCenter Content 11gR1 requires a JDBC driver version of or higher. The component will not work with older JDBC driver versions.

38.2.2 Manually Disabling 8.3 File Naming for Inbound Refinery on Windows 7

When running Oracle WebCenter Content: Inbound Refinery on Windows platforms, you may see this alert:

"The weblayout directory is on a filesystem with 8dot3 semantics. Legacy 16-bit 8dot3 filenames conflict with revision labels and will cause file loss. Disable 8dot3 semantics by running Installer DisableNtfs8dot3 and then restarting Windows."

On Windows 7, running Installer DisableNtfs8dot3 does not resolve this. You must make the configuration change manually in the Windows registry.

To change the Windows registry, go to the following key:


Then, set the value of the NtfsDisable8dot3NameCreation key to 1. You must restart Windows for the new setting to take effect.

Please note that Inbound Refinery is supported on Windows 7 in development environments only.

38.2.3 Setting Security Privileges for Modifying Folders

By default, users only need RW privileges to modify folders, 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:


38.2.4 SSXA Required DC Version for Oracle Content Server 10gR3

To use dynamic conversion of native documents on your Site Studio web sites running off of Oracle Content Server 10gR3, you must install and configure Dynamic Converter build version or greater.

38.2.5 Content Portlet Suite (SCPS) WebCenter as Producer Targeting Libraries

When creating a custom managed server, the following libraries need to be targeted to the newly created managed server (for example, CPS_Portlet). Note that the libraries for 11gR1 PS2 ( are different from the libraries for 11gR1 PS3 ( and 11gR1 PS4 ( installation of WebCenter.

Libraries for 11gR1 PS2 ( installation of WebCenter:

  • oracle-ridc-client-app-lib(10.3.2,10.3.2)

  • oracle-ucm-spi-app-lib(10.3.2,10.3.2)

  • p13n-app-lib-base(10.3.2,10.3.2)

  • vcr-app-lib(10.3.2,10.3.2)

  • oracle.webcenter.framework(11.1.1,11.1.1)

  • oracle.webcenter.spaces.fwk(11.1.1,11.1.1)

Libraries for 11gR1 PS3 ( and 11gR1 PS4 ( installation of WebCenter:

  • oracle.ucm.ridc.app-lib(11.1.1,11.1.1)

  • p13n-app-lib-base(10.3.2,10.3.2)

  • oracle.webcenter.framework(11.1.1,11.1.1)

  • oracle.webcenter.spaces.fwk(11.1.1,11.1.1)

  • oracle.webcenter.framework.core(11.1.1,11.1.1)

When consuming Oracle Content Portlet Suite 11gR1 PS3 ( on Oracle WebCenter 11gR1 PS3 (, users will see the exception "java.lang.IllegalArgumentException:IdcContext.setUser() method not valid, do not use this method."

Contact Oracle support for the options available to resolve this issue.

38.2.6 Logout URL for SSO Logout Integrating with Oracle Access Manager 11g

When integrating WebCenter Content with Oracle Access Manager 11g, add the following to the Logout URL setting for the WebGate:


38.2.7 Using the Custom Truststore with the JPS Connection to ActiveDirectory

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

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.

38.2.8 Using WebDAV on a Windows 7 Client

If you use WebDAV on a Windows 7 client, consider the following issues:

  1. 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\
        to 2.

      • Set HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\
        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,
      , 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\
      to 0.

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

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

    1. Select Computer in the Explorer navigation tree on the left, and select Add a network location on the right.

    2. Enter the WebDAV URL to Content Server

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

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

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

38.2.9 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:

  1. Modify your cell's jps-config.xml file with a text editor:

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

    2. 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"/>
  2. Synchronize all managed nodes.

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

38.2.10 File Store Provider Storage Rule "Default Storage" is not the Default

The File Store Provider (FSP) storage rule named "Default Storage" was the default in a previous release and is included in the current release solely for backwards compatibility. The current default storage rule is DispByContentId ("Dispersion by ContentId").

38.3 Documentation Errata

This section describes documentation errata. It includes the following topics:

38.3.1 EnableOptimizedLatestReleaseQuerying No Longer Valid in Idoc Script

EnableOptimizedLatestReleaseQuerying is no longer a valid Idoc Script variable and should be disregarded.

38.3.2 Kofax Version Certification for WebCenter Content

Kofax versions 8.0 and 9.0 are both certified to work with WebCenter Content 11g.

38.3.3 Content Portlet Suite (CPS) WSRP URLs for WebCenter as Producer

After deploying the CPS EAR file to WebCenter as a producer, the WSDL URL for 11g PS2 ( is different from the WSDL URL for PS3 ( and PS4 ( For more information, see the Deployment Guide for Content Portlet Suite, Section 3.1.4, Step 17.

WSRP URL for PS2 ( installation of WebCenter:


WSRP URL for PS3 ( and PS4 ( installations of WebCenter:


38.3.4 No Support for 8.3 File Naming on Windows

The 8.3 file naming method used by default on many Windows systems is not supported. This should be disabled as part of the pre-installation procedures for WebCenter Content.

38.3.5 Search-Based Content Folders in Desktop Cannot Be Made Available Offline

The Oracle WebCenter Content User's Guide for Desktop states that content folders can be made available offline, but fails to mention that this does not apply to search-based folders (query folders and retention query folders). The contents of these folders do not actually exist in the folders; they are just grouped there because their metadata matches the search criteria. The actual content items may exist under a different folder location, or they may not even appear in a 'standard' folder at all. For content items in a folder to be made available offline, they must actually reside in the folder.

38.3.6 Server Connection Registry Entries for Desktop 11gR1

The information on the Windows Registry entries that administrators can use to set up Content Server connections for Oracle WebCenter Content: Desktop were inadvertently left out of the 11gR1 documentation. The information in the "Configuring Content Servers" section of the Desktop Integration Suite Installation Guide for 10gR3 also applies to 11gR1:


38.3.7 Internet-Style Search Disabled in 11g

The documentation notes that Internet-style search is enabled by default. Internet-style search is not enabled by default in 11gR1.

38.3.8 Framework Folders Component Not Enabled by Default

Contrary to what is stated in the software help, the Framework Folders component is not enabled by default in Oracle WebCenter Content Server.

38.3.9 Maximum Role Length Incorrect in WebCenter Content Server Help

Contrary to what is stated in the Oracle WebCenter Content Server help, the maximum length of role names is 255 characters, not 30.

38.3.10 Incorrect BrowserUrlPath Variable Location

An incorrect location is stated for the BrowserUrlPath configuration variables. The documentation states that the variables are located in the UCM_ORACLE_HOME/ucm/idc/components/BrowserUrlPath/config.cfg file.

The configuration variables should be placed in the master configuration file located at IntradocDir/config/config.cfg.

38.3.11 Incorrect Example Regarding Calling IdcCommandUX

The documentation shows the following example:

Dim idcCMD
idcCmd.initRemote("sysadmin", "c:\domain\bin")

The correct example is as follows:

Dim idcCmd
idcCmd.init("sysadmin", "c:\domain\bin")

38.3.12 Incorrect Default Value for SearchCacheMaxItemAgeInMinutes

The documentation states that the default value for SearchCacheMaxItemAgeInMinutes is 60.

The correct default value is 240.

38.3.13 Incorrect Case for LOAD_FOLIO_NODE Parameter parentNodeId

The documentation states that a LOAD_FOLIO_NODE optional service parameter is parentNodeID. The parameter is case sensitive and should be parentNodeId.

38.3.14 UseBellevueLook and UseXpedioLook Variables No Longer Valid in Idoc Script

UseBellevueLook and UseXpedioLook are no longer valid Idoc Script variables and should be disregarded.

38.3.15 formatDateWithPattern Idoc Script Variable Returned Incorrectly

When using the Idoc Script variable formatDateWithPattern in a program (instead of dynamic page), add !rfc to the end of the date pattern. This provides a date format that conforms to the rfc standard. If !rfc is not added, a program will try to use the locale to create the date string, but in the case of a timed update event, no locale is specified. Consequently, the output uses integers instead of strings for the day and month.