| Oracle® Fusion Middleware Administrator's Guide for Oracle WebCenter Portal 11g Release 1 (11.1.1.6.0) Part Number E12405-17 |
|
|
PDF · Mobi · ePub |
| Oracle® Fusion Middleware Administrator's Guide for Oracle WebCenter Portal 11g Release 1 (11.1.1.6.0) Part Number E12405-17 |
|
|
PDF · Mobi · ePub |
Fusion Middleware Control Console provides a Web-based user interface for monitoring the real-time performance of WebCenter Portal applications (Framework applications and Spaces applications), including any producers and portlets that WebCenter Portal applications may use.
Performance monitoring helps administrators identify issues and performance bottlenecks in their environment. This chapter describes the range of performance metrics available for WebCenter Portal applications and how to monitor them through Fusion Middleware Control. It also describes how to troubleshoot issues by analyzing information that is recorded in WebCenter Portal diagnostic log files.
Administrators who monitor WebCenter Portal applications regularly will learn to recognize trends as they develop and prevent performance problems in the future.
This chapter includes the following sections:
Audience
The content of this chapter is intended for Fusion Middleware administrators (users granted the Admin, Operator, or Monitor role through the Oracle WebLogic Server Administration Console). See also Section 1.8, "Understanding Administrative Operations, Roles, and Tools".
Through Fusion Middleware Control, administrators can monitor the performance and availability of all the components and services that make up WebCenter Portal applications, and the application as a whole.
To make best use of the information displayed it is important that you understand how performance metrics are calculated and what they mean. All WebCenter Portal's performance metrics are listed and described here for your reference. Some applications (such as Spaces applications) might use the full range of social networking, personal productivity, and collaboration service metrics listed, while others may only use one or two of these services.
This section includes the following subsections:
Section 38.1.1, "WebCenter Portal Metric Collection: Recent History and Since Startup"
Section 38.1.3, "Common WebCenter Portal Performance Issues and Actions"
Section 38.1.5, "WebCenter Portal Service-Specific Performance Issues and Actions"
Performance metrics are automatically enabled for Oracle WebCenter Portal. In other words, you do not need to set options or perform any extra configuration to collect performance metrics. If you encounter a problem, such as, an application running slowly or hanging, you can view particular metrics to find out more information about the problem as Fusion Middleware Control provides real-time data.
The following metrics are collected for Oracle WebCenter Portal:
Since Startup: At any given time, real-time metrics are available for the duration for which the WebLogic Server hosting WebCenter Portal applications is up and running. Real-time metrics that are collected or aggregated since the startup of the container are displayed for WebCenter Portal as Since Startup. These metrics provide data aggregated over the lifetime of the WebLogic Server. The aggregated data enables you to understand overall system performance and compare the performance of recent requests shown in Recent History.
Note:
Metric collection starts afresh after the container is restarted. Data collected before the restart becomes unavailable.
Recent History: In addition to the Since Startup metrics, Oracle WebCenter Portal metrics are also configured to capture performance data every five minutes. This metric data is used with the Since Startup metrics, and is made available as Recent History metrics.
All metrics seen under Recent History are calculated using the recent metrics. For example, if a service is used for a short time, but it is not accessed at all for the last 15 minutes, then the Since Startup metrics for the service shows numbers greater than 0, while the Recent History metrics for that service are all zero. The Recent History metrics enable you to assess real-time performance of a live site based on data collected just from recent run-time access.
Typically, Recent History shows data for the most recent 10-15 minutes. However, there are situations when the data does not reflect the last 10-15 minutes:
If the WebLogic Server has just started up, and has been running for less than 10-15 minutes, then Recent History shows data for the duration for which the server has been up and running.
Metric collection stops temporarily if no metric requests are detected over a long period. The collection restarts when the client next requests metrics. If metric collection stops, then Recent History initially shows data for the period since metric collection stopped. As soon as the metric collection starts again, the data starts displaying metrics for the most recent 10-15 minutes.
While diagnosing a live site, you can navigate to the WebCenter Portal metric pages and see the Services Summary section to identify services that are actively used and/or are taking longer than expected. Click the Refresh icon next to the time stamp to refresh metrics with live data. Then, click the particular service and repeat these steps to determine which specific operation in the service is taking a long time. If needed, navigate to application pages that use the service and set the application to trigger the run-time metrics to get more data.
Fusion Middleware Control provides capabilities to monitor performance of WebCenter Portal services in the following ways:
Services summary: Summary of performance metrics for each service used in a WebCenter Portal application. Table 38-1 lists services that use common performance metrics. Table 38-2 describes service metrics.
Most popular operations and response time for individual service operations. Table 38-3 describes these metrics.
Per operation metrics: Performance metrics for individual service operations. Table 38-1 lists common performance metrics used to monitor performance of individual operations. Table 38-3 describes these metrics.
Table 38-1 Common Performance Metrics
| Service | Services Summary(Since Startup and Recent History) | Per Operation Metrics(Since Startup and Recent History) |
|---|---|---|
|
Announcements |
The performance metrics include:
|
The performance metrics include:
|
|
BPEL Worklist |
The performance metrics include:
|
Not applicable |
|
Discussion Forums |
The performance metrics include:
|
The performance metrics include:
|
|
External Applications |
The performance metrics include:
|
The performance metrics include:
|
|
Events |
The performance metrics include:
|
The performance metrics include:
|
|
Import/Export |
The performance metrics include:
|
The performance metrics include:
|
|
Instant Messaging and Presence (IMP) |
The performance metrics include:
|
The performance metrics include:
|
|
Lists |
The performance metrics include:
|
The performance metrics include:
|
|
|
The performance metrics include:
|
The performance metrics include:
|
|
Notes |
The performance metrics include:
|
The performance metrics include:
|
|
Pages |
The performance metrics include:
|
The performance metrics include:
|
|
People Connections |
The performance metrics include:
|
The performance metrics include:
|
|
Polls |
The performance metrics include:
|
The performance metrics include:
|
|
Recent Activity |
The performance metrics include:
|
Not available |
|
RSS |
The performance metrics include:
|
Not available |
|
Search |
The performance metrics include:
|
The performance metrics include:
|
Table 38-2 describes metrics used for monitoring performance of all operations.
Table 38-2 Description of Common Metrics - Summary (All Operations)
| Metric | Description |
|---|---|
|
Status |
The current status of the service:
|
|
Successful Invocations (%) |
Percentage of a service invocations that succeeded. Successful Invocations (%) equals the number of successful invocations divided by the invocation count: - Since Startup - Recent History If Successful Invocations (%) is below 100%, check the diagnostic logs to establish why service requests are failing. See, Section 38.3, "Viewing and Configuring Log Information". |
|
Invocations |
This metric shows number of service invocations per minute: - Since Startup - Recent History This metric provides data on how frequently a particular service is being invoked for processing of operations. Comparing this metric across services can help determine the most frequently used WebCenter Portal services in the application. |
|
Average Time (ms) |
The average time taken to process operations associated with a service. This metric can be used with the Invocations metric to assess the total time spent in processing service operations. - Since Startup - Recent History |
Table 38-3 describes metrics used to monitor performance of each operation performed by a service or component.
Table 38-3 Description of Common Metrics - Per Operation
| Metric | Description |
|---|---|
|
Most Popular Operations |
The number of invocations per operation (displayed on a chart). The highest value on the chart indicates which operation is used the most. The lowest value indicates which operation is used the least. |
|
Response Time |
The average time to process operations associated with a service since the WebCenter Portal application started up (displayed on a chart). The highest value on the chart indicates the worst performing operation. The lowest value indicates which operation is performing the best. |
|
Operation |
The operation being monitored. See also Section 38.1.4, "WebCenter Portal Service-Specific Metrics". |
|
Invocations |
The number of invocations, per operation: - Since Startup - Recent History This metric provides data on how frequently a particular service is being invoked for processing of operations. Comparing this metric across services can help determine the most frequently used WebCenter Portal services in the application. |
|
Average Time (ms) |
The average time taken to process each operation: - Since Startup - Recent History |
|
Maximum Time (ms) |
The maximum time taken to process each operation. |
This section provides information about identifying generic performance-related issues.
If a metric is out-of-bounds, do the following:
Check system resources, such as memory, CPU, network, external processes, or other factors.
Check other metrics to see if the problem is systemwide or only in a particular service.
If the issue is related to a particular service, then check if the back-end server is down or overloaded.
If the WebLogic Server has been running for a long time, compare the Since Startup metrics with the Recent History metrics to determine if performance has recently deteriorated, and if so, by how much.
Verify connection configuration information associated with the service to see if it is incorrect or no longer valid. See also Appendix A, "WebCenter Portal Configuration."
When the status of a service is Down or some operations do not work, then validate, test, and ping the back-end server through direct URLs. For details, refer to the "Testing Connection" section in the relevant chapter. For a list of chapters, see Part IV, "Managing Services, Portlet Producers, and External Applications".
If a service is reconfigured, but the container is not restarted to pick up the changes, then the service becomes unavailable.
This section describes per operation metrics for all services and components. This section includes the following sub sections:
To access live performance metrics for your WebCenter Portal application, see Section 38.2, "Viewing Performance Information."
Performance metrics associated with the Announcements service (Figure 38-1) are described in Table 38-4 and Section 38.1.2, "Common WebCenter Portal Metrics."
To monitor these metrics through Fusion Middleware Control, see Section 38.2, "Viewing Performance Information."
Table 38-4 Announcements Service - Operations Monitored
| Operation | Description | Performance Issues - User Action |
|---|---|---|
|
Login |
Logs a WebCenter Portal user (accessing the Announcements service) into the discussions server that is hosting announcements. |
For service-specific causes, see Section 38.1.5.1, "Announcements Service." For common causes, see Section 38.1.3, "Common WebCenter Portal Performance Issues and Actions." |
|
Logout |
Logs a WebCenter Portal user out of the discussions server that is hosting announcements. |
For service-specific causes, see Section 38.1.5.1, "Announcements Service." For common causes, see Section 38.1.3, "Common WebCenter Portal Performance Issues and Actions." |
|
Search |
Searches for terms within announcement text. |
If Announcement searches are failing, verify that Announcement text contains the search terms. For other causes, see Section 38.1.5.1, "Announcements Service." For common causes, see Section 38.1.3, "Common WebCenter Portal Performance Issues and Actions." |
|
Create |
Creates an announcement. |
For service-specific causes, see Section 38.1.5.1, "Announcements Service.". For common causes, see Section 38.1.3, "Common WebCenter Portal Performance Issues and Actions." |
|
List |
Retrieves a list of announcements. |
For service-specific causes, see Section 38.1.5.1, "Announcements Service." For common causes, see Section 38.1.3, "Common WebCenter Portal Performance Issues and Actions." |
Performance metrics associated with the BPEL Worklist service (Figure 38-2) are described in Section 38.1.2, "Common WebCenter Portal Metrics."
To monitor these metrics through Fusion Middleware Control, see Section 38.2, "Viewing Performance Information."
Performance metrics associated with the Documents service and Content Presenter (Figure 38-3 and Figure 38-4) are described in the following tables:
Table 38-6, "Content Repository Metrics - Summary (All Repositories)"
Table 38-7, "Content Repository Metrics - Operation Summary Per Repository"
Table 38-8, "Content Repository Metrics - Operation Detail Per Repository"
Figure 38-4 Content Repository Metrics - Per Operation
To monitor these metrics through Fusion Middleware Control, see Section 38.2, "Viewing Performance Information."
Table 38-5 Content Repository - Operations Monitored
Table 38-6 Content Repository Metrics - Summary (All Repositories)
| Metric | Description |
|---|---|
|
Status |
The current status of the Documents service:
|
|
Successful Invocations (%) |
The percentage of Documents service invocations that succeeded (Upload, Download, Search Login, Delete): - Since Startup - Recent History If Successful Invocations (%) is below 100%, check the diagnostic logs to establish why service requests are failing. See, Section 38.3, "Viewing and Configuring Log Information." |
|
Invocations |
The number of Documents service invocations per minute (Upload, Download, Search Login, Delete): - Since Startup - Recent History This metric provides data on how frequently a particular service is being invoked for processing of operations. Comparing this metric across services can help determine the most frequently used WebCenter Portal service in the application. |
|
Average Time (ms) |
The average time taken to process operations associated with the Documents service (Upload, Download, Search Login, Delete): - Since Startup - Recent History |
|
Most Popular Operations |
The number of invocations per operation (displayed on a chart). The highest value on the chart indicates which operation is used the most. The lowest value indicates which operations is used the least. |
|
Response Time |
The average time to process operations associated with the Documents service since the WebCenter Portal application started up (displayed on a chart). The highest value on the chart indicates the worst performing operation. The lowest value indicates which operations is performing the best. |
|
Download Throughput (bytes per second) |
The rate at which the Documents service downloads documents. |
|
Upload Throughput (bytes per second) |
The rate at which the Documents service uploads documents |
Table 38-7 Content Repository Metrics - Operation Summary Per Repository
| Metric | Description |
|---|---|
|
Status |
The current status of the content repository:
|
|
Successful Invocations (%) |
The percentage of Documents service invocations that succeeded (Upload, Download, Search, Login, Delete) for this content repository: - Since Startup - Recent History If Successful Invocations (%) is below 100%, check the diagnostic logs to establish why service requests are failing. See, Section 38.3, "Viewing and Configuring Log Information". |
|
Invocations |
The number of Documents service invocations per minute (Upload, Download, Search, Login, Delete) for this content repository: - Since Startup - Recent History This metric provides data on how frequently a particular service is being invoked for processing of operations. Comparing this metric across services can help determine the most frequently used WebCenter Portal service in the application. |
|
Average Time (ms) |
The average time taken to process operations associated with the Documents service (Upload, Download, Search, Login, Delete) for this content repository: - Since Startup - Recent History |
|
Bytes Downloaded |
The volume of data that the Documents service has downloaded from this content repository. |
|
Download Throughput (bytes per second) |
The rate at which the Documents service downloads documents from this content repository. |
|
Bytes Uploaded |
The volume of data that the Documents service has uploaded from this content repository. |
|
Upload Throughput (bytes per second) |
The rate at which the Documents service uploads documents from this content repository. |
|
Maximum Time (ms) |
The maximum time to process operations associated with the Documents service (Upload, Download, Search, Login, Delete) for this content repository. |
Table 38-8 Content Repository Metrics - Operation Detail Per Repository
| Metric | Description |
|---|---|
|
Invocations |
The number of Documents service invocations per operation (Upload, Download, Search, Login, Delete): - Since Startup - Recent History This metric provides data on how frequently a particular service is being invoked for processing of operations. Comparing this metric across services can help determine the most frequently used WebCenter Portal service in the application. |
|
Average Processing Time (ms) |
The average time taken to process each operation associated with the Documents service (Upload, Download, Search, Login, Delete): - Since Startup - Recent History |
Performance metrics associated with the Discussions service (Figure 38-5) are described in Table 38-9 and Section 38.1.2, "Common WebCenter Portal Metrics."
To monitor these metrics through Fusion Middleware Control, see Section 38.2, "Viewing Performance Information."
Table 38-9 Discussions Service - Operations Monitored
| Operation | Description | Performance Issues - User Action |
|---|---|---|
|
Login |
Logs a WebCenter Portal user (accessing the Discussions service) into the discussions server that is hosting discussions forums. |
For service-specific causes, see Section 38.1.5.4, "Discussions Service." For common causes, see Section 38.1.3, "Common WebCenter Portal Performance Issues and Actions." |
|
Logout |
Logs a WebCenter Portal user out of the discussions server that is hosting discussion forums. |
For service-specific causes, see Section 38.1.5.4, "Discussions Service." For common causes, see Section 38.1.3, "Common WebCenter Portal Performance Issues and Actions." |
|
Create Forum |
Creates a discussion forum in the discussions server, under a specific category. |
If you are having problems creating forums, it may be due to:
For other service-specific causes, see Section 38.1.5.4, "Discussions Service." For common causes, see Section 38.1.3, "Common WebCenter Portal Performance Issues and Actions." |
|
Create Topic |
Creates a topic in the discussions server, under a specific forum. |
If you are having problems creating forums, it may be due to:
For other service-specific causes, see Section 38.1.5.4, "Discussions Service". For information on common causes, see Section 38.1.3, "Common WebCenter Portal Performance Issues and Actions". |
|
List Forums |
Retrieves a list of forums, under a specific category, from the discussion server. |
If you are having problems creating forums, it may be due to:
For other service-specific causes, see Section 38.1.5.4, "Discussions Service." For common causes, see Section 38.1.3, "Common WebCenter Portal Performance Issues and Actions." |
|
List Topics |
Retrieves a list of topics, under a specific forum, from the discussion server. |
If you are having problems creating forums, it may be due to:
For other service-specific causes, see Section 38.1.5.4, "Discussions Service." For common causes, see Section 38.1.3, "Common WebCenter Portal Performance Issues and Actions." |
|
Search |
Searches for terms within discussion forum text, in the discussions server. |
If you are having problems creating forums, it may be due to:
For other service-specific causes, see Section 38.1.5.4, "Discussions Service." For common causes, see Section 38.1.3, "Common WebCenter Portal Performance Issues and Actions." |
Performance metrics associated with the Events service are described in Table 38-10 and Section 38.1.2, "Common WebCenter Portal Metrics."
To monitor these metrics through Fusion Middleware Control, see Section 38.2, "Viewing Performance Information."
Table 38-10 Events Service - Operations Monitored
| Operation | Description | Performance Issues - User Action |
|---|---|---|
|
Create Event |
Creates a space or personal event in the WebCenter Portal's repository. |
For service-specific causes, see Section 38.1.5.6, "Events Service." For common causes, see Section 38.1.3, "Common WebCenter Portal Performance Issues and Actions." |
|
Update Event |
Updates a space or personal event stored in the WebCenter Portal's repository. |
For service-specific causes, see Section 38.1.5.6, "Events Service." For common causes, see Section 38.1.3, "Common WebCenter Portal Performance Issues and Actions." |
|
Delete Event |
Deletes a space or personal event in the WebCenter Portal's repository. |
For service-specific causes, see Section 38.1.5.6, "Events Service." For common causes, see Section 38.1.3, "Common WebCenter Portal Performance Issues and Actions." |
|
List Event |
Retrieves a list of events from the WebCenter Portal's repository. |
For service-specific causes, see Section 38.1.5.6, "Events Service." For common causes, see Section 38.1.3, "Common WebCenter Portal Performance Issues and Actions." |
|
Search Event |
Searches for terms within event text. |
For service-specific causes, see Section 38.1.5.6, "Events Service." For common causes, see Section 38.1.3, "Common WebCenter Portal Performance Issues and Actions." |
Performance metrics associated with the External Application service are described in Table 38-11 and Section 38.1.2, "Common WebCenter Portal Metrics."
Figure 38-8 External Application Metrics - Per Operation
To monitor these metrics through Fusion Middleware Control, see Section 38.2, "Viewing Performance Information."
Table 38-11 External Applications - Operations Monitored
| Operation | Description | Performance Issues - User Action |
|---|---|---|
|
Fetch Credentials |
Retrieves credentials for an external application. |
For service-specific causes, see Section 38.1.5.5, "External Applications Service." For common causes, see Section 38.1.3, "Common WebCenter Portal Performance Issues and Actions." |
|
Store Credentials |
Stores user credentials for an external application. |
For service-specific causes, see Section 38.1.5.5, "External Applications Service." For common causes, see Section 38.1.3, "Common WebCenter Portal Performance Issues and Actions." |
|
Fetch External Application |
Retrieves an external application. |
For service-specific causes, see Section 38.1.5.5, "External Applications Service." For common causes, see Section 38.1.3, "Common WebCenter Portal Performance Issues and Actions." |
|
Automated Logins |
Logs a WebCenter Portal user in to an external application (using the automated login feature). |
For service-specific causes, see Section 38.1.5.5, "External Applications Service." For common causes, see Section 38.1.3, "Common WebCenter Portal Performance Issues and Actions." |
Performance metrics associated with the Instant Messaging and Presence (IMP) service (Figure 38-9) are described in Table 38-12 and Section 38.1.2, "Common WebCenter Portal Metrics."
To monitor these metrics through Fusion Middleware Control, see Section 38.2, "Viewing Performance Information."
Table 38-12 Instant Messaging and Presence Service - Operations Monitored
| Operation | Description | Performance Issues - User Action |
|---|---|---|
|
Get Presence |
Retrieves user presence information from the IMP server. |
For service-specific causes, see Section 38.1.5.7, "Instant Messaging and Presence (IMP) Service." For common causes, see Section 38.1.3, "Common WebCenter Portal Performance Issues and Actions." |
|
Login |
Logs a WebCenter Portal user (accessing the IMP service) into the IMP server. |
For service-specific causes, see Section 38.1.5.7, "Instant Messaging and Presence (IMP) Service." For common causes, see Section 38.1.3, "Common WebCenter Portal Performance Issues and Actions." |
|
Logout |
Logs a WebCenter Portal user (accessing the IMP service) out of the IMP server. |
For service-specific causes, see Section 38.1.5.7, "Instant Messaging and Presence (IMP) Service." For common causes, see Section 38.1.3, "Common WebCenter Portal Performance Issues and Actions." |
Performance metrics associated with import and export services (Figure 38-10) are described in Table 38-13 and Section 38.1.2, "Common WebCenter Portal Metrics." These metrics apply to Spaces only.
To monitor these metrics through Fusion Middleware Control, see Section 38.2, "Viewing Performance Information."
Table 38-13 Import/Export - Operations Monitored
| Operation | Description | Performance Issues - User Action |
|---|---|---|
|
Export |
Exports an entire WebCenter Portal application. |
For service-specific causes, see Section 38.1.5.8, "Import and Export." For common causes, see Section 38.1.3, "Common WebCenter Portal Performance Issues and Actions." |
|
Import |
Imports entire WebCenter Portal application. |
For service-specific causes, see Section 38.1.5.8, "Import and Export." For common causes, see Section 38.1.3, "Common WebCenter Portal Performance Issues and Actions." |
(WebCenter Portal: Spaces only) Performance metrics associated with the List service (Figure 38-11) are described in Table 38-14 and Section 38.1.2, "Common WebCenter Portal Metrics."
To monitor these metrics through Fusion Middleware Control, see Section 38.2, "Viewing Performance Information."
Table 38-14 List service - Operations Monitored
| Operation | Description | Performance Issues - User Action |
|---|---|---|
|
Create List |
Creates a list in the user session. The Save Data operation commits new lists to the MDS repository. |
For service-specific causes, see Section 38.1.5.9, "Lists Service." For common causes, see Section 38.1.3, "Common WebCenter Portal Performance Issues and Actions." |
|
Copy List |
Copies a list and its data in the user session. The Save Data operation commits copied lists and list data to the MDS repository and the WebCenter Portal's repository (the database where list data is stored). |
For service-specific causes, see Section 38.1.5.9, "Lists Service." For common causes, see Section 38.1.3, "Common WebCenter Portal Performance Issues and Actions." |
|
Delete List |
Deletes a list and its data in the user session. The Save Data operation commits list changes to the MDS repository and the WebCenter Portal's repository (the database where list data is stored). |
For service-specific causes, see Section 38.1.5.9, "Lists Service." For common causes, see Section 38.1.3, "Common WebCenter Portal Performance Issues and Actions." |
|
Create Row |
Creates row of list data in the user session. The Save Data operation commits list data changes to the WebCenter Portal's repository (the database where list data is stored). |
For service-specific causes, see Section 38.1.5.9, "Lists Service." For common causes, see Section 38.1.3, "Common WebCenter Portal Performance Issues and Actions." |
|
Update Row |
Updates row of list data in the user session. The Save Data operation commits list data changes to the WebCenter Portal's repository (the database where list data is stored). |
For service-specific causes, see Section 38.1.5.9, "Lists Service." For common causes, see Section 38.1.3, "Common WebCenter Portal Performance Issues and Actions." |
|
Delete Row |
Deletes row of list data in the user session. The Save Data operation commits list data changes to the WebCenter Portal's repository (the database where list data is stored). |
For service-specific causes, see Section 38.1.5.9, "Lists Service." For common causes, see Section 38.1.3, "Common WebCenter Portal Performance Issues and Actions." |
|
Search |
Retrieves a list by its ID from the Metadata repository. |
For service-specific causes, see Section 38.1.5.9, "Lists Service." For common causes, see Section 38.1.3, "Common WebCenter Portal Performance Issues and Actions." |
|
Save Data |
Saves all changes to lists and list data (in the user session) to the Metadata Services repository and the WebCenter Portal's repository (the database where list information is stored). |
For service-specific causes, see Section 38.1.5.9, "Lists Service." For common causes, see Section 38.1.3, "Common WebCenter Portal Performance Issues and Actions." |
Performance metrics associated with the Mail service (Figure 38-12) are described in Table 38-15 and Section 38.1.2, "Common WebCenter Portal Metrics."
To monitor these metrics through Fusion Middleware Control, see Section 38.2, "Viewing Performance Information."
Table 38-15 Mail Service - Operations Monitored
| Operation | Description | Performance Issues - User Action |
|---|---|---|
|
Login |
Logs a WebCenter Portal user into the mail server that is hosting mail services. |
For service-specific causes, see Section 38.1.5.10, "Mail Service." For common causes, see Section 38.1.3, "Common WebCenter Portal Performance Issues and Actions." |
|
Logout |
Logs a WebCenter Portal user out of the mail server that is hosting mail services. |
For service-specific causes, see Section 38.1.5.10, "Mail Service." For common causes, see Section 38.1.3, "Common WebCenter Portal Performance Issues and Actions." |
|
Receive |
Receives a mail. |
For service-specific causes, see Section 38.1.5.10, "Mail Service." For common causes, see Section 38.1.3, "Common WebCenter Portal Performance Issues and Actions." |
|
Send |
Sends a mail. |
For service-specific causes, see Section 38.1.5.10, "Mail Service." For common causes, see Section 38.1.3, "Common WebCenter Portal Performance Issues and Actions." |
|
Search |
Searches for mail that contains a specific term. |
For service-specific causes, see Section 38.1.5.10, "Mail Service." For information on common causes, see Section 38.1.3, "Common WebCenter Portal Performance Issues and Actions." |
Performance metrics associated with the Notes service (Figure 38-13) are described in Table 38-16 and Section 38.1.2, "Common WebCenter Portal Metrics."
To monitor these metrics through Fusion Middleware Control, see Section 38.2, "Viewing Performance Information."
Table 38-16 Notes Service - Operations Monitored
| Operation | Description | Performance Issues - User Action |
|---|---|---|
|
Create |
Creates a personal note. The Save Changes operation commits new notes to the MDS repository. |
For service-specific causes, see Section 38.1.5.11, "Notes Service." For common causes, see Section 38.1.3, "Common WebCenter Portal Performance Issues and Actions." |
|
Update |
Updates a personal note. The Save Changes operation commits note updates to the MDS repository. |
For service-specific causes, see Section 38.1.5.11, "Notes Service." For common causes, see Section 38.1.3, "Common WebCenter Portal Performance Issues and Actions." |
|
Find |
Retrieves a note from the MDS repository. |
For service-specific causes, see Section 38.1.5.11, "Notes Service." For common causes, see Section 38.1.3, "Common WebCenter Portal Performance Issues and Actions." |
|
Delete |
Deletes a note from the MDS repository. |
For service-specific causes, see Section 38.1.5.11, "Notes Service." For common causes, see Section 38.1.3, "Common WebCenter Portal Performance Issues and Actions." |
Performance metrics associated with the Page service (Figure 38-14) are described in Table 38-17 and Section 38.1.2, "Common WebCenter Portal Metrics."
To monitor these metrics through Fusion Middleware Control, see Section 38.2, "Viewing Performance Information."
Table 38-17 Page Service - Operations Monitored
| Operation | Description | Performance Issues - User Action |
|---|---|---|
|
Create |
Creates a page in the WebCenter Portal application. |
For service-specific causes, see Section 38.1.5.12, "Page Service." For common causes, see Section 38.1.3, "Common WebCenter Portal Performance Issues and Actions." |
|
Copy |
Copies a page. |
For service-specific causes, see Section 38.1.5.12, "Page Service." For common causes, see Section 38.1.3, "Common WebCenter Portal Performance Issues and Actions." |
|
Delete |
Deletes a page. |
For service-specific causes, see Section 38.1.5.12, "Page Service." For common causes, see Section 38.1.3, "Common WebCenter Portal Performance Issues and Actions." |
|
Search |
Searches for pages that contain a specific term. |
For service-specific causes, see Section 38.1.5.12, "Page Service." For common causes, see Section 38.1.3, "Common WebCenter Portal Performance Issues and Actions." |
Performance metrics associated with the portlet producers (Figure 38-15) are described in the following tables:
To monitor these metrics through Fusion Middleware Control, see Section 38.2, "Viewing Performance Information."
Table 38-18 Portlet Producers - Summary
| Metric | Description |
|---|---|
|
Status |
The current status of portlet producers used in the WebCenter Portal application:
|
|
Successful Invocations (%) |
The percentage of portlet producer invocations that succeeded: - Since Startup - Recent History Any request that fails will impact availability. This includes WebCenter Portal application-related failures such as timeouts and internal errors, and also client/server failures such as requests returned with response codes HTTP4xx or HTTP5xx, responses with a bad content type, and SOAP faults, where applicable. If Successful Invocations (%) is below 100%, check the diagnostic logs to establish why service requests are failing. See, Section 38.3, "Viewing and Configuring Log Information." |
|
Invocations |
The number of portlet producer invocations per minute: - Since Startup - Recent History This metric measures each WebCenter Portal application-related portlet request and therefore, due to cache hits, errors, or timeouts on the application, this total may be higher than the number of actual HTTP requests made to the producer server. |
|
Average Time (ms) |
The average time taken to make a portlet request, regardless of the result: - Since Startup - Recent History |
Table 38-19 Portlet Producer - Detail
| Metric | Description |
|---|---|
|
Most Popular Producers |
The number of invocations per producer (displayed on a chart). The highest value on the chart indicates which portlet producer is used the most. The lowest value indicates which portlet producer is used the least. |
|
Response Time |
The average time each portlet producer takes to process producer requests since the WebCenter Portal application started up (displayed on a chart). The highest value on the chart indicates the worst performing portlet producer. The lowest value indicates which portlet producer is performing the best. |
|
Producer Name |
The name of the portlet producer being monitored. Click the name of a portlet producer to pop up more detailed information about each portlet that the application uses. See also Table 38-21, "Portlet - Detail". |
|
Status |
The current status of each portlet producer:
|
|
Producer Type |
The portlet producer type: Web or WSRP
|
|
Successful Invocations (%) |
The percentage of producer invocations that succeeded: - Since Startup - Recent History |
|
Invocations |
The number of invocations, per producer: - Since Startup - Recent History By sorting the table on this column, you can find the most frequently accessed portlet producer in your WebCenter Portal application. |
|
Average Time (ms) |
The average time taken to make a portlet request, regardless of the result: - Since Startup - Recent History Use this metric to detect non-functional portlet producers. If you use this metric with the Invocations metric, then you can prioritize which producer to focus on. |
|
Maximum Time (ms) |
The maximum time taken to process producer requests: - Successes - HTTP200xx response code - Re-directs - HTTP300xx response code - Client Errors - HTTP400xx response code - Server Errors - HTTP500xx response code |
Performance metrics associated with portlets (Figure 38-16) are described in the following tables:
To monitor these metrics through Fusion Middleware Control, see Section 38.2, "Viewing Performance Information."
Table 38-20 Portlets - Summary
| Metric | Description |
|---|---|
|
Status |
The current status of portlets used in the WebCenter Portal application:
|
|
Successful Invocations (%) |
The percentage of portlet invocations that succeeded: - Since Startup - Recent History Any request that fails will impact availability. This includes WebCenter Portal application-related failures such as timeouts and internal errors, and also client/server errors. If Successful Invocations (%) is below 100%, check the diagnostic logs to establish why service requests are failing. See, Section 38.3, "Viewing and Configuring Log Information." |
|
Invocations |
The number of portlet invocations per minute: - Since Startup - Recent History This metric measures each WebCenter Portal application-related portlet request and therefore, due to cache hits, errors, or timeouts on the application, this total may be higher than the number of actual HTTP requests made to the portlet producer. |
|
Average Time (ms) |
The average time taken to process operations associated with portlets, regardless of the result: - Since Startup - Recent History |
Table 38-21 Portlet - Detail
| Metric | Description |
|---|---|
|
Most Popular Portlets |
The number of invocations per portlet (displayed on a chart). The highest value on the chart indicates which portlet is used the most. The lowest value indicates which portlet is used the least. |
|
Response Time |
The average time each portlet takes to process requests since the WebCenter Portal application started up (displayed on a chart). The highest value on the chart indicates the worst performing portlet. The lowest value indicates which portlet is performing the best. |
|
Portlet Name |
The name of the portlet being monitored. |
|
Status |
The current status of each portlet:
|
|
Producer Name |
The name of the portlet producer through which the portlet is accessed. |
|
Producer Type |
The portlet producer type: Web or WSRP
|
|
Successful Invocations (%) |
The percentage of portlet invocations that succeeded: - Since Startup - Recent History If Successful Invocations (%) is below 100%, check the diagnostic logs to establish why service requests are failing. See, Section 38.3, "Viewing and Configuring Log Information." |
|
Invocations |
The number of invocations, per portlet: - Since Startup - Recent History By sorting the table on this column, you can find the most frequently accessed portlet in your WebCenter Portal application. |
|
Average Time (ms) |
The average time each portlet takes to process requests, regardless of the result: - Since Startup - Recent History Use this metric to detect non-performant portlets. If you use this metric with the Invocations metric, then you can prioritize which portlet to focus on. |
|
Maximum Time (ms) |
The maximum time taken to process portlet requests: - Successes - HTTP200xx - Redirects - HTTP300xx - Client Errors - HTTP400xx - Server Errors - HTTP500xx The breakdown of performance statistics by HTTP response code can help you identify which factors are driving up the total average response time. For example, failures due to portlet producer timeouts would adversely affect the total average response time. |
Table 38-22 Portlet - HTTP Response Code Statistics
| Metric | Description |
|---|---|
|
Portlet Name |
The name of the portlet being monitored. |
|
Invocations Count - Successes - Redirects - Client Errors - Server Errors |
The number of invocations, by type (HTTP response code): - Since Startup - Recent History See also Table 38-23, "HTTP Response Codes". |
|
Average Time (ms) - Successes - Redirects - Client Errors - Server Errors |
The average time each portlet takes to process requests: - Since Startup - Recent History Use this metric to detect non-functional portlets. If you use this metric with the Invocations metric, then you can prioritize which portlet to focus on. |
Table 38-23 HTTP Response Codes
| HTTP Response and Error Code | Description |
|---|---|
|
200 -Successful Requests |
Portlet requests that return any HTTP2xx response code, or which were successful without requiring an HTTP request to the remote producer, for example, a cache hit. |
|
300 -Unresolved Redirections |
Portlet requests that return any HTTP3xx response code. |
|
400 -Unsuccessful Request Incomplete |
Portlet requests that return any HTTP4xx response code. |
|
500 -Unsuccessful Server Errors |
Portlet requests that failed for any reason, including requests that return HTTP5xx response codes, or which failed due to a WebCenter Portal application-related error, timeout, bad content type response, or SOAP fault. |
Performance metrics associated with the People Connections service are described in Table 38-24 and Section 38.1.2, "Common WebCenter Portal Metrics."
To monitor these metrics through Fusion Middleware Control, see Section 38.2, "Viewing Performance Information."
Table 38-24 People Connections Service - Operations Monitored
| Operation | Description | Performance Issues - User Action |
|---|---|---|
|
Get Profiles |
Retrieves profiles of a user. |
For service-specific causes, see Section 38.1.5.14, "People Connections Service." For common causes, see Section 38.1.3, "Common WebCenter Portal Performance Issues and Actions." |
|
Get Activities |
Retrieves the activities based on the user filter options. |
For service-specific causes, see Section 38.1.5.14, "People Connections Service." For common causes, see Section 38.1.3, "Common WebCenter Portal Performance Issues and Actions." |
|
Publish Activities |
Publishes an activity in the user session and saves it in the WebCenter Portal application. |
For service-specific causes, see Section 38.1.5.14, "People Connections Service." For common causes, see Section 38.1.3, "Common WebCenter Portal Performance Issues and Actions." |
|
Get Messages |
Retrieves the messages of the user. |
For service-specific causes, see Section 38.1.5.14, "People Connections Service." For common causes, see Section 38.1.3, "Common WebCenter Portal Performance Issues and Actions." |
|
Get Feedback |
Retrieves the feedback of the user. |
For service-specific causes, see Section 38.1.5.14, "People Connections Service." For common causes, see Section 38.1.3, "Common WebCenter Portal Performance Issues and Actions." |
|
Get Connections |
Retrieves the connections of users. |
For service-specific causes, see Section 38.1.5.14, "People Connections Service." For common causes, see Section 38.1.3, "Common WebCenter Portal Performance Issues and Actions." |
Performance metrics associated with the Polls service (Figure 38-18) are described in Table 38-25 and Section 38.1.2, "Common WebCenter Portal Metrics."
To monitor these metrics through Fusion Middleware Control, see Section 38.2, "Viewing Performance Information."
Table 38-25 Polls Service - Operations Monitored
| Operation | Description | Performance Issues - User Action |
|---|---|---|
|
Create Poll |
Creates a poll in the WebCenter Portal application. |
For service-specific causes, see Section 38.1.5.15, "Polls Service." For common causes, see Section 38.1.3, "Common WebCenter Portal Performance Issues and Actions." |
|
Edit Poll |
Edit a poll in the WebCenter Portal application. |
For service-specific causes, see Section 38.1.5.15, "Polls Service." For common causes, see Section 38.1.3, "Common WebCenter Portal Performance Issues and Actions." |
|
Delete Poll |
Deletes the ongoing poll. |
For service-specific causes, see Section 38.1.5.15, "Polls Service." For common causes, see Section 38.1.3, "Common WebCenter Portal Performance Issues and Actions." |
|
Get Poll By ID |
Displays the ongoing poll. |
For service-specific causes, see Section 38.1.5.15, "Polls Service." For common causes, see Section 38.1.3, "Common WebCenter Portal Performance Issues and Actions." |
|
Submit Poll |
Submits the ongoing poll. |
For service-specific causes, see Section 38.1.5.15, "Polls Service." For common causes, see Section 38.1.3, "Common WebCenter Portal Performance Issues and Actions." |
|
Analyze Results |
Analyzes the poll result. |
For service-specific causes, see Section 38.1.5.15, "Polls Service." For common causes, see Section 38.1.3, "Common WebCenter Portal Performance Issues and Actions." |
Performance metrics associated with the RSS service (Figure 38-19) are described in Section 38.1.2, "Common WebCenter Portal Metrics."
To monitor these metrics through Fusion Middleware Control, see Section 38.2, "Viewing Performance Information."
Performance metrics associated with the Recent Activities service (Figure 38-20) are described in Section 38.1.2, "Common WebCenter Portal Metrics."
To monitor these metrics through Fusion Middleware Control, see Section 38.2, "Viewing Performance Information."
Performance metrics associated with the Search service (Figure 38-21) are described in Table 38-26 and Section 38.1.2, "Common WebCenter Portal Metrics."
To monitor these metrics through Fusion Middleware Control, see Section 38.2, "Viewing Performance Information."
Table 38-26 Search Service - Search Sources
| Operation | Description |
|---|---|
|
Announcements |
Announcement text is searched. |
|
Documents |
Contents in files and folders are searched. |
|
Discussion Forums |
Forums and topics are searched. |
|
Spaces |
Contents saved in a space, such as links, lists, notes, tags, and events are searched. |
|
Space Events |
Space events are searched. |
|
Links |
Objects to which links have been created are searched (for example, announcements, discussion forum topics, documents, and events). |
|
Lists |
Information stored in lists is searched. |
|
Notes |
Notes text, such as reminders, is searched. |
|
Oracle Secure Enterprise Search |
Contents from the Document Library task flow, discussions, tag clouds, notes, and other WebCenter Portal services are searched. |
|
Pages |
Contents added to application, personal, public, wiki, and blog pages are searched. |
This section describes service-specific performance issues and user actions required to address those issue. This section includes the following sub sections:
Note:
For information about tuning the performance of WebCenter Portal services, see Appendix A, "WebCenter Portal Configuration."
Section 38.1.5.3, "Content Repository (Documents and Content Presenter) Service"
Section 38.1.5.7, "Instant Messaging and Presence (IMP) Service"
If you are experiencing problems with the Announcements service and the status is Down, check the diagnostic logs to establish why this service is unavailable. Some typical causes of failure include:
Discussions server is down or not responding.
Network connectivity issues exist between the application and the Discussions server.
Connection configuration information associated with the Announcements service is incorrect or no longer valid.
If you are experiencing problems with the BPEL Worklist service and the status is Down, check the diagnostic logs to establish why this service is unavailable. Some typical causes of failure include:
BPEL server being queried is not available.
Network connectivity issues exist between the application and the BPEL server.
Connection configuration information associated with the Worklist service is incorrect or no longer valid.
If you are experiencing problems with the Documents service and the status is Down, check the diagnostic logs to establish why this service is unavailable. Also, do one of the following:
For Oracle WebCenter Content: Content Server (Content Server) and Oracle Portal, verify that the back-end server is up and running.
For Content Server, verify that the socket connection is open for the client for which the service is not functioning properly.
For Oracle Portal, verify the status of the JDBC connection using Oracle WebLogic Administration Console.
(Functional check) Check logs on the back-end server. For Content Server, go to Content Server > Administration > Log files > Content Server Logs. For Oracle Portal use Fusion Middleware Control.
(Functional check) Search for log entries in which the module name starts with oracle.vcr, oracle.webcenter.content, oracle.webcenter.doclib, and oracle.stellent.
If you are experiencing problems with the Discussions service and the status is Down, check the diagnostic logs to establish why this service is unavailable. Some typical causes of failure include:
Discussions server is down or not responding.
Network connectivity issues exist between the application and the discussion server.
Connection configuration information associated with the Discussions service is incorrect or no longer valid.
If you are experiencing problems with the External Applications service and the status is Down, check the diagnostic logs to establish why this service is unavailable. Some typical causes of failure include:
Credential store is not configured for the application.
Credential store that is configured, for example Oracle Internet Directory, is down or not responding.
If you are experiencing problems with the Events (space events or personal events) service and the status is Down, check the diagnostic logs to establish why this service is unavailable. Some typical causes of failure include:
WebCenter Portal's repository is not available (the database where event information is stored).
Network connectivity issues exist between the application and the WebCenter Portal's repository.
Connection configuration information associated with the Events service is incorrect or no longer valid.
If you are experiencing problems with the IMP service and the status is Down, check the diagnostic logs to establish why this service is unavailable. Some typical causes of failure include:
Instant Messaging and Presence server is not available.
Network connectivity issues exist between the application and the Instant Messaging and Presence server.
Connection configuration information associated with the IMP service is incorrect or no longer valid.
If you are experiencing import and export problems and the status is Down, check the diagnostic logs to establish why this service is unavailable.
If you are experiencing problems with the Lists service and the status is Down, check the diagnostic logs to establish why this service is unavailable. Some typical causes of failure include:
MDS repository or WebCenter Portal's repository, in which the data of the Lists service is stored, is not available.
Network connectivity issues exist between the application and the repository.
Connection configuration information associated with the Lists service is incorrect or no longer valid.
If you are experiencing problems with the Mail service and the status is Down, check the diagnostic logs to establish why this service is unavailable. Some typical causes of failure include:
Mail server is not available.
Network connectivity issues exist between the application and the mail server.
Connection configuration information associated with the Mail service is incorrect or no longer valid.
If you are experiencing problems with the Notes service, check if the MDS repository is unavailable or responding slowly (the repository where note information is stored).
If you are experiencing problems with the Page service and the status is Down, check the diagnostic logs to establish why this service is unavailable. Some typical causes of failure include:
WebCenter Portal's repository is not available (the database where page information is stored).
Network connectivity issues exist between the application and the WebCenter Portal's repository.
If you are experiencing problems with a portlet producer and the status is Down, check the diagnostic logs to establish why this service is unavailable. Some typical causes of failure include:
Portlet producer server is down or not responding.
Connection configuration information associated with the portlet producer is incorrect or no longer valid.
Producer requests are timing out.
There may be a problem with a particular producer, or the performance issue is due to a specific portlet(s) from that producer.
If you are experiencing problems with the People Connections service and the status is Down, check the diagnostic logs to establish why this service is unavailable. Some typical causes of failure include:
The service is down or not responding.
Connection configuration information associated with the service is incorrect or no longer valid.
WebCenter Portal's repository is not available (the database where page information is stored).
Network connectivity issues exist between the application and the WebCenter Portal's repository.
If you are experiencing problems with the Polls service and the status is Down, check the diagnostic logs to establish why this service is unavailable. Some typical causes of failure include:
The service is down or not responding.
Connection configuration information associated with the service is incorrect or no longer valid.
WebCenter Portal's repository is not available (the database where page information is stored).
Network connectivity issues exist between the application and the WebCenter Portal's repository.
If you are experiencing problems with the RSS service and the status is Down, check the diagnostic logs to establish why this service is unavailable. Some typical causes of failure include:
The Search service is not available.
A service being searched for recent activities has failed
Unable to Get Discussions Data
If you are experiencing performance issues, check the performance of the Discussions service.
Unable to Get Lists Data
If you are experiencing performance issues, check the performance of the Lists service.
Unable to Get Recent Activities Data
If you are experiencing performance issues, check the performance of the Recent Activity service.
If you are facing problems with the Recent Activities service and the status is Down, check the diagnostic logs to establish why this service is unavailable. Some typical causes of failure include:
Search Service is not available.
A service being searched for recent activity has failed
If you are facing problems with the Search service (a service executor) and the status is Down, check the diagnostic logs to establish why this executor is unavailable. Some typical causes of failure include:
The repository of the executor is not available.
Network connectivity issues exist between the application and the repository of the executor.
Connection configuration information associated with the executor is incorrect or no longer valid.
Content repositories being searched is currently unavailable.
(WebCenter Portal: Spaces only) Performance metrics associated with the space activity (Figure 38-22) are described in Table 38-27 and Section 38.1.2, "Common WebCenter Portal Metrics."
To monitor these metrics through Fusion Middleware Control, see Section 38.2, "Viewing Performance Information."
You can filter the data in the following ways:
Search for a specific space through the Space Name Filter field. (Does not show metrics for Home spaces.)
Display a specific number of rows through the Maximum Rows field.
Display most accessed, least performant, or pages that have maximum errors, through the Display dropdown list.
Table 38-27 Space Metrics
| Metric | Description |
|---|---|
|
Oracle WebCenter Portal: Spaces URL |
The Spaces application being managed. |
|
WebLogic Server |
The WebLogic Server instance in which the Spaces application is deployed. |
|
J2EE Application |
The name of the Spaces application. |
|
Page Response |
The current average response time (in milliseconds) of space pages. |
|
Most Active Spaces |
Graph showing the most active spaces, that is, spaces recording the most invocations. To compare a different set of spaces, select one or more spaces in the table, and then click Display in Chart. |
|
Page Throughput |
Graph showing the average number of pages processed per minute for each space. To compare a different set of spaces, select one or more spaces in the table, and then click Display in Chart. |
|
Average Processing Time |
Graph showing the average page processing time (in milliseconds) per space. To compare a different set of spaces, select one or more spaces in the table, and then click Display in Chart. |
|
Status |
The current status of each space:
|
|
Successful Invocations (%) |
The percentage of space invocations that succeeded: - Since Startup - Recent History If Successful Invocations (%) is below 100%, check the diagnostic logs to establish why service requests are failing. See, Section 38.3, "Viewing and Configuring Log Information." |
|
Invocations |
The number of space invocations per minute: - Since Startup - Recent History |
|
Errors |
The number of errors occurred in a space per minute. |
|
Page Throughput |
The average number of pages processed per minute for each space: - Since Startup - Recent History |
|
Average Time (ms) |
The average time (in ms) to display space pages: - Since Startup - Recent History |
|
Maximum Time (ms) |
The maximum time taken to display a space page. |
|
Minimum Time (ms) |
The minimum time taken to display a space page. |
Performance metrics associated with the page activity (Figure 38-24) are described in Table 38-28. You can display page metrics for both full and partial pages associated with Spaces applications and Framework applications.
Full Page and Partial Page Metrics
Full page metrics do not include partial page metrics. Partial page rendering of a component on a page increases only partial page metrics and does not cause any change in full page metrics. For example, a calendar refresh on a page increases partial page invocations by 1, but full page invocations remain unchanged.
Partial page requests render only portions of the page. Therefore, you can monitor the performance of pages within a page. Partial page refresh behavior is called partial page rendering (PPR). PPR allows only certain components on a page to be rerendered without the need to refresh the entire page. A common scenario is when an output component displays what a user has chosen or entered in an input component. Similarly, a command link or button can cause another component on the page to be rerendered without refreshing the entire page. For example, if a user takes a quick poll and clicks the Vote button, only the quick poll component is updated and rendered. Hence the full page invocations remain unchanged and the partial page invocations go up by 2. For more information about PPR, see the chapter "Rerendering Partial Page Content" in the Oracle Fusion Middleware Web User Interface Developer's Guide for Oracle Application Development Framework.
Note:
The page metrics discussed in this section are different from the Page service metrics discussed in Section 38.1.4.12, "Page Metrics." The Page service metrics, which show up as service metrics, monitor individual operations like creating pages. The Page metrics for spaces, which are discussed in this section, monitor the individual page performance when they are accessed. The Page metrics capture only view/display operations (do not include page edit operations).
Metrics Display for Pages
You can filter the data in the following ways:
Search for a specific page through the Page Name Filter field.
Search for a specific space through the Space Name Filter field. (relevant only to Spaces applications)
Display a specific number of rows through the Maximum Rows field.
Display most accessed, least performant, or pages that have maximum errors, through the Display dropdown list.
By default the Pages Per Minute for full page metrics is hidden. To show this metric, go to the View menu > Columns > Since Startup/Recent History > Full Page > Pages Per Minute (Figure 38-23). Similarly, to hide columns that are not required, deselect the column names.
Figure 38-23 Pages Per Minute Option in the View Menu
Metrics are shown only for custom pages. The metrics for the following types of pages are not shown:
All pages from any space named Home space
Welcome page of a space
Service pages such as documents and events
Table 38-28 Page Metrics - Full Page and Partial Page
| Metric | Description |
|---|---|
|
Invocations |
The number of page invocations per minute: - Since Startup - Recent History |
|
Average Time (ms) |
The average time (in ms) to display pages: - Since Startup - Recent History |
|
Maximum Time (ms) |
The maximum time taken to display a page. |
|
Errors (Only for full page) |
The number of errors occurred in a page per minute. |
|
Successful Invocations (Only for full page) |
The percentage of page invocations that succeeded: - Since Startup - Recent History If Successful Invocations (%) is below 100%, check the diagnostic logs to establish why service requests are failing. See, Section 38.3, "Viewing and Configuring Log Information." |
Fusion Middleware Control monitors a wide range of performance metrics for WebCenter Portal applications. You can view performance data for all the dependent services, external applications, and portlet producers used by your WebCenter Portal application.
This section includes the following subsections:
Administrators can monitor the performance and availability of all the components and services that make up a Spaces application, and the application as a whole. These detailed metrics will help diagnose performance issues and, if monitored regularly, you will learn to recognize trends as they develop and prevent performance problems in the future.
Some key metrics display on the Spaces home page. You can see at a glance which spaces are the most popular, identify the best and worst performing spaces and more. For details, see Section 38.1.6, "Space Metrics".
The Spaces home page also summarizes the status and performance of individual services, external applications, and any portlet producers that the application uses. When a service is Down or running slowly you can drill down to more detailed metrics to troubleshoot the problem, and take corrective action. For metric information, see Section 38.1, "Understanding Oracle WebCenter Portal Performance Metrics ."
This section includes the following subsections:
Section 38.2.1.3, "Monitoring Page Metrics for the Spaces Application"
Section 38.2.1.4, "Monitoring All Metrics Through the Metrics Palette"
To access service metrics for the Spaces application:
In Fusion Middleware Control Console, navigate to the home page for the Spaces application.
See Section 6.2, "Navigating to the Home Page for the Spaces Application".
From the WebCenter Portal menu, choose Monitoring > Service Metrics.
Use Services Summary at the top of the WebCenter Portal Service Metrics page to quickly see which services are up and running, and to review individual and relative performances of those services used by Spaces application.
Statistics become available when a service, application, or portlet is accessed for the first time. If a service is not configured or has never been used it will not appear in the Summary table.
Click the name of a service to drill down to more detailed metrics.
To learn more about individual metrics, see Section 38.1, "Understanding Oracle WebCenter Portal Performance Metrics ".
To access performance metrics for spaces created in the Spaces application:
In Fusion Middleware Control Console, navigate to the home page for Spaces application.
See Section 6.2, "Navigating to the Home Page for the Spaces Application."
From the WebCenter Portal menu, choose Monitoring > Space Metrics.
In the Space Name Filter field, enter the name of a space, then press the [Enter] key. For information about the space filtering options, see Section 38.1.6, "Space Metrics."
OR
In the Name column, click the space name (link) for which you want to display performance metrics. The metrics for the selected space display, as shown in Figure 38-25.
To access the page metrics:
In Fusion Middleware Control Console, navigate to the home page for the Spaces application.
See Section 6.2, "Navigating to the Home Page for the Spaces Application".
From the WebCenter Portal menu, choose Monitoring > Page Metrics.
For information about available page filtering options, see Section 38.1.7, "Page Metrics."
To see metrics for all pages in a space, enter the name of the space in the Space Name Filter field and press [Enter]. See Figure 38-26.
To see metrics for a particular page of a space, enter the page name in the Page Name Filter field and the name of the space to which this page belongs, in the Space Name Filter field, and then press [Enter]. See Figure 38-27.
To access performance summary for space and associated pages in the Spaces application:
In Fusion Middleware Control Console, navigate to the home page for the Spaces application.
See Section 6.2, "Navigating to the Home Page for the Spaces Application".
From the WebCenter Portal menu, choose Monitoring > Performance Summary.
Use the Show Metric Palette button at the top of the Performance Summary page to display the Metric Palette. This palette enables you to select metrics for services that are up and running, and to review live performances of individual services in graphical and tabular formats.
Statistics become available when a service, application, or portlet is accessed for the first time. If a service is not configured or has never been used it will not appear in the performance summary graphs and tables.
In the Metric Palette, expand a service folder and select the metric checkboxes to view the service performance in graphical or tabular format.
Figure 38-28 shows the Performance Summary page and Metric Palette. In addition to WebCenter Portal performance metrics, the Metric Palette also displays general performance metrics associated with any J2EE application, for example, ADF Application Pool metrics. To display the help content for any metric, right-click the required directory or any metric in the directory and select Help.
Figure 38-28 WebCenter Portal: Spaces - Performance Summary and Metric Palette
Administrators can monitor the performance and availability of all the components and services that make up Framework applications, and the application as a whole. These detailed metrics will help diagnose performance issues and, if monitored regularly, you will learn to recognize trends as they develop and prevent performance problems in the future.
This section includes the following subsections:
Section 38.2.2.2, "Monitoring Page Metrics for Framework Applications"
Section 38.2.2.3, "Monitoring All Metrics Through the Metrics Palette"
To access performance metrics for a service associated with a Framework application:
In Fusion Middleware Control Console, navigate to the home page for Framework applications.
See Section 6.3, "Navigating to the Home Page for Framework Applications".
From the Application Deployment menu, choose WebCenter Portal > Service Metrics.
Use the Services Summary at the top of the WebCenter Service Metrics page to quickly see which services are up and running, and to review individual and relative performances of all the services used by the Framework application.
Statistics become available when a service, application, or portlet is accessed for the first time. If a service is not configured or has never been used it will not appear in the Services Summary table.
Click the name of a service to drill down to more detailed metrics (Figure 38-28). To display the help content for any metric, right-click the required directory or any metric in the directory and select Help.
To learn more about individual metrics for each service, see Section 38.1, "Understanding Oracle WebCenter Portal Performance Metrics ".
To access performance metrics for a page associated with a Framework application:
In Fusion Middleware Control Console, navigate to the home page for Framework applications.
See Section 6.3, "Navigating to the Home Page for Framework Applications".
From the Application Deployment menu, choose WebCenter Portal > Page Metrics.
For information about available page filtering options, see Section 38.1.7, "Page Metrics."
To see metrics for a page, enter the page name in the Page Name Filter field and press [Enter].
To access service and page performance summary for a Framework application:
In Fusion Middleware Control Console, navigate to the home page for Framework applications.
See Section 6.3, "Navigating to the Home Page for Framework Applications".
From the Application Deployment menu, choose Performance Summary.
Use the Show Metric Palette button at the top of the Performance Summary page to display the Metric Palette. This palette enables you to select metrics for services that are up and running, and to review live performances of individual services in graphical and tabular formats.
Statistics become available when a service, application, or portlet is accessed for the first time. If a service is not configured or has never been used it will not appear in the performance summary graphs and tables.
In the Metric Palette, expand a service folder and select the metric checkboxes to view the service performance in graphical or tabular format.
Figure 38-29 shows the Performance Summary page and Metric Palette. In addition to WebCenter Portal performance metrics, the Metric Palette also displays general performance metrics associated with any J2EE application, for example, ADF Application Pool metrics. To display the help content for any metric, right-click the required directory or any metric in the directory and select Help.
Figure 38-29 WebCenter Portal: Framework Application - Performance Summary and Metric Palette
All diagnostic information related to startup and shutdown information, errors, warning messages, access information on HTTP requests, and additional information get stored in log files. To learn how to find information about the cause of an error and its corrective action, see the chapter "Managing Log Files and Diagnostic Data" in Oracle Fusion Middleware Administrator's Guide. To learn how to enable diagnostic logging to identify issues, see the section "Configuring Settings for Log Files" in Oracle Fusion Middleware Administrator's Guide.
For Spaces applications, the log file, WC_Spaces-diagnostic.log is stored in the DOMAIN_HOME/servers/WC_Spaces/logs directory.
For Framework applications, the log file is available in the DOMAIN_HOME/servers/ServerName/logs directory. The log file follows the naming convention of ServerName-diagnostic.log.
For example, for a managed server, WC_Custom, the logs will be stored in the DOMAIN_HOME/servers/WC_Custom/logs, and the log file name will be WC_Custom-diagnostic.log.
This section includes the following sub sections:
To view log messages for a Spaces application:
In Fusion Middleware Control Console, navigate to the home page for the Spaces application.
See Section 6.2, "Navigating to the Home Page for the Spaces Application".
From the WebCenter Portal menu, choose Logs > View Log Messages.
In the Log Messages page, search for warnings, errors, notifications, and so on.
To configure log files for Spaces:
In Fusion Middleware Control Console, navigate to the home page for the Spaces application.
See Section 6.2, "Navigating to the Home Page for the Spaces Application".
From the WebCenter Portal menu, choose Logs > Log Configuration.
In the Log Configuration page, in the Log Files tab, configure log settings.
For more information, see the section "Searching and Viewing Log Files" in Oracle Fusion Middleware Administrator's Guide.
To view log messages for Framework applications:
In Fusion Middleware Control Console, navigate to the home page for the Framework application.
See Section 6.3, "Navigating to the Home Page for Framework Applications".
From the Application Deployment menu, choose Logs > View Log Messages.
In the Log Messages page, search for warnings, errors, notifications, and so on.
To configure log files for Framework applications:
In Fusion Middleware Control Console, navigate to the home page for the Framework application.
See Section 6.3, "Navigating to the Home Page for Framework Applications".
From the Application Deployment menu, choose Logs > Log Configuration.
In the Log Configuration page, in the Log Files tab, configure log settings.
For more information, see the section "Searching and Viewing Log Files" in Oracle Fusion Middleware Administrator's Guide.
|
 Copyright © 2009, 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
