This chapter describes issues associated with Oracle WebCenter Portal. It includes the following topics:
This section describes general issues and workarounds. It includes the following topics:
Oracle supports the embedded discussions server from Jive Software. Use the supplied task flows that come with WebCenter Portal to call this discussions server. Any custom development against APIs in the Jive Web Service layer are subject to review by Oracle and may not be supported.
There are a limited set of beta features that Jive Software delivers as part of the discussions server that Oracle does not recommend and cannot yet support.
Documentation for Jive Forums is included for reference only. Jive software installations and upgrades outside of the WebCenter Portal product installation are not supported.
Oracle WebCenter Portal's Pagelet Producer supports failover in a clustered configuration. However, the in-flight data (unsaved or pending changes) is not preserved. On failover, administrators must reestablish their administrative session. End users may also need to reestablish the session if the proxy is required to have a state. If SSO is configured, credentials are automatically provided, and the session is reestablished.
You can bring runtime task flows into JDeveloper, edit them, and export them back to the deployed application. However, Oracle recommends that you not expose task flows created in JDeveloper as portal resources. When you create an ADF task flow inside the
/oracle/webcenter/portalapp folder, the context menu on the task flow definition file displays the Create Portal Resource option. Do not use this option to expose a design-time task flow as a portal resource. Task flows typically involve multiple files. When you export a new task flow from JDeveloper, all files may not be exported properly, and this may result in the task flow being broken post-deployment.
When using a SQL data control, you may encounter an error if the query contains a column with the
NCHAR data type. As a workaround, you can use the
to_char(NCHAR_COLUMN NAME) function.
Setting up Windows Native Authentication-based single sign-on using SUN JDK 1.6.22 produces an error. Use the jrockit JDK instead of the Sun JDK, or contact Oracle Support to get a backport request for bug 10631797.
For certain features of the WebCenter Portal REST server to work correctly when using a REST client like the Oracle WebCenter Portal iPhone application, the flag
WLForwardUriUnparsed must be set to
ON for the Oracle WebLogic Server Plugin that you are using.
If you are running Apache in front of WebLogic Server, add this flag to
If you are running Oracle HTTP Server (OHS) in front of WebLogic Server, add this flag to
The examples below illustrate the possible configurations for both of these cases.
For more information about how to configure WebLogic Server Plugins, see Oracle Fusion Middleware Using Web Server 1.1 Plug-Ins with Oracle WebLogic Server.
Example 1: Using
<location /rest> to apply the flag only for
/rest URIs (recommended)
<Location /rest> # the flag below MUST BE set to "On" WLForwardUriUnparsed On # other settings, example: WebLogicCluster or WebLogicHost & WebLogicPort # set the handler to be weblogic SetHandler weblogic-handler </Location>
Example 2: Applying the flag to all URIs served by Oracle WebLogic Server
<IfModule mod_weblogic.c> # the flag below MUST BE set to "On" WLForwardUriUnparsed On # other settings, example: WebLogicCluster or WebLogicHost & WebLogicPort WebLogicCluster johndoe02:8005,johndoe:8006 Debug ON WLLogFile c:/tmp/global_proxy.log WLTempDir "c:/myTemp" DebugConfigInfo On KeepAliveEnabled ON KeepAliveSecs 15 </IfModule>
If a Framework application has been customized at runtime to add new resources through the Resource Manager, those new resources are lost after a new deployment or a redeployment of the same application.
Any new pages created at runtime that use the lost resources are still available even though the resources themselves are no longer available in the Resource Manager.
This issue happens when the application version or the redeployment version is changed during the redeployment of the application, either using Fusion Middleware Control or WLST. It can also happen on redeployment when the
generic-site-resources.xml file has been changed at design time (for example, by creating new resources).
This issue occurs because the
generic-site-resources.xml file is overwritten on redeployment.
To work around this issue, you must manually add the
mds-transfer-config.xml file to the application.
Any resources created at design time must be manually added to the runtime application before redeploying the application.
mds-transfer-config.xml file from the following location:
Extract the MAR file (for example
AutoGeneratedMar.mar) from the EAR file.
In the extracted MAR file directory, create a new directory, called
META-INF, and copy the
mds-transfer-config.xml file to the new directory.
Update the MAR file with
META-INF\mds-transfer-config.xml, for example:
jar -uvf AutoGeneratedMar.mar META-INF\mds-transfer-config.xml
Update the EAR file with the updated MAR file:
jar -uvf YourApp.ear AutoGeneratedMar.mar
If Oracle HTTP Server is used as a front end for the Sample WSRP Portlets producer, the style sheets for the WSRP Producer Test Pages of the WSRP Tools and Rich Text Editor portlet producers are not loaded properly in Mozilla Firefox or Google Chrome. However, the style sheets do load properly in Internet Explorer. Functionality of the portlets is not affected.
When clicking OK after customizing or personalizing a JSF portlet (that is, a portlet created using the Oracle JSF Portlet Bridge), the portlet does not respond and displays a timeout message. This is caused by performing an edit action and changing the portlet mode in a single operation. End users can work around this issue by clicking Apply (instead of OK) to perform the edit action first, then clicking Return to change the portlet mode back to View mode.Portlet developers can avoid the issue occurring by editing the code for the generated Edit Defaults mode (in the
edit_defaults.jspx file) and Edit mode (in the
edit.jspx file) and removing the code for the OK button so that end users are forced to use the Apply button instead.
There is no fallback support for custom translations. For example, if you create a custom translations file named
scope-resource-bundle_fr.xlf and the space language setting is country-specific (fr-FR), the custom translation file is not used because Spaces is looking for
scope-resource-bundle_fr-FR.xlf.As a workaround, copy
_fr xlf and include the country specification in the names of the custom translation files (for example,
When users access the Spaces application through OAM, spaces do not display the language selected on the OAM login page. The Spaces application does not use the same
xlf file name standard as OAM.
When the display language is set to Thai, the announcement publication format can be incorrect. This happens when announcements are opened to edit and are then saved, even if nothing in the announcement itself is updated.
If you add a seeded page, such as the Activities page, to your list of Favorites, and then change your preferred application language from en-US using Preferences, the favorite seeded page cannot be found.
You can create a JSF portlet (that is, a portlet that uses the Oracle JSF Portlet Bridge) using the Create JSR 286 Java Portlet Wizard by selecting the Generate ADF-Faces JSPX implementation method on the third step of the wizard.
If you create a JSF portlet in this way, you may find that clicking the Run as Servlet link on the portlet's Producer Test Page produces an error. The portlet itself, however, runs correctly.
To avoid this issue, add the ADF Page Flow scope to the project that contains the portlet. For information, see the section "Adding and Removing Technology Scopes" in Oracle Fusion Middleware Developer's Guide for Oracle WebCenter.
Pagelets based on OpenSocial gadgets are not able to post activities to a user's activity stream. To implement a temporary solution, grant User Profile 'edit' permission to Oracle WebCenter Portal's Pagelet Producer using the following WLST/WSAdmin command:
grantPermission(appStripe="pagelet-producer", principalClass="oracle.security.jps.internal.core.principals.JpsAuthenticatedRoleImpl", principalName="authenticated-role", permClass="oracle.webcenter.peopleconnections.profile.security.ProfilePermission", permTarget="/oracle/webcenter/peopleconnections/profile/s8bba98ff_4cbb_40b8_beee_296c916a23ed/.*", permActions="view,edit")
After running the command, restart the Pagelet Producer server.
To access owners' Profile/Activities/Friends information using the OpenSocial API with Oracle WebCenter Portal's Pagelet Producer, you must target the
WebCenterDS data source to the
WC_Portlet managed server as described in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter. After saving this configuration, Activities and Friends information can be fetched, but Profile information is not returned. To access Profile information, restart the
WC_Portlet managed server.
When you grant the
View Document permission to the
Authenticated-User roles on a hierarchical space, equivalent "Read" permissions are not set correctly in Content Server. If you want public users and authenticated users to have
View Document permissions on a space, you do not need to grant the permission to both the roles separately. When you grant the
View Document permission to public users, authenticated users inherit the
View Document permission automatically.
If you want to revoke
View Document permissions from public users but grant
View Document permissions to authenticated users, then revoke the permission from the
Public-User role and add it for the
In the Spaces application when the language is set to Russian, you cannot perform certain user management tasks for spaces, including adding a new user to a space, inviting a registered user to a space, and modifying or revoking a user's role assignment.
If the language is set to Swedish, the Roles page under Spaces Administration is not accessible.
Users can delete only messages from the Activity Stream that were entered from the Publisher task flow and include a link. (In other words, messages in the Activity Stream that were not entered via the Publisher and do not include a link cannot be deleted.)Users can delete only messages with a link from the Activity Stream. Other activity stream entries, such as notifications of page creations, cannot be deleted.
In Release 18.104.22.168.0, discussions server is shipped with no message protection for Web Service interaction between discussions server and Spaces; this allows you to use discussions server without any further configuration. However, after patching your Oracle WebCenter 22.214.171.124.0 or earlier version, if you encounter WS-Security-related errors, you must reconfigure the discussions server security settings. For information, see the "Configuring Security Policies for Spaces, Discussions, and Portlet Producer Web Service End Points" section in Oracle Fusion Middleware Patching Guide.
The Apple iOS platform does not display scrollbars. When you view a page on an iPad, content may appear truncated because scrollbars are not displayed. Also, iFrame components ignore dimensions on iPad. To view the entire content area, use the two-finger scroll gesture on your iPad.
The Apple iOS platform renders RSS links by loading them through the site
reader.mac.com. If the WebCenter Portal instance is not accessible outside your firewall, RSS links cannot be viewed.
The Apple iOS platform does not support a native file system browser. Therefore, you cannot upload content from an iPad. All upload actions, such as publish, upload, and share are disabled or hidden when you access WebCenter Portal from an iPad.
If you access a page through an iPad, you cannot copy the text displayed on the page. This is a limitation from the Apple iOS platform.
The Mail task flow does not render embedded images. If an email contains inline images, they are shown as attachments, and not within the message body.
The first time you access WebCenter Portal using the Mozilla Firefox browser, and attempt to open a document using Desktop Integration over an SSL or HTTPS connection, you will receive a warning that the certificate is not trusted, even if the environment has a valid certificate. You can open the document, but cannot check in or check out the document from within a Microsoft Office application. However, subsequent use of Desktop Integration through the Firefox browser will work as expected and you will be able to check documents in and out from within a Microsoft Office application.
When using only the keyboard in WebCenter Portal in Internet Explorer 9, on the General Preferences page in the Preferences dialog, the Expression Editor dialog loses cursor focus after a value is changed using the down arrow key. The cursor focus goes back to the General Preferences page instead of the Expression Editor dialog. To work around this issue, use Internet Explorer 8 or any other supported browser like Safari 23.x or Firefox 10.x.
The Web Clipping portlet is deprecated in Release 11g (126.96.36.199.0) and should not be used. Instead, create a clipper pagelet using Oracle WebCenter Portal's Pagelet Producer.
While accessing WebCenter Portal: Spaces using Internet Explorer 10, progress messages displayed during import or export space appear incomplete. To workaround this issue, click the browser compatibility icon next to the address bar to enable browser compatibility.
Application versioning is no longer supported by default for ADF applications. Upon initial deployment, an existing 188.8.131.52.0 (or earlier) or new application (184.108.40.206.0 or later) deploys successfully regardless of the application's versioning. However, when redeploying an unversioned application from JDeveloper 220.127.116.11.0 to a WebLogic Server where a versioned instance of that application is already running, deployment will fail. This is because the server is already running a versioned instance and WebLogic Server does not allow deploying an unversioned instance of the same application. You will see an error message like this:
Weblogic Server Exception: weblogic.management.ManagementException: [Deployer:149082]You cannot deploy application 'Application1_application1' without version. The application was previously deployed with version 'V2.0'.
To resolve this issue, undeploy the versioned application first and then deploy the unversioned application.
In the Rich Text Editor, if you switch from the Rich Text or HTML pane to the Wiki Markup pane, you might encounter formatting issues. For example, only the image source and title properties or attributes are saved when switching to Wiki Markup.
If you have a navigation model with many nodes, depending on the page template used for your portal, you may not be able to access all those nodes when you render that navigation model in a page. If there are more nodes than fit in the area of the page template used for navigation, a
>> icon provides access to a drop-down list of the remaining nodes. However, if this drop-down list is longer than the available screen size, you will not be able to access the nodes at the end of the list. For example, this situation may arise if you are using a page template where the navigation is displayed in a bar along the top of the page.
To work around this issue, consider using a different page template that displays navigation down the side of the page. Alternatively, you can use folders in your navigation model to group similar nodes together and reduce the number of nodes displayed at any one level of the navigation model.
This section describes documentation errata. It includes the following topic:
In Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter, in "Table 22-3 Oracle SES Connection - Name", the definition of Active Connection should read as follows:
"Select to use the Oracle SES instance defined on this connection as your search platform for your WebCenter Portal application. While you can register multiple Oracle SES connections for an application, only one connection is used—the default (or active) connection."
If you want to develop custom resources or build custom shared libraries for the Spaces application (18.104.22.168.0) you must use Oracle JDeveloper 22.214.171.124.0 to develop your extensions.
In Oracle Fusion Middleware Developer's Guide for Oracle WebCenter, section "Downloading a Workspace for Spaces Development" incorrectly states to use Oracle JDeveloper 126.96.36.199.0. Specifically, step 2 should read as follows:
"Step 2 Download and install Oracle JDeveloper 11g (188.8.131.52.0).
Oracle JDeveloper 11g (184.108.40.206.0) is available for download from:
In Oracle Fusion Middleware Developer's Guide for Oracle WebCenter, section "Deploying Your Own Custom Code and Task Flows in Shared Libraries" incorrectly refers to the accompanying whitepaper as "Using Spaces Extension Samples (220.127.116.11.0)". For WebCenter Portal 18.104.22.168.0, you must refer to the whitepaper "Using Spaces Extension Samples (22.214.171.124.0)".
In Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter, the "Configuring Microsoft Exchange Server 2007 or 2010 for WebCenter Portal" section and the "Third-Party Product Integration" appendix incorrectly specify Microsoft Exchange Server 2010 as a supported mail server. Microsoft Exchange Server 2010 is not certified for use with Oracle WebCenter Portal.
In Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter the "Microsoft Live Communications Server (LCS) Prerequisites" section and the "Third-Party Product Integration" appendix do not provide complete product details about the presence servers supported by the Instant Messaging and Presence (IMP) service. You can configure any of the following servers as the communication server for the IMP service:
Microsoft Office Live Communications Server (LCS) 2005 R2
Microsoft Office Communications Server (OCS) 2007 SP1
Microsoft Lync 2010