Thank you for your feedback!This chapter describes issues associated with Oracle WebCenter. It includes the following topic:
This section describes general issues and workarounds. It includes the following topics:
Section 13.1.1, "Using Oracle WebLogic Communications Server"
Section 13.1.3, "Application Role Names Cannot Include Thai Characters"
Section 13.1.5, "File Upload Browse Button Not Selectable with Enter Key (Accessibility Issue)"
Section 13.1.6, "Configuring a Client Security Policy for Oracle Content Server Connections"
Section 13.1.7, "Importing Space Templates with Public Access"
Section 13.1.8, "Task Flow Customizations Saved Automatically"
Section 13.1.9, "Option to Create a Portal Resource Displayed for Design-Time Task Flows"
Section 13.1.10, "Reading Items in the Resource Catalog (Accessibility Issue)"
Section 13.1.11, "Connections Network Task Flow on System Pages Not Supported"
Section 13.1.12, "Cannot Log In to WebCenter Spaces if Oracle BPM is Down"
Section 13.1.13, "SQL Query with NCHAR Data Type Throws Exception"
Section 13.1.14, "Modifying Default Resource Strings for Language Support"
Section 13.1.15, "Setting Up WNA-Based SSO Using JDK 1.6.22 Produces an Error"
Section 13.1.16, "Unable to Edit General Options Through WebCenter Spaces Administration"
Section 13.1.18, "Login Outcome Fails to Navigate to Privileged Pages"
Section 13.1.21, "Performing Security-Related Operations on Business Role Pages"
Section 13.1.22, "Unable to Access SSL-Protected WebCenter Endpoints"
Section 13.1.23, "Unable to Export Content to Excel by using a Custom ADF Taskflow"
Section 13.1.24, "Errors for Activity Graph Queries When the Activity Graph Engines are Running"
Section 13.1.25, "Page Not Found Error When Clicking Back to Portal Link"
Section 13.1.26, "Turning Off Automatic Event Listening in WebCenter Spaces"
Section 13.1.27, "Applying Item Level Security On WebCenter Spaces Content"
Oracle WebLogic Communications Server (OWLCS) is provided as a sample for development only. It should not be used for production deployments.
Oracle WebCenter Discussions (Jive Forums) is an optional component of Oracle WebCenter. Complete documentation for Jive Forums is included for reference. However, Jive software installations and upgrades outside of the WebCenter product installation are not supported.
In this release, application role names cannot contain Thai characters.
Oracle WebCenter 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.
In Internet Explorer 7 or Firefox, when you select the Upload action on the Documents page or in a Documents service task flow, you are not able to specify a file by pressing the Enter key to select the Browse button:
In Internet Explorer 7, this action opens the File Upload dialog to select a file, but when you select the Upload button, an error message displays "Please verify your upload data" and the selected file is removed from the Document to Upload field.
In Firefox: This action has no effect.
As a workaround in both Internet Explorer 7 and Firefox, press the spacebar to select the Browse button.
If your environment supports Global Policy Attachments (GPA), leave the Client Security Policy property blank when you configure the Oracle 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 "Oracle Content Server Connection Parameters" in Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.
When a Space template with public access is imported into another instance of WebCenter Spaces, the template appears as public but the grants are not imported properly. Creating a Space based on this template by using the UI works fine, but creating a Space by using the WebService call fails with an exception.
As a workaround, in the Spaces UI, revoke the public access from the template, and then grant the public access again.
Customizations made to task flows created at runtime are base document edits, and therefore, cannot be reset. Consequently, when editing a task flow created at runtime in Oracle Composer, customizations are saved even if you do not explicitly click Save.
Although the Reset Task Flow button is displayed for runtime task flows, it is does not reset customizations.
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.
If you use a screen reader, when you are adding resources from the Resource Catalog, JAWS announces all Resource Catalog items as "Add". This makes it difficult to identify the selected resource. To work around this issue, press the Tab key to get to the Add link for the resource, then press the Down Arrow key. JAWS then reads the description of the resource.
If you include the Connections Network task flow in a custom Resource Catalog and use that catalog in your application, and then try to add this task flow to a system page, you get an error. This error prevents you from editing any other task flow on the page. To work around this issue, click the Restore Default link on the system page to undo all changes made to the page, including removal of the Connections Network task flow.
If the WebCenter domain has been extended using the Oracle BPM Spaces template, and Process Spaces has been installed, any attempt to log in to WebCenter Spaces throws exceptions if the Oracle BPM server is down.
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.
In a WebCenter Portal application, to provide language support for component properties edited at runtime, Oracle Composer enables users to edit resource strings for properties that take String values. At runtime, when you try to override the default content in the resource bundle by directly entering values in the Select Text Resource dialog, the changes do not take effect and the page may appear blank.
The workaround is to create a new resource string instead of directly entering values in the Select Text Resource dialog. To create a new resource string, use the Create link in the Select Text Resource dialog and enter the required values in the search results table. Clicking the Use button in the last column selects this string for use as the current property value. For information, see the "Edit Resource Strings" section in Oracle Fusion Middleware Developer's Guide for Oracle WebCenter."
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.
If you upgrade a WebCenter Spaces application in which the display order of business role pages was customized, you may find that you cannot edit options on the Administration-General page. To workaround this issue:
Use WLST to export the base document webcenter-config.xml:
exportMetadata(application='webcenter', server='WC_Spaces', toLocation='/tmp/mydata', docs='/oracle/webcenter/webcenterapp/metadata/webcenter-config.xml')
Delete or comment out the : <br-pages-sequence> node.
For example, remove:
<webcenter:br-pages-sequence> /oracle/webcenter/page/scopedMD/s8bba98ff_4cbb_40b8_beee_296c916a23ed/businessRolePages/ActivityStreamMainView.jspx /oracle/webcenter/page/scopedMD/s8bba98ff_4cbb_40b8_beee_296c916a23ed/businessRolePages/DocumentsMainView.jspx /oracle/webcenter/page/scopedMD/s8bba98ff_4cbb_40b8_beee_296c916a23ed/businessRolePages/SpacesMainView.jspx /oracle/webcenter/page/scopedMD/s8bba98ff_4cbb_40b8_beee_296c916a23ed/businessRolePages/SpaceTemplatesMainView.jspx /oracle/webcenter/page/scopedMD/s8bba98ff_4cbb_40b8_beee_296c916a23ed/businessRolePages/MyProfileMainView.jspx /oracle/webcenter/page/scopedMD/s8bba98ff_4cbb_40b8_beee_296c916a23ed/businessRolePages/TagCenterMainView.jspx /oracle/webcenter/page/scopedMD/s8bba98ff_4cbb_40b8_beee_296c916a23ed/businessRolePages/AnalyticsConsoleMainView.jspx </webcenter:br-pages-sequence>
Save the changes.
Use WLST to import the modified file back to MDS.
importMetadata(application='webcenter', server='WC_Spaces', fromLocation='/tmp/mydata', docs='/oracle/webcenter/webcenterapp/metadata/webcenter-config.xml')
Navigating to the same page as the current page with the out-of-the-box navigation task flows fails in WebCenter Portal applications.
The workaround for this issue is to extend the CustomPortalNavigation class and register it in web.xml.
Create a new Java class in your Portal project that extends oracle.webcenter.portalframework.sitestructure.PreferencesBean.
For example:
Sign Inpackage portal;
import oracle.webcenter.portalframework.sitestructure.PreferencesBean;
public class CustomPortalNavigation extends PreferencesBean {
public CustomPortalNavigation () {
super();
}
}
Register this new Java class in web.xml with the navigation framework as a CustomPortalNavigation as follows:
<context-param> <param-name> Oracle.webcenter.portalframework.sitestructure.CustomPortalNavigationImpl </param-name> <param-value>portal.CustomPortalNavigation</param-value> </context-param>
If an application is configured to automatically navigate to a page that is accessible only to authenticated users, login to the application fails to navigate to the target page. The browser either shows an empty popup or 404 error.
The workaround for this issue is as follows:
Create a Java class in the application that extends the framework's CustomViewHandler and overload the getActionURL method, for example:
package portal;
import java.beans.Beans;
import javax.faces.application.ViewHandler;
import javax.faces.context.FacesContext;
import oracle.webcenter.portalframework.sitestructure.SiteStructure;
import oracle.webcenter.portalframework.sitestructure.SiteStructureContext;
import oracle.webcenter.portalframework.sitestructure.SiteStructureResource;
import oracle.webcenter.portalframework.sitestructure.SiteStructureUtils;
import oracle.webcenter.portalframework.sitestructure.handler.CustomViewHandler;
public class ApplicationViewHandler extends CustomViewHandler {
public ApplicationViewHandler(ViewHandler viewHandler) {
super(viewHandler);
}
/*
* Extend to address issue with bug 11076967 involving login
*/
@Override
public String getActionURL(FacesContext fctx, String viewId) {
String urlStr = viewId;
if (Beans.isDesignTime()) {
return m_baseHandler.getActionURL(fctx, urlStr);
}
// Only perform the pretty url lookup if the request was from our
// navigation processAction
if (isRequestDrivenByNavigation(fctx)) {
SiteStructure model =
SiteStructureContext.getInstance().getCurrentModel();
if (model != null) {
SiteStructureResource resource = model.getCurrentSelection();
if (resource != null) {
// Bug 11076967
// Only translate to pretty URL if the viewId is that of the
// resource.
// There is a usecase (bug 11076967) where the viewId is
// the login_success outcome in which case, we shouldn't touch it
String resourceViewId = findTargetViewId(fctx, resource);
if (resourceViewId != null &&
resourceViewId.equals(viewId))
urlStr = "/" +
SiteStructureUtils.encodeUrl(resource.getPrettyUrl());
}
}
}
// Get the base handler to tag on anything else that might be needed
// which includes the _adf.ctrl-state
String ret = m_baseHandler.getActionURL(fctx, urlStr);
return ret;
}
}
Register the above view handler with JSF in faces-config.xml, replacing the existing oracle.webcenter.portalframework.sitestructure.handler.CustomViewHandler entry:
<faces-config version="1.2" xmlns="http://java.sun.com/xml/ns/javaee">
<application>
<default-render-kit-id>oracle.adf.rich</default-render-kit-id>
<view-handler>portal.ApplicationViewHandler</view-handler>
</application>
...
The URL for the Administration Page has changed in 11.1.1.4.0, therefore any hardcoded links in page templates that point to the Administration Page must be changed to use the new URL:
/oracle/webcenter/webcenterapp/view/pages/admin/WebCenterAdmin-Communities.jspx
Alternatively, create a new page template and use the Administration link Spaces component to link to the Administration Page without having to explicitly provide a URL.
If users change their language preference, it overrides the language selected for the Space. To display the language selected for the Space, users must clear the browser cookies and reload the Space.
Seeded business role pages, such as Activities and Spaces, are available to all users by default. Currently, the WebCenter Spaces UI does not provide a means of performing security-related operations on seeded business role pages. This means you cannot hide seeded business role pages from all users through the WebCenter Spaces UI. However, there is a workaround:
Export the pages.xml files for anonymous-role and authenticated-role from MDS.
exportMetadata(application='webcenter',server='WC_Spaces',toLocation='/scratch/mdsdump',
docs='/oracle/webcenter/page/scopedMD/s8bba98ff_4cbb_40b8_beee_296c916a23ed/role/anonymous-role/pages.xml')
exportMetadata(application='webcenter',server='WC_Spaces',toLocation='/scratch/mdsdump',
docs='/oracle/webcenter/page/scopedMD/s8bba98ff_4cbb_40b8_beee_296c916a23ed/role/authenticated-role/pages.xml')
Go through these pages.xml files and, based on your requirement, mark business role pages hidden or shown:
<!-- Business Role Pages -->
<pageDef
id="Page_2eb852ac_10f5902cb2f__7ff7"
contentMRef="/oracle/webcenter/page/scopedMD/s8bba98ff_4cbb_40b8_beee_296c916a23ed/businessRolePages/ActivityStreamMainView.jspx"
shared="false"
hidden="false"
/>...
Set hidden="true" for the pages that should not be shown.
Set hidden="false" for pages that should be shown.
Upload the changed files back to the repository.
importMetadata(application='webcenter',server='WC_Spaces',fromLocation='/scratch/mdsdump',
docs='/oracle/webcenter/page/scopedMD/s8bba98ff_4cbb_40b8_beee_296c916a23ed/role/anonymous-role/pages.xml')
importMetadata(application='webcenter',server='WC_Spaces',fromLocation='/scratch/mdsdump',
docs='/oracle/webcenter/page/scopedMD/s8bba98ff_4cbb_40b8_beee_296c916a23ed/role/authenticated-role/pages.xml')
An Oracle WebCenter Source (for searching WebCenter Spaces objects, such as lists, pages, Spaces, and people connections profiles) currently cannot access SSL-protected WebCenter endpoints. Oracle is working on a patch for this.
In a WebCenter Portal application that contains a custom ADF taskflow that enables you to generate a downloadable Excel spreadsheet, the export operation may fail when you click the Export to Excel button for the first time. If you encounter this problem, try to export the content to Excel again.
The process of building and storing similarity scores for Activity Graph can consume a large amount of temporary and undo table space when the size of the graph grows large. To prevent errors, ensure that the temporary and undo tablespaces assigned to the Activities schema are configured to auto-extend.
The Back to Portal link redirects to http://server:port/contextroot. The default value in web.xml for this is /index.html and the default value in index.html redirects to ./faces/pages_home. If there is no pages_home node in the selected default navigation model for the application, this results in a page not found error. To resolve this issue, update web.xml and index.html to reflect the structure of your application.
If your application uses dynamically created navigations at runtime, it is advisable to change the landing page to be a .jsp page. This enables you to drive the actual node to redirect to within the navigation from a backing bean. The bean can either choose to go to the first navigable page, or can navigate to a node based on an external ID. In the latter case, you must set the external ID in the navigation model.
In WebCenter Spaces, when a portlet is added to a page, the portlet binding is configured to automatically listen for parameters and events generated on the page. Currently, there is no way to turn off this automatic parameter and event listening in the WebCenter Spaces UI.
To turn off automatic parameter and event listening:
Export the Space.
In JDeveloper, open the page definition for the page containing the portlet.
Edit the portlet binding to set the listenForAutoDeliveredPortletEvents and listenForAutoDeliveredParameterChanges attributes to false:
<portlet id="p2_1"
...
listenForAutoDeliveredPortletEvents="false"
listenForAutoDeliveredParamtersChange="false"
...
/>
Import the Space back into WebCenter Spaces.
In WebCenter Spaces, using ILS as the primary security mechanism for a Space may become difficult to administer when the number of users grow. Moreover, ILS may not be as efficient as the Space security model. Therefore, Oracle recommends using ILS only to define security for the documents or folders that do not fit within the Space security model. For example, documents and folders to which only a restricted set of users have access. For information about security, see the section "Managing Roles and Permissions for a Space" in Oracle Fusion Middleware User's Guide for Oracle WebCenter Spaces.