Oracle® Fusion Middleware

Topics:

• New Features

• Certification Information

• Product Documentation

• Oracle Support

• Deprecated Features

• Issues Related to Installing and Configuring Oracle WebCenter Portal

• Issues Related to Patching and Upgrading Oracle WebCenter Portal

• Issues Related to Mobile Applications

• General Issues and Workarounds

Install Secure Enterprise Search in a Separate Oracle Home

Bug: 18398641

Platform: All

Installing Secure Enterprise Search (SES) 11.2.2.2 into the same Fusion Middleware home as WebCenter Portal 11.1.1.7 and above is not supported. The recommended and supported topology is to install SES into a separate Fusion Middleware home. That is, treat SES 11.2.2.2 as a remote service for WebCenter Portal.

Irregular Translation When IE 10 or 11 Browser Is Set to Some Chinese Language Locales

Bug: 19566825

Platform: All

This note refers to more recent versions of the Internet Explorer browser 10+. These browsers support BCP47 style language tags, such as the Chinese locales zh-Hans-SG, zh-Hans-CN, zh-Hant-HK, zh-Hant-MO, and zh-Hant-TW.

If you set your browser language to zh-Hans-SG, zh-Hant-HK, or zh-Hant-MO, and the same language is not set in WebCenter Portal, you will likely see translation inconsistencies on a page. For example, some WebCenter Portal user interface elements may default to the locale selected for the server; some content may default to Traditional or Simplified Chinese.

Workaround: Set your IE 10+ browser locale to zh-Hans-CN or zh-Hant-TW, or select a language preference through the WebCenter Portal UI under user preferences. You can also select your preferred language from the WebCenter Portal login UI.

Top Banner Not Rendering Correctly

Bug: 16786746

Platform: All

In Oracle WebCenter Portal, when you open a portal that was upgraded from a previous 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].

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

Unable to View Entire Content on iPad Because Scrollbars Not Shown

Bug: 14488651

Platform: iOS (mobile)

The Apple iOS platform does not use scrollbars. When you view a page on an iPad, content may appear truncated because scrollbars are not shown. Also, iFrame components ignore dimensions on an iPad.

Workaround: To view the entire content area, use the two-finger scroll gesture on your iPad.

RSS Links Not Working Properly on iPad

Bug: 14487974

Platform: iOS (mobile)

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 of your firewall, RSS links cannot be viewed.

Cannot Upload Content Using iPad

Bugs: 14488559 and 14487904

Platform: iOS (mobile)

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.

Cannot Copy Text on a Page Using iPad

Bug: 14488336

Platform: iOS (mobile)

When you access a page through an iPad, you cannot copy the text that is shown on the page. This is a limitation from the Apple iOS platform.

Mobile Page Variants Not Displayed Correctly on Nexus 4 Devices

Bug: 16954597

Platform: Mobile

Mobile page variants are not displayed on the Nexus 4 devices.

Workaround: To resolve this issue, create a new device with the following user agent string:

SQL Query with NCHAR Data Type Throws Exception

Bug: 12956478

Platform: All

When using a SQL data control, you may encounter an error if the query contains a column with the NCHAR data type.

Workaround: You can workaround this issue by using the to_char (NCHAR_COLUMN NAME) function.

Cannot Customize or Personalize a JSF Portlet

Bug: 13331428

Platform: All

When you click OK after customizing or personalizing a JSF portlet (that is, a portlet created using the Oracle JSF Portlet Bridge), the portlet produces a time-out message and ceases to respond. This occurs when performing two actions in single operation (editing and then changing the portlet mode).

Workaround: First perform the edit action and click Apply (instead of OK), and then click Return to change the portlet mode back to View mode. Portlet developers can avoid the issue entirely by editing the code for the generated Edit Defaults mode in the edit_defaults.jspx file and the Edit mode in the edit.jspx file: Remove the code for the OK button so users must use Apply.

Embedded Images Not Rendered in the Mail Task Flow

Bug: 14407330 (Enhancement Request: 14552633)

Platform: All

The Mail task flow does not render embedded images. Emails that contain inline images show them as attachments rather than render them within the message body.

Error When Page Name Includes a Space

Bug: 16977809

Platform: All

When accessing a portal page on a device, such as a tablet or iPhone, an issue arises when all of the following conditions are true:

• The page name has a space

• 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 listed conditions are true, the content of the page appears (without the page title) on the device in lieu of the Page Not Available message.

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 Building Portals with Oracle WebCenter Portal.

Unable to Edit Box Properties

Bug: 20356197

Platform: All

Building Portals with Oracle WebCenter Portal discusses Working with Web Development Components on a Page. Note that Box components cannot be modified or deleted since the View Actions menu is not rendered.

Error While Re-running Portlet Application on IntegratedWebLogicServer

Bug: 21876587

Platform: All

When you attempt to run a portlet application (such as a JSR 286 Portlet or Portlet Bridge application) on the IntegratedWebLogicServer more than one time, you get the following deployment error:

There is more than one webservice with the name of "{urn:oasis:names:tc:wsrp:v1:wsdl}WSRP_v1_Service".

Resolve this issue by not running the portlet application again. Instead, deploy the application's EAR deployment profile to the IntegratedWebLogicServer by creating an Application Server Connection to the IntegratedWebLogicServer.

Administrator Console Skin Does Not Load Properly

Bug: 21933886

Platform: All

The Administration Console Skin does not load correctly after updating the Default Page Template and Application Skin to a custom page template and custom skin. This issue appears when attempting to restart the portal server, and may create difficulties when attempting to perform administrative operations such as clicking on a portal template, or when creating a new portal.

To resolve this issue, create a new skin at the shared asset level and then log in. The new skin is simply used for a one-time triggering of skin registration, and can be deleted afterwards.

Connection Timeout Occurs when a WebCenter Portal Server Connection is Created in a Production Environment

Bug: 21982436

Platform: All

When creating a WebCenter Portal Server connection, you enter the host name and port number for the Portal Server you are connecting to. For the host, you can enter either the fully qualified domain name, localhost, or the server name. When the Portal Server is a cluster in an enterprise deployment topology, use the host name and port of the individual server node and not that of the load balancer.

Secured Portlets Return the Remote Portlet Communication Error

Bug: 21943690

Platform: All

When you try to access a secured portlet, it returns the remote portlet communication error. To work around this issue:

1. Log on to Enterprise Manager Fusion Middleware Control.

2. From the Weblogic Domain menu, select Security, then Credentials.

3. Expand the webcenter-1111 folder.

4. Select the key for the WSRP portlet producer connection. For example, if WSRP connection name is wsrp1, the credential key is anonymous#wsrp1-wsconn.

5. Click Edit.

6. For the keystore.type property, specify the value KSS.

7. Click OK.

8. Restart the WC_Portal and WC_Portlets managed servers.

WebCenter Portal JDeveloper Extension Names Modified

Bug: 23637247

Platform: All

JDeveloper Extension names/IDs in Oracle WebCenter Portal are updated:

• WebCenter Core Design Time (oracle.webcenter.core) is changed to WebCenter Core Design Time (oracle.webcenter.common).

• WebCenter Framework and Services Design Time (oracle.webcenter.app) is changed to WebCenter Portal Design Time (oracle.asset-publishing-ext).

Warning Displayed When Installing the WebCenter Core Design Time Extension for JDeveloper

Bug: 21968195

Platform: All

When restarting JDeveloper after installing the WebCenter Core Design Time extension, you can ignore the following warning message:

Installing updates...  
oracle.ideimpl.deferredupdate.task.InstallExtensionTask perform  
WARNING: No Extensions In Bundle: .../oracle.webcenter.wccore_bundle.zip

Installing WebCenter Portal JDeveloper Extensions from Local File

Bug: 21968195

Platform: All

When installing the WebCenter Portal extensions for Oracle JDeveloper by using the Install From Local File option, you must install the WebCenter Core Design Time extension first and restart JDeveloper before installing the WebCenter Portal Design Time extension.

Analytics Collector Not Accessible on the Second Node

Bug: 21463877

Platform: All

When starting servers in a cluster topology, you must allow one server to completely start and be in the Running mode before attempting to start other servers. You can then start all the other servers simultaneously. This is required only when you start the servers for the first time after a fresh WebCenter Portal installation. If you start all the servers simultaneously, Analytics Collector might not be accessible on the other nodes in the cluster.

Document Service Operations Fail When Using JAX-WS Connections to Content Server

Bug: 21929314

Platform: All

If WebCenter Portal uses the JAX-WS connection to Content Server, certain document service operations, such as service provisioning, might fail if the WebCenter Portal instance is not used for some time. To work around this issue, restart the WC_Portal managed server and perform the operation again.

Use createContentServerConnection to Create a JAX-WS Connection to Content Server

Bug: 21929314

Platform: All

If you create a JAX-WS connection to Content Server using Enterprise Manager Fusion Middleware Control, logging into WebCenter Portal returns an internal server error. To work around this issue, instead of Fusion Middleware Control use the createContentServerConnection WLST command to create the JAX-WS connection to Content Server.

Unable to Delete Pages With SubPages in WebCenter Portal Installed with SQL Server

Bug 21835983/Support Note 2061433.1

Platform: All

In a WebCenter Portal instance using SQL Server, when you try to delete a page with subpages, the page will still exist in the UI but the following error is shown in the managed server logs:

oracle.webcenter.portal.transaction.TransactionException: An error occurred executing a transactional method. 
at  
oracle.webcenter.portal.persistence.transaction.TransactionManagerImpl.execute (TransactionManagerImpl.java:295) 
...  

Caused by: java.sql.SQLIntegrityConstraintViolationException: [FMWGEN][SQLServer JDBC Driver][SQLServer] The DELETE statement conflicted with the SAME TABLE REFERENCE constraint "WC_PORTAL_ENTITY_SEC_ENTITY". The conflict occurred in database "certdb", table "MSSQLCERT_WEBCENTER.WC_PORTAL_ENTITY", column 'SECURITY_ENTITY_ID'.

To work around this issue:

1. Connect to the SQL Server using the WebCenter schema.

2. Drop the trigger WC_PORTAL_ENTITY_SEC_ENTITY_TRIGGER.

3. Recreate the trigger as follows:     

           CREATE TRIGGER WC_PORTAL_ENTITY_SEC_ENTITY_TRIGGER ON WC_PORTAL_ENTITY               
                   INSTEAD OF DELETE AS               
                   UPDATE WC_PORTAL_ENTITY SET SECURITY_ENTITY_ID = NULL WHERE SECURITY_ENTITY_ID IN (SELECT ID FROM DELETED)               
                   DELETE FROM WC_PORTAL_ENTITY WHERE ID IN (SELECT ID FROM DELETED);
   

4. Delete the page again in WebCenter Portal.

Unable to Modify displayName for Resources Using REST APIs

Bug 18631878

Platform: All

The displayName parameter is a derived parameter and cannot be modified directly for any resources by using REST APIs.

Workaround: You need to modify the name parameter.

Query Parameter for a Portal Using REST API

Bug 18631878

Platform: All

The REST API documentation states that the q search query parameter can accept the following value: NameNamespaceQuery;name:;namespace: portal. However, you can also search for portals using the following parameters:

“NameDescriptionLikeQuery;name:Query" (Search using Portal name)

"SinceQuery;date: yyyy-mm-dd'T'HH:mm:ss.SSS'Z' (Search using created date)

Where,

• yyyy-mm-dd refers to the year, month, date format

• HH:mm:ss.SSS refers to the time in the hour, minutes, and seconds format

• Z refers to the zone designator with or without offsets

Example: SinceQuery; date:2015-04-07T02:28:01.815-07:00

For more information, see REST API Reference for Oracle WebCenter Portal.

Post or Put Request Using REST API in Pagelets Fails

Bug 20634297

Platform: All

When you initiate a Post or Put request using REST API in pagelets, the 500 Internal Server Error message is displayed.

Workaround: Use Content-Type as "application/x-www-form-urlencoded" in the request header while invoking the pagelet REST API.

Unable to Create a Navigation Node Using POST in REST API

Bug 23328326

Platform: All

When you try to create a navigation node using the POST method in REST API, the create operation fails with a 403 Forbidden error message. This is a known issue.

EL Expressions are Not Supported in REST APIs

Bug: 23751693

Platform: All

Webcenter objects having EL expressions cannot be accessed using REST APIs as EL expressions are not supported with REST.

Page Navigation Fails if the First Navigation Item is a Link

Bug 22607786

Platform: All

If a link is specified as the first navigation item in the navigation model of a portal, page navigation fails. This is a known issue.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.