Documentation Corrections and Additions
Installing Secure Enterprise Search (SES) 184.108.40.206 into the same Fusion Middleware home as WebCenter Portal 220.127.116.11 and above is not supported. The recommended and supported topology is to install SES into a separate Fusion Middleware home. That is, treat SES 18.104.22.168 as a remote service for WebCenter Portal.
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.
Workaround: 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.
Platform: iOS (mobile)
Workaround: To view the entire content area, use the two-finger scroll gesture on your iPad.
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.
Platform: iOS (mobile)
Workaround: 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 more information about creating new devices and specifying the user agent string, see Administering Device Settings in Administrating Oracle WebCenter Portal.
Workaround: You can workaround this issue by using the to_char (NCHAR_COLUMN NAME) function.
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.
Bug: 14407330 (Enhancement Request: 14552633)
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:
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.
Building Portals with 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.
In 12c (12.2.1), all Content Presenter templates exported from JDeveloper to the Portal Server are detected as multiple-item templates. To designate a Content Presenter template as a single-item template, the following workaround must be implemented:
You should see the updated single-item Content Presenter template.
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 "
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.
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 login. The new skin is simply used for a one-time triggering of skin registration, and can be deleted afterwards.
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.
When you try to access a secured portlet, it returns the remote portlet communication error. To work around this issue:
wsrp1, the credential key is
keystore.typeproperty, specify the value KSS.
Bug: 21968195 (RN1)
When restarting JDeveloper after installing the WebCenter Core Design Time extension, you can ignore the following warning message:
WARNING: No Extensions In Bundle: .../oracle.webcenter.wccore_bundle.zip
Bug: 21968195 (RN2)
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 Framework and Services Design Time extension.
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.
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.
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.
Bug 21835983/Support Note 2061433.1
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.
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:
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);
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.
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)
Example: SinceQuery; date:2015-04-07T02:28:01.815-07:00
For more information, see REST API.
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.
In Oracle WebCenter Portal 11g, the default names of managed servers are WC_Spaces, WC_Portlet, WC_Collaboration, and WC_Utilities. In a fresh Oracle WebCenter Portal 12c installation, WC_Utilities, which hosted Analytics, is deprecated, and WC_Spaces is replaced by WC_Portal and hosts Analytics. When you upgrade from Oracle WebCenter Portal 11g to 12c, the default managed server names are not changed. Further, Analytics remains deployed on the WC_Utilities managed server.
Platform: AllIn the Upgrading Oracle WebCenter guide, the Upgrading Oracle WebCenter Portal 11g Installations topic incorrectly specifies that you need to run the upgradeDocumentsILS WLST command. While upgrading Oracle WebCenter Portal, do not run upgradeDocumentsILS.