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:
Section 20.1.2, "Site Studio Publisher Does Not Support Multibyte Characters"
Section 20.1.3, "Oracle WebCenter Content Servers and IPv6 Support"
Section 20.1.4, "Content Categorizer Trace Log Settings Discontinued"
Section 20.1.5, "Extra Lines Displayed Viewing Contribution Folders in Internet Explorer 8"
Section 20.1.6, "WebDAV Connection Fails After Logout or Restart"
Section 20.1.7, "Detailed Oracle OpenOffice Configuration Settings"
Section 20.1.8, "Clarification When Setting Classpath to OpenOffice Class Files"
Section 20.1.9, "Inbound Refinery PDF Conversion May Differ Visually from the Original Content"
Section 20.1.12, "Manual Addition of xdoruntime.ear Library for Records Management"
Section 20.1.14, "Backing Up Site Studio Websites Using Chrome"
Section 20.1.15, "DAM Video Storyboard Errors With Chrome and Safari"
Section 20.1.16, "Issues Applying Table Styles When Using FireFox and FCK Editor"
Section 20.1.17, "Content Information Server Is Not Supported for 11g"
Section 20.1.20, "Using URLs With SSP Include and Exclude Filters"
Section 20.1.21, "Disabling the Folders_g Deprecation Alert"
Section 20.1.22, "Accessing ZipRenditionStaticAccess Scheduled Job Information"
Section 20.1.23, "Check-in and Search Forms Pop Up Error Messages when UCM is in EBR Mode"
Section 20.1.24, "View Publishing Errors Are Observed in Logs When UCM is in EBR Mode"
Section 20.1.25, "Optimization Errors with External OracleTextSearch"
Section 20.1.26, "Propagating the cwallet.sso Changes to Deployment Manager"
Section 20.1.27, "UCM in EBR Mode Fails to Start when Dynamic Converter Component is Enabled"
Section 20.1.28, "Content Tracker Report Date Format Supported in Nine Languages"
Section 20.1.29, "Inbound Refinery PDF Optimization Not Supported with Ghostscript 9.07"
Section 20.1.30, "Thai Locale in Firefox Browser Displays Larger Asian Font"
Section 20.1.32, "Using Dropdown Menu on Chrome When Ask.com Toolbar Present"
Section 20.1.33, "Using Tabular View in Screen Reader Mode in WebCenter Content User Interface"
Section 20.1.34, "Framework Folders AutoSuggest Type-Ahead Feature Limitation"
Section 20.1.35, "Site Studio ASP and JSP Sites Functionality in 11gR1"
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.
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
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.
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.
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.
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:
http://download.oracle.com/docs/cd/E10316_01/ouc.htm
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:
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:
JAVA_CLASSPATH_openoffice_jars=<OfficePath>/Basis/program/classes/unoil.jar:<OfficePath>/URE/java/ridl.jar:<OfficePath>/URE/java/jurt.jar:<OfficePath>/URE/java/juh.jar
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
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.
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.
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.
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:
/FMW_HOME/Oracle_ECM1/ucm/idc/components/ReportPublisher/lib/xdoruntime.ear
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:
/FMW_HOME/Oracle_ECM1/ucm/idc/components/ServletPlugin/cs.ear
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 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:
<mime-mapping>
<extension>hcsp</extension>
<mime-type>text/html</mime-type>
</mime-mapping>
This will allow the files related to the custom element to be executed rather than downloaded.
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.
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.
When using FCK editor and the Firefox browser 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.
Oracle Content Information Server (CIS) is not supported for WebCenter Content 11g connections in any formats.
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.
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 the '.' have been escaped with '\'
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:
DisableFoldersgDeprecationMesssage=1
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.
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.
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.
When using OracleTextSearch using an Oracle 11.2.0.2.0 database as an external search provider, optimization errors may appear in the logs. It is an issue with the database, not UCM. This issue is resolved in the 11.2.0.3.0 database.
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.
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 the Component Wizard.
Auto-filled dates in the Content Tracker Report page are only supported in nine languages. If the admin locale is not set to one of the nine languages, the date format is displayed in the default (English).
The nine supported admin locales are: Chinese-Simplified, Chinese-Traditional, Deutsche, English-UK, English-US, Espanol, Francais, Italiano, Japanese.
When using Inbound Refinery WinNativeConverter to convert documents to PDF, the PDF Optimization option does not work if the distiller being used is Ghostscript version 9.07. PDF Optimization does work with Ghostscript version 9.06.
When using Firefox browser with Content Server set for the Thai locale, the font size for Asian characters is larger than for non-Asian characters. This issue is specific to Firefox. A general recommendation is to use a different browser.
A workaround for using Firefox with the Thai locale is to access the Accessibility preferences in Content Server and select Use Large Fonts. Then in the Firefox Options, open the Advanced dialog in the Fonts & Colors section and deselect "Allow pages to choose their own fonts." The Thai font will display more accurately.
When using the WebCenter Content user interface (as opposed to the native 11g 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 11g interface) and Chrome, the presence of the Ask.com toolbar disables dropdown menu functionality. A workaround is to remove the Ask.com toolbar.
When using the WebCenter Content user interface (not the native 11g interface) in Screen Reader mode to access a Documents, Libraries, Favorites, or Folders page, then switching to the Tabular view, an error will occur if you perform a right click to get to the Context menu. The workaround is to select the desired document and then access the Context menu by using the menu bar and More menu. This situation only occurs when using the Screen Reader mode with the Tabular view.
When the WebCenter Content user interface is implemented instead of the native 11g interface, Framework Folders must be enabled (Folders_g cannot be used). As of 11.1.1.8.0, Framework Folders uses an AutoSuggest type-ahead feature when users enter search terms. The AutoSuggest feature is required and is enabled as part of the AutoSuggestConfig component with the WebCenter Content user interface. 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.
Active Server Page (ASP) and Java Server Pages (JSP) sites are still available for legacy (pre-10gR4) projects, but they do not have 11gR1 functionality. They will function as they did with previous releases of Site Studio.
ASP sites will work only when the Site Studio 11gR1 component is installed on a 10g Content Server. IIS is not a supported web server for 11g Content Server, so it is not possible for ASP sites to work out-of-the-box on 11g Content Server.
This section describes configuration issues and their workarounds. It includes the following topics:
Section 20.2.1, "Minimum JDBC Driver Version Required for Oracle Text Search Component"
Section 20.2.2, "Setting Security Privileges for Modifying Contribution Folders"
Section 20.2.4, "SSXA Required DC Version for Oracle Content Server 10gR3"
Section 20.2.5, "Content Portlet Suite (SCPS) WebCenter as Producer Targeting Libraries"
Section 20.2.6, "Logout URL for SSO Logout Integrating with Oracle Access Manager 11g"
Section 20.2.7, "Using the Custom Truststore with the JPS Connection to ActiveDirectory"
Section 20.2.11, "Setting Maximum Windows Per Session Parameter"
Section 20.2.12, "AutoSuggestConfig Component Must Be Disabled in Native 11g Interface"
Section 20.2.13, "Content Server Localization and Verbose Tracing"
Section 20.2.14, "FrameworkFolders Patch for Release 11gR1 (11.1.1.8.0)"
The Oracle Text Search component that is part of WebCenter Content 11gR1 requires a JDBC driver version of 10.2.0.4 or higher. The component will not work with older JDBC driver versions.
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
The JDeveloper Site Studio for External Applications connections dialog is pre-populated with a default web connection port value of 16200 for an Oracle Content Server 11g instance. Oracle Content Server 10gR3 web servers most often listen on port 80. As such, this value will likely have to be changed when connecting to an Oracle Content Server 10gR3 instance.
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 8.1.0.736 or greater.
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 (11.1.1.3) are different from the libraries for 11gR1 PS3 (11.1.1.4) and 11gR1 PS4 (11.1.1.5) installation of WebCenter.
Libraries for 11gR1 PS2 (11.1.1.3) 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 (11.1.1.4) and 11gR1 PS4 (11.1.1.5) 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 (11.1.1.4) on Oracle WebCenter 11gR1 PS3 (11.1.1.4), 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.
When integrating WebCenter Content with Oracle Access Manager 11g, add the following to the Logout URL setting for the WebGate:
/oamsso/logout.html
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.
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.
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: ESigCookieTimeOut=30
For systems using the WebCenter Content user interface instead of the native 11g 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 11g interface, the configuration parameter maximumWindowsPerSession is used to limit the number of active Doc Properties windows. The default is set to 10. If the WebCenter Content instance is experiencing higher than desired memory consumption, the setting can be changed to 6 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 11g interface. When using the WebCenter Content user interface, both the FrameworkFolders and AutoSuggestConfig components are required and must be enabled. When using the native 11g interface, the AutoSuggestConfig component must be disabled, even if the FrameworkFolders component is enabled.
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.
Administrators should contact Support to obtain a patch for the following FrameworkFolders bugs in release 11gR1 (11.1.1.8.0):
17171852: FLD_PROPAGATE Should Not Allow Content to Have xLibraryGUID Altered
17171834: UPDATE_DOCINFO Should Not Allow Content to Have xLibraryGUID Altered
17171818: UPDATE_DOCINFO Should Not Allow Content to be Unfiled
17164502: UPDATE_DOCINFO to Move Content from EL to ADHOC Does Not Error
17160600: UPDATE_DOCINFO to Move Content from EL to Another EL Does Not Update GUID
17153780: Move of an EL Folder to Another EL Folder, Subfolder Content Fail to Update GUID
17362858: FLD_MOVE to /Enterprise Libraries Does Not Update xLibraryGUID
17323595: Copying a Folder: All Files Are Flattened into One Directory
17317268: FLD_MOVE with OverrideDuplicates Does Not Correctly Handle xLibraryGUID
17314494: Folder Move with RESOLVE on a Folder Renames Subfolders in Conflict Resolution
17312366: FLD_COPY with ReviseDuplicates Does Not Correctly Handle xLibraryGUID
This section describes documentation errata. It includes the following topics:
Section 20.3.1, "Content Portlet Suite (CPS) WSRP URLs for WebCenter as Producer"
Section 20.3.2, "Update Component Configuration Information Missing in 11.1.1.8.0 Documentation Set"
After deploying the CPS EAR file to WebCenter as a producer, the WSDL URL for 11g PS2 (11.1.1.3) is different from the WSDL URL for PS3 (11.1.1.4) and PS4 (11.1.1.5). For more information, see the Deployment Guide for Content Portlet Suite, Section 3.1.4, Step 17.
WSRP URL for PS2 (11.1.1.3) installation of WebCenter:
http://Host_Name:Port/cps/portlets/wsrp1?wsdl
WSRP URL for PS3 (11.1.1.4) and PS4 (11.1.1.5) installations of WebCenter:
http://Host_Name:Port/cps/portlets/wsrp2?WSDL
Update component configuration information included in the 11.1.1.6.0 documentation set is not included in the 11.1.1.7.0 and 11.1.1.8.0 documentation sets. The information in section A.3.7 "Update Component Configuration Interface" in the 11.1.1.6.0 Oracle WebCenter Content System Administrator's Guide for Content Server is valid and can be viewed on the Oracle online documentation library at http://docs.oracle.com/cd/E23943_01/doc.1111/e10792/e01_interface.htm#CIACFBAG