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. The interfaces to call the discussions server directly from an application should be done by leveraging the supplied task flows that come with WebCenter Portal. 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.
When you create a group space, an error similar to the following might be seen if provisioning a service exceeds the time allowed:
Group space created with the following warnings:
Issues were faced while provisioning the services. Errors were encountered for the following services - Discussions and Announcements. Check if these services have been configured correctly.
When a group space is created, services are provisioned in parallel in multiple threads. If provisioning a service exceeds the specified timeout, the thread is interrupted. The timeout may be exceeded due to time needed to copy the metadata when the latency between the midtier and the database is too high, network issues, database performance issues, and so on.
To check if the issue is due to exceeding the timeout, search the log file for a message similar to the following:
<Nov 3, 2009 4:44:06 PM GMT> <Warning> <oracle.webcenter.webcenterapp> <BEA-000000> <Concurr: The thread is timed out in 10000 milisec. for oracle.webcenter.collab.forum:Execution timedout queued : 12 ms suspended : 0 ms running : 5842 ms timeout : 5000 ms service : oracle.webcenter.community resource : oracle.webcenter.collab.forum source : oracle.webcenter.concurrent.RunnableTask@23268a92 (oracle.webcenter.concurrent.RunnableTask) submission : 15> <Nov 3, 2009 4:44:06 PM GMT> <Warning> <oracle.webcenter.webcenterapp> <BEA-000000> <Concurr: The thread is timed out in 5000 milisec. for oracle.webcenter.collab.announcement:Execution timedout queued : 37 ms suspended : 0 ms running : 5875 ms timeout : 5000 ms service : oracle.webcenter.community resource : oracle.webcenter.collab.announcement source : oracle.webcenter.concurrent.RunnableTask@37538945 (oracle.webcenter.concurrent.RunnableTask) submission : 18> <Nov 3, 2009 4:44:06 PM GMT> <Warning> <oracle.webcenter.collab.forum.internal.jive.CategoryTaxanomyCreator> <BEA-000000> <java.io.InterruptedIOException: Operation interrupted
In this case, the running time of 5875 ms exceeded the timeout of 5000 ms. The root cause of the timeout should be addressed; for example, resolve networking or database performance issues.
The networking issues could be resolved by incresing the TCP/IP timeout value.To change the timeout values, log in as a
root user and execute the following command:
ndd -set /dev/tcp tcp_time_wait_interval 480000 (default value is 60000)
Restart the Administration and Managed Servers. Once this is done, the group space can be created again and the error will not be encountered. If the performance cannot be improved and the error persists, the timeout value may be increased for the service encountering the error. For more information, see Section A.5.5, "Configuring Concurrency Management."
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.
If your environment supports Global Policy Attachments (GPA), leave the Client Security Policy property blank when you configure the Content Server connection. The hint text and online help indicates that you must enter the value 'GPA' but this information is not correct. See also, the table "Content Server Connection Parameters" in Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.
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 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 and 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.
In some circumstances, permissions on a folder in Content Server that stores the documents for a space may not reflect the permissions set in the Spaces application. In such cases, one or more users may not be able to perform actions on documents in that space, even though they have been assigned appropriate permissions in Spaces.
To resolve this situation when it affects only one user, the space moderator (or a space member assigned Manage Membership permission) can do either of the following:
Revoke the user's membership to the space, then add them back to the space: in the space administration settings, on the Members page, click Remove Members to revoke membership, then Add People to add them back as members of the space.
Change the user's role to a different role, then change it back to the required role:in the space administration settings, on the Members page, select the user, then click Change Role.
To resolve this situation when it affects more than one user, the space moderator (or a space member assigned Manage Membership permission) can perform the following steps:
Identify the membership role that the affected users have, then edit that role: in the space administration settings, on the Roles page, select the role, then click Edit Permissions.
Clear all permissions for the role, and click Save.
Edit the role again, select all permissions for the role, and click Save.
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.
After configuring WebCenter Portal: Spaces to have a active connection to a Content Repository connection (Oracle WebCenter Content: Content Server) and bouncing WebCenter Portal: Spaces, the Documents Service does not appear to be available in Spaces. For example, in the Home space or a space there are no documents available. The cause of the issue is likely to be in the Content Repository connection settings or that the WebCenter Portal data was not successfully seeded into the Content Server.
To resolve this problem:
Check that the Content Server is up and running. Ensure the server has the Server Port (
intradoc) configured and the Server IP Filter allows connection from WebCenter Portal: Spaces:
Log in to the Content Server.
Click Configuration for instance name
Click the Server Configurations link under System Configuration.
Ensure that Server Port is listed and that Server IP Filter allows access from WebCenter Portal: Spaces.
Check the Content Repository Connection settings are correct for the Content Server being used for the Document store:
Using either WLST or Fusion Middleware Control display the Content Repository Connection settings.
Ensure that the connection for the Content Server is marked as the Active Connection or Primary Connection.
Ensure that the settings for the Content Server are correct.
Ensure that the Content Administrator, Root Folder and Application Name have been specified:
The Content Administrator must have administration rights in the Content Server. This user will be used to create and maintain folders for spaces content, security groups and roles, and manage content access rights.
The Root Folder and Application Name must be unique and not used by any other WebCenter Portal: Spaces application using the same Content Server. If you change these values, ensure that both values are changed and not just one of them.
It is recommended the Application Name is less than 14 characters as it is used as a prefix for items created in Content Server, such as workflows, which have a limit on the length of the item name.
Check the log at the time of the WebCenter Portal: Spaces start-up for any errors connecting to the Content Server or seeding the data in the Content Server:
When WebCenter Portal: Spaces has an active or primary Content Repository connection and the Content Administrator, Root Folder and Application Name have been specified, then when the WebCenter Portal: Spaces server starts up, data is seeded in the Content Server for that application (if it does not already exist).
If both Step 1 and 2 are correct, check the WebCenter Portal: Spaces log for any errors when WebCenter Portal: Spaces is started up. There may be errors when seeding the data in the Content Server.
If the log does not show any useful log information, turn up the logging for the Documents server and bounce WebCenter Portal: Spaces to see the log messages regarding seeding the WebCenter Portal: Spaces seed data:
Either use the Fusion Middleware Control or edit the
logging.xml file to increase the logging for
Restart WebCenter Portal: Spaces.
View the log for any messages regarding the seeding of the WebCenter Portal: Spaces data.
If the data is seeded correctly there should be a message logged at TRACE level similar to the following:
Content Server already contains the Space container, therefore no need to seed any data
If the seed data does not already exist, there should be a message logged at TRACE level similar to the following:
Creating WebCenter Seeded Data
On creating a space based on a template with the Documents service, the space creation fails with an error such as the following:
Granting permissions for Documents failed
To resolve this issue, view the WebCenter Portal: Spaces log to see if there are any log messages indicating the source of the error.
If it is not clear what the cause of the error is, try resetting all the Document permissions for all the roles to see if the role mapping completes successfully. Any failures should be logged in the WebCenter Portal: Spaces log.
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
In the Spaces application when the language is set to Russian, you cannot manage user membership in spaces, including the following: 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 188.8.131.52.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 184.108.40.206.0 or earlier version, if you encounter WS-Security-related errors, you must reconfigure the discussions server security settings. For information, see the "Configuring Web Services Security for Discussions" section in Oracle Fusion Middleware Patching Guide.
This section describes documentation errata. It includes the following topics:
In Oracle Fusion Middleware WebCenter Portal User's Guide, in "Table 32-1 Activities Tracked by Activity Stream", the Lists row incorrectly states that the following activities are tracked by Activity Stream:
Create a list
Add a row to a list
Edit a list row
Activity Stream does not track addition of a row to a list or editing of a list row.
The Oracle Fusion Middleware WebLogic Scripting Tool Command Reference lists
synchronizeUserInformation as a WebCenter Portal WLST command. This command is not available or valid for release 220.127.116.11.0.