13 Oracle WebCenter

This chapter describes issues associated with Oracle WebCenter. It includes the following topic:

13.1 General Issues and Workarounds

This section describes general issues and workarounds. It includes the following topics:

13.1.1 Using Oracle WebLogic Communications Server

Oracle WebLogic Communications Server (OWLCS) is provided as a sample for development only. It should not be used for production deployments.

13.1.2 Using Jive Forums Documentation

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.

13.1.3 Application Role Names Cannot Include Thai Characters

In this release, application role names cannot contain Thai characters.

13.1.4 Pagelet Producer Failover Support

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.

13.1.5 Configuring a Client Security Policy for Oracle Content Server Connections

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.

13.1.6 Importing Space Templates with Public Access

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.

13.1.7 Option to Create a Portal Resource Displayed for Design-Time Task Flows

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.

13.1.8 Connections Network Task Flow on System Pages Not Supported

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.

13.1.9 Cannot Log In to WebCenter Spaces if Oracle BPM is Down

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.

13.1.10 SQL Query with NCHAR Data Type Throws Exception

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.

13.1.11 Modifying Default Resource Strings for Language Support

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."

13.1.12 Setting Up WNA-Based SSO Using JDK 1.6.22 Produces an Error

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.

13.1.13 Cannot Navigate to the Current Page Using Out-of-the-Box Navigation Task Flows in WebCenter Portal Applications

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.

  1. Create a new Java class in your Portal project that extends oracle.webcenter.portalframework.sitestructure.PreferencesBean.

    For example:

    package portal;
    import oracle.webcenter.portalframework.sitestructure.PreferencesBean;
    public class CustomPortalNavigation extends PreferencesBean {
         public CustomPortalNavigation () {
  2. Register this new Java class in web.xml with the navigation framework as a CustomPortalNavigation as follows:


13.1.14 Login Outcome Fails to Navigate to Privileged Pages

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:

  1. 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) {
      * Extend to address issue with bug 11076967 involving login
      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 =
          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 &&
                  urlStr = "/" +
        // 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;
  2. 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">

13.1.15 Space Language Does Not Take Effect

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.

13.1.16 Performing Security-Related Operations on Business Role Pages

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:

  1. Export the pages.xml files for anonymous-role and authenticated-role from MDS.

  2. Go through these pages.xml files and, based on your requirement, mark business role pages hidden or shown:

    <!-- Business Role Pages -->
    • Set hidden="true" for the pages that should not be shown.

    • Set hidden="false" for pages that should be shown.

  3. Upload the changed files back to the repository.


13.1.17 Unable to Access SSL-Protected WebCenter Endpoints

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.

13.1.18 Unable to Export Content to Excel by using a Custom ADF Taskflow

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.

13.1.19 Errors for Activity Graph Queries When the Activity Graph Engines are Running

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.

13.1.20 Page Not Found Error When Clicking Back to Portal Link

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.

13.1.21 Turning Off Automatic Event Listening in WebCenter Spaces

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:

  1. Export the Space.

  2. In JDeveloper, open the page definition for the page containing the portlet.

  3. Edit the portlet binding to set the listenForAutoDeliveredPortletEvents and listenForAutoDeliveredParameterChanges attributes to false:

    <portlet id="p2_1"
  4. Import the Space back into WebCenter Spaces.

13.1.22 Cannot Add Certain Task Flows on a Space Page with the Default Page Template Catalog

When using the Default Page Template Catalog (for example, when editing page templates), users are unable to add the following task flows to a Space page:

  • All Saved Searches

  • Similarly Tagged Items

  • Tags

  • Tag Cloud

  • Tag Cloud Related Items

  • Publisher

This is due to a missing single quote in the attr.text attribute, which causes a parse exception when the task flow is added to a page.

The workaround is to edit the Default Page Template Catalog to add the missing quotes. For example:

  1. Log on as an administrator.

  2. Navigate to the Administration - Resources - Resource Catalogs page.

  3. With the Default Page Template Catalog selected, click Edit - Copy.

  4. With this new (copied) catalog selected, select Edit, and for each of these entries (under either the Tagging and Searching group or the Social and Communications group), do the following:

    1. Select the entry and click Edit (pencil).

    2. Click the Options tab, and add the missing single quote in the attr.text attribute; for example, ['TAGS.TITLE'].

  5. Click OK, then OK again to save and close the catalog.

  6. Back on the Administration - Resources - Resource Catalogs page, select this new catalog, and click Edit - Show to make it available.

  7. Navigate to the Administration – Configuration page.

  8. In the Resources section, select this new catalog for the following:

    • Resource Catalog for Page Templates in Spaces

    • Resource Catalog for Page Templates in Home Space

  9. Click Apply to save these changes.

13.1.23 Search Limitations with Special Characters

Several special characters are filtered out in WebCenter search. For example, when you search for the keyword Q2$Total, WebCenter does not return the wiki page named Q2$Total in search results.

With Oracle SES, the following special characters are not recognized:

! @ # $ % ^ & ( ) + = [ ] { } | ; ' \ " , < > / ? ` ~

With WebCenter live search, the hyphen [-] and wildcard [*] characters additionally are not recognized.

13.1.24 Configuring the REST Server Post-Installation

For certain features of the WebCenter REST server to work correctly when using a REST client like the Oracle WebCenter 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 weblogic.conf.

  • If you are running Oracle HTTP Server (OHS) in front of Weblogic Server, add this flag to mod_wl_ohs.conf.

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

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

13.1.25 Resources in WebCenter Portal Application Disappear after Redeployment of Application

If a WebCenter Portal 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.
  1. Download the mds-transfer-config.xml file from the following location:


  2. Extract the MAR file (for example AutoGeneratedMar.mar) from the EAR file.

  3. 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.

  4. Update the MAR file with META-INF\mds-transfer-config.xml, for example:

    jar -uvf AutoGeneratedMar.mar META-INF\mds-transfer-config.xml
  5. Update the EAR file with the updated MAR file:

    jar -uvf YourApp.ear AutoGeneratedMar.mar
  6. Redeploy YourApp.mar.

13.1.26 Configuring a Proxy Server for External Links in Activity Stream

You must configure a proxy server if you want to display external links in Activity Stream task flows. Both the RSS service and the Activity Stream

service share the same proxy server settings. For information, see "Setting Up a Proxy Server for External RSS News Feeds" in Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

13.1.27 Installing Oracle SES

Oracle Secure Enterprise Search (SES) release now is available and is recommended as the Oracle SES release to use with WebCenter release

Download Oracle SES from http://www.oracle.com/technetwork/search/oses/downloads/index.html. No additional Oracle patches are required with Oracle SES release


Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter describes required steps for installing Oracle SES that involve unzipping the webcenter_search_ses_plugins.zip file to add several WebCenter jar files to Oracle SES. This zip file is not necessary with Oracle SES release

For more information, refer to the Oracle SES Online Documentation Library 11g Release 1 ( available here on OTN: