|Oracle® Fusion Middleware Release Notes
11g Release 1 (11.1.1) for Linux x86-64
Part Number E14770-52
|PDF · Mobi · ePub|
This chapter describes issues associated with Oracle WebCenter Portal. It includes the following topics:
For release notes related to WebCenter Portal installed on IBM WebSphere, see Chapter 7, "Oracle Fusion Middleware on IBM WebSphere."
This section describes general issues and workarounds. It includes the following topics:
The WebCenter Portal extension is an add-in that provides JDeveloper with the complete set of WebCenter Portal capabilities and features. Oracle WebCenter Portal 184.108.40.206.0 works only with WebCenter Portal extension 220.127.116.11.x and Oracle JDeveloper 18.104.22.168.0. By default, JDeveloper will recommend you to download the WebCenter Portal extension for release 22.214.171.124.0 as it is the latest version. You must ensure that you have the correct version installed. For information about installing the extension, see the "Installing the WebCenter Portal Extension for JDeveloper" section in Oracle Fusion Middleware Developing Portals with Oracle WebCenter Portal and Oracle JDeveloper.
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.
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.
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>
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.
When users access WebCenter Portal through OAM, portals do not display the language selected on the OAM login page. WebCenter Portal 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.
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 "Adding and Removing Technology Scopes" section in Oracle Fusion Middleware Developing Portals with Oracle WebCenter Portal and Oracle JDeveloper.
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.
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.
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.
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.
When you start the
WC_Spaces managed server, the following exception is reported in server logs after the server reaches the running state.
"Could not fetch the default portal configuration from webcenter-config oracle.webcenter.webcenterapp.WebCenterException: Getting WebCenter Attributes "
This does not cause any functionality loss. It is a known issue.
In WebCenter Portal, when you display a portal upgraded from a previous Oracle WebCenter Portal installation, the top banner of the portal does not render correctly. This happens when the portal has a page template set to a specific value, and the skin is left as
[System Default]. To work around this issue, you must choose a skin to match the page template. Configure the upgraded portal to use the
Spaces FX or
Fusion FX skin, depending on the page template.
An issue exists when accessing a portal page on a device (such as a tablet or iPhone) when all of the following conditions are true:
The page has a space in its name
The page does not have a page variant defined
The Page Fallback setting for the page or the portal is Display No Page
In this case, the expected behavior is to see Page Not Available on the device. However, when all of the condition above are true, the content of the page displays (without the page title) on the device instead of Page Not Available.
For more information, see the "Setting Page Behavior for a Portal When No Page Variant Exists" and "Setting Page Behavior for a Specific Page When No Page Variant Exists" sections in Oracle Fusion Middleware Building Portals with Oracle WebCenter Portal.
This release has a known issue when integrating PeopleSoft and WebCenter Portal leveraging WSS1.0 Username Token with Password. This is the recommended approach for customers who require secure consumption of PeopleSoft portlets in WebCenter Portal. Customers should contact Oracle Customer Support to obtain a patch to address this issue.
Oracle does not recommend using WSS1.0 SAML Token with Message Protection. This approach is not supported for integration between WebCenter Portal and PeopleSoft.
In a portal created using WebCenter Portal REST APIs, you will face problems creating pages. To work around this issue, you need to reapply Page permissions. Navigate to the Security page in WebCenter Portal Builder Administration. On the Roles tab, deselect all the permissions for Pages and save the setting. Now select the same permissions again and save the settings.
Mobile page variants are not displayed on the new Nexus 4 devices. To resolve this issue, create a new device with the following user agent string:
Mozilla/5.0 \(Linux; Android.+4.2.+Nexus 4.+Chrome.*Mobile Safari.*
For information about creating new devices and specifying the user agent string, see the "Creating and Managing Devices" section in Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.
Oracle WebCenter Portal release 18.104.22.168.0 supports Oracle SES 22.214.171.124. If you patch your existing Oracle SES installation to release 126.96.36.199, you must install the new version of Oracle WebCenter Portal's Document Service Manager on Oracle SES and configure Oracle SES facets and sorting attributes. For information, see the "Installing Oracle SES 188.8.131.52" section in Oracle Fusion Middleware Installation Guide for Oracle WebCenter Portal.
This section describes documentation errata. It includes the following topics:
In Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter, in table 11-2 "Configuring Analytics for Use in WebCenter Portal", in the last row the URL of the main Analytics business role page is incorrect. The following is the correct URL:
The "What's New?" sections in Oracle WebCenter Portal documentation incorrectly state that rich user profiles can consolidate information from multiple profiles. The feature to consolidate profile information is not available in release 184.108.40.206.0.