27 WebCenter

This chapter describes Oracle WebCenter metrics.

27.1 Response

This metric indicates the current status of the WebCenter application:

Up (Green Up Arrow) - The WebCenter application is up and running and the last operation was successful.

Down (Red Down Arrow) - The WebCenter application is not currently available. The last operation was unsuccessful due to an unexpected error or exception. User errors, such as an authentication failure, do not change the status to ‘Down’.

Unknown (Clock) - Unable to query the status of the WebCenter application for some reason.

27.1.1 UpDown Status

This metric indicates the current status of the WebCenter application:

Up (Green Up Arrow) - The WebCenter application is up and running and the last operation was successful.

Unknown (Clock) - Unable to query the status of the WebCenter application for some reason.

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version	Evaluation and Collection Frequency	Upload Frequency	Operator	Default Warning Threshold	Default Critical Threshold	Consecutive Number of Occurrences Preceding Notification	Alert Text
All Versions	Every Minute	After Every 60 Samples	=	Not Defined	0	1	The WebCenter Application is down

User Action

If you are having problems with the WebCenter application and the status is 'Down' or 'Unavailable', check the diagnostic logs to establish why the application is not up and running. The WebCenter application, and maybe the WebLogic server, must be restarted.

27.2 WebCenter Spaces (Aggregated)

Provides information about the WebCenter Spaces (Aggregated) metrics

27.2.1 Application Name

This metric identifies the WebCenter application to which these Space metrics apply.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

No action required.

27.2.2 Status

This metric indicates whether WebCenter Spaces is up or down. If the value is 1, the service is up. If the value is 0, it is down.

27.2.3 Successful Invocations (%)

This metric indicates the percentage of Space invocations that succeeded.

Successful Invocations (%) is equal to the number of successful invocations divided by the invocation count. All Spaces in the WebCenter application are included in this count. Processing time is available on application's main metric page.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If Successful Invocations (%) is below 100%, investigate this metric further. Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also, Analyzing Space Metrics.

You can also check the diagnostic logs to establish why Space invocations are failing.

27.2.4 Failed Invocations (%)

This metric indicates the percentage of Space invocations that failed.

Failed Invocations (%) is equal to the number of failed invocations divided by the invocation count. All Spaces in the WebCenter application are included in this count. Processing time is available on application's main metric page.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also, Analyzing Space Metrics.

You can also check the diagnostic logs to establish why Space invocations are failing.

27.2.5 Invocations (per minute)

This metric indicates the number of Space invocations per minute.

All Spaces in the WebCenter application are included in this count. The number of invocations per Space is available on application's Space metric page. See, Monitoring WebCenter Spaces Information.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to monitor minimum, typical, and peak usage, and to evaluate service performance under peak load conditions. You can use this information to assess whether additional resources or hardware are required for scalability.

If you are experiencing performance issues and the total number of invocations per minute for Spaces is high (compared with other WebCenter services), consider prioritizing troubleshooting efforts in this area.

See also, Analyzing Space Metrics.

27.2.6 Page Throughput (per minute)

This metric shows the average number of pages accessed per minute.

All Spaces in the WebCenter application are included in this count.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to monitor typical and peak usage of Spaces. You can evaluate when pages are accessed the most, as well as the maximum and minimum usage.

See also, Analyzing Space Metrics.

27.2.7 Average Page Processing Time (ms)

This metric indicates the average time (in ms) spent processing Space operations.

All Spaces in the WebCenter application are included in the count. Processing times for individual Spaces are available on application's main metric page. See, Monitoring WebCenter Spaces Information.

The last 10-15 minutes of data is used to calculate the average page processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to determine the performance of Space operations.

If this metric is out-of-bounds (the average time for Space operations is increasing or higher than expected), navigate to the application's metric pages where more detailed metric data for individual Spaces is available.

See also, Analyzing Space Metrics.

27.2.8 Service Name

These metrics apply to the WebCenter Space.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

No action required.

27.3 WebCenter Content Repositories (Aggregated)

Provides information about the WebCenter Content Repositories (Aggregated) metrics.

27.3.1 Application Name

This metric identifies the WebCenter application to which these content repository metrics apply.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

No action required.

27.3.2 Average Delete Time (ms)

This metric indicates the average time the Documents service spends deleting documents stored in all content repositories in this WebCenter application.

The last 10-15 minutes of data is used to calculate the average time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing metrics that are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Delete operation is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for individual operations is available. See, Viewing Performance Information.

27.3.3 Average Download Time (ms)

This metric indicates the average time the Documents service spends downloading documents from all content repositories in this WebCenter application.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Download operation is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for individual operations is available. See, Viewing Performance Information.

27.3.4 Average GetItem Time (ms)

This metric indicates the average time the Documents service spends selecting and displaying items, such as a document or image, in all content repositories in this WebCenter application.

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing metrics that are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Get Item operation is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for individual operations is available. See, Viewing Performance Information.

See also, Analyzing Content Repository Metrics.

27.3.5 Average ListFolder Time (ms)

This metric indicates the average time Content Presenter task flows spend listing folders stored in all content repositories in this WebCenter application.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the List Folder operation is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for individual operations is available. See, Viewing Performance Information.

27.3.6 Average Login Time (ms)

This metric indicates the average time spent logging in to content repositories (in ms).

All the content repositories used by the WebCenter application are included in this count.

The last 10-15 minutes of data is used to calculate the average login time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to determine the performance of the Login operation. If this metric is out-of-bounds (the average time to login is increasing or higher than expected), navigate to the application’s main metric page where more detailed metric data for the Login operation (and all other operations) is available. Use the information on this page to help determine the underlying cause of the time delay. See, Viewing Performance Information.

See also, Analyzing Content Repository Metrics.

27.3.7 Average Processing Time (ms)

This metric indicates the average time the Documents service spends processing content repository operations (in ms).

Content repository operations include: Download, Upload, Search, Login, Delete. Processing times for individual operations are available on the application's main metric page. See, Viewing Performance Information.

All the content repositories used by the WebCenter application are included in this count.

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for content repository operations is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for individual operations is available. See, Viewing Performance Information.

See also, Analyzing Content Repository Metrics.

27.3.8 Average Search Time (ms)

This indicates the average time the Documents service spends searching for documents stored in all content repositories in this WebCenter application.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Search operation is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for individual operations is available. See, Viewing Performance Information.

27.3.9 Average Upload Time (ms)

This indicates the average time the Documents service spends uploading documents to all content repositories in this WebCenter application.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Upload operation is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for individual operations is available. See, Viewing Performance Information.

27.3.10 Deletes (per minute)

This indicates total number of Delete operations the Documents service performs in a minute on all content repositories in this WebCenter application.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues, and the number of the Delete operation is high (compared with other services) consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See Viewing Performance Information.

27.3.11 Download (per minute)

This metric indicates total number of Download operations the Documents service performs in a minute on all content repositories in this WebCenter application.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues, and the number of the Download operation is high (compared with other services) consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See Viewing Performance Information.

27.3.12 GetItems (per minute)

This metric indicates the number of times, in a minute, an item such as a document or image, is selected or displayed in all content repositories in this WebCenter application.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing metrics that are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the number of the Get Item operation is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See Viewing Performance Information.

27.3.13 Invocations (per minute)

This metric indicates the total number of Documents service invocations per minute. All the content repositories used by this WebCenter application are included in this count.

Invocation rates and invocation counts for individual content repositories are available on application's main metric page. See, Viewing Performance Information.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of invocations per minute for the Documents service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Content Repository Metrics.

27.3.14 ListFolder (per minute)

This metric indicates the number of times folder content is displayed through Content Presenter task flows per minute, in all content repositories in this WebCenter application.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing metrics that are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the number of the List Folder operation is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See Viewing Performance Information.

See also, Analyzing Content Repository Metrics.

27.3.15 Logins (per minute)

This metric counts the number of times a WebCenter user logs in to a content repository per minute.

All the content repositories used by the WebCenter application are included in this count.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to monitor typical and peak usage of content repositories. You can evaluate when most logins occur, as well as the maximum and minimum usage--which can be useful for tuning content repository performance.

If you are experiencing performance issues outside normal peak login times, navigate to the application's main metric page where detailed metric data for all operations is available. See, Viewing Performance Information.

See also, Analyzing Content Repository Metrics.

27.3.16 Searches (per minute)

This metric indicates the number of times content is searched per minute in all content repositories in this WebCenter application.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing metrics that are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the number of the Search operation is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See Viewing Performance Information.

27.3.17 Status

This metric indicates whether the Documents service is up or down. If the value is 1, the service is up. If the value is 0, it is down

27.3.18 Successful Invocations (%)

This metric indicates the percentage of Documents service invocations that succeeded.

Successful Invocations (%) is equal to the number of successful invocations divided by the invocation count. All the content repositories used by the WebCenter application are included in this count.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If Successful Invocations (%) is below 100%, investigate this metric in more detail. Navigate to the application's main metric page where more detailed metric data for individual content repositories is also available. See, Viewing Performance Information.

See also, Analyzing Content Repository Metrics.

You can also check the diagnostic logs to establish why service requests are failing.

27.3.19 Failed Invocations (%)

This metric indicates the percentage of the Documents service invocations that failed.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also, Analyzing Content Repository Metrics.

27.3.20 Uploads (per minute)

This metric indicates the number of times the Documents service uploads documents in all content repositories in this WebCenter application per minute.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing metrics that are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the number of the Upload operation is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See Viewing Performance Information.

27.3.21 Service Name

These metrics apply to content repositories used by the Documents service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

No action required.

27.4 WebCenter Events (Aggregated)

Provides information about WebCenter Events (Aggregated).

27.4.1 Application Name

This metric identifies the WebCenter application to which the Events service metrics apply.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

No action required.

27.4.2 Average Create Time (ms)

This metric indicates the average time the Events service spends creating events in the WebCenter repository (in ms).

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Create operations is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Events Metrics.

27.4.3 Average Delete Time (ms)

This metric indicates the average time the Events service spends deleting events in a WebCenter repository (in ms).

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Delete operations is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Events Metrics.

27.4.4 Average List Time (ms)

This metric indicates the average time the Events service spends retrieving a list of events from the WebCenter repository (in ms).

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the List operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Events Metrics.

27.4.5 Average Processing Time (ms)

This metric indicates the average time the Events service spends processing events operations in a WebCenter repository (in ms).

Events service operations include: Create Event, Update Event, List Event, Delete Event, Search Event. Processing times for individual operations are available on application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to determine the performance of Events service operations. If this metric is out-of-bounds (the average time for Events operations is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Events Metrics.

27.4.6 Average Search Time (ms)

This metric indicates the average time the Events service spends searching for terms within event text in a WebCenter repository (in ms).

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Search operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Events Metrics.

27.4.7 Average Update Time (ms)

This metric indicates the average time the Events service spends updating events in the WebCenter repository (in ms).

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Update operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Events Metrics.

27.4.8 Creates (per minute)

This metric indicates the total number of Create operations per minute for the Events service for a WebCenter application.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Create operations per minute for the Events service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Events Metrics.

27.4.9 Deletes (per minute)

This metric indicates the total number of Delete operations per minute for the Events service for a WebCenter application.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Delete operations per minute for the Events service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Events Metrics.

27.4.10 Failed Invocations (%)

This metric indicates the percentage of Events service invocations that failed for a WebCenter application.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also, Analyzing Events Metrics.

27.4.11 Invocations (per minute)

This metric indicates the total number of invocations per minute for the Events service.

The number of invocations per operation is available on application's main metric page. See, Viewing Performance Information.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of invocations per minute for the Events service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Events Metrics.

27.4.12 Lists (per minute)

This metric indicates the total number of List operations per minute for the Events service for a WebCenter application.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of List operations per minute for the Events service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Events Metrics.

27.4.13 Searches (per minute)

This metric indicates the total number of Search operations per minute for the Events service for a WebCenter application.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Search operations per minute for the Events service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Events Metrics.

27.4.14 Status

This metric indicates whether the Events service is up or down. If the value is 1, the service is up. If the value is 0, it is down.

27.4.15 Successful Invocations (%)

This metric indicates the percentage of the Events service invocations that succeeded.

Successful Invocations (%) is equal to the number of successful invocations divided by the invocation count.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If Successful Invocations (%) is below 100%, investigate this metric further. Navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Events Metrics.

You can also check the diagnostic logs to establish why service requests are failing.

27.4.16 Updates (per minute)

This metric indicates the total number of Update operations per minute for the Events service for a WebCenter application.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Update operations per minute for the Events service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Events Metrics.

27.4.17 Service Name

These metrics apply to events used by the WebCenter application.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

No action required.

27.5 WebCenter External Applications (Aggregated)

Provides information about the WebCenter External Applications (Aggregated) metrics.

27.5.1 Application Name

This metric identifies the WebCenter application to which these external application metrics apply.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

No action required.

27.5.2 Automated Logins (per minute)

This metric indicates the total number of logins per minute -- when WebCenter users logs in to external applications using the automated login feature.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of automated logins per minute for external applications is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing External Application Metrics.

27.5.3 Average Automated Login Time (ms)

This metric indicates the average time spent logging WebCenter users to external applications using the automated login feature (in ms).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to determine the performance of the Login operation. If this metric is out-of-bounds (the average time to login is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for the Login operation (and all other operations) is available. Use the information on this page to help determine the underlying cause of the time delay. See, Viewing Performance Information.

See also, Analyzing External Application Metrics.

27.5.4 Average Fetch Credentials Time (ms)

This metric indicates the average time spent retrieving credentials for external applications (in ms).

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to determine the performance of the Fetch Credential operation. If this metric is out-of-bounds (the average time to fetch credentials is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for the Login operation (and all other operations) is available. Use the information on this page to help determine the underlying cause of the time delay. See, Viewing Performance Information.

See also, Analyzing External Application Metrics.

27.5.5 Average Fetch External Applications Time (ms)

This metric indicates the average time spent retrieving external applications (in ms).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to determine the performance of the Fetch External Application operation. If this metric is out-of-bounds (the average time to fetch credentials is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for the Login operation (and all other operations) is available. Use the information on this page to help determine the underlying cause of the time delay. See, Viewing Performance Information.

See also, Analyzing External Application Metrics.

27.5.6 Average Processing Time (ms)

This metric indicates the average time spent processing external application operations (in ms).

External application operations include: Fetch Credentials, Store Credentials, Fetch External Application, and Automated Logins. Processing times for individual operations are available on application's main metric page. See, Viewing Performance Information.

All external applications used by the WebCenter application are included in this count.

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to determine the overall external application performance. If this metric is out-of-bounds (the average time for external application operations is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing External Application Metrics.

27.5.7 Average Store Credentials Time (ms)

This metric indicates the average time spent storing user credentials for external applications (in ms).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to determine the performance of the Store Credential operation. If this metric is out-of-bounds (the average time to fetch credentials is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for the Login operation (and all other operations) is available. Use the information on this page to help determine the underlying cause of the time delay. See, Viewing Performance Information.

See also, Analyzing External Application Metrics.

27.5.8 Credential Fetches (per minute)

This metric indicates the total number of Fetch Credential operations per minute for external applications.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Fetch Credential operations per minute for external applications is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing External Application Metrics.

27.5.9 Credential Stores (per minute)

This metric indicates the total number of Store Credential operations per minute for external applications.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Store Credential operations per minute for external applications is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing External Application Metrics.

27.5.10 External Applications Fetches (per minute)

This metric indicates the total number of Fetch External Application operations per minute for external applications.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Fetch External Application operations per minute for external applications is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing External Application Metrics.

27.5.11 Failed Invocations (%)

This metric indicates the percentage of External Applications service invocations that failed.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also, Analyzing External Application Metrics.

27.5.12 Invocations (per minute)

This metric indicates the total number of external application invocations per minute.

All external applications used by this WebCenter application are included in this count. Invocation rates and invocation counts for individual external applications are available on application's main metric page.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to monitor minimum, typical, and peak usage, and to evaluate application performance under peak load conditions. You can use this information to assess whether additional resources or hardware are required for scalability.

If you are experiencing performance issues and the total number of invocations per minute for external applications is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing External Application Metrics.

27.5.13 Status

This metric indicates whether the External Applications service is up or down. If the value is 1, the service is up. If the value is 0, it is down.

27.5.14 Successful Invocations (%)

This metric indicates the percentage of external application invocations that succeeded.

Successful Invocations (%) is equal to the number of successful invocations divided by the invocation count. All the external applications accessed by the WebCenter application are included in this count.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If Successful Invocations (%) is below 100%, check the diagnostic logs to establish why service operations are failing. Typical examples are, trying to invoke the automated login servlet without being authenticated or specifying an incorrect external application name. Navigate to the application's main metric page where more detailed metric data for individual external applications is also available. See, Viewing Performance Information.

See also, Analyzing External Application Metrics.

27.5.15 Service Name

These metrics apply to the External Applications service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

No action required.

27.6 WebCenter Portlets (Aggregated)

Provides information about WebCenter Portlets (Aggregated) metrics.

27.6.1 Application Name

This metric identifies the WebCenter application to which these portlet metrics apply.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

No action required.

27.6.2 Failed Invocations (%)

This metric indicates the percentage of portlet invocations that failed.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also, Analyzing Portlet Metrics.

27.6.3 Average HTTP 2xx Time (ms)

This metric indicates the average time portlets take to process requests returning a HTTP2xx response code (in ms).

All portlets used in the WebCenter application are included in this count.

The last 10-15 minutes of data is used to calculate the average HTTP 2xx time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

See, Viewing Performance Information.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to track overall portlet performance.

If this metric is out-of-bounds, consider prioritizing troubleshooting efforts for the portlets. Navigate to the application's main metric page where additional metric data is available. See, Viewing Performance Information.

See also, Analyzing Portlet Metrics.

27.6.4 Average HTTP 3xx Time (ms)

This metric indicates the average time portlets take to process requests returning a HTTP3xx response code (in ms).

All portlets used in the WebCenter application are included in this count.

The last 10-15 minutes of data is used to calculate the average HTTP 3xx time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

See, Viewing Performance Information.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to track overall portlet performance.

See also, Analyzing Portlet Metrics.

27.6.5 Average HTTP 4xx Time (ms)

This metric indicates the average time portlets take to process requests returning a HTTP4xx response code (in ms).

All portlets used in the WebCenter application are included in this count.

The last 10-15 minutes of data is used to calculate the average HTTP 4xx time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

See, Viewing Performance Information.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to track overall portlet performance.

See also, Analyzing Portlet Metrics.

27.6.6 Average HTTP 5xx Time (ms)

This metric indicates the average time portlets take to process requests returning a HTTP 5xx response code (in ms).

All portlets used in the WebCenter application are included in this count.

The last 10-15 minutes of data is used to calculate the average HTTP 5xx time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

See, Viewing Performance Information.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to track overall portlet performance.

See also, Analyzing Portlet Metrics.

27.6.7 Average Processing Time (ms)

This metric indicates the average time spent processing portlet operations (in ms).

All portlets used in the WebCenter application are included in this count. Maximum processing times for individual HTTP request types are also available on the application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to determine the portlet performance. If this metric is out-of-bounds (the average time for portlet operations is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Portlet Metrics.

27.6.8 Average HTTP 2xx Requests (per minute)

This metric indicates total time portlets take to process requests returning a HTTP 2xx response code per minute.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of time taken (per minute) by portlets to process requests is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Portlet Metrics.

27.6.9 Average HTTP 3xx Requests (per minute)

This metric indicates total time portlets take to process requests returning a HTTP 3xx response code per minute.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Portlet Metrics.

27.6.10 Average HTTP 4xx Requests (per minute)

This metric indicates total time portlets take to process requests returning a HTTP 4xx response code per minute.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Portlet Metrics.

27.6.11 Average HTTP 5xx Requests (per minute)

This metric indicates total time portlets take to process requests returning a HTTP 5xx response code per minute.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Portlet Metrics.

27.6.12 Invocations (per minute)

This metric indicates the total number of portlet invocations per minute.

All portlets used in the WebCenter application are included in this count. The number of invocations is available on application's main metric page. See Viewing Performance Information.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to monitor minimum, typical, and peak usage, and to evaluate portlet performance under peak load conditions. You can use this information to assess whether additional resources or hardware are required for scalability.

If you are experiencing performance issues and the invocation rate for portlets is high (compared with other WebCenter services), consider prioritizing troubleshooting efforts in this area. Navigate to the application's main metric page where additional metric data is available. See Viewing Performance Information.

27.6.13 Status

This metric indicates whether portlets are up or down. If the value is 1, the service is up. If the value is 0, it is down.

27.6.14 Successful Invocations (%)

This metric indicates the percentage of portlet invocations that succeeded.

All portlets used in the WebCenter application are included in this count.

Any request that fails will impact this percentage. This includes WebCenter application-related failures such as timeouts and internal errors, as well as remote/server failures such as requests returned with response codes HTTP4xx or HTTP5xx, responses with a bad content type, and SOAP faults, where applicable. Maximum processing times for individual HTTP request types are also available on the application's main metric page. See, Viewing Performance Information.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If Successful Invocations (%) is below 100%, investigate the metric in more detail. Navigate to the application's main metric page where more detailed metric data is available. See Viewing Performance Information.

27.6.15 Service Name

These metrics apply to WebCenter portlets.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

No action required.

27.7 WebCenter Producers (Aggregated)

Provides information about WebCenter Producers (Aggregated) metrics.

27.7.1 Application Name

This metric identifies the WebCenter application to which these portlet producer metrics apply.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

No action required.

27.7.2 Average HTTP 2xx Time (ms)

This metric indicates the average time that all portlets used in the WebCenter application take to process requests returning a HTTP 2xx response code (in ms).

See, Viewing Performance Information.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to track the overall performance of producers in the WebCenter application.

If this metric is out-of-bounds, consider prioritizing troubleshooting efforts for the producers. Navigate to the application's main metric page where additional metric data is available. See, Viewing Performance Information.

See, Analyzing Portlet Producer Metrics.

27.7.3 Average HTTP 3xx Time (ms)

This metric indicates the average time that all portlets used in the WebCenter application take to process requests returning a HTTP 3xx response code (in ms).

See, Viewing Performance Information.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to track the overall performance of producers in the WebCenter application.

See, Analyzing Portlet Producer Metrics.

27.7.4 Average HTTP 4xx Time (ms)

This metric indicates the average time that all portlets used in the WebCenter application take to process requests returning a HTTP 4xx response code (in ms).

See, Viewing Performance Information.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to track the overall performance of producers in the WebCenter application.

See, Analyzing Portlet Producer Metrics.

27.7.5 Average HTTP 5xx Time (ms)

This metric indicates the average time that all portlets used in the WebCenter application take to process requests returning a HTTP 5xx response code (in ms).

See, Viewing Performance Information.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to track the overall performance of producers in the WebCenter application.

See, Analyzing Portlet Producer Metrics.

27.7.6 Average Processing Time (ms)

This metric indicates the average time spent processing portlet producer operations (in ms).

All portlet producers used in the WebCenter application are included in this count. Maximum processing times for individual HTTP request types are also available on the application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to determine the portlet producer performance. If this metric is out-of-bounds (the average time for producer operations is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also Analyzing Portlet Producer Metrics.

27.7.7 Failed Invocations (%)

This metric indicates the percentage of producers invocations that failed.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also Analyzing Portlet Producer Metrics.

27.7.8 Average HTTP 2xx Requests (per minute)

This metric indicates total time (per minute) that all portlets used in the WebCenter application take to process requests returning a HTTP 2xx response code.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Portlet Producer Metrics.

27.7.9 Average HTTP 3xx Requests (per minute)

This metric indicates total time (per minute) that all portlets used in the WebCenter application take to process requests returning a HTTP 3xx response code.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Portlet Producer Metrics.

27.7.10 Average HTTP 4xx Requests (per minute)

This metric indicates total time (per minute) that all portlets used in the WebCenter application take to process requests returning a HTTP 4xx response code.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Portlet Producer Metrics.

27.7.11 Average HTTP 5xx Requests (per minute)

This metric indicates total time (per minute) that all portlets used in the WebCenter application take to process requests returning a HTTP 5xx response code.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Portlet Producer Metrics.

27.7.12 Invocations (per minute)

This metric indicates the total number of producer invocations per minute.

All portlet producers used in the WebCenter application are included in this count. The number of invocations is available on application's main metric page. See, Viewing Performance Information.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to monitor minimum, typical, and peak usage, and to evaluate producer performance under peak load conditions. You can use this information to assess whether additional resources or hardware are required for scalability.

If you are experiencing performance issues and the invocation rate for producers is high (compared with other WebCenter services), consider prioritizing troubleshooting efforts in this area. Navigate to the application's main metric page where additional metric data is available. See, Viewing Performance Information.

See also, Analyzing Portlet Producer Metrics.

27.7.13 Status

This metric indicates whether producers are up or down. If the value is 1, the service is up. If the value is 0, it is down.

27.7.14 Successful Invocations (%)

This metric indicates the percentage of producer invocations that succeeded.

Successful Invocations (%) is equal to the number of successful invocations divided by the invocation count. All portlet producers used in the WebCenter application are included in this count.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

You can also check the diagnostic logs to establish why producer requests are failing.

If Successful Invocations (%) is below 100%), investigate the metric in more detail. Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Portlet Producer Metrics.

27.7.15 Service Name

These metrics apply to the portlet producers used by the WebCenter application.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

No action required.

27.8 WebCenter Search (Aggregated)

Provides information about WebCenter Search (Aggregated) metrics.

27.8.1 Application Name

This metric identifies the WebCenter application to which these Search service metrics apply.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

No action required.

27.8.2 Average Processing Time (ms)

This metric indicates the average time (in ms) the Search service spends processing search operations.

All WebCenter search sources are included in the count: Announcements, Documents, Discussion Forums, Spaces, Events, Lists, Notes, Oracle Secure Enterprise Search, Pages, People Connections, Wikis and Blogs, and Tagged Items. Processing times for individual search sources are available on the application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to determine the performance of Search service operations.

If this metric is out-of-bounds (the average time for search operations is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for individual search sources is available. See, Viewing Performance Information.

See also, Analyzing Search Metrics.

27.8.3 Failed Invocations (%)

This metric indicates the percentage of Search service invocations that failed.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also, Analyzing Search Metrics.

27.8.4 Invocations (per minute)

This metric indicates the total number of Search service invocations per minute across all WebCenter search sources: Announcements, Documents, Discussion Forums, Spaces, Events, Links, Lists, Notes, Oracle Secure Enterprise Search, Pages, People Connections, Wikis and Blogs, and Tagged Items.

Invocation rates and invocation counts for individual search sources are available on application's main metric page. See, Viewing Performance Information.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of invocations per minute for the Search service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Search Metrics.

27.8.5 Status

This metric indicates whether the Search service is up or down. If the value is 1, the service is up. If the value is 0, it is down

27.8.6 Successful Invocations (%)

This metric indicates the percentage of Search service invocations that succeeded.

Successful Invocations (%) is equal to the number of successful invocations divided by the invocation count. All WebCenter search sources are included in the count: Announcements, Documents, Discussion Forums, Spaces, Events, Lists, Notes, Oracle Secure Enterprise Search, Pages, People Connections, Wikis and Blogs, and Tagged Items.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If Successful Invocations (%) is below 100%, investigate the metric in more detail. Navigate to the application's main metric page where more detailed metric data for individual search sources is available. See, Viewing Performance Information.

See also, Analyzing Search Metrics.

You can also check the diagnostic logs to establish why search requests are failing.

27.8.7 Service Name

These metrics apply to the Search service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

No action required.

27.9 WebCenter Services

Provides information about WebCenter Services metrics.

27.9.1 Application Name

This metric identifies the WebCenter application to which these WebCenter service metrics apply.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

No action required.

27.9.2 Average Processing Time (ms)

This metric indicates the average time spent processing operations for this WebCenter service (in ms).

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to determine the performance of WebCenter services. If this metric is out-of-bounds (the average time for operations is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Understanding WebCenter Performance Metrics Information.

27.9.3 Failed Invocations (%)

This metric indicates the percentage of services invocations that failed.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See, Understanding WebCenter Performance Metrics Information.

27.9.4 Invocations (per minute)

This metric indicates the total number of invocations per minute for this WebCenter service. The number of invocations is available on application's main metric page. See, Viewing Performance Information.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the invocation rate for this WebCenter service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

See, Understanding WebCenter Performance Metrics Information.

27.9.5 Status

This metric indicates whether a specific service is up or down. If the value is 1, the service is up. If the value is 0, it is down

27.9.6 Successful Invocations (%)

This metric indicates the percentage of invocations that succeeded for this WebCenter service. Any operation or request that fails will impact this percentage.

Successful Invocations (%) is equal to the number of successful invocations divided by the invocation count.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If Successful Invocations (%) is below 100%, investigate this metric. Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Understanding WebCenter Performance Metrics Information.

You can also check the diagnostic logs to establish why service requests are failing.

27.10 WebCenter BPEL Worklists (Aggregated)

Provides information about WebCenter BPEL Worklists (Aggregated) metrics.

27.10.1 Application Name

This metric identifies the WebCenter application to which these Worklists service metrics apply.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

No action required.

27.10.2 Average Processing Time (ms)

This metric indicates the average time the Worklists service spends processing operations (in ms).

All the BPEL worklists used by the WebCenter application are included in this count. Processing times for individual worklists are available on application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to determine the performance of Worklists service operations. If this metric is out-of-bounds (the average time for worklist operations is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Worklist Metrics.

27.10.3 Failed Invocations (%)

This metric indicates the percentage of Worklists service invocations that failed.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also, Analyzing Worklist Metrics.

27.10.4 Invocations (per minute)

This metric indicates the total number of Worklists service invocations per minute.

All the BPEL worklists used by the WebCenter application are included in this count. Invocation rates and invocation counts for individual worklists are available on application's main metric page. See, Viewing Performance Information.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of invocations per minute for the Worklists service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Worklist Metrics.

27.10.5 Status

This metric indicates whether the Worklists service is up or down. If the value is 1, the service is up. If the value is 0, it is down

27.10.6 Successful Invocations (%)

This metric indicates the percentage of Worklists service invocations that succeeded.

Successful Invocations (%) is equal to the number of successful invocations divided by the invocation count. All the BPEL worklists used by the WebCenter application are included in this count.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If Successful Invocations (%) is below 100%, investigate this metric in more detail. Navigate to the application's main metric page where more detailed metric data for individual worklists is also available. See, Viewing Performance Information.

See also, Analyzing Worklist Metrics.

You can also check the diagnostic logs to establish why service requests are failing.

27.10.7 Service Name

These metrics apply to the Worklists service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

No action required.

27.11 WebCenter Portlets

Provides information about WebCenter Portlet metrics.

27.11.1 Application Name

This metric identifies the WebCenter application to which these portlet metrics apply.

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All versions	Every 300 seconds

27.11.2 Average HTTP 2xx Time (ms)

This metric indicates the average time the portlet takes to process requests returning a HTTP 2xx response code (in ms).

See, Viewing Performance Information.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to detect the most performant portlets. If you use this metric in conjunction with the Invocations (per minute) metric, then you can identify the top performing portlet.

See, Viewing Performance Information.

See also, Analyzing Portlet Metrics.

27.11.3 Average HTTP 3xx Time (ms)

This metric indicates the average time the portlet takes to process requests returning a HTTP 3xx response code (in ms).

See, Viewing Performance Information.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to detect the most performant portlets. If you use this metric in conjunction with the Invocations (per minute) metric, then you can identify the top performing portlet.

See, Viewing Performance Information.

See also, Analyzing Portlet Metrics.

27.11.4 Average HTTP 4xx Time (ms)

This metric indicates the average time the portlet takes to process requests returning a HTTP 4xx response code (in ms).

See, Viewing Performance Information.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to detect the most performant portlets. If you use this metric in conjunction with the Invocations (per minute) metric, then you can identify the top performing portlet.

See, Viewing Performance Information.

See also, Analyzing Portlet Metrics.

27.11.5 Average HTTP 5xx Time (ms)

This metric indicates the average time the portlet takes to process requests returning a HTTP 5xx response code (in ms).

See, Viewing Performance Information.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to detect the most performant portlets. If you use this metric in conjunction with the Invocations (per minute) metric, then you can identify the top performing portlet.

See, Viewing Performance Information.

See also, Analyzing Portlet Metrics.

27.11.6 Average Processing Time (ms)

This metric indicates the average time spent processing portlet requests (in ms). Maximum processing times for individual HTTP request types are also available on the application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to determine portlet performance. If this metric is out-of-bounds (the average time for portlet operations is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Portlet Metrics.

27.11.7 Failed Invocations (%)

This metric indicates the percentage of portlet invocations that failed.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also, Analyzing Portlet Metrics.

27.11.8 Average HTTP 2xx Requests (per minute)

This metric indicates total time the portlet takes to process requests returning a HTTP 2xx response code per minute.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of time taken (per minute) by this portlet to process requests is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Portlet Metrics.

27.11.9 Average HTTP 3xx Requests (per minute)

This metric indicates total time the portlet takes to process requests returning a HTTP 3xx response code per minute.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Portlet Metrics.

27.11.10 Average HTTP 4xx Requests (per minute)

This metric indicates total time the portlet takes to process requests returning a HTTP 4xx response code per minute.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Portlet Metrics.

27.11.11 Average HTTP 5xx Requests (per minute)

This metric indicates total time the portlet takes to process requests returning a HTTP 5xx response code per minute.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Portlet Metrics.

27.11.12 Invocations (per minute)

This metric indicates the total number of invocations per minute for a portlet. The number of invocations is available on application's main metric page. See, Viewing Performance Information.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the invocation rate for the portlet is high (compared with other portlets), consider prioritizing troubleshooting efforts in this area. Navigate to the application's main metric page where additional metric data is available. See, Viewing Performance Information.

See also, Analyzing Portlet Metrics.

27.11.13 Status

This metric indicates whether portlets are up or down. If the value is 1, the service is up. If the value is 0, it is down.

27.11.14 Successful Invocations (%)

This metric indicates the percentage of portlet invocations that succeeded.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If Successful Invocations (%) is below 100%, investigate this metric in more detail. Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

You can also check the diagnostic logs to establish why portlet requests are failing.

27.11.15 Producer Type

The portlet producer type: Web or WSRP

Web portlet producer - deployed to a J2EE application server, which is often remote and communicates through Simple Object Access Protocol (SOAP) over HTTP.

WSRP portlet producer - Web Services for Remote Portlets (WSRP) is a Web services standard that allows interoperability between a standards enabled container and a WSRP client application.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

No action required.

27.12 WebCenter Producers

Provides information about the WebCenter Producers metrics.

27.12.1 Application Name

This metric identifies the WebCenter application to which these portlet producer metrics apply.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

No action required.

27.12.2 Average HTTP 2xx Time (ms)

This metric indicates the average time that all portlets from this producer take to process requests returning a HTTP 2xx response code (in ms).

See, Viewing Performance Information.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to detect the most performant producers. If you use this metric in conjunction with the Invocations (per minute) metric, then you can identify the top-performing producer.

See, Viewing Performance Information.

See also, Analyzing Portlet Producer Metrics.

27.12.3 Average HTTP 3xx Time (ms)

This metric indicates the average time that all portlets from this producer take to process requests returning a HTTP 3xx response code (in ms).

See, Viewing Performance Information.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to detect the most performant producers. If you use this metric in conjunction with the Invocations (per minute) metric, then you can identify the top-performing producer.

See, Viewing Performance Information.

See also, Analyzing Portlet Producer Metrics.

27.12.4 Average HTTP 4xx Time (ms)

This metric indicates the average time that all portlets from this producer take to process requests returning a HTTP 4xx response code (in ms).

See, Viewing Performance Information.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to detect the most performant producers. If you use this metric in conjunction with the Invocations (per minute) metric, then you can identify the top-performing producer.

See, Viewing Performance Information.

See also, Analyzing Portlet Producer Metrics.

27.12.5 Average HTTP 5xx Time (ms)

This metric indicates the average time that all portlets from this producer take to process requests returning a HTTP 5xx response code (in ms).

See, Viewing Performance Information.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to detect the most performant producers. If you use this metric in conjunction with the Invocations (per minute) metric, then you can identify the top-performing producer.

See, Viewing Performance Information.

See also, Analyzing Portlet Producer Metrics.

27.12.6 Average Processing Time (ms)

This metric indicates the average time spent processing operations for a particular portlet producer (in ms). Maximum processing times for individual HTTP request types are also available on the application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to determine the performance of portlet producers. If this metric is out-of-bounds (the average time for producer operations is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Portlet Producer Metrics.

27.12.7 Failed Invocations (%)

This metric indicates the percentage of producer invocations that failed.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also, Analyzing Portlet Producer Metrics.

27.12.8 Average HTTP 2xx Requests (per minute)

This metric indicates total time (per minute) that all portlets in this producer take to process requests returning a HTTP 2xx response code.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Portlet Producer Metrics.

27.12.9 Average HTTP 3xx Requests (per minute)

This metric indicates total time (per minute) that all portlets in this producer take to process requests returning a HTTP 3xx response code.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Portlet Producer Metrics.

27.12.10 Average HTTP 4xx Requests (per minute)

This metric indicates total time (per minute) that all portlets in this producer take to process requests returning a HTTP 4xx response code.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Portlet Producer Metrics.

27.12.11 Average HTTP 5xx Requests (per minute)

This metric indicates total time (per minute) that all portlets in this producer take to process requests returning a HTTP 5xx response code.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Portlet Producer Metrics.

27.12.12 Invocations (per minute)

This metric indicates the total number of invocations per minute for a producer. The number of invocations is available on application's main metric page. See, Viewing Performance Information.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the invocation rate for the producer is high (compared with other producers), consider prioritizing troubleshooting efforts in this area. Navigate to the application's main metric page where additional metric data is available. See, Viewing Performance Information.

See, Analyzing Portlet Producer Metrics.

27.12.13 Status

This metric indicates whether producers are up or down. If the value is 1, the service is up. If the value is 0, it is down.

27.12.14 Successful Invocations (%)

This metric indicates the percentage of portlet invocations that succeeded for this producer.

Successful Invocations (%) is equal to the number of successful invocations divided by the invocation count.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

See also, Analyzing Portlet Producer Metrics.

You can also check the diagnostic logs to establish why producer requests are failing.

27.12.15 Producer Type

The portlet producer type: Web or WSRP

Web portlet producer - deployed to a J2EE application server, which is often remote and communicates through Simple Object Access Protocol (SOAP) over HTTP.

WSRP portlet producer - Web Services for Remote Portlets (WSRP) is a Web services standard that allows interoperability between a standards enabled container and a WSRP client application.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

No action required.

27.13 WebCenter Announcements

Provides information about the WebCenter Announcements metrics.

27.13.1 Application Name

This metric identifies the WebCenter application to which these Announcements service metrics apply.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

No action required.

27.13.2 Average Create Time (ms)

This metric indicates the average time the Announcements service spends creating announcements (in ms).

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Create operation is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for individual operations is available. See, Viewing Performance Information.

See also, Analyzing Announcement Metrics.

27.13.3 Average List Time (ms)

This metric indicates the average time the Announcements service spends retrieving a list of announcements (in ms).

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the List operation is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for individual operations is available. See, Viewing Performance Information.

See also, Analyzing Announcement Metrics.

27.13.4 Average Login Time (ms)

This metric indicates the average time spent logging in to the back-end discussions server hosting announcements (in ms).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to determine the performance of the Login operation. If this metric is out-of-bounds (the average time to login is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for the Login operation (and all other operations) is available. Use the information on this page to help to determine the underlying cause of the time delay. See, Viewing Performance Information.

See also, Analyzing Announcement Metrics.

27.13.5 Average Logout Time (ms)

This metric indicates the average time spent logging out from the back-end discussions server hosting announcements (in ms).

The last 10-15 minutes of data is used to calculate the average logout time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to determine the performance of the Logout operation. If this metric is out-of-bounds (the average time to logout is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for the Login operation (and all other operations) is available. Use the information on this page to help to determine the underlying cause of the time delay. See, Viewing Performance Information.

See also, Analyzing Announcement Metrics.

27.13.6 Average Processing Time (ms)

This metric indicates the average time the Announcements service spends processing announcement operations (in ms).

Announcement operations include: Create, List, Search, Login, Logout. Processing times for individual operations are available on the application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to determine the performance of Announcements service operations.

If this metric is out-of-bounds (the average time for announcement operations is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for individual operations is available. See, Viewing Performance Information.

See also, Analyzing Announcement Metrics.

27.13.7 Average Search Time (ms)

This metric indicates the average time the Announcements service spends searching for terms within announcement text (in ms).

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

See also, Analyzing Announcement Metrics.

27.13.8 Creates (per minute)

This metric indicates the total number of Create operations the Announcements service performs per minute.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Create operations per minute for the Announcements service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Announcement Metrics.

27.13.9 Failed Invocations (%)

This metric indicates the percentage of Announcements service invocations that failed.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also, Analyzing Announcement Metrics.

27.13.10 Invocations (per minute)

This metric indicates the total number of Announcements service invocations per minute.

The number of invocations per operation is available on application's main metric page. See, Viewing Performance Information.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of invocations per minute for the Announcements service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Announcement Metrics.

27.13.11 Lists (per minute)

This metric indicates the total number of List operations the Announcements service performs per minute.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of the List operation per minute for the Announcements service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Announcement Metrics.

27.13.12 Logins (per minute)

This metric counts the number of times per minute a WebCenter user logs in to the back-end discussions server hosting announcements.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to monitor typical and peak usage of the Announcements service. You can evaluate when most logins occur, as well as the maximum and minimum usage-- which can be useful for tuning discussion server performance.

See also, Analyzing Announcement Metrics.

27.13.13 Logouts (per minute)

This metric counts the number of times per minute a WebCenter user logs out from the back-end discussions server hosting announcements.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to monitor typical and peak usage of the Announcements service. You can evaluate when most logouts occur, as well as the maximum and minimum usage-- which can be useful for tuning discussion server performance.

See also, Analyzing Announcement Metrics.

27.13.14 Searches (per minute)

This metric indicates the total number of Search operations the Announcements service performs per minute.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Search operations per minute for the Announcements service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Announcement Metrics.

27.13.15 Status

This metric indicates whether the Announcements service are up or down. If the value is 1, the service is up. If the value is 0, it is down.

27.13.16 Successful Invocations (%)

This metric indicates the percentage of Announcements service invocations that succeeded.

Successful Invocations (%) is equal to the number of successful invocations divided by the invocation count.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If Successful Invocations (%) is below 100%, investigate this metric in more detail. Navigate to the application's main metric page where more detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Announcement Metrics.

You can also check the diagnostic logs to establish why service requests are failing.

27.13.17 Service Name

These metrics apply to the Announcements service.

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

No action required.

27.14 WebCenter Spaces

Provides information about WebCenter Spaces metrics.

27.14.1 Application Name

The application name

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

No action required.

27.14.2 Failed Invocations (%)

This metric indicates the percentage of Space invocations that failed.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also, Analyzing Space Metrics.

27.14.3 Successful Invocations (%)

This metric indicates the percentage of Space invocations that succeeded. Processing time is available on application's main metric page.

Successful Invocations (%) is equal to the number of successful invocations divided by the invocation count.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If Successful Invocations (%) is below 100% investigate this metric in more detail. Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

27.14.4 Invocations (per minute)

This metric indicates the number of Space invocations per minute.

The number of invocations for this Space is available on application's Space metric page. See, Monitoring WebCenter Spaces Information.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of invocations per minute for this Space is high (compared with other Spaces), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

27.14.5 Page Throughput (per minute)

This metric shows the average number of pages accessed per minute for the Space.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to monitor typical and peak usage of the Space. You can evaluate when pages are accessed the most, as well as the maximum and minimum usage.

See also, Analyzing Space Metrics.

27.14.6 Errors (per minute)

This metric shows the average number of errors that occur per minute in the Space.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If this metric is out-of-bounds (the average number of errors is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also, Analyzing Space Metrics.

27.14.7 Average Page Processing Time (ms)

This metric indicates the average time spent processing operations for a particular Space (in ms).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to determine the performance of a Space.

If this metric is out-of-bounds (the average time for Space operations is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also, Analyzing Space Metrics.

27.15 WebCenter Content Repositories

Provides information about WebCenter Content Repository metrics.

27.15.1 Application Name

This metric identifies the WebCenter application to which these content repository metrics apply.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

No action required.

27.15.2 Average Delete Time (ms)

This metric indicates the average time the Documents service spends deleting documents stored in a content repository.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

27.15.3 Average Download Time (ms)

This metric indicates the average time the Documents service spends downloading documents from a content repository.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

27.15.4 Average Get Item Time (ms)

This metric indicates the average time spent selecting and displaying items, such as a document or image, in Content Presenter task flows.

User Action

27.15.5 Average List Folder Time (ms)

This metric indicates the average time Content Presenter task flows spend listing folders stored in a content repository.

User Action

If this metric is out-of-bounds (the average time for the List folder operation is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for individual operations is available. See Viewing Performance Information.

27.15.6 Average Login Time (ms)

This metric indicates the average time spent logging in to the content repository (in ms).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to determine the performance of the Login operation. If this metric is out-of-bounds (the average time to login is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for the Login operation (and all other operations) is available. Use the information on this page to help determine the underlying cause of the time delay. See, Viewing Performance Information.

See also, Analyzing Content Repository Metrics.

27.15.7 Average Processing Time (ms)

This metric indicates the average time the Documents service spends processing operations relating to this content repository (in ms).

Content repository operations include: Download, Upload, Login, Delete. Processing times for individual operations are available on the application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to determine the performance of Document service operations, for this content repository.

See also, Analyzing Content Repository Metrics.

27.15.8 Average Search Time (ms)

This indicates the average time the Documents service spends searching for documents stored in a content repository.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

27.15.9 Average Upload Time (ms)

This indicates the average time the Documents service spends uploading documents to a content repository.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

27.15.10 Deletes (per minute)

This indicates total number of Delete operations the Documents service performs in a minute on a content repository.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues, and the number of Delete operations is high (compared with other services) consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See Viewing Performance Information.

27.15.11 Downloads (per minute)

This metric indicates total number of Download operations the Documents service performs in a minute on a content repository.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues, and the number of Download operations is high (compared with other services) consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See Viewing Performance Information.

27.15.12 Download Throughput (bytes per second)

This metric shows the average download speed per second.

All content repositories in the WebCenter application are included in this count.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to monitor typical and peak download time. You can evaluate when information is downloaded the most, as well as the maximum and minimum downloads.

27.15.13 Failed Invocations (%)

This metric indicates the percentage of the Documents service invocations that failed.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

27.15.14 Get Item

This metric indicates the number of times an item, such as a document or image, is selected or displayed in Content Presenter task flows.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing metrics that are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

User Action

If you are experiencing performance issues and the number of Get Item operations is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See Viewing Performance Information.

27.15.15 Invocations (per minute)

This metric indicates the total number of Documents service invocations per minute for this content repository.

The number of invocations per operation is available on the application's main metric page. See, Viewing Performance Information.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of invocations per minute for this content repository is high (compared with other content repositories), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Content Repository Metrics.

27.15.16 List Folder

This metric indicates the number of times folder content is displayed through Content Presenter task flows.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing metrics that are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

User Action

If you are experiencing performance issues and the number of List Folder operations is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See Viewing Performance Information.

27.15.17 Logins (per minute)

This metric counts the number of times a WebCenter user logs in to the content repository per minute.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to monitor typical and peak usage of the content repository. You can evaluate when most logins occur, as well as the maximum and minimum usage--which can be useful for tuning content repository performance.

See also, Analyzing Content Repository Metrics.

27.15.18 Searches (per minute)

This metric indicates the number of times content is searched per minute in a content repository.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing metrics that are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the number of Search operations is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See Viewing Performance Information.

27.15.19 Status

This metric indicates whether the Documents service is up or down. If the value is 1, the service is up. If the value is 0, it is down.

27.15.20 Successful Invocations (%)

This metric indicates the percentage of Documents service invocations that succeeded for this content repository.

Successful Invocations (%) is equal to the number of successful invocations divided by the invocation count.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If Successful Invocations (%) is below 100%, investigate this metric in more detail. Navigate to the application's main metric page where more detailed metric data for individual operations is available. See, Viewing Performance Information.

See also, Analyzing Content Repository Metrics.

You can also check the diagnostic logs to establish why service requests are failing.

27.15.21 Uploads (per minute)

This metric indicates the number of times the Documents service uploads documents in a content repository per minute.

The last 10-15 minutes of data is used to calculate this metric. If 10-15 minutes of data is not yet available, the metric is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing metrics that are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the number of Upload operations is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See Viewing Performance Information.

27.15.22 Upload Throughput (bytes per second)

This metric shows the average upload speed per second.

All content repositories in the WebCenter application are included in this count.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to monitor typical and peak upload time. You can evaluate when information is uploaded the most, as well as the maximum and minimum uploads.

27.16 WebCenter Events

Provides information about the WebCenter events metrics.

27.16.1 Application Name

This metric identifies the WebCenter application to which the Events service metrics apply.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

No action required.

27.16.2 Average Create Time (ms)

This metric indicates the average time the Events service spends creating an event in the WebCenter repository (in ms).

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for Create operations is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Events Metrics.

27.16.3 Average Delete Time (ms)

This metric indicates the average time the Events service spends deleting events in a WebCenter repository (in ms).

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for Delete operations is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Events Metrics.

27.16.4 Average List Time (ms)

This metric indicates the average time the Events service spends retrieving a list of events from the WebCenter repository (in ms).

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for List operations is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Events Metrics.

27.16.5 Average Processing Time (ms)

This metric indicates the average time the Events service spends processing operations (in ms) associated with events.

Events operations include: Create Event, Update Event, List Event, Delete Event, Search Event. Processing times for individual operations are available on the application's main metric page for events. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate the average processing time. If 10- 15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

See also, Analyzing Events Metrics.

27.16.6 Average Search Time (ms)

This metric indicates the average time the Events service spends searching for terms within event text (in ms).

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for Search operations is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Events Metrics.

27.16.7 Average Update Time (ms)

This metric indicates the average time the Events service spends updating events in the WebCenter repository (in ms).

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for Update operations is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Events Metrics.

27.16.8 Creates (per minute)

This metric indicates the total number of Create operations per minute for the Events service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Events Metrics.

27.16.9 Deletes (per minute)

This metric indicates the total number of Delete operations per minute for the Events service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Events Metrics.

27.16.10 Failed Invocations (%)

This metric indicates the percentage of Events service invocations that failed.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also, Analyzing Events Metrics.

27.16.11 Invocations (per minute)

This metric indicates the total number of invocations per minute for the Events service.

The number of invocations per operation for events is available on the application's main metric page. See, Viewing Performance Information.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Events Metrics.

27.16.12 Lists (per minute)

This metric indicates the total number of List operations per minute for the Events service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Events Metrics.

27.16.13 Searches (per minute)

This metric indicates the total number of Search operations per minute for the Events service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Events Metrics.

27.16.14 Status

This metric indicates whether the Events service up or down. If the value is 1, the service is up. If the value is 0, it is down.

27.16.15 Successful Invocations (%)

This metric indicates the percentage of Events service invocations that succeeded.

Successful Invocations (%) is equal to the number of successful invocations divided by the invocation count.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

See also, Analyzing Events Metrics.

27.16.16 Updates (per minute)

This metric indicates the total number of Update operations per minute for the Events service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Events Metrics.

27.17 WebCenter External Applications Connections

Provides information about WebCenter External Applications metrics.

27.17.1 Application Name

This metric identifies the WebCenter application to which these External Application metrics apply.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

No action required.

27.17.2 Invocations (per minute)

This metric indicates the total number of times per minute a single external application was accessed.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of invocations per minute for this external application is high (compared with other external applications), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See, Analyzing External Application Metrics.

27.18 WebCenter External Applications

Provides information about the WebCenter external applications metrics.

27.18.1 Application Name

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

27.18.2 Automated Logins (per minute)

This metric indicates the total number of logins per minute -- when WebCenter users logs in to an external application using the automated login feature.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of automated logins per minute for the external application is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing External Application Metrics.

27.18.3 Average Automated Login Time (ms)

This metric indicates the average time spent logging WebCenter users to an external application using the automated login feature (in ms).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to determine the performance of the Login operation. If this metric is out-of-bounds (the average time to login is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for the Login operation (and all other operations) is available. Use the information on this page to help determine the underlying cause of the time delay. See, Viewing Performance Information.

See also, Analyzing External Application Metrics.

27.18.4 Average Fetch Credential Time (ms)

This metric indicates the average time spent retrieving credentials for an external application (in ms).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

See also, Analyzing External Application Metrics.

27.18.5 Average Fetch External Application Time (ms)

This metric indicates the average time spent retrieving an external application (in ms).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

See also, Analyzing External Application Metrics.

27.18.6 Average Processing Time (ms)

This metric indicates the average time spent processing external application operations (in ms).

All external applications used by the WebCenter application are included in this count.

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

See also, Analyzing External Application Metrics.

27.18.7 Average Store Credentials Time (ms)

This metric indicates the average time spent storing user credentials for an external application (in ms).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

See also, Analyzing External Application Metrics.

27.18.8 Credential Fetches (per minute)

This metric indicates the total number of Fetch Credential operations per minute for an external application.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Fetch Credential operations per minute for an external application is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing External Application Metrics.

27.18.9 Credential Stores (per minute)

This metric indicates the total number of Store Credential operations per minute for an external application.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Store Credential operations per minute for an external application is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing External Application Metrics.

27.18.10 External Application Fetches (per minute)

This metric indicates the total number of Fetch External Application operations per minute for an external application.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Fetch External Application operations per minute for an external application is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing External Application Metrics.

27.18.11 Failed Invocations (%)

This metric indicates the percentage of External Applications service invocations that failed.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also, Analyzing External Application Metrics.

27.18.12 Invocations (per minute)

This metric indicates the total number of times per minute a single external application was accessed.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See, Analyzing External Application Metrics.

27.18.13 Status

This metric indicates whether the External Applications service is up or down. If the value is 1, the service is up. If the value is 0, it is down.

27.18.14 Successful Invocations (%)

This metric indicates the percentage of external application invocations that succeeded.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

See also, Analyzing External Application Metrics.

27.18.15 Name

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

27.19 WebCenter Discussion Forum

Provides information about the WebCenter Discussion forum metrics.

27.19.1 Application Name

This metric identifies the WebCenter application to which these Discussions service metrics apply.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

No action required.

27.19.2 Average Create Forum Time (ms)

This metric indicates the average time the Discussions service spends creating a discussion forum in the discussions server, under a specific category (in ms).

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for Create Forum operations is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Discussions Metrics.

27.19.3 Average Create Topic Time (ms)

This metric indicates the average time the Discussions service spends creating a discussion topic in the discussions server, under a specific forum (in ms).

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for Create Topic operations is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Discussions Metrics.

27.19.4 Average List Forums Time (ms)

This metric indicates the average time the Discussions service spends retrieving a list of forums, under a specific category, from the discussion server (in ms).

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for List Forums operations is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Discussions Metrics.

27.19.5 Average List Topics Time (ms)

This metric indicates the average time the Discussions service spends retrieving a list of topics, under a specific forum, from the discussion server (in ms).

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for List Topics operations is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Discussions Metrics.

27.19.6 Average Login Time (ms)

This metric indicates the average time spent logging in to the back-end discussions server hosting discussion forums (in ms).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to determine the performance of Login operations. If this metric is out-of-bounds (the average time to login is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for the Login operation (and all other operations) is available. Use the information on this page to help to determine the underlying cause of the time delay. See, Viewing Performance Information.

See also, Analyzing Discussions Metrics.

27.19.7 Average Logout Time (ms)

This metric indicates the average time spent logging out from the back-end discussions server hosting discussion forums (in ms).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

See also, Analyzing Discussions Metrics.

27.19.8 Average Processing Time (ms)

This metric indicates the average time the Discussions service spends processing operations (in ms).

Discussions service operations include: Login, Create Forum, Create Topic, List Forums, List Topics, Search, Logout. Processing times for individual operations are available on the application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to determine the performance of Discussions service operations.

If this metric is out-of-bounds (the average time for discussion forum operations is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for individual operations is available. See, Viewing Performance Information.

See also, Analyzing Discussions Metrics.

27.19.9 Average Reply Time (ms)

This metric indicates the average time the Discussions service spends replying to a topic, under a specific forum, from the discussion server (in ms).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Reply operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Discussions Metrics.

27.19.10 Average Search Time (ms)

This metric indicates the average time the Discussions service spends searching for terms within discussion forum text, in the discussions server (in ms).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

See also, Analyzing Discussions Metrics.

27.19.11 Create Forum (per minute)

This metric indicates the total number of Create Forum operations per minute for the Discussions service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Create Forum operations per minute for the Discussions service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Discussions Metrics.

27.19.12 Create Topic (per minute)

This metric indicates the total number of Create Topic operations per minute for the Discussions service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Create Topic operations per minute for the Discussions service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Discussions Metrics.

27.19.13 Failed Invocations (%)

This metric indicates the percentage of Discussions service invocations that failed.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also, Analyzing Discussions Metrics.

27.19.14 Invocations (per minute)

This metric indicates the total number of Discussions service invocations per minute. The number of invocations per operation is available on the application's main metric page. See, Viewing Performance Information.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of invocations per minute for the Discussions service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Discussions Metrics.

27.19.15 List Forums (per minute)

This metric indicates the total number of List Forums operations per minute for the Discussions service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of List Forums operations per minute for the Discussions service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Discussions Metrics.

27.19.16 List Topics (per minute)

This metric indicates the total number of List Topics operations per minute for the Discussions service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Discussions Metrics.

27.19.17 Logins (per minute)

This metric counts the number of times per minute a WebCenter user logs in to the back-end discussions server hosting discussion forums.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to monitor typical and peak usage of the Discussions service. You can evaluate when most logins occur, as well as the maximum and minimum usage-- which can be useful for tuning discussion server performance.

See also, Analyzing Discussions Metrics.

27.19.18 Logouts (per minute)

This metric counts the number of times per minute a WebCenter user logs out from the back-end discussions server hosting discussion forums.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to monitor typical and peak usage of the Discussions service. You can evaluate when most logouts occur, as well as the maximum and minimum usage-- which can be useful for tuning discussion server performance.

See also, Analyzing Discussions Metrics.

27.19.19 Replies (per minute)

This metric indicates the total number of replies to discussion topics per minute.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of replies per minute is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Discussions Metrics.

27.19.20 Searches (per minute)

This metric indicates the total number of searches in the discussions server per minute.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of searches per minute is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Discussions Metrics.

27.19.21 Status

This metric indicates whether the Discussions service is up or down. If the value is 1, the service is up. If the value is 0, it is down.

27.19.22 Successful Invocations (%)

This metric indicates the percentage of Discussions service invocations that succeeded.

Successful Invocations (%) is equal to the number of successful invocations divided by the invocation count.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If Successful Invocations (%) is below 100%, investigate this metric in more detail. Navigate to the application's main metric page where more detailed metric data for individual operations is available. See, Viewing Performance Information.

See also, Analyzing Discussions Metrics.

You can also check the diagnostic logs to establish why service requests are failing.

27.19.23 Service Name

These metrics apply to the Discussions service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

No action required.

27.20 WebCenter Pages

Provides information about WebCenter pages metrics.

27.20.1 Application Name

This metric identifies the WebCenter application to which these page metrics apply.

User Action

No action required.

27.20.2 Average Page Processing Time (ms)

This metric indicates the average time (in ms) to display the page.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to determine the performance of a page.

If this metric is out-of-bounds (the average time to display pages is increasing or higher than expected), navigate to the application's page metric page where more detailed metric data is available.

See, Monitoring Page Metrics for Spaces and Monitoring Page Metrics for WebCenter Applications.

27.20.3 Average Partial Page Processing Time (ms)

This metric indicates the average time (in ms) to refresh the partial page.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

27.20.4 Errors (per minute)

This metric shows the average number of errors that occur per minute in the page.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

See, Monitoring Page Metrics for Spaces and Monitoring Page Metrics for WebCenter Applications.

27.20.5 Failed Invocations (%)

This metric indicates the percentage of page invocations that failed.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See, Monitoring Page Metrics for Spaces and Monitoring Page Metrics for WebCenter Applications.

27.20.6 Invocations (per minute)

This metric indicates the total number of page invocations per minute.

The number of invocations for this page is available on application's main metric page. See Monitoring Page Metrics for Spaces and Monitoring Page Metrics for WebCenter Applications.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to monitor minimum, typical, and peak usage, and to evaluate page performance under peak load conditions. You can use this information to assess whether additional resources or hardware are required for scalability.

If you are experiencing performance issues and the total number of invocations per minute for this page is high (compared with other pages), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's page metric page where more detailed metric data is available. See, Monitoring Page Metrics for Spaces and Monitoring Page Metrics for WebCenter Applications.

27.20.7 Page Throughput (per minute)

This metric shows the average number of pages accessed per minute.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to monitor typical and peak usage of the page. You can evaluate when this page is accessed the most, as well as the maximum and minimum usage.

See, Monitoring Page Metrics for Spaces and Monitoring Page Metrics for WebCenter Applications.

27.20.8 Partial Page Invocations (per minute)

This metric indicates the total time per minute to refresh the partial page.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to monitor minimum, typical, and peak usage, and to evaluate partial page performance under peak load conditions. You can use this information to assess whether additional resources or hardware are required for scalability.

If you are experiencing performance issues and the total number of invocations per minute for this partial page is high (compared with other pages), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's page metric page where more detailed metric data is available.

See, Monitoring Page Metrics for Spaces and Monitoring Page Metrics for WebCenter Applications.

27.20.9 Status

This metric indicates whether or not the page is available. If the value is 1, the service is up. If the value is 0, it is down.

27.20.10 Successful Invocations (%)

This metric indicates the percentage of page invocations that succeeded.

Successful Invocations (%) is equal to the number of successful invocations divided by the invocation count.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If Successful Invocations (%) is below 100%, navigate to the application's page metric page where more detailed metric data is available.

See Monitoring Page Metrics for Spaces and Monitoring Page Metrics for WebCenter Applications.

You can also check the diagnostic logs to establish why page invocations are failing.

27.21 WebCenter Import/Export

Provides information about WebCenter Import/Export metrics.

27.21.1 Application Name

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

27.21.2 Average Processing Time (ms)

This metric indicates the average time in which an entire WebCenter application is imported or exported (in ms).

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to determine the performance of import/export operations. If this metric is out-of-bounds (the average time for import/export operations is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

27.21.3 Failed Invocations (%)

This metric indicates the percentage of import/export invocations that failed.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

27.21.4 Invocations (per minute)

This metric indicates the total number of import/export invocations per minute.

The number of invocations for this page is available on application's main metric page.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to monitor minimum, typical, and peak usage, and to evaluate import/export performance under peak load conditions. You can use this information to assess whether additional resources or hardware are required for scalability.

If you are experiencing performance issues and the total number of invocations per minute for import/export is high (compared with other pages), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's import/export metric page where more detailed metric data is available.

27.21.5 Status

This metric indicates whether import/export is up or down. If the value is 1, the service is up. If the value is 0, it is down.

27.21.6 Successful Invocations (%)

This metric indicates the percentage of page invocations that succeeded.

Successful Invocations (%) is equal to the number of successful invocations divided by the invocation count.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If Successful Invocations (%) is below 100%, navigate to the application's import/export metric page where more detailed metric data is available.

You can also check the diagnostic logs to establish why page invocations are failing.

27.21.7 Service Name

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

27.22 WebCenter Lists

Provides information about WebCenter Lists metrics.

27.22.1 Application Name

This metric identifies the WebCenter application to which these Lists service metrics apply.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

No action required.

27.22.2 Average Copy List Time (ms)

This metric indicates the average time the Lists service spends copying a list in the user session (in ms).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Copy List operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing List Metrics.

27.22.3 Average Copy List Type Time (ms)

This metric indicates the average time the Lists service spends copying a list type in the user session (in ms).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Copy List Type operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing List Metrics.

27.22.4 Average Copy Rows Time (ms)

This metric indicates the average time the Lists service spends copying rows of list data in the user session (in ms).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Copy Rows operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing List Metrics.

27.22.5 Average Create List Time (ms)

This metric indicates the average time the Lists service spends creating a list in the user session (in ms).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Create List operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing List Metrics.

27.22.6 Average Create List Type Time (ms)

This metric indicates the average time the Lists service spends creating a list type in the user session (in ms).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Create List Type operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing List Metrics.

27.22.7 Average Create Row Time (ms)

This metric indicates the average time the Lists service spends creating rows of list data in the user session (in ms).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Create Row operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing List Metrics.

27.22.8 Average Delete List Time (ms)

This metric indicates the average time the Lists service spends deleting a list and its data in the user session (in ms).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Delete List operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing List Metrics.

27.22.9 Average Delete List Type Time (ms)

This metric indicates the average time the Lists service spends deleting a list type in the user session (in ms).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Delete List Type operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing List Metrics.

27.22.10 Average Delete Row Time (ms)

This metric indicates the average time the Lists service spends deleting a row of list data in the user session (in ms).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Delete Row operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing List Metrics.

27.22.11 Average Processing Time (ms)

This metric indicates the average time the Lists service spends processing list operations (in ms).

List operations include: Create List, Copy List, Delete List, Create Row, Delete Row, Update Row, Search, and Save Data. Processing times for individual operations are available on application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to determine the performance of Lists service operations. If this metric is out-of-bounds (the average time for list operations is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for individual operations is available. See, Viewing Performance Information.

See also, Analyzing List Metrics.

27.22.12 Average Query Time (ms)

This metric indicates the average time the Lists service spends querying list data in the user session (in ms).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Query operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing List Metrics.

27.22.13 Average Retrieve Rows Time (ms)

This metric indicates the average time the Lists service spends retrieving rows and their data in the user session (in ms).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Retrieve Rows operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing List Metrics.

27.22.14 Average Save Time (ms)

This metric indicates the average time the Lists service spends saving lists in the WebCenter repository (in ms).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Save operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing List Metrics.

27.22.15 Average Update Row Time (ms)

This metric indicates the average time the Lists service spends updating rows of list data in the user session (in ms).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Update Row operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing List Metrics.

27.22.16 Copy List (per minute)

This metric indicates the total number of Copy List operations per minute for the Lists service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Copy List operations per minute for the Lists service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing List Metrics.

27.22.17 Copy List Type (per minute)

This metric indicates the total number of Copy List Type operations per minute for the Lists service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Copy List Type operations per minute for the Lists service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing List Metrics.

27.22.18 Copy Rows (per minute)

This metric indicates the total number of Copy Rows operations per minute for the Lists service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Copy Rows operations per minute for the Lists service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing List Metrics.

27.22.19 Create List (per minute)

This metric indicates the total number of Create List operations per minute for the Lists service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Create List operations per minute for the Lists service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing List Metrics.

27.22.20 Create List Type (per minute)

This metric indicates the total number of Create List Type operations per minute for the Lists service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Create List Type operations per minute for the Lists service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing List Metrics.

27.22.21 Create Row (per minute)

This metric indicates the total number of Create Row operations per minute for the Lists service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Create Row operations per minute for the Lists service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing List Metrics.

27.22.22 Delete List (per minute)

This metric indicates the total number of Delete List operations per minute for the Lists service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Delete List operations per minute for the Lists service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing List Metrics.

27.22.23 Delete List Type (per minute)

This metric indicates the total number of Delete List Type operations per minute for the Lists service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Delete List Type operations per minute for the Lists service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing List Metrics.

27.22.24 Delete Row (per minute)

This metric indicates the total number of Delete Row operations per minute for the Lists service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Delete Row operations per minute for the Lists service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing List Metrics.

27.22.25 Failed Invocations (%)

This metric indicates the percentage of Lists service invocations that failed.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also, Analyzing List Metrics.

27.22.26 Invocations (per minute)

This metric indicates the total number of Lists service invocations per minute. The number of invocations per operation is available on the application's main metric page. See Viewing Performance Information.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of invocations per minute for the Lists service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing List Metrics.

27.22.27 Queries (per minute)

This metric indicates the total number of queries per minute for the Lists service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of queries per minute for the Lists service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing List Metrics.

27.22.28 Retrieve Rows (per minute)

This metric indicates the total number of Retrieve Rows operations per minute for the Lists service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Retrieve Rows operations per minute for the Lists service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing List Metrics.

27.22.29 Saves (per minute)

This metric indicates the total number of times lists data is saved per minute.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Save operations per minute for the Lists service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing List Metrics.

27.22.30 Status

This metric indicates whether the Lists service is up or down. If the value is 1, the service is up. If the value is 0, it is down.

27.22.31 Successful Invocations (%)

This metric indicates the percentage of Lists service invocations that succeeded. Successful Invocations (%) is equal to the number of successful invocations divided by the invocation count.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If Successful Invocations (%) is less than 100%, navigate to the application's main metric page where more detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing List Metrics.

You can also check the diagnostic logs to establish why service requests are failing.

27.22.32 Update Row (per minute)

This metric indicates the total number of Update Row operations per minute for the Lists service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Update Row operations per minute for the Lists service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing List Metrics.

27.22.33 Service Name

These metrics apply to the Lists service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

No action required.

27.23 WebCenter Mail

Provides information about the WebCenter Mail metrics.

27.23.1 Application Name

This metric identifies the WebCenter application to which these Mail service metrics apply.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

No action required.

27.23.2 Average Login Time (ms)

This metric indicates the average time spent logging in to the mail server that is hosting mail services (in ms).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to determine the performance of the Login operation. If this metric is out-of-bounds (the average time to login is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for the Login operation (and all other operations) is available. Use the information on this page to help determine the underlying cause of the time delay. See, Viewing Performance Information.

See also, Analyzing Mail Metrics.

27.23.3 Average Logout Time (ms)

This metric indicates the average time spent logging out from the mail server that is hosting mail services (in ms).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

See also, Analyzing Mail Metrics.

27.23.4 Average Processing Time (ms)

This metric indicates the average time the Mail service spends processing operations (in ms).

Mail operations include: Login, Logout, Receive, Send, Search. Processing times for individual operations are available on the application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to determine the performance of Mail service operations.

If this metric is out-of-bounds (the average time for mail operations is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for individual operations is available. See, Viewing Performance Information.

See also, Analyzing Mail Metrics.

27.23.5 Average Receive Time (ms)

This metric indicates the average time the Mail service spends receiving a mail (in ms).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Receive operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Mail Metrics.

27.23.6 Average Search Time (ms)

This metric indicates the average time the Mail service spends searching for a mail that contains a specific term (in ms).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

See also, Analyzing Mail Metrics.

27.23.7 Average Send Time (ms)

This metric indicates the average time the Mail service spends sending a mail (in ms).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Send operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Mail Metrics.

27.23.8 Failed Invocations (%)

This metric indicates the percentage of Mail service invocations that failed.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also, Analyzing Mail Metrics.

27.23.9 Invocations (per minute)

This metric indicates the total number of Mail service invocations per minute.

The number of invocations per operation is available on the application's main metric page. See, Viewing Performance Information.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of invocations per minute for the Mail service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Mail Metrics.

27.23.10 Logins (per minute)

This metric counts the number of times per minute a WebCenter user logins to the back-end mail server that is hosting mail services.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to monitor typical and peak usage of the Instant Messaging and Presence (IMP) service.

Use this metric to monitor typical and peak usage of the Mail service. You can evaluate when most logins occur, as well as the maximum and minimum usage--which can be useful for tuning mail server performance.

See also, Analyzing Mail Metrics.

27.23.11 Logout (per minute)

This metric counts the number of times per minute a WebCenter user logs out from the mail server that is hosting mail services.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to monitor typical and peak usage of the Mail service. You can evaluate when most logouts occur, as well as the maximum and minimum usage-- which can be useful for tuning discussion server performance.

27.23.12 Receives (per minute)

This metric indicates the total number of Receive operations per minute for the Mail service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Receive operations per minute for the Mail service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Mail Metrics.

27.23.13 Searches (per minute)

This metric indicates the total number of Search operations per minute for the Mail service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Search operations per minute for the Mail service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Mail Metrics.

27.23.14 Sends (per minute)

This metric indicates the total number of Send operations per minute for the Mail service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Send operations per minute for the Mail service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Mail Metrics.

27.23.15 Status

This metric indicates whether the Mail service is up or down. If the value is 1, the service is up. If the value is 0, it is down.

27.23.16 Successful Invocations (%)

This metric indicates the percentage of Mail service invocations that succeeded.

Successful Invocations (%) is equal to the number of successful invocations divided by the invocation count.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If Successful Invocations (%) is below 100%, investigate this metric in more detail. Navigate to the application's main metric page where more detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Mail Metrics.

You can also check the diagnostic logs to establish why service requests are failing.

27.23.17 Service Name

These metrics apply to the Mail service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

No action required.

27.24 WebCenter Notes

Provides information about the WebCenter Notes metrics.

27.24.1 Application Name

This metric identifies the WebCenter application to which these Notes service metrics apply.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

No action required.

27.24.2 Average Create Time (ms)

This metric indicates the average time the Notes service spends creating a personal note (in ms).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Create operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Note Metrics.

27.24.3 Average Delete Time (ms)

This metric indicates the average time the Notes service spends deleting a personal note (in ms).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Delete operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Note Metrics.

27.24.4 Average Find Time (ms)

This metric indicates the average time the Notes service spends retrieving a note from the MDS repository (in ms).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Retrieve operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Note Metrics.

27.24.5 Average Processing Time (ms)

This metric indicates the average time the Notes service spends processing note operations (in ms).

Notes operations include: Create, Update, Find. Processing times for individual operations are available on the application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to determine the performance of Notes service operations. If this metric is out-of-bounds (the average time for note operations is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for individual operations is available. See, Viewing Performance Information.

See also, Analyzing Note Metrics.

27.24.6 Average Save Changes Time (ms)

This metric indicates the average time the Notes service spends saving new notes to the MDS repository (in ms).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Save Changes operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Note Metrics.

27.24.7 Average Update Time (ms)

This metric indicates the average time the Notes service spends updating a personal note (in ms).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

See also, Analyzing Note Metrics.

27.24.8 Creates (per minute)

This metric indicates the total number of Create operations per minute for the Notes service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Create operations per minute for the Notes service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Note Metrics.

27.24.9 Deletes (per minute)

This metric indicates the total number of Delete operations per minute for the Notes service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Delete operations per minute for the Notes service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Note Metrics.

27.24.10 Failed Invocations (%)

This metric indicates the percentage of Notes service invocations that failed.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also, Analyzing Note Metrics.

27.24.11 Finds (per minute)

This metric indicates the total number of Find operations per minute for the Notes service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Find operations per minute for the Notes service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Note Metrics.

27.24.12 Invocations (per minute)

This metric indicates the total number of Notes service invocations per minute.

The count includes the following Notes operations: Create, Delete, Find, Find All Notes, Save Changes, Update. The number of invocations per operation is available on the application's main metric page. See, Viewing Performance Information.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of invocations per minute for the Notes service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

Also see, Analyzing Note Metrics.

27.24.13 Save Changes (per minute)

This metric indicates the total number of Save Changes operations per minute for the Notes service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Save Changes operations per minute for the Notes service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Note Metrics.

27.24.14 Status

This metric indicates whether the Notes service is up or down. If the value is 1, the service is up. If the value is 0, it is down.

27.24.15 Successful Invocations (%)

This metric indicates the percentage of Notes service invocations that succeeded.

Successful Invocations (%) is equal to the number of successful invocations divided by the invocation count.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If Successful Invocations (%) is below 100%), investigate this metric further. Navigate to the application's main metric page where more detailed metric data for individual operations is available. See, Viewing Performance Information.

See also, Analyzing Note Metrics.

You can also check the diagnostic logs to establish why service requests are failing.

27.24.16 Updates (per minute)

This metric indicates the total number of Update operations per minute for the Notes service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Update operations per minute for the Notes service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Note Metrics.

27.24.17 Service Name

These metrics apply to the Notes service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

No action required.

27.25 WebCenter Page Service

Provides information about the WebCenter Page Service metrics.

27.25.1 Application Name

This metric identifies the WebCenter application to which these Page service metrics apply.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

No action required.

27.25.2 Average Copy Time (ms)

This metric indicates the average time the Page service spends copying a page in the WebCenter application (in ms).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Copy operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Page Metrics.

27.25.3 Average Create Time (ms)

This metric indicates the average time the Page service spends creating a page in the WebCenter application (in ms).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

See also, Analyzing Page Metrics.

27.25.4 Average Delete Time (ms)

This metric indicates the average time the Page service spends deleting a page in the WebCenter application (in ms).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

See also, Analyzing Page Metrics.

27.25.5 Average Processing Time (ms)

This metric indicates the average time the Page service spends processing operations associated with the Page service (in ms).

Page operations include: Create, Update Properties, Copy, Delete, Search. Processing times for individual operations are available on the application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric whilst assessing the overall performance of the Page service.

If this metric is out-of-bounds (the average time for page operations is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for individual operations is available. See, Viewing Performance Information.

See also, Analyzing Page Metrics.

27.25.6 Average Search Time (ms)

This metric indicates the average time the Page service spends searching for pages that contain a specific term (in ms).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

See also, Analyzing Page Metrics.

27.25.7 Average Update Time (ms)

This metric indicates the average time the Page service spends updating a page (in ms).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

See also, Analyzing Page Metrics.

27.25.8 Copies (per minute)

This metric indicates the total number of Copy operations per minute for the Page service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Copy operations per minute for the Page service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Page Metrics.

27.25.9 Creates (per minute)

This metric indicates the total number of Create operations per minute for the Page service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Create operations per minute for the Page service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Page Metrics.

27.25.10 Deletes (per minute)

This metric indicates the total number of Delete operations per minute for the Page service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Delete operations per minute for the Page service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Page Metrics.

27.25.11 Failed Invocations (%)

This metric indicates the percentage of Pages service invocations that failed.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also, Analyzing Page Metrics.

27.25.12 Invocations (per minute)

This metric indicates the total number of Page service invocations per minute.

The number of invocations per operation is available on the application's main metric page. See, Viewing Performance Information.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of invocations per minute for the Page service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

27.25.13 Searches (per minute)

This metric indicates the total number of Search operations per minute for the Page service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Search operations per minute for the Page service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Page Metrics.

27.25.14 Status

This metric indicates whether the Pages service is up or down. If the value is 1, the service is up. If the value is 0, it is down.

27.25.15 Updates (per minute)

This metric indicates the total number of Update operations per minute for the Page service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Update operations per minute for the Page service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Page Metrics.

27.25.16 Successful Invocations (%)

This metric indicates the percentage of Page service invocations that succeeded.

Successful Invocations (%) is equal to the number of successful invocations divided by the invocation count.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If Successful Invocations (%) is below 100%, investigate this metric in more detail. Navigate to the application's main metric page where more detailed metric data for individual operations is available. See, Viewing Performance Information.

See also, Analyzing Page Metrics.

You can also check the diagnostic logs to establish why service requests are failing.

27.25.17 Service Name

These metrics apply to the Page service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

No action required.

27.26 WebCenter People Connections

Provides information about the WebCenter People Connections metrics.

27.26.1 Application name

This metric identifies the WebCenter application to which these People Connections service metrics apply.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

No action required.

27.26.2 Average Processing Time (ms)

This metric indicates the average time the People Connections service spends processing user operations (in ms).

People Connection operations include: Get Profiles, Get Activities, Publish Activities, Get Messages, Get Feedback, Get Connections. Processing times for individual operations are available on the application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to determine the performance of People Connection service operations. If this metric is out-of-bounds (the average time for user operations is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for individual operations is available. See, Viewing Performance Information.

See also, Analyzing People Connection Metrics.

27.26.3 Failed Invocations (%)

This metric indicates the percentage of people connection invocations that failed.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also, Analyzing People Connection Metrics.

27.26.4 Get Feedback (per minute)

This metric indicates the total number of Get Feedback operations per minute for the People Connections service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Get Feedback operations per minute for the People Connections service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing People Connection Metrics.

27.26.5 Get Feedback Average Time (ms)

This metric indicates the average time the People Connections service spends getting the feedback of the user (in ms).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Get Feedback operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing People Connection Metrics.

27.26.6 Invocations (per minute)

This metric indicates the total number of People Connection service invocations per minute.

The count includes the following People Connection operations: Get Profiles, Get Activities, Publish Activities, Get Messages, Get Feedback, Get Connections. The number of invocations per operation is available on the application's main metric page. See, Viewing Performance Information.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of invocations per minute for the People Connections service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

Also see, Analyzing People Connection Metrics.

27.26.7 Publish Activity (per minute)

This metric indicates the total number of Publish Activity operations per minute for the People Connections service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Publish Activity operations per minute for the People Connections service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing People Connection Metrics.

27.26.8 Publish Activity Average Time (ms)

This metric indicates the average time the People Connections service spends publishing an activity in the user session and saving it in the WebCenter application (in ms).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Publish Activity operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing People Connection Metrics.

27.26.9 Retrieve Activities (per minute)

This metric indicates the total number of Retrieve Activity operations per minute for the People Connections service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Retrieve Activity operations per minute for the People Connections service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing People Connection Metrics.

27.26.10 Retrieve Activities Average Time (ms)

This metric indicates the average time the People Connections service spends retrieving activities based on the user filter options (in ms).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Retrieve Activity operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing People Connection Metrics.

27.26.11 Retrieve Connections Average Time (ms)

This metric indicates the average time the People Connections service spends retrieving connections of users (in ms).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Retrieve Connections operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing People Connection Metrics.

27.26.12 Retrieve Messages (per minute)

This metric indicates the total number of Retrieve Message operations per minute for the People Connections service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Retrieve Message operations per minute for the People Connections service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing People Connection Metrics.

27.26.13 Retrieve Messages Average Time (ms)

This metric indicates the average time the People Connections service spends retrieving messages of users (in ms).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Retrieve Messages operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing People Connection Metrics.

27.26.14 Retrieve Profiles (per minute)

This metric indicates the total number of Retrieve Profile operations per minute for the People Connections service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Retrieve Profile operations per minute for the People Connections service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing People Connection Metrics.

27.26.15 Retrieve Profiles Average Time (ms)

This metric indicates the average time the People Connections service spends retrieving profiles of users (in ms).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Retrieve Profiles operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing People Connection Metrics.

27.26.16 Status

This metric indicates whether the People Connections service is up or down. If the value is 1, the service is up. If the value is 0, it is down.

27.26.17 Successful Invocations (%)

This metric indicates the percentage of People Connections service invocations that succeeded.

Successful Invocations (%) is equal to the number of successful invocations divided by the invocation count.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

See also, Analyzing People Connection Metrics.

You can also check the diagnostic logs to establish why service requests are failing.

27.26.18 Service Name

These metrics apply to the People Connections service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

No action required.

27.27 WebCenter Polls

Provides information about WebCenter Polls metrics.

27.27.1 Application Name

This metric identifies the WebCenter application to which these Poll service metrics apply.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

No action required.

27.27.2 Analyze Poll (per minute)

This metric indicates the total number of Analyze Poll operations per minute for the Polls service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Analyze Poll operations per minute for the Polls service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Poll Metrics.

27.27.3 Analyze Poll Average Time (ms)

This metric indicates the average time the Polls service spends analyzing poll results (in ms).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Analyze Poll operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Poll Metrics.

27.27.4 Average Processing Time (ms)

This metric indicates the average time the Polls service spends processing poll operations (in ms).

Polls operations include: Create Poll, Edit Poll, Delete Poll, Get Poll By ID, Submit Poll, Analyze Results. Processing times for individual operations are available on the application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to determine the performance of Poll service operations. If this metric is out-of-bounds (the average time for poll operations is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for individual operations is available. See, Viewing Performance Information.

See also, Analyzing Poll Metrics.

27.27.5 Create Poll (per minute)

This metric indicates the total number of Create Poll operations per minute for the Polls service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Create Poll operations per minute for the Polls service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Poll Metrics.

27.27.6 Create Poll Average Time (ms)

This metric indicates the average time the Polls service spends creating a poll in the WebCenter application (in ms).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Create Poll operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Poll Metrics.

27.27.7 Create Response (per minute)

This metric indicates the total number of Create Response operations per minute for the Polls service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Create Response operations per minute for the Polls service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Poll Metrics.

27.27.8 Create Response Average Time (ms)

This metric indicates the average time the Polls service spends creating a response to a poll in the WebCenter application (in ms).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Create Response operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Poll Metrics.

27.27.9 Delete Poll (per minute)

This metric indicates the total number of Delete Poll operations per minute for the Polls service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Delete Poll operations per minute for the Polls service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Poll Metrics.

27.27.10 Delete Poll Average Time (ms)

This metric indicates the average time the Polls service spends deleting a poll in the WebCenter application (in ms).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Delete Poll operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Poll Metrics.

27.27.11 Edit Poll (per minute)

This metric indicates the total number of Edit Poll operations per minute for the Polls service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Edit Poll operations per minute for the Polls service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Poll Metrics.

27.27.12 Edit Poll Average Time (ms)

This metric indicates the average time the Polls service spends editing a poll in the WebCenter application (in ms).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Edit Poll operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Poll Metrics.

27.27.13 Failed Invocations (%)

This metric indicates the percentage of Polls service invocations that failed.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also, Analyzing Poll Metrics.

27.27.14 Get Poll (per minute)

This metric indicates the total number of Get Poll operations per minute for the Polls service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Get Poll operations per minute for the Polls service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Poll Metrics.

27.27.15 Get Poll By Id (per minute)

This metric indicates the total number of Get Poll By Id operations per minute for the Polls service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Get Poll By Id operations per minute for the Polls service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Poll Metrics.

27.27.16 Get Poll By Id Average Time (ms)

This metric indicates the average time the Polls service spends displaying the ongoing poll (in ms).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Get Poll By Id operation is increasing or higher than expected), navigate to the application's main metric page where detailed metric data for individual operations is also available. See, Viewing Performance Information.

See also, Analyzing Poll Metrics.

27.27.17 Get Poll Response Average Time (per minute)

This metric indicates the total number of Get Poll Response operations per minute for the Polls service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Get Poll Response operations per minute for the Polls service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Poll Metrics.

27.27.18 Status

This metric indicates whether the Polls service is up or down. If the value is 1, the service is up. If the value is 0, it is down.

27.27.19 Successful Invocations (%)

This metric indicates the percentage of Poll service invocations that succeeded.

Successful Invocations (%) is equal to the number of successful invocations divided by the invocation count.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

See also, Analyzing Poll Metrics.

You can also check the diagnostic logs to establish why service requests are failing.

27.27.20 Invocations (per minute)

This metric indicates the total number of Poll service invocations per minute.

The count includes the following Polls operations: Create Poll, Edit Poll, Delete Poll, Get Poll By ID, Submit Poll, Analyze Results. The number of invocations per operation is available on the application's main metric page. See, Viewing Performance Information.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of invocations per minute for the Polls service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

Also see, Analyzing Poll Metrics.

27.27.21 Service Name

These metrics apply to the Polls service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

No action required.

27.28 WebCenter Recent Activity

Provides information about the WebCenter Recent Activity metrics.

27.28.1 Application Name

This metric identifies the WebCenter application to which these Recent Activity metrics apply.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

No action required.

27.28.2 Average Processing Time (ms)

This metric indicates the total time the Recent Activities service spends processing Recent Activity operations (in ms).

Processing time is available on the application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to determine the performance of Recent Activities service operations.

If this metric is out-of-bounds (the average time for recent activity operations is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Recent Activity Metrics.

27.28.3 Failed Invocations (%)

This metric indicates the percentage of Recent Activities invocations that failed.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also, Analyzing Recent Activity Metrics.

27.28.4 Invocations (per minute)

This metric indicates the total number of Recent Activities service invocations per minute.

The number of invocations is available on the application's main metric page. See, Viewing Performance Information.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of invocations per minute for the Recent Activities service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Recent Activity Metrics.

27.28.5 Status

This metric indicates whether the Recent Activities service is up or down. If the value is 1, the service is up. If the value is 0, it is down

27.28.6 Successful Invocations (%)

This metric indicates the percentage of Recent Activities service invocations that succeeded.

Successful Invocations (%) is equal to the number of successful invocations divided by the invocation count.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

See also, Analyzing Recent Activity Metrics.

You can also check the diagnostic logs to establish why service requests are failing.

27.28.7 Service Name

These metrics apply to the Recent Activities service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

No action required.

27.29 WebCenter RSS News Feeds

Provides information about the WebCenter RSS News Feeds metrics.

27.29.1 Application Name

This metric identifies the WebCenter application to which these RSS News Feed metrics apply.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

No action required.

27.29.2 Average Processing Time (ms)

This metric indicates the average time the RSS service spends processing operations (in ms).

Processing time is available on application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to determine the performance of RSS service operations.

If this metric is out-of-bounds (the average time for RSS operations is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing RSS News Feed Metrics.

27.29.3 Failed Invocations (%)

This metric indicates the percentage of RSS service invocations that failed.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also, Analyzing RSS News Feed Metrics.

27.29.4 Invocations (per minute)

This metric indicates the total number of RSS New Feed invocations per minute.

The number of invocations is available on the application's main metric page. See, Viewing Performance Information.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of invocations per minute for RSS news feeds is high (compared with other services consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing RSS News Feed Metrics.

27.29.5 Status

This metric indicates whether the RSS service is up or down. If the value is 1, the service is up. If the value is 0, it is down

27.29.6 Successful Invocations (%)

This metric indicates the percentage of RSS service invocations that succeeded.

Successful Invocations (%) is equal to the number of successful invocations divided by the invocation count.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

See also, Analyzing RSS News Feed Metrics.

You can also check the diagnostic logs to establish why service requests are failing.

27.29.7 Service Name

These metrics apply to the RSS service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

No action required.

27.30 WebCenter Instant Messaging and Presence

Provides information about the WebCenter Instant Messaging and Presence metrics.

27.30.1 Application Name

This metric identifies the WebCenter application to which these Instant Messaging and Presence service metrics apply.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

No action required.

27.30.2 Average Get Presence Time (ms)

This metric indicates the average time the IMP service spends retrieving user presence information from the IMP server (in ms).

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If this metric is out-of-bounds (the average time for the Get Presence operation is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for individual operations is available. See, Viewing Performance Information.

See also, Analyzing Instant Messaging and Presence (IMP) Metrics.

27.30.3 Average Login Time (ms)

This metric indicates the average time spent logging in to the back-end server hosting instant messaging and presence services (in ms).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to determine the performance of the Login operation. If this metric is out-of-bounds (the average time to login is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for the Login operation (and all other operations) is available. Use the information on this page to help determine the underlying cause of the time delay. See, Viewing Performance Information.

See also, Analyzing Instant Messaging and Presence (IMP) Metrics.

27.30.4 Average Logout Time (ms)

This metric indicates the average time spent logging out from the IMP server hosting presence information (in ms).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

See also, Analyzing Instant Messaging and Presence (IMP) Metrics.

27.30.5 Average Processing Time (ms)

This metric indicates the average time the Instant Messaging and Presence (IMP) service spends processing IMP operations (in ms).

IMP operations include: Get Presence, Login, Logout. Processing times for individual operations are available on the application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to determine the performance of Instant Messaging and Presence (IMP) service operations.

If this metric is out-of-bounds (the average time for IMP operations is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for individual operations is available. See, Viewing Performance Information.

See also, Analyzing Instant Messaging and Presence (IMP) Metrics.

27.30.6 Failed Invocations (%)

This metric indicates the percentage of IMP service invocations that failed.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also, Analyzing Instant Messaging and Presence (IMP) Metrics.

27.30.7 Get Presence (per minute)

This metric indicates the total number of Get Presence operations per minute for the Polls service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of Get Presence operations per minute for the Polls service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Instant Messaging and Presence (IMP) Metrics.

27.30.8 Invocations (per minute)

This metric indicates the total number of Instant Messaging and Presence (IMP) service invocations per minute.

The number of invocations per operation is available on the application's main metric page. See, Viewing Performance Information.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of invocations per minute for the IMP service is high (compared with other services), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Instant Messaging and Presence (IMP) Metrics.

27.30.9 Logins (per minute)

This metric counts the number of times a minute a WebCenter user logins to the server that is hosting instant messaging and presence services.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to monitor typical and peak usage of the Instant Messaging and Presence (IMP) service. You can evaluate when most logins occur, as well as the maximum and minimum usage-- which can be useful for tuning IMP server performance.

See also, Analyzing Instant Messaging and Presence (IMP) Metrics.

27.30.10 Logouts (per minute)

This metric counts the number of times per minute a WebCenter user logs out from the IMP server hosting presence information.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to monitor typical and peak usage of the IMP service. You can evaluate when most logouts occur, as well as the maximum and minimum usage-- which can be useful for tuning discussion server performance.

See also, Analyzing Instant Messaging and Presence (IMP) Metrics.

27.30.11 Status

This metric indicates whether the Instant Messaging and Presence (IMP) service is up or down. If the value is 1, the service is up. If the value is 0, it is down.

27.30.12 Successful Invocations (%)

This metric indicates the percentage of Instant Messaging and Presence (IMP) service invocations that succeeded.

Successful Invocations (%) is equal to the number of successful invocations divided by the invocation count.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If Successful Invocations (%) is below 100%, investigate this metric in more detail. Navigate to the application's main metric page where more detailed metric data for individual operations is available. See, Viewing Performance Information.

See also, Analyzing Instant Messaging and Presence (IMP) Metrics.

You can also check the diagnostic logs to establish why service requests are failing.

27.30.13 Service Name

These metrics apply to the Instant Messaging and Presence (IMP) service.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

No action required.

27.31 WebCenter Search

Provides information about WebCenter Search metrics.

27.31.1 Application Name

This metric identifies the WebCenter application to which these Search service metrics apply.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

No action required.

27.31.2 Failed Invocations (%)

This metric indicates the percentage of Search service invocations that failed.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also, Analyzing Search Metrics.

27.31.3 Successful Invocations (%)

This metric indicates the percentage of Search service invocations that succeeded for a particular search source.

Successful Invocations (%) is equal to the number of successful invocations divided by the invocation count.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If Successful Invocations (%) is below 100%, investigate this metric in more detail. Navigate to the application's main metric page where more detailed metric data for the search source is available. See, Viewing Performance Information.

See also, Analyzing Search Metrics.

You can also check the diagnostic logs to establish why service requests are failing.

27.31.4 Invocations (per minute)

This metric indicates the total number of Search service invocations per minute for a single search source.

The number of invocations for this search source is available on application's main metric page. See, Viewing Performance Information.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of invocations per minute for this search source is high (compared with other search sources), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Search Metrics.

27.31.5 Query Throughput (queries per minute)

This metric shows the average search rate per minute.

All Spaces in the WebCenter application are included in this count.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to monitor typical and peak search time. You can evaluate when information is searched the most, as well as the maximum and minimum search rate.

27.31.6 Status

This metric indicates whether the Search service is up or down. If the value is 1, the service is up. If the value is 0, it is down

27.31.7 Average Processing Time (ms)

This metric indicates the average time the Search service spends processing search operations (in ms) for a single search source.

WebCenter search sources include data associated with: Announcements, Documents, Discussion Forums, Spaces, Events, Lists, Notes, Oracle Secure Enterprise Search, Pages, Wikis and Blogs, People Connections, and Tagged Items. Processing times for all search sources are available on the application's main metric page. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to determine the performance of Search service operations for a single search source.

If this metric is out-of-bounds (the average time for search operations is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data for the search source is available. See, Viewing Performance Information.

See also, Analyzing Search Metrics.

27.32 WebCenter BPEL Worklists

Provides information about the WebCenter BPEL worklists metrics.

27.32.1 Application Name

This metric identifies the WebCenter application to which these Worklists service metrics apply.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

No action required.

27.32.2 Failed Invocations (%)

This metric indicates the percentage of Worklists service invocations that failed.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Navigate to the application's metric pages where more detailed metric data is available. See, Monitoring WebCenter Spaces Information.

See also, Analyzing Worklist Metrics.

27.32.3 Status

This metric indicates whether the Worklists service is up or down. If the value is 1, the service is up. If the value is 0, it is down

27.32.4 Successful Invocations (%)

This metric indicates the percentage of Worklists service invocations, for this BPEL worklist, that succeeded.

Successful Invocations (%) is equal to the number of successful invocations divided by the invocation count.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If Successful Invocations (%) is below 100%), investigate this metric in more detail. Navigate to the application's main metric page where more detailed metric data is also available. See, Viewing Performance Information.

See also, Analyzing Worklist Metrics.

You can also check the diagnostic logs to establish why service requests are failing.

27.32.5 Invocations (per minute)

This metric indicates the total number of Worklists service invocations per minute for a single BPEL worklist. The number of invocations is available on the application's main metric page. See, Viewing Performance Information.

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

If you are experiencing performance issues and the total number of invocations per minute for this BPEL worklist is high (compared with other worklists), consider prioritizing troubleshooting efforts in this area.

Navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Worklist Metrics.

27.32.6 Average Processing Time (ms)

This metric indicates the average time the Worklists service spends processing operations relating to this BPEL worklist (in ms).

Processing time is available on application's main metric page where detailed metric data is available. See, Viewing Performance Information.

The last 10-15 minutes of data is used to calculate the average processing time. If 10-15 minutes of data is not yet available, the average is calculated over the collection period (until 10-15 minutes is reached). Metric collection starts when the application first starts up and continues indefinitely providing that metrics are requested by the client (Enterprise Manager or WLST). Metric collection stops temporarily if no metric requests are detected over a long period of time and will restart when the client next requests metrics. In this instance, the metric shows data for the delta period since metric collection stopped (until 10-15 minutes is reached).

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 300 Seconds

User Action

Use this metric to determine the performance of Worklists service operations, for this BPEL worklist. If this metric is out-of-bounds (the average time for worklist operations is increasing or higher than expected), navigate to the application's main metric page where more detailed metric data is available. See, Viewing Performance Information.

See also, Analyzing Worklist Metrics.