Troubleshooting WebCenter Portal

Using My Oracle Support for Additional Troubleshooting Information

You can use My Oracle Support (formerly MetaLink) to help resolve Oracle WebCenter Portal problems. My Oracle Support contains several useful troubleshooting resources, such as:

Knowledge base articles
Community forums and discussions
Patches and upgrades
Certification information

Note:

You can also use My Oracle Support to log a service request.

You can access My Oracle Support at https://support.oracle.com.

Troubleshooting Oracle WebCenter Portal Configuration Issues

This section includes the following subsections:

Configuration Options Unavailable

Problem

When you try to configure WebCenter Portal through Fusion Middleware Control, the following message displays:

Configuration options currently unavailable. The application application_name might be down, did not start-up properly, or is incorrectly packaged.
Check the log files for further details.

For example, you try to change options available through the Application Settings screen or configure connections through the WebCenter Portal Service Configuration screen in Fusion Middleware Control.

Solution

Check the application's diagnostic logs. For WebCenter Portal, the log file is available in the DOMAIN_HOME/servers/ServerName/logs directory. The log file follows the naming convention of ServerName-diagnostic.log. See also, Viewing and Configuring WebCenter Portal Logs.

Analyze messages for the modules oracle.adf.mbean.share.connection and oracle.adf.mbean.share.config, and determine what must be done.

Logs Indicate Too Many Open Files

Problem

WebCenter Portal is inaccessible or displaying error messages and the diagnostic log files indicates that there is an issue with 'too many open files'.

Solution

Do the following:

Check the number of file handles configured on each of the back-end servers, primarily the database, and increase appropriately.
If the problem persists after increasing the file handles, check the value of fs.file-max in the /etc/sysctl.conf file and increase the value appropriately.

Troubleshooting Oracle WebCenter Portal WLST Command Issues

This section includes the following topics:

No Oracle WebCenter Portal WLST Commands Work

Problem

You are unable to run any WLST commands.

Solution

Ensure the following:

Always run Oracle WebCenter Portal WLST commands from Oracle home directory (ORACLE_HOME/common/bin).

If you attempt to run Oracle WebCenter Portal WLST commands from the wrong directory you will see a NameError.
No files other than Python are stored in the WLST source directory: WCP_ORACLE_HOME/common/bin/wlst. This directory must contain files with the .py extension only.

The default set of files in this location contain legal Python files from Oracle. It is possible that a user copied some non-python script to this directory, for example, a backup file or a test python file with syntax errors.
webcenter-wlst.jar is located at WCP_ORACLE_HOME/common/bin/wlst/lib.

Connection Name Specified Already Exists

Problem

You are unable to create a connection with the name Connection_Name. The following message displays:

A connection with name Connection_Name already exists.

For example, you try to create an external application connection using the WLST command createExtAppConnection or connect to a mail server using createMailConnection.

Solution

Connection names must be unique (across all connection types) within WebCenter Portal. This error occurs when you try to create a connection with a name that is in use. Ensure that you use a unique name for your connection.

WLST Shell is Not Connected to the WebLogic Server

Problem

You must connect to the Administration Server for Oracle WebCenter Portal before running WLST commands. Oracle WebCenter Portal WLST commands do not work without a connection.

Solution

Run the following command to connect the WLST shell to the managed server:

connect(username, password , serverhost:serverport)

More Than One Application with the Same Name Exists in the Domain

Problem

You attempt to perform an operation on WebCenter Portal, such as create a connection for a service or register a portlet producer, and the following message displays:

Another application named "YourApplicationName" exists. Specify the Server on which your application is deployed. Use: server="YourServerName".

This message displays if there are multiple applications with the same name in the domain. This usually happens in a cluster environment, where the same application is deployed to multiple managed servers.

For example, you tried to register a portlet producer for WebCenter Portal using the following WLST command:

registerWSRPProducer(appName='webcenter', name='MyWSRPSamples', url='http://myhost.com:9999/ portletapp/portlets/wsrp2?WSDL')

Solution

Specify on which managed server you want to run the WLST command, that is, include the server argument. For example:

registerWSRPProducer(appName='webcenter', name='MyWSRPSamples', url='http://myhost.com:9999/portletapp/portlets/wsrp2?WSDL', server=WC_CustomPortal2)

More Than One Application with the Same Name Exists on a Managed Server

Problem

You attempt to perform an operation on WebCenter Portal such as create a connection for a service or register a portlet producer, and the following message displays:

Another application named application_name" exists on the server managedServerName.

This message indicates that there are multiple applications with the same name on specified managed server. This usually happens when applications are assigned different versions.

For example, you tried to register a portlet producer for an application named "MyApp" using the following WLST command:

registerWSRPProducer(appName='myApp', name='MyWSRPSamples', url='http://myhost.com:9999/portletapp/portlets/wsrp2?WSDL')

Solution

Specify on which application version you want to run the WLST command, that is, include the server and applicationVersion arguments. For example:

registerWSRPProducer(appName='myApp', name='MyWSRPSamples', url='http://myhost.com:9999/portletapp/portlets/wsrp2?WSDL', server=WC_CustomPortal1, applicationVersion=2)

Already in Domain Runtime Tree Message Displays

Problem

While running a WLST command, the following message displays:

Already in Domain Runtime Tree

Solution

None required. This is for information only.

Troubleshooting Oracle WebCenter Portal Performance Issues

Use the information in this section to help diagnose performance-related issues for Oracle WebCenter Portal.

This section contains the following sub sections:

About Performance Monitoring and Troubleshooting Tools

Various tools are available for monitoring and troubleshooting performance issues with your Oracle WebCenter Portal environment.

Table F-1 Performance Monitoring and Troubleshooting Tools

Tool	Use to...	See
Enterprise Manager
Fusion Middleware Control	Monitor WebCenter Portal metrics and log files in real-time mode for a single Oracle Fusion Middleware Farm. Check service configuration, including MDS and partitions for WebCenter Portal deployments.	Starting Enterprise Manager Fusion Middleware Control
Grid Control	Monitor WebCenter Portal metrics in real time and from a historical perspective for trend analysis, as well as monitor the underlying host and operating system, databases, and more. Oracle Enterprise Manager 11g Grid Control must be installed separately as it is not a part of the Oracle Fusion Middleware 11g installation. With Grid Control, you can centrally manage multiple Oracle Fusion Middleware Farms and WebLogic Domains.	Oracle Enterprise Manager Cloud Control
WebCenter Portal Page Performance Analyzer	Analyze the performance of portal pages in WebCenter Portal. This tool dynamically measures and presents the performance of individual page components when you display pages in WebCenter Portal.	How to Identify Slow Page Components
JConsole	Graphically monitor Java applications and Java virtual machines (JVM).	How to Use JConsole to Monitor JVM
JRockit Mission Control	Capture and present live data about memory, CPU usage, and other runtime metrics.	Troubleshooting Slow Requests Using JFR Recordings
Eclipse Memory Analyzer	Find memory leaks and reduce memory consumption.	Troubleshooting Memory Leaks and Heap Usage Problems
Threadlogic	Analyze thread dumps.	Generating Thread Dumps to Diagnose Extremely Slow Page Performance, High Thread Counts, and System Hangs

How to Identify Slow Pages

Use Fusion Middleware Control to determine the slowest pages in WebCenter Portal. If a poorly performing page is also very popular (the Invocation metric is high) then it makes sense for you to focus efforts to improve performance on those pages.

To find the slowest pages:

Log in to Fusion Middleware Control and navigate to the home page for WebCenter Portal, as described in Navigating to the Home Page for WebCenter Portal.
From the WebCenter Portal menu, select Monitoring > Recent Page Metrics.

Page requests that respond slower than the pageResponseTime threshold display "red" in the chart at the top of the page.
Click the Sort Descending arrow in the Time (ms) column to sort the page requests by response times.

Page response times that exceed the threshold display "orange" in the table.
Identify the slowest pages and make a note of the portal in which the page displays.
For more detailed metrics, including how frequently the slowest pages are requested, From the WebCenter Portal menu, select Monitoring > Overall Page Metrics.

Note: Requests for pages in the Home portal are excluded from the "Overall Page Metrics" page.

How to Identify Slow Page Components

Use WebCenter Portal's page performance analyzer to quickly see how long individual components take to display on a portal page, as well as the overall time taken to display a page. When enabled, this tool dynamically measures and presents the performance of individual page components whenever you display a portal page.

The portal page performance analyzer is useful to developers who are performing first level performance analysis, customers who build their own pages, and any user who customizes pages in WebCenter Portal.

This section includes the following subsections:

About the Portal Page Performance Analyzer

The portal page analyzer offers a simple way to diagnose slow pages and requires minimal set up or configuration. When this feature is on, the time spent on "high level" page components is calculated and displayed so you can see at a glance which components are slowing down your page. The overall time spent on the page also displays at the top left of the page (see Figure F-1).

Figure F-1 Portal Page Displays Timing Information

Description of "Figure F-1 Portal Page Displays Timing Information"

About Page Component Timings

In WebCenter Portal, "high level" page components are wrapped in a ShowDetailFrame so they can be moved, hidden or shown on the page, and edited by Oracle Composer and it is the overall timing for each ShowDetailFrame that displays.

About Overall Page Time

The overall page time is the sum of the individual page component timings, plus some additional processing time for page-level operations such as session replication, save and restore page state, page level security checks, and so on. For more consistent results, refresh the pages by clicking through the testing pages before enabling Page Performance Analysis.

Color Coding

Performance timings display in various colors to help alert you to problem areas. Refer to the following table:

Color	Time to Display
Green	< 100 ms
Green/Yellow	100 - 500 ms
Yellow	500 ms - 1 second
Orange	1 - 3 seconds
Red	> 3 seconds

Enabling and Disabling Portal Page Performance Analysis

The portal page performance analyzer is disabled out-of-the-box. To make use of this feature, an administrator must specifically enable its use; while the impact on page performance to run this tool is minimal some additional page processing is required.

In a production environment, Oracle recommends that the analyzer is generally disabled to avoid the additional performance data collection and processing and then dynamically enabled when someone reports performance issues for a particular page.

If you do not want end users to see performance data in a production environment, this is another reason to disable the analyzer most of the time.

To enable or disable the portal page analyzer for a WebCenter Portal instance:

Use the WLST command exportMetadata to export the base webcenter-config.xml file from MDS.

For example:

exportMetadata(application='webcenter', server='WC_Portal', toLocation='/tmp/mydata', docs='/oracle/webcenter/webcenterapp/metadata/webcenter-config.xml')

Open webcenter-config.xml exported from MDS in a text editor and set the perfdebug-enabled attribute to true to enable or false to disable this feature.
For example:
```
<webcenter:perfdebug-enabled>true</webcenter:perfdebug-enabled>
```
Save and close webcenter-config.xml.

Import the updated webcenter-config.xml file to MDS.

For example:

importMetadata(application='webcenter', server='WC_Portal', fromLocation='/tmp/mydata', docs='/oracle/webcenter/webcenterapp/metadata/webcenter-config.xml')

There is no need to restart WebCenter Portal to effect this change.

Page performance information does not automatically display after you enable this feature. Anyone who wants to see timing information on portal pages must specifically request that the information displays. For details, see Displaying and Hiding Page Timing Information for Your Current Session.

Displaying and Hiding Page Timing Information for Your Current Session

When an administrator enables the page performance analyzer in an WebCenter Portal instance, anyone with access to that WebCenter Portal instance can elect to display or hide page timing information, for their current user session, by appending the perfDebug parameter to the page URL as follows:

To...	Add a perfDebug parameter to the page URL
Display timing information on portal pages	`&perfDebug=on`
Stop displaying page performance information	`&perfDebug=off`

To display timing information on portal pages:

Verify that your administrator enabled the page performance analyzer in your WebCenter Portal instance.

See also Enabling and Disabling Portal Page Performance Analysis.
Log in to WebCenter Portal and navigate to the portal page that you want to investigate.

You do not need to log in if the page is a public page.

Add &perfDebug=on to the end of the page URL (Figure F-2).

For example:

http://mycompany.com/webcenter/portal/MySalesPortal?_adf.ctrl-state=mji8314i6_4&_afrLoop=474789135539036&perfDebug=on

Click "Go" or press Enter to redisplay the page with timing information (as shown in Figure F-1).

All subsequent pages that you display show timing information as well.

Figure F-2 Appending the perfDebug Parameter to Page URLs

Description of "Figure F-2 Appending the perfDebug Parameter to Page URLs"

To stop displaying page timing information:

In your browser, add &perfDebug=on to the end of any page URL (Figure F-2).

For example:

http://mycompany.com/webcenter/portal/MySalesPortal?_adf.ctrl-state=mji8314i6_4&_afrLoop=474789135539036&perfDebug=off

Click "Go" or press Enter to display the page again without timing information.

Using the Page Performance Analyzer to Troubleshoot Performance Issues

The steps in this section describe how to troubleshoot slow pages using WebCenter Portal tools:

If a user reports performance issues with a particular page, navigate to the slow pages and confirm that the slow performance consistently reproduces.

Alternatively, use Fusion Middleware Control to proactively identify the slowest pages in your application. See How to Identify Slow Pages.
Append &perfDebug=on to the page URL to display timing information for the page.

See also, Displaying and Hiding Page Timing Information for Your Current Session.

Note:

If page timing information does not display, ask your administrator to enable the page performance analyzer. For details, see Enabling and Disabling Portal Page Performance Analysis.
Identify the slowest page components, and troubleshoot the issue further:
For example, if the slow component contains:
- Document, wiki, or content presenter, check the performance of the back-end Content Server and the database that Content Server is using.
- Activity stream, use AWR reports to check database performance and to see if you can tune the database table used by activity stream.
- Collaboration features, check the performance of the associated back-end server. For example, for announcements or discussions, monitor the performance of the discussions server.
- Portlets, use Fusion Middleware Control to monitor portlet request timing information, errors, portlet producer performance, and so on
If necessary, add the slow page component to a separate "blank" page and then do further profiling.

For example, use JRockit flight recording to pinpoint the bottleneck.

How to Troubleshoot Slow Page Requests

Use the information in this section to diagnose issues relating to poor page performance:

Troubleshooting Live Requests

To troubleshoot slow page requests that are still running, extract and view a JRockit Flight Recorder (JFR) recording against the server on which the user session is running. See also, How to Troubleshooting Requests using JRockit Flight Recordings.

If you compare the thread dumps, you might see threads that spent a long time on certain method calls as the call stacks are the same in several consecutive thread dumps. For example, you might see a method call to a database, Oracle WebCenter Content Server, collaboration server, portlet producer, LDAP server, and so on, in which case you can investigate the associated backend server to diagnose the issue further.

Troubleshooting Stuck Threads

Stuck threads can occur for several reasons:

Server is nearly out of memory. If the server is close to out of memory, all requests slow down. To resolve out-of-memory issues, see Troubleshooting Slow Requests Using JFR Recordings.
Deadlock threads. Take thread dumps and search for deadlock threads. This normally exposes an issue with the product code.

Extremely slow page requests. Take several evenly spaced thread dumps and find out which method is taking a long time to execute.

If a request is taking longer than 10 minutes, the stuck thread is reported to Oracle WebLogic Server server_name.out in the following directories:

(UNIX) DOMAIN_HOME/servers/server_name/logs
(Windows) DOMAIN_HOME\servers\server_name\logs

For example:

<Mar 4, 2012 7:44:08 AM PST> <Error> <WebLogicServer> <BEA-000337> 
<[STUCK] ExecuteThread: '19' for queue: 'weblogic.kernel.Default (self-tuning)'
 has been busy for "600" seconds working on the request
 "weblogic.servlet.internal.ServletRequestImpl@18986012[

GET
 /server_name/faces/PimDashboardUiShellPage?_afrLoop=1398820150000&_afrWindowMod
e=0&_adf.ctrl-state=a44e7uxcc_13 HTTP/1.1
Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg,
 application/x-shockwave-flash, application/x-ms-application,
 application/x-ms-xbap, application/vnd.ms-xpsdocument, application/xaml+xml,
 application/vnd.ms-excel, application/vnd.ms-powerpoint, application/msword,
 */*
Accept-Language: fr
UA-CPU: x86
...
]", which is more than the configured time (StuckThreadMaxTime) of "600"
 seconds
. Stack trace:
Thread-164 "[STUCK] ExecuteThread: '19' for queue: 'weblogic.kernel.Default
 (self-tuning)'" <alive, in native, suspended, priority=1, DAEMON> {
    jrockit.net.SocketNativeIO.readBytesPinned(SocketNativeIO.java:???)
    jrockit.net.SocketNativeIO.socketRead(SocketNativeIO.java:24)
    java.net.SocketInputStream.socketRead0(SocketInputStream.java:???)
    java.net.SocketInputStream.read(SocketInputStream.java:107)
...

Diagnosing a Stuck Thread

If the stack shows the thread is waiting for a response from another server, check the status of the other server and see it has performance problems before proceeding with the steps below.

To determine what the stuck thread was doing prior to becoming stuck, perform the following steps:

Look at the next few log messages in server_name.out for a message indicating an incident has been created. For example:
```
<Mar 4, 2012 7:44:10 AM PST> <Alert> <Diagnostics> <BEA-320016>  <Creating diagnostic image in DOMAIN_HOME/servers /server_name/adr/diag/ofm/MyDomain/ server_name_1/incident/incdir_394 with a lockout minute  period of 1.>
```
The above message may not always appear after each stuck thread reported. It is printed at most four times an hour. If the message does not appear, manually look for the incident directory by checking the readme file in the subdirectories under the following directories:
```
(UNIX) DOMAIN_HOME/servers/server_name/adr/diag/ofm/domain_name/server_name/incident
(Windows) DOMAIN_HOME\servers\server_name\adr\diag\ofm\domain_name\server_name\incident
```
The incident directory contains a WLDF diagnostic image which contains the JFR recording, and a file containing the thread dump.

For more information about diagnosing incidents, see Diagnosing Problems in the Administering Oracle Fusion Middleware.
Review the thread dump to find the call stack of the thread. If the thread is blocked waiting for a lock, check what the thread holding the lock is doing.
If the call stack shows that JDBC calls are taking a long time, generate an AWR report on the database to find the query and which table to look and tune.
Review the JRockit flight recording file JRockitFlightRecorder.jfr for more details. You will also need the ECID of the request which is recorded in the readme.txt file of the incident directory, and also the Oracle WebLogic Server log.

See also, How to Troubleshooting Requests using JRockit Flight Recordings.

The ECID of the request that caused the stuck thread is recorded in the error message.

Troubleshooting Slow Requests Using JFR Recordings

See How to Troubleshooting Requests using JRockit Flight Recordings.

Troubleshooting Memory Leaks and Heap Usage Problems

If WebCenter Portal performance degrades over time, heap usage and garbage collection activity is increasing, and you see OutOfMemoryErrors, there could be memory leaks in the application causing the amount of free memory in the JVM to continuously decrease.

Figure F-3 Typical Memory Leak Trend in JConsole

Description of "Figure F-3 Typical Memory Leak Trend in JConsole"

To solve this problem:

Determine the cause of OutOfMemoryErrors errors:
- Review the server_name.out file for OutOfMemoryErrors errors.
  
  The server_name.out file is located at:
```
(UNIX) DOMAIN_HOME/servers/server_name/logs
(Windows) DOMAIN_HOME\servers\server_name\logs
```
- Take a memory dump when OutOfMemoryErrors errors occur.
  
  For example:
  
  On Sun HotSpot: jmap -dump:live,format=b,file=<path>/heap.hprof <pid>
  
  On JRockit: jrcmd <pid> hprofdump filename=<path>/heap.hprof
  
  You can configure JRockit to automatically generate a heap dump in HPROF binary format (.hprof file) each time an OutOfMemoryErrors occurs, by setting the JRockit JVM option, -XX:+HeapDumpOnOutOfMemoryError.
Restart the managed server.

If the problem persists, proceed to Step 3.
Open the heap.hprof file with a heap-dump analysis tool that can handle binary HPROF format, such as Eclipse Memory Analyzer.
Determine which objects and classes are retaining the most memory.
If necessary, take several heap dumps to determine which objects or classes are consuming and increasing the amount of memory.
Take at least two memory dumps:
- Take the first dump when the system is warmed up and stabilized.
- Take the second dump, when the system is about to run out of memory, that is, full garbage collection gets less than 300MB from the maximum heap size.
Instructions on how to take a heap dump using Sun HotSpot (jmap) or JRockit (jcrcmd) is described in step 1.

Many heap dump analysis tools, such as Eclipse Memory Analyzer, enable you to compare two heap dumps to identify memory growth areas.

Heap dumps provide information on why memory is retained (Retained Heap). Sometimes it is necessary to know how memory is allocated to further resolve the issue. For these cases, proceed to Step 6.
Use the JRockit Memory Leak Detector tool that is part of JRockit Mission Control Client to understand how memory is allocated.

Troubleshooting Slow Requests for Content

If slow page performance is due to content/document-related components, for example, Documents service task flows, Content Presenter task flows, wikis or blogs, Oracle recommends that you review performance metrics for the backend Oracle WebCenter Content Server (System Audit Information page). For details, see Viewing System Audit Information in Administering Oracle WebCenter Content.

Ensure that the systemdatabase tracing option is selected so you can see performance information for each query that is sent to the database. For details, see Server-Wide Tracing in Administering Oracle WebCenter Content.

How to Troubleshooting Requests using JRockit Flight Recordings

JRockit Flight Recorder (JFR) files contain a record of various events that consume time. If requests are slow, you can analyze the JRockit Flight Recorder (JFR) file to find out why request are taking time.

To create a JFR file:

Extract a JFR file from theOracle WebLogic Server server by running the following command:

UNIX) JROCKIT_HOME/bin/jrcmd jrockit_pid dump_flightrecording recording=1 copy_to_file=path compress_copy=true

(Windows) JROCKIT_HOME\bin\jrcmd.exe jrockit_pid dump_flightrecording recording=1 copy_to_file=path compress_copy=true

To view the file, start the JRockit Mission Control Client from the following directories:
```
(UNIX) JAVA_HOME/bin/bin/jrmc

(Windows) JAVA_HOME\bin\jrmc.exe
```
Select File > Open File to select the JFR file.

Locate the slowest requests or investigate a specific request:

To locate the slowest requests: To investigate a specific request:

To locate the slowest requests:	To investigate a specific request:
In the JRockitFlightRecorder.jfr page, click the Events icon. Click the Log tab at the bottom of the page. In the Event Type navigation pane on the left, locate Dynamic Monitoring System and then HttpRequest. Click HTTP request; de-select all the other event types. In the Log tab, in the Event Log section, click the Duration column to sort the duration in descending order. Each row corresponds to a HTTP Request and the duration column shows the response time for that request. Click the row in the table to view the attributes of the requests. In the Event Attributes sections, note the start time and the thread that serviced the request.	Find the Execution Context Identifier (ECID) of that request. If the request is related to an incident triggered by a `STUCK` thread, the incident `readme.txt` file will contain the ECID. Alternatively, you can search the Oracle WebLogic Server HTTP `access.log` for requests from specific users. See Viewing and Searching Log Files in the Administering Oracle Fusion Middleware. In the JRockit Mission Control Client, in the JRockitFlightRecorder.jfr page, select the WebLogic icon. Note: If the Weblogic icon is not available, select Help > Install Plugins to download the Oracle WebLogic Server plug-in. Click the ECIDs tab at the bottom of the page. In the ECIDs section, from Filter Column list, select ECID. Enter the ECID in the search box and select <Enter>. In the results table, highlight the row with the matching ECID and right-click to bring up the menu. Select Operative Set > Clear, and then Operative Set > Add matching ECID > ECID to add the ECID to the operative set. This enables users to view only events associated with the operative set. Click the Events icon. In the Event Type navigation pane on the left, locate Dynamic Monitoring System and then HttpRequest. Click HTTP request; de-select all the other event types. ** In the Event Log section, click Show Only Operative Set. Each row corresponds to the request with the matching ECID. Click the row in the table to view the attributes of the requests. Note the start time and the thread that serviced the request.

In the JRockitFlightRecorder.jfr page, click the Events icon.
Click the Log tab at the bottom of the page.
In the Event Type navigation pane on the left, locate Dynamic Monitoring System and then HttpRequest.
Click HTTP request; de-select all the other event types.
In the Log tab, in the Event Log section, click the Duration column to sort the duration in descending order.

Each row corresponds to a HTTP Request and the duration column shows the response time for that request.
Click the row in the table to view the attributes of the requests.
In the Event Attributes sections, note the start time and the thread that serviced the request.

Find the Execution Context Identifier (ECID) of that request.

If the request is related to an incident triggered by a STUCK thread, the incident readme.txt file will contain the ECID.

Alternatively, you can search the Oracle WebLogic Server HTTP access.log for requests from specific users. See Viewing and Searching Log Files in the Administering Oracle Fusion Middleware.
In the JRockit Mission Control Client, in the JRockitFlightRecorder.jfr page, select the WebLogic icon.

Note: If the Weblogic icon is not available, select Help > Install Plugins to download the Oracle WebLogic Server plug-in.
Click the ECIDs tab at the bottom of the page.
In the ECIDs section, from Filter Column list, select ECID.
Enter the ECID in the search box and select <Enter>.
In the results table, highlight the row with the matching ECID and right-click to bring up the menu.
Select Operative Set > Clear, and then Operative Set > Add matching ECID > ECID to add the ECID to the operative set.

This enables users to view only events associated with the operative set.
Click the Events icon.
In the Event Type navigation pane on the left, locate Dynamic Monitoring System and then HttpRequest.
Click HTTP request; de-select all the other event types. ** In the Event Log section, click Show Only Operative Set.

Each row corresponds to the request with the matching ECID.
Click the row in the table to view the attributes of the requests.
Note the start time and the thread that serviced the request.

Once you have identified the start time and the thread that serviced the request, navigate to the Logs tab, and drag the time selector at the top of the screen to include only the time window for the duration of the request.
In the Event Log section, perform the following search:
1. Deselect Show Only Operative Set.
2. Enter the thread name in the search box.
3. From the Filter Column list, select Thread.
4. Select <Enter>.
In the Event Type navigation pane on the left, click the events of interest. Typically, these events are located under nodes Dynamic Monitoring System, Java Application, and WebLogic > JDBC.

The selected events appear in the table in the Event Log section.
Click the Start Time column to sort the time when these events occur, or click the Duration column to view the events that took longest.

The JDBC Statement Execute events corresponds to SQL execution. If there are slow SQL statements, the event details give the SQL text. These events do not have callstacks.
To check the call stacks for slow SQL statements, view the Socket Read event that happens immediately after the JDBC Statement Execute event.

This event corresponds to Oracle WebLogic Server waiting for the SQL results to return, and it has callstack in the event details.
Review the call stacks for long Java Blocked and Java Wait events to see if you can identify what is causing slow performance.

See Analyzing Flight Recorder Data in JRockit Mission Control in Configuring and Using the Diagnostics Framework for Oracle WebLogic Server.
If you need more detail than the information captured in the default recording, and you can reproduce the slow requests, you can start an explicit recording.

Troubleshooting WebCenter Portal Workflows

If you experience issues with WebCenter Portal workflows, review the following sections:

Email Notifications Not Working

Problem

Notifications for workflows are not being sent by email to BPM Worklist, as described in Configuring WebCenter Portal Workflow Notifications to be Sent by Email.

Note:

To identify causes of failures, examine log files on the managed SOA server, hosting BPM Worklist processes, you have configured.

Solution

Check the error logs on the WebCenter and SOA servers for errors at the time when the invite process is instigated. If there appears to be an issue with the email configuration, then validate that you can use the exact same LDAP settings and user accounts to send and receive emails using a different email client.

Note:

To identify causes of failures, examine log files for any SOA BPEL servers you have configured.

Validating the WebCenter Portal Workflow Configuration

The Installing and Configuring Oracle WebCenter Portal describes how to install and configure WebCenter Portal workflows. For details, see Back-End Requirements for WebCenter Portal Workflows . You can validate the workflow configuration as follows:

Log in to WebCenter Portal.
Create a portal and then navigate to the Members tab (click the Administration link, then Security, then Members).
Invite a new member with any role (say User2).
Log out, and then log in to BPM Worklists as User2.
You will be able to view the notification in your worklist items that you have been added to the portal in the specified role.
Open the invite notification and click the Acknowledge button.

If the WebCenter Portal workflows are working properly, the newly created portal ia available to User2. If the portal is not available or listed, there is some issue with the configuration.

Troubleshooting Issues with WebCenter Portal Workflows

If WebCenter Portal workflows are not working properly, follow these steps to help troubleshoot the issue:

Check that WebCenter Portal workflows are deployed on the Oracle SOA server:
1. Log in to Fusion Middleware Control.
2. Check that WebCenterWorklistDetailApp.ear is deployed.
3. Verify that sca_CommunityWorkflows.jar is deployed.
For details, see Oracle SOA Server - Extending the Domain in Installing and Configuring Oracle WebCenter Portal.
Ensure the Web Service connection between the Oracle SOA server and the WebCenter Portal application is secure:
1. Check the alias in the keystore file on the Oracle SOA server.
  
  For example, use the following command to list the content of the keystore file on the Oracle SOA server:
  
  keytool -list -v -keystore bpel.jks -storepass <password>
  
  There should be an entry with:
```
Alias name: webcenter_portals_ws
```
2. Verify that the credential stores for both WebCenter Portal and Oracle SOA server are configured correctly.
3. Check that keystores exist at both ends of the connection, for example:
  
  - webcenter.jks (copied to WebCenter Portal server end)
  
  - bpel.jks (copied to Oracle SOA server end)
  
  For example, the following commands generate webcenter.jks and bpel.jks:
```
keytool -genkeypair -keyalg RSA -dname "cn=webcenter,dc=us,dc=oracle,dc=com" -alias webcenter -keypass mypassword -keystore webcenter.jks -storepass mypassword -validity 360
keytool -exportcert -v -alias webcenter -keystore webcenter.jks -storepass mypassword -rfc -file webcenter.cer
keytool -importcert -alias webcenter_spaces_ws  -file webcenter.cer -keystore bpel.jks -storepass mypassword
keytool -genkeypair -keyalg RSA -dname "cn=bpel,dc=us,dc=oracle,dc=com" -alias bpel -keypass mypassword -keystore bpel.jks -storepass mypassword -validity 360
keytool -exportcert -v -alias bpel -keystore bpel.jks -storepass mypassword -rfc -file bpel.cer
keytool -importcert -alias bpel -file bpel.cer -keystore webcenter.jks -storepass mypassword
```
  See Creating the SOA Domain Keystore.
4. Configure role members for the BPMWorkflowAdmin application role in Oracle SOA server (soa-infra).
  
  When associating the domain with an identity store that does not contain the user weblogic, you must assign some other valid user to the application role BPMWorkflowAdmin. Use WLST commands to do this from the SOA Oracle home, for example, to assign a user named "monty" that exists in LDAP:
```
cd $SOA_ORACLE_HOME/common/bin/
wlst.sh
 
connect('<admin username>','<admin password>', 'mysoahost.example.com:7001')
revokeAppRole(appStripe="soa-infra", appRoleName="BPMWorkflowAdmin", principalClass="oracle.security.jps.service.policystore.ApplicationRole", principalName="SOAAdmin")
grantAppRole(appStripe="soa-infra", appRoleName="BPMWorkflowAdmin", principalClass="weblogic.security.principal.WLSUserImpl", principalName="monty")
```
  See Overview of Oracle WebCenter Portal WLST Command Categories in WebCenter WLST Command Reference Reference.

Troubleshooting WebCenter Portal Import and Export

This section contains the following subsections:

ResourceLimitException Issue

Problem

The ResourceLimitException error displays when you try to export all portals or the entire WebCenter Portal instance:

Weblogic.common.resourcepool.ResourceLimitException

Solution

Increase the maximum capacity in the JDBC connection pool. To reconfigure the connection pool, log in to the WLS Administration Console. From Services, select Data Sources, WebCenterDS, and then the Connection Pool tab.

LockRefreshTask Issue

Problem

A LockRefreshTask warning displays similar to that below when you try to import or export an entire WebCenter Portal instance or a portal:

[WARNING] [][oracle.webcenter.lifecycle.operation.LockRefreshTask]

If you try the import or export operation again, an error similar to that shown here displays:

Starting WebCenter Portal application import...
WebCenter Portal application import started.

Error occurred while performing import
None
Check the WebCenter Portal log files for additional details.
Unable to contact MBeanServer for
oracle.webcenter.lifecycle:ApplicationName=webcenter,Location=WC_Portal,name=Lifec
ycleManager,type=LifecycleManager,Application=webcenter,ApplicationVersion=11.1.1.
4.0
Error occurred while destroying MBean
The lock hasnt been released from the previous failed import.

Solution

Use the deleteMetadata WLST command to delete unwanted locks in MDS that may be created and not destroyed due to an unexpected and unusual import or export operation failure. Depending on the operation that failed, run one of the following commands:

For WebCenter Portal application import failure, run:

deleteMetadata(application='webcenter', server='WC_Portal', docs='/oracle/webcenter/lock/applicationImport/applicationImport.xml')

For WebCenter Portal application export failure, run:

deleteMetadata(application='webcenter', server='WC_Portal', docs='/oracle/webcenter/lock/applicationExport/applicationExport.xml')

For portal import failure, run:

deleteMetadata(application='webcenter', server='WC_Portal', docs='/oracle/webcenter/lock/scopeImport/**')

For portal export failure, run:

deleteMetadata(application='webcenter', server='WC_Portal', docs='/oracle/webcenter/lock/gsExportImport/**')

Portals and Portal Templates Not Available After Import

Problem

When you first log in to WebCenter Portal after the import operation, the portals and portal templates that you migrated are not available as expected. This can sometimes occur if the portal or portal template cache fails to refresh properly.

Solution

Refresh the portal or portal template cache manually using the refreshGroupSpaceCache and refreshSpaceTemplateCache WLST commands.

To completely clear the cache (all portals):

refreshGroupSpaceCache(appName='webcenter', spaceNames='', syncMode=1,updateType='all', cleanCache=1)

To completely clear the cache (all portal templates):

refreshSpaceTemplateCache(appName='webcenter', spaceTemplateNames='',syncMode=1, updateType='all', cleanCache=1)

For information on how to run WLST commands, see Running Oracle WebLogic Scripting Tool (WLST) Commands.

Unable to Migrate Portals or Documents If the Source and Target Applications Share the Same Content Server

You cannot migrate portals or portal templates between two different WebCenter Portal instances that share the same Content Server.

Target Portal Server Shown As Unavailable When Creating a Connection

While creating a Portal Server connection to a target server, you can test the connection by clicking the Test button. After clicking Test, if you view the state of the target Portal Server in its administration console, it is shown as unavailable even if the server is up and running. This happens when the name of the target domain or server is same as the source domain or server. This does not lead to any functionality loss.

Troubleshooting Individual Portal and Portal Template Import and Export

This section contains the following subsections:

Portal Blocked After Unsuccessful Export or Import

If an error occurs during a portal export/import operation, some portals may appear blocked. To unblock a portal, bring the portal back online temporarily, and then take the portal offline again to complete the export/import operation. Switching between the online and offline modes will unblock the portal. For more information, see Taking Any Portal Offline and Bringing Any Portal Back Online. See also, the WLST command setSpaceState in WebCenter WLST Command Reference Reference.

Page or Portal Not Found Message After Import

When users first log in to WebCenter Portal after an import operation, they may see a "Page not found" or "Portal not found" message if the page or portal they last visited no longer exists. Last accessed page information is retained during import operations which is why these messages display sometimes.

Portal Import Archive Exceeds Maximum Upload File Size

Problem

There is a file size limitation uploading content to WebCenter Portal. If your export archive exceeds the maximum upload size, the import operation through WebCenter Portal Administration will fail.

Solution

Import the portal archive using WLST. For details, see Importing a Portal from an Archive Using WLST.

Alternatively, modify the maximum upload size in webcenter-config.xml. The default maximum upload size is 2 GB. See Changing the Maximum File Upload Size.

Maximum Number of Portals Exceeded on Export

Problem

The maximum number of portals that you can export must be less than or equal to 80% of the connection pool size specified for the MDS Data Source. If you try to export too many portals you might see a ResourceLimitException error:

Weblogic.common.resourcepool.ResourceLimitException

Solution

Export fewer portals. Alternatively, modify the connection pool setting. For details, see the Tuning Performance.

Lists Not Imported Properly

Problem

Lists are not importing properly due to list definition differences in the source and target systems.

Solution

Consider exporting and importing list data. This ensures that list data is consistent with the list definitions being imported.

If you choose to import without data, the list data in the target system is migrated to be consistent with the imported list definitions. If a list column data type is changed, the column values are converted from the target data type to the imported data type, if possible, otherwise the value is deleted. If a list column is removed during import, the column values are deleted.

Exporting and Importing Portals with Tools and Services Configured

Problem

The following error message displays when you try to export a portal with tools and services configured, and try to import the same portal from an instance where some or all of those tools or services are not configured.

The following services are not configured: <list of tools and services>. Please configure these services and try again.

Solution

You can work around this problem by either adding the tools and services to the target, or removing the service-related info from the data.xml file of the archive as described below.

To remove service-related info:

Extract the archive.

The archive contains two files: policy-store.xml and transport.mar.
Expand the transport.mar into a directory.

The data.xml file is located in the oracle\webcenter\lifecycle\importexport directory.

Remove the service tags for all the tools and services that are not present in the target as listed in the error message.

For the example error message above, we would need to remove the following:

      <service id="oracle.webcenter.collab.forum" version="11.1.1.0">
         <metadataUsages>
            <metadataUsage includeBaseDocuments="YES" includeSystemCustomizations="YES">
               <paths>
                  <include path="/oracle/webcenter/collab/forum/scopedMD/s516227ec_dde1_4991_9e18_28d487cb3bce/**"/>
               </paths>
            </metadataUsage>
         </metadataUsages>
      </service>
 
   <service id="oracle.webcenter.collab.rtc" version="11.1.1.0"/>

Repack the transport.mar file by zipping the top-level directories Oracle and pagedefs into a file named transport.mar.
Repack the export archive by zipping the newly created transport.mar and the policy-store.xml file into an archive.
Import the new archive.

Tools and Services Disabled After Import

Problem

When you navigate directly to the Tools and Services tab in portal administration after importing a portal, all the tools and services are disabled even though they were enabled in the source portal.

Solution

Select the Enable check box for tools and services, as required.

Alternatively, open the portal after you import instead of navigating to portal administration. When you access the portal for the first time, tools and services enable automatically.

Importing from the Subportals Page

Problem

When you import a portal from the Portals page, the imported portal does not automatically become a subportal of the current portal. The newly imported portal displays in the Portals switcher menu, Portals Browser task flow, or the Portals page, which display all the portals that are available to you.

Solution

You can import a portal as a subportal by selecting the parent portal on the Portals page before you import the archive.

Unable to Import a Portal If the Source and Target Applications Share the Same Content Server

You cannot export/import portals or portal templates between two different WebCenter Portal applications that share the same Content Server.

Similarly, you cannot use the Document Migration Utility to migrate portal documents between two different WebCenter Portal applications that share the same Content Server.

Shared Library Changes Not Available after Portal Deployment

Problem

Changes made to the shared library are not showing up in the newly deployed portal.

Solution

Shared library deployment might have failed. To find out about the deployment status of the shared library, go to the WebLogic Server Admin console on the target instance and check the state of the latest version of the shared library that you deployed. The newly deployed library must be in "active" state on the target.

If the shared library deployment failed, and the state of the last deployed version on the target is shown as failed, delete the failed version and either redeploy the portal or propagate the portal to include shared library changes.

If the shared library deployment failed, and the shared library on the target is not shown in the failed state but some other intermediate state (such as Distribute running/Deploy running/New), try restarting the servers and then click on Activate Changes in the console (if it is enabled). If the shared library state is still not shown as active, delete the shared library version from the target server and redeploy or propagate the portal. If you get an error message that this version of the library cannot be deleted as it is being referenced by one or more applications, stop the WebCenter Portal managed server (WC_Portal), delete the library, and then start the managed server again. After restart, it will start using the last active version of the shared library.

Members Not Listed in an Imported Portal

Problem

After you have imported a portal from a portal archive (PAR file) containing members under various roles, like Viewer or Portal Manager, member names are not displayed on the Portal's members page.

Solution

Users on both the source and target instances must be identical. If a shared identity store is not used, your system administrator must synchronize users in WebCenter Portal by using the synchronizeUserInformation WLST command. For information about this command, contact Oracle Support.

Deployment Messages Not Displayed in the Browser Locale

When you deploy a portal, the deployment progress messages coming from the target server might be displayed in the source server’s environment locale instead of the browser locale. This happens when your source server's environment locale is different than the browser locale set in WebCenter Portal.

Troubleshooting Issues with Mail

This section includes the following subsections:

Mail is Not Accessible in Secure Mode

Problem

You configured mail to function in secure mode, but it is not accessible.

Solution

Ensure the following:

IMAP and SMTP ports are specified correctly. See Registering Mail Servers.
Properties are set to true in your mail server.
- mail.imap.secured = true
- mail.smtp.secured = true

Mail is Not Accessible in Non-Secure Mode

Problem

You configured mail to function in non-secure mode, but it is not accessible.

Solution

Ensure the following:

IMAP and SMTP ports are specified correctly. See, Registering Mail Servers.
Properties are set to false in your mail server.
- mail.imap.secured = false
- mail.smtp.secured = false

Unable to Create Distribution Lists in the Non-Secure Mode

Problem

You are unable to create portal distribution lists in non-secure mode; that is, SSL is not configured on the LDAP server.

Solution

Check if the mail server has been reinstalled or the user has been deleted. Also ensure that the following parameters are configured accurately in non-secure mode, in the LDAP server:

ldapHost
defaultUser
ldapAdminPassword
ldapBaseDN
ldapPort

See Registering Mail Servers.

Unable to Create Distribution Lists in the Secure Mode

Problem

You are unable to create WebCenter Portal distribution lists in secure mode, that is, SSL is configured on the LDAP server.

Solution

Check if the mail server has been reinstalled or the user has been deleted. Also ensure that the following parameters are configured accurately in secure mode, in the LDAP server:

ldapHost
defaultUser
ldapAdminPassword
ldapBaseDN
ldapPort
ldap.connection.secure, 'true'

Provisioning of Mail Fails in a Portal (Default Distribution List not Created)

Problem

In WebCenter Portal, when accessing a portal's Tools and Services Mail page, the following error message appears "Provisioning of Mail service for this portal has failed" and the Distribution List field is blank.

Solution

Make sure that the portal name is unique. If the portal name is not unique, a distribution list already exists. You can select the existing distribution list or select another distribution list.

Unable to Configure the Number of Mail Messages Downloaded

Problem

You cannot configure how many mail messages are downloaded to each user's Inbox.

Solution

Use the setMailServiceProperty WLST command. For example, to download 100 mail messages from the mail client, specify the mail.messages.fetch.size parameter as 100, as shown in the following example:

setMailServiceProperty(appName='webcenter',  property='mail.messages.fetch.size', value='100')

For command syntax and examples, see the setMailServiceProperty in WebCenter WLST Command Reference Reference.

Unable to Publish and Archive WebCenter Portal Mail

Problem

You are unable to archive WebCenter Portal mail.

Solution

If the archiving fails, check the following:

In WebCenter Portal, navigate to Administration > Tools and Services > Discussions. Check whether the required configuration is accurate. For details, see Publishing Portal Mail in a Discussion Forum in Building Portals with Oracle WebCenter Portal.
Check whether the user account configured here is a member of the distribution list.
For a particular portal, check whether the forum configured is available in the discussions server. For details, see Publishing Portal Mail in a Discussion Forum in Building Portals with Oracle WebCenter Portal.
Check whether the user who sends mail to the distribution list is available in the discussions server and the mail address is the same.

Changing Passwords on Microsoft Exchange

Problem

If multiple users log on to Microsoft Exchange with the same user name and password, and then one user changes the password, the original password remains valid until all users log off.

For example, say the current password of the user monty is mypassword. Two users, A and B, log on from different clients using WebCenter Portal or Microsoft Exchange. Both log on as monty/mypassword, and both are able to see the mail messages. Now user A changes the password in Microsoft Exchange to oracle1. Because there currently are clients using the passwords oracle1 and mypassword, both are valid passwords; that is, new users can log on as monty/mypassword and still see the mail messages.

Solution

After all existing users with the original password log off, the new password takes effect. Until then, users can use both passwords to log on.

Troubleshooting Issues with Announcements and Discussions

This troubleshooting section includes the following subsections:

Authentication Failed

Problem

WS-Security does not appear to be set properly for the connection between WebCenter Portal and the back-end discussions server. You may see the following error:

failure to authenticate the user WebLogic, due to: Authentication Failed

Solution

This error may be caused due to various reasons. Check the following:

Ensure that the OWSM SAML policy setting is appropriately defined between the discussions connection and the discussions server.
Review WC_Portal-diagnostic.log for errors and exceptions relating to discussion services in WebCenter Portal. If the log does not provide enough information to correct errors, then turn on debugging for the oracle.webcenter.collab.share and oracle.webcenter.collab.forum packages.
For the discussions server, review WC_Collaboration-diagnostics.log and jive.error.log inside your domain's DOMAIN_HOME/config/fmwconfig/servers/SERVER_NAME/owc_discussions/logs directory. If the logs do not provide enough information to correct errors, then turn debugging on for the discussions server. To turn on debug logs, log on to the discussions server admin console, go to page logs, the Debug tab, and enable. Restart the WC_Collaboration managed server to change the logging setting.
Make sure that time settings on WebCenter Portal and the back-end discussions server are in sync. This is important with OWSM WS-Security.

Discussions Cannot Be Enabled in WebCenter Portal

Problem

Discussions cannot be enabled in any portal in your WebCenter Portal installation.

Solution

This error may be caused due to various reasons. Check the following:

The back-end discussions server is up and running and accessible. See Testing Discussions Server Connections.
Administrator User Name (adminUser) property configured for the active connection has administrative privileges on the application root category (the category configured for WebCenter Portal). See Registering Discussions Servers.

It is not necessary for this user to be a super admin. However, the user must have administrative privileges on the application root category configured for WebCenter Portal, that is, the category (on the discussions server) under which all WebCenter Portal discussions and announcement are stored.
Application root category, where all WebCenter Portal discussions and announcements are stored, exists on the back-end discussions server.

You can check the application root category ID configured for WebCenter Portal by navigating to WebCenter Portal Administration, then selecting Tools and Services, and then Discussions. See Specifying Where Discussions and Announcements are Stored on the Discussions Server.

Login Failed

Problem

You may see the following login exception:

caught exception running task oracle.webcenter.collab.share.LoginFailedException: failure to authenticate the user monty, due to: Failed to read user monty from database.
at oracle.webcenter.collab.forum.internal.jive.JiveAuthenticator.login(JiveAuthenticator.java:213)

This occurs when an incorrect admin user name is specified.

Solution

Follow these steps:

Confirm that the admin user specified while creating the discussion forum connection has access to the Discussions Administration console at http://host:port/owc_discussions/admin.

If the user does not have admin privileges, then use the WLST command addDiscussionsServerAdmin to provision the user. For more information, see Granting the Discussions Server Administrator Role Using WLST.
Confirm that you have configured the discussion server with the appropriate DISCUSSIONS schema. If not, then create or extend the domain using config.sh or was_config.sh.

Login Does Not Function Properly After Configuring Oracle Access Manager

Problem

When you log in to WebCenter Portal's Discussion Server after configuring Oracle Access Manager single sign-on, a 500 - Internal Server Error occurs.

Solution

If one does not exist, add a user as super admin on WebCenter Portal's Discussion Server using the WLST command addDiscussionsServerAdmin. For command syntax and examples, see addDiscussionsServerAdmin in WebCenter WLST Command Reference Reference.
Log on to the Discussions Admin Console with the super admin account, and navigate to System - System Properties.

See Accessing the Discussions Server Admin Console.
Create or edit the property owc_discussions.sso.mode, and set its value to true.

For more information, see Configuring the Discussions Server for SSO.
Restart WebCenter Portal's Discussion Server.

Category Not Found Exceptions

Problem

If you change the connection to use a different discussions server, and if you change WebCenter Portal's root category ID from Administration - Tools and Services - Discussions, then you could see exceptions like, "Category Not Found."

Solution

Restart the managed server on which WebCenter Portal is deployed.

Watched Topics and Recent Topics Not Displaying Topics From Multiple Discussion Forums

Problem

Portals created from the Discussion Site template include Recent Topics and Watched Topics task flows on the Home page. By default, both these task flows are configured to display information for a single forum. If your portal is configured to support multiple forums, topics from the other forums do not display in these task flows.

Solution

Edit the Watched Topics and Recent Topics task flows to remove the task flow parameters from the Forum ID field. In this instance, the Forum ID will be set to ${sessionContext['oracle.webcenter.collab.forum'].groupInfo[portalContext.currentPortalName].forumId}. Delete this value and save the page.

Discussion and Announcement Updates Not Displayed

Problem

If clustered caching is enabled in your environment, content updates to discussions and announcements may not refresh immediately.

Solution

Click the Refresh icon to force a manual refresh at any time.

Announcements Page Displays "User Is Not Authorized"

Problem

A user creates an announcement, then changes their user name. When they try to log in with the new user name to access the page, a message indicating that the user is not authorized to view the announcement is displayed even if the two user names were synced.

Solution

This can occur if the same Identity Store is not used by WebCenter Portal and the Discussions server; the user must exist in both stores if the store is not shared.

Discussions Page Displays "User Is Not Authorized"

Problem

A user creates a discussion topic, then changes their user name. When they try to log in with the new user name to access the page, a message indicating that the user is not authorized to view the discussion page is displayed even if the two user names were synced..

Solution

This can occur if the same Identity Store is not used by WebCenter Portal and the Discussions server; the user must exist in both stores if the store is not shared.

Troubleshooting Issues with Events

If users cannot see their personal events, verify the following:

Is the Microsoft Exchange Server/IIS server accessible from the managed server on which WebCenter Portal is deployed? Can they ping each other?
Is the configuration correct on the Microsoft Exchange Server? For more information, see Events Prerequisites for Personal Events.
Is the events server connection correct in the managed server? For more information, see Registering Events Servers.
Did the user enter the correct user name and password for the account on the Microsoft Exchange Server? The user name is usually an email address.

Troubleshooting Issues with Users and Roles

For Oracle WebCenter Portal to properly maintain enterprise group-to-role mappings, the back-end discussions server and content server must support enterprise groups. The WebCenter Portal's Discussion Server and WebCenter Content's Content Server versions provided with Oracle WebCenter Portal 11.1.1.2.0 and later both support enterprise groups, but previous versions may not. If a back-end server does not support enterprise groups, an error message similar to the following displays when you try to add a group.

Warning: Group [name] not found in Identity Store

Also, an error is logged containing more detailed information as shown here:

[2011-03-28T01:03:07.143-07:00] [WC_Spaces] [NOTIFICATION] [WCS-07855] 
oracle.webcenter.doclib.internal.spaces.AbstractDoclibRoleMapper] [tid: pool-1-daemon-thread-1] [userId: monty] 
[ecid: a4789a41d7e6bc9f:36de4556:12efb72d049:-8000-00000000000002c0,0:5] 
[APP: webcenter#11.1.1.4.0] Adding groups [oracle.webcenter.security.common.WCGroup@18b96a3] to documents service roles [Administration, Delete Documents, Create and Edit Documents, View Documents] for
 scope Scope[name=rbgs25mar01, guid=sbf125dd4_cd43_41cc_9d3d_467d06e84100][2011-03-28T01:03:09.122-07:00] [WC_Spaces] [ERROR] [WCS-44002] [oracle.webcenter.security.rolemapping.RoleManager] 
[tid: [ACTIVE].ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: monty] 
[ecid: a4789a41d7e6bc9f:36de4556:12efb72d049:-8000-00000000000002c0,0] 
[APP: webcenter#11.1.1.4.0] The Role Mapping provider encountered an exception while performing security role mapping for service oracle.webcenter.doclib.
[[oracle.webcenter.security.rolemapping.spi.RoleMappingSPIException: Cannot add role null and permissions, 15, to the account for the folder, rbgs25mar01 for the user/group Admin.        at
oracle.webcenter.doclib.internal.spaces.UCMSpacesUtils$2.newException(UCMSpacesUtils.java:2595)

Note:

In previous releases, if a back-end server did not support enterprise groups, users belonging to enterprise groups were individually added to WebCenter Portal roles; this behavior has changed.

Troubleshooting Issues with Content Repositories

This section includes the following subsections:

Documents Tools Unavailable in WebCenter Portal

Documents Tools Unavailable in WebCenter Portal

If document tools are not available in WebCenter Portal, that is, the Documents tab is not available in your Home portal or other portals, there may be a connection issue to the backend WebCenter Content Server, or the WebCenter Content Server does not contain some required WebCenter Portal data.

To diagnose the problem, follow these steps:

Check that the WebCenter Content Server is up and running. Ensure the server has the Server Port (intradoc) configured and the Server IP Filter allows WebCenter Portal to connect:
1. Log in to the Content Server.
2. Click Administration.
3. Click Configuration for instance name.
4. Click the Server Configurations link under System Configuration.
5. Ensure that Server Port is listed and that Server IP Filter allows access from WebCenter Portal.
Check the connection between WebCenter Portal and the WebCenter Content Server that is being used as the backend document store:
1. Login to Fusion Middleware Control, and navigate to Content Repository Connection settings.
2. Select and edit the required connection.
3. Ensure the Active Connection check box is selected.
4. Ensure that Content Administrator, Portal Server Identifier and Security Group are specified correctly:
  - Content Administrator - the Content Administrator must have administration rights on the Content Server. This user will be used to create and maintain folders for portal content, security groups and roles, and manage content access rights.
  - Portal Server Identifier and Security Group - both must be unique and not used by any other WebCenter Portal instance using the same WebCenter Content Server. If you change these values, ensure that both values are changed and not just one of them.
  - Security Group - must be 14 characters or less as it is used as a prefix for items created in WebCenter Content Server, which have a limit on the length of the item name.
5. If you make changes, click Test to verify that the connection works.
6. Click OK to save the connection.
7. If you made changes, you must restart WC_Portal, the managed server on which WebCenter Portal is deployed.
8. Log in to WebCenter Portal to see if the documents tools are available after your connection updates.
If the Document service is still not available, check log messages around WebCenter Portal start-up for any errors connecting to the WebCenter Content Server or saving data on the WebCenter Content Server.

For details, see Viewing and Configuring WebCenter Portal Logs.
If the log does not show any useful log information, increase the logging level for the WebCenter Content Server, and then restart WebCenter Portal to investigate the messages in more detail:
1. 1. Use Fusion Middleware Control (or edit the logging.xml file) to increase logging for oracle.webcenter.doclib.internal.model and oracle.webcenter.doclib.internal.spaces.
    
    See also, Viewing and Configuring WebCenter Portal Logs.
  2. Restart WebCenter Portal.
  3. View the logs again:

Troubleshooting Issues with Analytics

Problem

If users cannot see analytics in WebCenter Portal, verify the following:

Solution

Check that the Analytics Collector configuration is correct and in particular that both Enable WebCenter Event Collection and Active Connection are both set. See Registering an Analytics Collector for Your Application.

Figure F-4 Enabling the Connection and Analytics Collection

If you make changes to the connection you must restart the managed server on which WebCenter Portal is deployed. For more information, see Starting and Stopping Managed Servers for WebCenter Portal Application Deployments.
If WebCenter Portal was recently upgraded, verify that the domain startup script does not contain legacy Analytics Collector settings as these values override any connection details that you specify through Fusion Middleware Control or using WLST.
Perform the following:
1. Shut down the managed server on which WebCenter Portal is deployed (WC_Portal).
2. Edit the domain startup script setDomainEnv located at:
  
  UNIX: DOMAIN_HOME/bin/setDomainEnv.sh
  
  Windows: DOMAIN_HOME\bin\setDomainEnv.cmd
3. Remove Analytics Collector settings.
4. Restart the managed server.

Problem

Analytics Collector deployment fails when configured with the Pluggable Database (PDB), if the number of cursors in the database exceeds the maximum limit.

Solution

Try to increase the number of open_cursors in the Pluggable Database (PDB), for example 3000. The allowed value for the open_cursors is from 0 to 65535.

where, open_cursors specifies the maximum number of open cursors allowed per session.

Troubleshooting Issues with Notifications

Problem

No notifications are received.

Solution

If the log indicates that the Notification Sender is not configured, then it means the service is unable to find the connection to use.
Ensure that Notifications is configured to use either a valid BPEL or MAIL connection. This can be verified through the getNotificationsConfig() WLST command (see Specifying the Notifications Channel Using WLST) or through the Fusion Middleware Control user interface (see Specifying the Notifications Channel Using Fusion Middleware Control).

Problem

Notifications is configured (BPEL or MAIL) correctly, but still no notifications.

Solution

Notifications relies on a valid BPEL or MAIL connection. Run the respective connection validations and troubleshooting scenarios as described in Managing Mail or Managing the SOA Connection for WebCenter Portal Membership Workflows.

Problem

MAIL or BPEL connections are set up appropriately, but still do not receive notifications.

Solution

Notifications are generated based on user subscriptions. Apart from notification for invitations to connect, which is configured out of the box, other notifications are generated only when a user has specifically subscribed. Ensure that the user has created subscriptions through his or her personal Preferences or through application- or object-level subscriptions. For more information, see Subscribing to the Application, to Portals, and to Objects in Using Portals in Oracle WebCenter Portal.

Problem

Users have set up their subscriptions, but still receive no notifications.

Solution

Depending on how it is configured, Notifications delegates the delivery of notifications to BPEL/UMS or the Mail service. For the Mail service, ensure that the user's email address is configured. For UMS, look in Fusion Middleware Control under the Message Status section of User Messaging Service, where you see the status of each outgoing message from UMS. For more information, see Monitoring Oracle User Messaging Service in Administering Oracle SOA Suite and Oracle Business Process Management Suite.
For UMS, this problem could also mean that the configuration of the sender on the WebCenter Portal side does not match or find a corresponding driver on the UMS side. Ensure that the sender address (domain) allows UMS to match at least one driver for outbound messages.
For the Mail service, ensure that the mail connection points to a shared connection as described in About Connection Channels.

Problem

For UMS configurations, users receive notifications on some channels but not on others.

Solution

This is most likely due to the way the user's messaging channels and filters are configured. For more information, see Establishing and Managing Your Messaging Channels and Filters in Using Portals in Oracle WebCenter Portal.

Troubleshooting External Application Issues

This section contains common issues and workarounds related to external applications.

This section contains the following topic:

Users Experience Password Lockout

Users Experience Password Lockout

Problem

Using an external application to store or retrieve credentials for collaboration connections when your identity store uses a password change policy that causes the password to be changed in the identity store directly, may lead users to experience a password lockout.

Solution

The external applications cannot know that a password has been changed directly in the identity store and consequently cannot react to it. A partial solution is to define one external application for all your collaboration connections.

Troubleshooting Security Configuration Issues

This section includes the following subsections:

WebCenter Portal Application Does Not Find Users in LDAP Provider

Problem

Weblogic Server was configured with an external LDAP provider. Users in the external LDAP can log in to WebCenter Portal, but when you try to assign the administrator role in WebCenter Portal to a user from the external LDAP, no users are found.

Solution

Change the Control Flag for the DefaultAuthenticator Authentication Provider to Sufficient as described in Configuring the Identity Store. Restart the Administration Server and Managed Servers for the domain.

Portal Created with Errors When Logged in as OID User

Problem

When logged in to WebCenter Portal as an OID user (for example, orcladmin), and you try to create a portal, the portal gets created but with errors. The error message appears as "No matching users were found with search string <login user>".

Solution

The following property is missing in the jps-config.xml file:

<property name="jps.user.principal.class.name" value="weblogic.security.principal.WLSUserImpl"/>

To fix this:

Edit DOMAIN_HOME/config/fmwconfig/jps-config.xml.
Add this line in the general properties:

<property name="jps.user.principal.class.name" value="weblogic.security.principal.WLSUserImpl"/>
Restart the WC_Portal server.

Users Cannot Self-Register when WebCenter Portal Configured with Active Directory

Problem

Users cannot self-register with Active Directory after configuring WebCenter Portal to use AD authenticator. When a user tries to self-register, the following error message appears:

"User not created. Either the user name or the password does not adhere to the registration policy or the identity store is unavailable. Specify the required user credentials or contact your administrator for assistance."

Solution

To fix the problem:

Set the user name attribute to sAMAccountName while configuring Active Directory in the WebLogic Administration Console.
Use the HTTPS port of the LDAP and enable the SSL checkbox while configuring Active Directory in the WebLogic Administration Console.

User Made Administrator Does Not Have Administrator Privileges

Problem

After logging in as orcladmin and making a user an administrator, after logging out and logging in as that user, the Administrator link is still not available.

Solution

The problem is due to duplicate cn entries in the identity store. Since cn is mapped to the username attribute, it must be unique. Remove the duplicate from the identity store and the user should have the appropriate privileges.cn.

Deploying the SAML SSO-specific Discussions EAR file Produces an Exception

Problem

Undeploying the discussions EAR file and deploying the SAML SSO-specific discussions EAR file and then starting the application in the WLS Administration Console produces the following exception:

java.lang.ClassCastException:
org.apache.xerces.parsers.XIncludeAwareParserConfiguration

Solution

Restart the WC_Collaboration server. This should fix the issue and the discussions application will be in an active state.

Configuring SAML Single Sign-on Produces 403 Error

Problem

While testing a SAML SSO configuration you encounter 403 errors, and after turning on debug logging, as described in Checking Your Configuration, you see the following kind of error logs in the destination server:

####<Oct 11, 2010 10:20:31 PM PDT> <Debug> <SecuritySAMLLib> <adc2170966>
<soa_server1> <[ACTIVE] ExecuteThread: '1' for queue:
'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <>
<efaf471a17d5a745:-5ba0524a:12b9b0b7849:-8000-0000000000015385>
<1286860831335> <BEA-000000> <SAMLSignedObject.verify(): validating
signature>
####<Oct 11, 2010 10:20:31 PM PDT> <Debug> <SecuritySAMLService> <adc2170966>
<soa_server1> <[ACTIVE] ExecuteThread: '1' for queue:
'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <>
<efaf471a17d5a745:-5ba0524a:12b9b0b7849:-8000-0000000000015385>
<1286860831336> <BEA-000000> <SAMLDestinationSiteHelper: Signature
verification failed with exception: org.opensaml.InvalidCryptoException:
SAMLSignedObject.verify() failed to validate signature value>
####<Oct 11, 2010 10:20:31 PM PDT> <Debug> <SecuritySAMLService> <adc2170966>
<soa_server1> <[ACTIVE] ExecuteThread: '1' for queue:
'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <>
<efaf471a17d5a745:-5ba0524a:12b9b0b7849:-8000-0000000000015385>
<1286860831336> <BEA-000000> <SAMLDestinationSiteHelper: Unable to validate
response -- returning SC_FORBIDDEN>
####<Oct 11, 2010 10:20:31 PM PDT> <Debug> <SecuritySAMLService> <adc2170966>
<soa_server1> <[ACTIVE] ExecuteThread: '1' for queue:
'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <>
<efaf471a17d5a745:-5ba0524a:12b9b0b7849:-8000-0000000000015385>
<1286860831336> <BEA-000000> <SAMLSingleSignOnService.doACSGet: Failed to get
SAML credentials -- returning>

Solution

Chances are that something went wrong with your certificate setup due to which SAML assertions are not being validated. This is likely because the certificate registered in the SAML Identity asserter is incorrect. Export the certificate used for SAML SSO setup in the WebCenter Portal domain specified by certAlias and certPassword and copy it to a accessible location in the destination domain.

Update the relevant config section in the wcsamlsso.properties file in the WebCenter Portal domain (for example, if the certificate was invalid for the SOA configuration, update the certPath in the soa_config section).
Open the WebLogic Server Admin Console, and from the WC_Portal domain go to Security Realm > Providers > Credential Mapping > wcsamlcm > Management > Relying Parties and delete the relying parties relevant to the domain (for example, for SOA, it would be Worklist Detail.)
Go to Destination Domain > Security Realm > Providers > Authentication >wcsamlia > Management > Asserting Parties and delete the corresponding asserting parties.
Open the Certificates tab and delete the certificate as well.
Go back to the WebCenter Portal domain and re-run the scripts for creating asserting-relying parties pairs. For SOA, for example, you would need to re-run:
```
WCP_ORACLE_HOME/webcenter/scripts/samlsso/configureWorklistDetail.py
```
Test your configuration again. If all works well, you can disable SAML logging.

Impersonation Session Produces Error with OAM 11.1.2.2.0

Problem

An internal error is produced when switching between users in an impersonation session with OAM 11.1.2.2.0.

Solution

Check that:

The EnableImpersonation flag in oam-config.xml is set to true
The new OID identity store you created in the OAM 11.1.2.2 console does not contain spaces (for example, Oracle Identity Store rather than OracleIdentityStore)
The UserPassword attribute for the new identity store is userPassword

Troubleshooting Issues with External Links

An external URL specified in a WebCenter Portal component, such as a link or wiki, may fail validation checks with the following message:

The URL entered is not available in the list of valid URLs. Contact your system administrator for the list of valid URLs.

For an external URL to be found valid, the system administrator must add it to the list of valid URLs in the valid-link-url.xml file. See Adding a List of Valid External URLs.

Troubleshooting Issues with Elasticsearch

This section includes the following topics.

Profile Crawling Fails with 401 Error

Profile Crawling Fails with 401 Error

Problem

Profile crawling is a part of portal crawling and happens in batches. Sometimes one of the batches fails with 401 errors which can be observed in the diagnostic logs. You see the following kind of error logs:

Crawl failed for service 
oracle.webcenter.peopleconnections.profile using crawl url
 http://host:port/rsscrawl?context=&startIndex=77000&serviceId=oracle.webcenter.peopleconnections.profile&command=GetData&jsonFormat with status 401

Solution

This issue appears when the service times out on the client-side. Increase the Results Time Limit value for the LDAP authentication provider in the WebLogic server console.

One of the reasons to see a 401 intermittently is due to LDAP client timeout issue. To determine if the reason is LDAP client timeout issue, do the following:

Log in to the WebLogic Server Administration Console.
Navigate to the managed server on which WebCenter Portal is deployed. Select Environment then, Servers, and then select the WebCenter Portal instance (WC_Portal).
Open the Debug tab, and expand weblogic, then security, and then atn.
Select the authentication logger that you want to enable and click Enable.
Schedule a crawl again. See Manually Starting a Full Crawl.

This time you are expected to see a lot more debug logs in WC_Portal.log.

Around the time stamp you can see 401 in portal diagnostic log, check for server debug logs in WC_Portal.log and check if you see the following kind of error logs:

<weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.loginexception:java.security.PrivilegedActionException:weblogic.security.providers.authentication.LoginServerUnavailableException:Time to complete operation exceeded

This confirms that it is a client-side timeout issue. To rectify this, increase the Results Time Limit value for the LDAP authentication provider in the WebLogic server console.

To update the Results Time Limit value:

Log in to the WebLogic Server Administration Console.
From the Domain Structure pane, click Security Realms. The Summary of Security Realms pane displays.
Click your security realm. The Settings page for the security realm displays.
Open the Providers tab and select the LDAP authentication provider you are configuring.
Open Provider Specific tab and verify if the Results Time Limit is set to some value, other than 0.

Figure F-5 Specifying the Results Time Limit Value
Increase the Results Time Limit value and click Save.
Restart WebLogic Server for the changes to take effect.
schedule a crawl again. See Manually Starting a Full Crawl.