This chapter describes how to monitor your services in Oracle Service Bus (OSB) using the OSB Administration Console. Topics include working with SLA and pipeline alerts, statistics, operational settings, and metrics.
When you create a business or proxy service, monitoring is disabled by default for that service. To learn how to enable monitoring for proxy services, see Section 26.8, "Configuring Operational Settings for Proxy Services"; for business services, see Section 26.9, "Configuring Operational Settings for Business Services."
To enable or disable monitoring of all services that have individually been enabled or disabled for monitoring, use the Enable Monitoring option on the Operations > Global Settings page. See Section 27.2, "Enabling Global Settings."
To learn more about monitoring at runtime, see "Monitoring Oracle Service Bus at Runtime" in the Oracle Fusion Middleware Administrator's Guide for Oracle Service Bus.
Use the SLA Alerts page to view a summary of SLA alerts and access detailed alert history information, shown in Table 26-1.
The SLA Alerts page includes the following:
Tabs for displaying Pipeline Alerts, Service Health, and Server Health information.
On the SLA Alerts tab header, a numeric indicator shows the number of new alerts that have occurred since you last viewed them or during the last Dashboard refresh period, whichever is more recent. By default, the Dashboard refresh rate is No Refresh. To change the Dashboard refresh rate interval, see Section 27.3, "Setting User Preferences."
Caution:
By selecting a dashboard refresh rate interval other than the default (No Refresh), the browser refreshes the Dashboard at regular intervals. This prevents your session from timing out, even without you interacting with the Administration Console.Oracle recommends that you use the Dashboard refresh rate feature with caution. You should never leave an Administration Console session unattended. While your Administration Console session is active others can gain access to it from your computer, without re-authentication.
A pie chart of the services with SLA alerts over the past 30 minutes, which is the default alert history duration interval. To change the time interval for displaying historical alert data, see Section 27.3, "Setting User Preferences."
The number of SLA alerts on the page match the pie chart which displays the breakdown of alerts by severity level, over the same time interval. You can click the area in the chart corresponding to the alert severity to display more details.
The top 10 services with SLA alerts are listed in descending order of the number of alerts issued by those services. Each service name is a link to the service monitoring details. See Section 26.11, "Viewing Service Metrics."
Fields that display alert information depending on your customized settings for the alert table. For example, timestamp, alert name, alert severity, action, and the names of the service and service type associated with the alert. To learn more about these fields, see Table 26-1.
An Annotation icon next to an alert name indicates annotations. Positioning the mouse pointer over the icon previews the annotation text. Click the icon to view the entire annotation text.
A Table Customizer icon. See Section 2.2, "Customizing Table Views."
A link to the Extended Alert History page. See Section 26.3, "Locating Alerts."
Table 26-1 SLA Alert History Information
| Property | Description |
|---|---|
|
Timestamp |
The date and time that the alert rule last evaluated to true. By default, all the alerts are sorted according to the timestamp. |
|
Alert Name |
The name assigned to the alert. The name is a link to the Alert Details page. See Section 26.5, "Viewing Alert Details." An Annotation icon next to an alert name indicates annotations. Positioning the mouse pointer over the icon previews the annotation text. |
|
Alert Severity |
The user-defined severity of the alert.
|
|
Service |
The name of the service associated with the alert. The name is a link to the Service Monitoring Details page (only when the service is being actively monitored). See Section 26.11, "Viewing Service Metrics." |
|
Service Type |
The parent service type: proxy service or business service. |
|
Action |
The View Alert Rule Details icon is a link to the Alert Rule General Configuration page. See Section 26.24, "Viewing Alert Rule Configurations." |
Use the Pipeline Alerts page to view a summary of pipeline alerts and access detailed alert history information, shown in Table 26-2.
The Pipeline Alerts page includes the following:
Tabs for displaying SLA Alerts, Service Health, and Server Health information.
On the Pipeline Alerts tab header, a numeric indicator shows the number of new alerts that have occurred since you last viewed them or during the last Dashboard refresh period, whichever is more recent. By default, the Dashboard refresh rate is No Refresh. To change the Dashboard refresh rate interval, see Section 27.3, "Setting User Preferences."
Caution:
By selecting a dashboard refresh rate interval other than the default (No Refresh), the browser refreshes the Dashboard at regular intervals. This prevents your session from timing out, even without you interacting with the Administration Console.Oracle recommends that you use the Dashboard refresh rate feature with caution. You should never leave an Administration Console session unattended. While your Administration Console session is active others can gain access to it from your computer, without re-authentication.
A pie chart of the services with pipeline alerts over the past 30 minutes, which is the default alert history duration interval. To change the time interval for displaying historical alert data, see Section 27.3, "Setting User Preferences."
The number of pipeline alerts on the page match the pie chart which displays the breakdown of alerts by severity level, over the same time interval. You can click the area in the chart corresponding to the alert severity to display more details.
The top 10 services with pipeline alerts are listed in descending order of the number of alerts issued by those services. Each service name is a link to the service monitoring details. See Section 26.11, "Viewing Service Metrics."
Fields that display alert information depending on your customized settings for the alert table. For example, timestamp, alert summary, alert severity, action, and the names of the service and service type associated with the alert. To learn more about these fields, see Table 26-2.
An Annotation icon next to an alert summary indicates annotations. Positioning the mouse pointer over the icon previews the annotation text. Click the icon to view the entire annotation text.
A Table Customizer icon. See Section 2.2, "Customizing Table Views."
A link to the Extended Alert History page.
Table 26-2 Pipeline Alert History Information
| Property | Description |
|---|---|
|
Timestamp |
The date and time that the alert occurred. By default, all the alerts are sorted according to the timestamp. |
|
Alert Summary |
A short description of the pipeline alert action or Oracle Service Bus Alert (the default value provided to pipeline alert actions that were designed without alert summary text). The alert summary is a link to the Alert Details page. See Section 26.5, "Viewing Alert Details." An Annotation icon next to an alert summary indicates annotations. Positioning the mouse pointer over the icon previews the annotation text. |
|
Alert Severity |
The user-defined severity of the alert.
|
|
Service |
The name of the service associated with the alert. The name is a link to the Service Monitoring Details page (only when the service is being actively monitored). See Section 26.11, "Viewing Service Metrics." |
|
Service Type |
Only proxy services can define pipeline alerts, therefore, for pipeline alerts, all parent services are proxy services. |
|
Action |
The Edit Message Flow icon is a link to the Edit Message Flow page of that proxy service. |
To locate alerts:
Select Operations > Dashboard.
Select the SLA Alerts or Pipeline Alerts tab to display SLA or pipeline alerts.
Click the Extended Alert History link. The Extended SLA Alert History and Extended Pipeline Alert History pages display detailed alert history information.
To restrict the number of items in the list or locate specific alerts:
Click the Open icon to display additional search filters. If you specify multiple search criteria, only results that match all the criteria will be returned.
Filter by date range. Do one of the following:
Select All to ignore the date range and time interval filter criteria and display all alerts.
In the From and To fields, enter a date and time in the format MM/DD/YY HH:MM AM|PM, then click Search. The alerts that occurred over the specified date and time range are displayed.
In the For the Last field, enter the number of days, then specify hours and minutes, then click Search. The alerts that occurred over the specified time range are displayed.
Filter by alert severity. From the Alert Severity list, select to restrict alerts to the specified severity level, then click Search.
Select the or above check box to restrict your search to the specified severity level or above (listed from the most inclusive to the most restrictive level): Normal, Warning, Minor, Major, Critical, and Fatal.
Filter by parent Service. Click Browse to display the Select Service page. Select the parent service from the list and click Submit. Click Clear to remove the parent service filter criteria, or click Search.
For SLA alerts only, filter by Alert Name (Any String). Enter any string, including wildcard characters, then click Search. For more details, see Section 26.3.1, "WebLogic Diagnostics Framework Query Language."
For pipeline alerts only, filter by Alert Summary (Any String). Enter any string, including wildcard characters, then click Search. For more details, see Section 26.3.1, "WebLogic Diagnostics Framework Query Language." To find pipeline alert actions that were designed without alert summary text, enter Oracle Service Bus Alert.
Click View All to remove the search filters and display all alerts.
Use the Extended SLA Alert History and Extended Pipeline Alert History pages also to do the following:
To display the alert data in a pie chart, select Pie Chart View.
To display the same data in a bar chart, select Bar Chart View.
To display the data in tabular format, select Table View.
To display an updated version of the data, click Refresh.
To delete individual alerts, select the corresponding check boxes and click Delete at the bottom of the page.
To delete all alerts or those that were issued within a specified date and time range, click the Purge Alert History link at the top of the page. See Section 26.4, "Purging Alerts."
Alerts are stored using the WebLogic Diagnostics Framework, which provides its own query language, including wildcards. For filtering alerts in extended alert history, use the syntax described in "WLDF Query Language" in Oracle Fusion Middleware Configuring and Using the Diagnostics Framework for Oracle WebLogic Server.
Use this page to permanently delete the specified SLA or pipeline alerts.
Note:
This action cannot be undone.Select Operations > Dashboard.
Select the SLA Alerts or Pipeline Alerts tab, then click the Extended Alert History link.
On the upper right-hand side of the Extended Alert History page, click Purge SLA Alert History or Purge Pipeline Alert History.
Do one of the following steps, shown in Table 26-3.
Table 26-3 Alert Purging Options
| To... | Complete These Steps... |
|---|---|
|
Purge all SLA or pipeline alerts |
|
|
Purge SLA or pipeline alerts within a specified time frame |
|
Note:
If the server from which the alerts are being purged is unavailable, the logging framework persists a record of the purge and polls the server every 30 minutes to check its availability. When the logging framework finds the server available, it purges the alert(s).This page displays details of specific alerts including the information shown in Table 26-4.
| Property | Description |
|---|---|
|
Alert Name |
For SLA alerts only: The name assigned to the alert. The name is a link to the Alert Rule Configuration page. See Section 26.24, "Viewing Alert Rule Configurations." |
|
Alert Summary |
For pipeline alerts only: A short description of the pipeline alert action or Oracle Service Bus Alert (the default value provided to pipeline alert actions that were designed without alert summary text). |
|
Description |
A description for the alert rule. |
|
Timestamp |
|
|
Severity |
The user-defined severity of the alert.
|
|
Service |
The name and path of the service associated with this alert. The field is a link to the Service Monitoring Details page (only when the service is being actively monitored). See Section 26.11, "Viewing Service Metrics." |
|
Service Type |
The parent service type: proxy service or business service. Only proxy services can define pipeline alerts, therefore, for pipeline alerts, all parent services are proxy services. |
|
Server |
The name of the server in which this alert was generated. For SLA alerts only: N/A is displayed. |
|
Annotation |
A text box in which you can enter notes for this alert. An Annotation icon is displayed in the Alert History for alerts with annotations. |
The Service Health page displays metrics for services that have monitoring enabled. To learn how to enable monitoring for services, see Section 26.8, "Configuring Operational Settings for Proxy Services" and Section 26.9, "Configuring Operational Settings for Business Services."
By default, the Dashboard refresh rate is No Refresh. To change the Dashboard refresh rate interval, see Section 27.3, "Setting User Preferences."
Caution:
By selecting a dashboard refresh rate interval other than the default (No Refresh), the browser refreshes the Dashboard at regular intervals. This prevents your session from timing out, even without you interacting with the Administration Console.Oracle recommends that you use the Dashboard refresh rate feature with caution. You should never leave an Administration Console session unattended. While your Administration Console session is active others can gain access to it from your computer, without re-authentication.
On the Service Health tab header, these icons may be present:
A Warning icon and numeric indicator.
Click the icon to filter the services displayed using Has Errors criteria.
The number indicates the number of services with errors since the page was last refreshed.
An Endpoints Offline icon and numeric indicator.
Click the icon to filter the services displayed using Has Offline Endpoint URIs criteria.
The number indicates the number of services with endpoints that have become offline since the page was last refreshed.
The Service Health page displays service metrics and monitoring information, shown in Table 26-5.
In the Display Statistics field, do one of the following:
To display monitoring statistics for each service for the period of the current aggregation interval, select Current Aggregation Interval. The Current Aggregation Interval view displays a moving statistic view of the service metrics.
To display monitoring statistics for the period since you last reset statistics for a service, select Since Last Reset. The Since Last Reset view displays a running count of the metrics.
Select a Server from the list to display metrics for that server.
If a cluster exists, cluster-wide metrics are displayed by default. Select an individual Managed Server to display metrics for that server.
To restrict the number of items in the list or locate specific services:
Click the Open icon to display additional search filters. If you specify multiple search criteria, only results that match all the criteria will be returned.
Filter by service name. In the Name field, enter the name of the search target or enter wildcard characters (use * and ? as wildcard characters to perform a more general search), then click Search.
This search method is preferable if the name of the service is unique across all projects and paths.
Filter by service path. In the Path field, enter the path of the search target, which is the project name and the name of the folder in which services reside. You can use * and ? as wildcard characters to perform a more general search. All the services that reside in that path are displayed.
The format for the Path field is as follows:
project-name/root-folder/ . . ./parent-folder
If a service is directly under the project, the format is as follows: project-name
Filter by service name and path. This search method is preferable if there is more than one service with the same name that reside in different paths.
Filter by parent service. From the Service list, select the parent service type: Proxy Services or Business Services, then click Search. Select All Services to ignore the parent service filter criteria.
Filter by services with messages. Select the Has Messages option, then click Search.
Filter by services with alerts. Select the Has Alerts option, then click Search.
Filter by services with errors. Select the Has Errors option, then click Search.
Filter by services with offline URIs. Select the Has Offline Endpoint URIs option, then click Search.
Filter by services invoked by a particular proxy service. Enter the name and path of a proxy service in the field provided or click Browse to display the Select Proxy Service page. Select the proxy service from the list and click Submit. Click Search. The business services invoked by the proxy service you specified are displayed.
Wildcard characters are not supported in the Invoked by Proxy field.
Click View All to remove the search filters and display all services.
Table 26-5 Service Monitoring Information
| Property | Description |
|---|---|
|
Name |
The name assigned to the service. The name is a link to the Service Monitoring Details page. See Section 26.11, "Viewing Service Metrics." |
|
Path |
The project associated with the service. If the service resides in a project folder, this folder is also listed. The path is displayed in the format: project-name/root-folder/ . . ./parent-folder The path is a link to the corresponding path in the Project Explorer. |
|
Service Type |
The parent service type: proxy service or business service. |
|
Aggregation Interval |
This field is displayed only when you have selected Current Aggregation Interval in the Display Statistics field. The current aggregation interval set for monitoring this service, in terms of hours and minutes. You set this interval on the Operational Settings page. See Section 26.10, "Setting the Aggregation Interval for a Service." |
|
Avg. Response Time |
The average response time (in msec) that this service has taken to execute messages within the period of the current aggregation interval or for the period since the last reset. |
|
Messages |
The number of messages associated with this service for the period of the current aggregation interval or for the period since the last reset. |
|
Errors |
The number of error messages associated with this service for the period of the current aggregation interval or for the period since the last reset. |
|
Alerts |
This field is hidden by default. The number of alerts (SLA and pipeline) associated with this service for the period of the current aggregation interval or for the period since the last reset. For an individual Managed Server in a cluster, for proxy services, it shows the number of pipeline alerts only associated with this service for the period of the current aggregation interval or for the period since the last reset. For business services, for individual Managed Servers, displays N/A. |
|
SLA Alerts |
The number of SLA alerts associated with this service for the period of the current aggregation interval or for the period since the last reset. For an individual Managed Server in a cluster, SLA Alerts will be N/A (only cluster-wide SLA alerts are displayed). |
|
Pipeline Alerts |
For proxy services only: The number of pipeline alerts associated with this service for the period of the current aggregation interval or for the period since the last reset. |
|
Endpoint URI Status |
For business services only, the status of endpoint URIs. The status is a link to the Endpoint URIs page. See Section 26.15, "Viewing Business Services Endpoint URIs Metrics." For a single node domain (individual server instances):
For a clustered domain:
|
|
Action |
This field is displayed only when you have selected Since Last Reset in the Display Statistics field. In this column, you can click the Reset icon for a specific service to reset the statistics for that service. When you confirm you want to do this, the system deletes all monitoring statistics that were collected for the service since you last reset statistics. However, the system does not delete the statistics being collected during the Current Aggregation Interval for the service. Additionally, after you click the Reset icon, the system immediately starts collecting monitoring statistics for the service again. |
You can use the Service Health page to reset monitoring statistics for all services in your configuration. You can reset statistics whether you are in a session.
Select Operations > Dashboard > Service Health.
In the Display Statistics field, select Since Last Reset. The Since Last Reset view displays a running count view of the metrics.
To reset the monitoring statistics for a specific service, click the Reset icon in the Action column for that service.
When you confirm that you want to do this, the system deletes all monitoring statistics that were collected for the service since you last reset statistics. However, the system does not delete the statistics being collected during the Current Aggregation Interval for the service. Additionally, after you click the Reset icon, the system immediately starts collecting monitoring statistics for the service again.
To reset monitoring statistics for all services, click the Reset All Statistics link at the top of the page.
Note:
Clicking Reset All Statistics resets the statistics for all monitored services regardless of whether they are displayed on the page or not.When you confirm that you want to reset statistics, the system deletes all monitoring statistics that were collected for all services in your configuration since you last reset statistics. The system does not delete the statistics being collected during the Current Aggregation Interval for any of the services. Additionally, after you click Reset All Statistics, the system immediately starts collecting monitoring statistics for the services again.
Use the Operational Settings page to enable and disable a proxy service and monitoring for specific proxy services. Similarly, you can specify these same service-specific operational settings on the Operations > Smart Search page, with the following exceptions: you cannot set an aggregation interval or specify an alerting or logging severity level. For more information, see Section 27.1, "Finding and Updating Operational Settings."
The runtime effects of the service-level settings depend on their corresponding global settings. You must enable both the global and service-level settings for a service to be completely enabled at runtime. Additionally, the Service State must also be enabled. See Section 27.2, "Enabling Global Settings."
You can change and save monitoring configuration settings even if the service will be not be enabled at runtime. For example, you can change and save the Aggregation Interval even if Service Monitoring is disabled. In this manner, you can edit settings and later enable them.
If you have not already done so, click Create to create a new session or click Edit to enter an existing session. See Section 3.1, "Using the Change Center."
Select Resource Browser > Proxy Services.
Click the proxy service name.
The View a Proxy Service page displays the information shown in Table 26-6.
Table 26-6 Proxy Service Information
| Property | Description |
|---|---|
|
Last Modified By |
The user who created or edited this service, or imported it into the configuration. |
|
Last Modified On |
The date and time that the user created or edited this service, or imported it into the configuration. Click the date and time link to view the change history of this resource. See Section 4.23, "View Change History Page." |
|
References |
The number of objects that this service references. If such references exist, click the numeric link to view a list of the objects. See Section 4.22, "Viewing References to Resources." |
|
Referenced By |
The number of objects that reference this service. If such references exist, click the numeric link to view a list of the objects. See Section 4.22, "Viewing References to Resources." |
|
Description |
A description of the service, if one exists. |
Select the Operational Settings tab.
You must be in an active session to configure proxy service operational settings shown in Table 26-7.
Table 26-7 Configuring Proxy Service Operational Settings
| To... | Do This... |
|---|---|
|
Disable State |
Clear the Enabled check box. When you activate the session, the service stops processing messages. Disabling a service no longer causes the system to delete all monitoring statistics previously collected for the service. |
|
Enable State |
Select the Enabled check box. When you activate the session, the service resumes processing messages. |
|
Disable Monitoring |
Clear the Enabled check box. When you activate the session, the system stops collecting monitoring statistics for the service, and deletes any statistics collected previously. |
|
Enable Monitoring |
Select the Enabled check box next to Monitoring. From the Enable Pipeline Monitoring at list, select to restrict monitoring to the specified level or above (listed from the most inclusive to the most restrictive level): Action, Pipeline, and Service. When you activate the session, the system starts collecting monitoring statistics for the service. |
|
Set an Aggregation Interval for a service |
Select the interval in terms of hours or minutes, then click Update. If your selection for hours exceeds 1, then the default selection for minutes is always zero. However, if your selection for hours is 0 or 1, then you can configure intervals in terms of minutes. See Section 26.10, "Setting the Aggregation Interval for a Service." You can change and save the Aggregation Interval setting whether or not you have enabled monitoring. To enable monitoring at runtime, make sure the Enable Monitoring check box is selected. |
|
Disable SLA Alerts |
Clear the Enabled check box. The system stops evaluating any alert rules configured for the service; therefore, you no longer receive SLA alerts associated with the service. |
|
Enable SLA Alerts |
Select the Enabled check box. From the Enable Alerting at list, select to restrict SLA alerts to the specified level or above (listed from the most inclusive to the most restrictive level): Normal (default), Warning, Minor, Major, Critical, and Fatal. Service SLA alerting depends on both the global and service-level monitoring states—both must be enabled for SLA alerting to be enabled at runtime. See Section 27.2.3, "Enabling SLA Alerts Globally." |
|
Disable Pipeline Alerts |
Clear the Enabled check box. When you activate the session, the system stops executing pipeline alert actions; therefore, you no longer receive pipeline alerts associated with the service. |
|
Enable Pipeline Alerts |
Select the Enabled check box. From the Enable Alerting at list, select to restrict pipeline alerts to the specified severity level or above (listed from the most inclusive to the most restrictive level): Normal (default), Warning, Minor, Major, Critical, and Fatal. |
|
Disable the report action of a proxy service |
Clear the Enabled check box next to Message Reporting. When you activate the session, the system stops executing report actions; therefore, you no longer receive message reporting associated with the service. |
|
Enable the report action of a proxy service |
Select the Enabled check box next to Message Reporting. |
|
Disable logging output for a pipeline log action |
Clear the Enabled check box next to Logging. When you activate the session, the system stops executing log actions; therefore, you no longer receive logging output associated with the service. |
|
Enable logging output for a pipeline log action |
Select the Enabled check box next to Logging. From the Enable Logging at list, choose to restrict logging output to the specified level or above (listed from the most inclusive to the most restrictive level): Debug (default), Info, Warning, and Error. |
|
Enable runtime execution tracing for a proxy service |
Select the Enabled check box next to Execution Tracing. After you enable execution tracing, the system logs various details culled from the Message Flow Context and the Message Context. These details include: stage name; pipeline or route node name; and the current Message Context. Note: To see tracing in the log file or standard out (server console), Oracle WebLogic Server logging must be set to the following severity levels:
For information on setting log severity levels, see "Using Log Severity Levels" in Oracle Fusion Middleware Configuring Log Files and Filtering Log Messages for Oracle WebLogic Server. |
|
Disable runtime tracing for a proxy service |
Clear the Enabled check box next to Execution Tracing. |
|
Enable message tracing for a proxy service |
Select the Enabled check box next to Message Tracing. After you enable message tracing, the system logs messages exchanged between the Oracle Service Bus pipeline and the proxy service (inbound request and response, as well as outbound request and response messages). Note: To see tracing in the log file or standard out (server console), Oracle WebLogic Server logging must be set to the following severity levels:
For information on setting log severity levels, see "Using Log Severity Levels" in Oracle Fusion Middleware Configuring Log Files and Filtering Log Messages for Oracle WebLogic Server. When applicable, logged outbound messages can also include the retry number, error code, and error message. From the Detail Level list, choose to specify the level of detail from among the following:
If you choose Full from the Detail Level list, specify the maximum size (in kilobytes) for the message payload using the Payload Tracing Limit field. Also, specify the default encoding for logging the payload using the Default Encoding field. This can be useful when logging binary payloads or SOAP messages with binary attachments. The default encoding value can be Base64 or any Java-supported encoding as defined in: Leaving the Default Encoding field empty causes Oracle Service Bus to use the host's default encoding for the payload. The default encoding depends on a combination of the JVM, the underlying operating system (OS), and OS-level locale settings. If the setting specified in the Default Encoding field cannot be used (for example, it is not a valid option for the configuration), then Oracle Service Bus uses Base64 encoding for the payload. |
|
Disable message tracing for a proxy service |
Clear the Enabled check box next to Message Tracing. |
Use the Operational Settings page to enable and disable a business service and monitoring for specific business services. Similarly, you can specify these same service-specific operational settings on the Operations > Smart Search page, with the following exceptions: you cannot set an aggregation interval or specify an alerting severity level. For more information, see Section 27.1, "Finding and Updating Operational Settings."
The runtime effects of the service-level settings depend on their corresponding global settings. You must enable both the global and service-level settings for a service to be completely enabled at runtime. Additionally, the Service State must also be enabled. See Section 27.2, "Enabling Global Settings."
You can change and save monitoring configuration settings even if the service will be not be enabled at runtime. For example, you can change and save the Aggregation Interval even if Service Monitoring is disabled. In this manner, you can edit settings and later enable them.
If you have not already done so, click Create to create a new session or click Edit to enter an existing session. See Section 3.1, "Using the Change Center."
Select Resource Browser > Business Services.
Click the business service name.
The View a Business Service page displays the information shown in Table 26-8.
Table 26-8 Business Service Information
| Property | Description |
|---|---|
|
Last Modified By |
The user who created or edited this service, or imported it into the configuration. |
|
Last Modified On |
The date and time that the user created or edited this service, or imported it into the configuration. Click the date and time link to view the change history of this resource. See Section 4.23, "View Change History Page."Section 4.23, "View Change History Page." |
|
References |
The number of objects that this service references. If such references exist, click the numeric link to view a list of the objects. See Section 4.22, "Viewing References to Resources." |
|
Referenced By |
The number of objects that reference this service. If such references exist, click the numeric link to view a list of the objects. See Section 4.22, "Viewing References to Resources." |
|
Description |
A description of the service, if one exists. |
Select the Operational Settings tab.
You must be in an active session to configure business service operational settings shown in Table 26-9.
Table 26-9 Configuring Business Service Operational Settings
| To... | Do This... |
|---|---|
|
Disable State |
Clear the Enabled check box. When you activate the session, the service stops processing messages. Disabling a service no longer causes the system to delete all monitoring statistics previously collected for the service. |
|
Enable State |
Select the Enabled check box. When you activate the session, the service resumes processing messages. |
|
Enable business service endpoint URIs to be taken offline Set a retry interval for offline URIs |
Select the Enable with Retry Interval check box. When you select this option, the business service removes non-responsive endpoint URIs (takes them offline), at runtime, so that only the responsive URIs are used for retry attempts and for processing subsequent requests. To keep non-responsive URIs offline until you take corrective action and then re-enable the URIs, do not provide a retry interval. For example, a zero retry interval indicates that the endpoint remains offline indefinitely. To bring it back online, use the Mark Endpoint Online action on the Endpoint URIs page. See Section 26.15, "Viewing Business Services Endpoint URIs Metrics." To configure the business service to take non-responsive URIs offline and then re-attempt accessing the same URI endpoint for subsequent message processing after a specified time interval, you do so by specifying a retry interval value. Use the hours, minutes, and seconds fields to specify how long to keep the non-responsive URIs out of the active URIs processing loop. The URI is kept offline for the specified time interval and then retried. If the endpoint responds, the URI becomes online again, or else it remains offline and the process repeats itself. You can specify a retry interval only if you have selected the Enable with Retry Interval option. |
|
Disable Monitoring |
Clear the Enabled check box. When you activate the session, the system stops collecting monitoring statistics for the service, and deletes any statistics collected previously. |
|
Enable Monitoring |
Select the Enabled check box. When you activate the session, the system starts collecting monitoring statistics for the service. |
|
Set an Aggregation Interval for a service |
Select the interval in terms of hours or minutes, then click Update. If your selection for hours exceeds 1, then the default selection for minutes is always zero. However, if your selection for hours is 0 or 1, then you can configure intervals in terms of minutes. See Section 26.10, "Setting the Aggregation Interval for a Service." You can change and save the Aggregation Interval setting whether or not you have enabled monitoring. To enable monitoring at runtime, make sure the Enable Monitoring check box is selected. |
|
Disable SLA Alerts |
Clear the Enabled check box. The system stops evaluating any alert rules configured for the service; therefore, you no longer receive SLA alerts associated with the service. |
|
Enable SLA Alerts |
Select the Enabled check box. From the Enable Alerting at list, select to restrict SLA alerts to the specified level or above (listed from the most inclusive to the most restrictive level): Normal (default), Warning, Minor, Major, Critical, and Fatal. Service SLA alerting depends on both the global and service-level monitoring states—both must be enabled for SLA alerting to be enabled at runtime. See Section 27.2.3, "Enabling SLA Alerts Globally." |
|
Restrict the flow of messages sent to the set of endpoints configured in the business service |
Select the Enabled check box next to Throttling State. When enabled, messages are processed by priority. You can optionally assign messages a priority using routing options; otherwise, messages are de-queued on a first-in, first-out basis. For more information, see "Throttling" in the Oracle Fusion Middleware Administrator's Guide for Oracle Service Bus. |
|
Restrict the number of messages being dispatched to a set of endpoints configured in the business service |
If Throttling State is enabled, this field is required. Specify a Maximum Concurrency value; it must be a positive integer value, it cannot be zero. If exceeded, incoming messages are put into a wait (throttling) queue, if one exists. If not, the messages are discarded. If the queue is full, messages in the queue with a lower priority are removed and a runtime error is raised. If an error handler is configured, it will be triggered. The new incoming messages will be enqueued. |
|
Specify whether messages sent to business services that have exceeded their message concurrency limit should be held in a wait queue Set the maximum number of messages that are held in the wait queue |
If Throttling State is enabled, this field is required. Specify a Throttling Queue value; it must be a positive integer value or keep the default value, zero, meaning there is no throttling queue. When the throttling queue value is zero (no throttling queue) and the number of messages exceed the Maximum Concurrency value, the messages are discarded and an error is raised. If an error handler is configured, it will be triggered. If you disable throttling at runtime, all the messages in the throttling queue will be processed. When you delete or rename a business service, all the messages in the throttling queue are discarded. |
|
Specify the maximum length of time that messages will be held in a wait queue |
If Throttling State is enabled, this field is optional. Specify a Message Expiration value in milliseconds; it must be a positive integer value. A value of zero means the message will never be expired. This value is set at the queue level; all messages put in the queue have the same Message Expiration value. When exceeded, messages are removed from the queue without being processed. |
|
Enable message tracing for a business service |
Select the Enabled check box next to Message Tracing. After you enable message tracing, the system logs messages exchanged between the Oracle Service Bus pipeline and the business service (outbound request and response messages). Note: To see tracing in the log file or standard out (server console), Oracle WebLogic Server logging must be set to the following severity levels:
For information on setting log severity levels, see "Using Log Severity Levels" in Oracle Fusion Middleware Configuring Log Files and Filtering Log Messages for Oracle WebLogic Server. When applicable, logged outbound messages can also include the retry number, error code, and error message. From the Detail Level list, choose to specify the level of detail from among the following:
If you choose Full from the Detail Level list, specify the maximum size (in kilobytes) for the message payload using the Payload Tracing Limit field. Also, specify the default encoding for logging the payload using the Default Encoding field. This can be useful when logging binary payloads or SOAP messages with binary attachments. The default encoding value can be Base64 or any Java-supported encoding as defined in: Leaving the Default Encoding field empty causes Oracle Service Bus to use the host's default encoding for the payload. The default encoding depends on a combination of the JVM, the underlying operating system (OS), and OS-level locale settings. If the setting specified in the Default Encoding field cannot be used (for example, it is not a valid option for the configuration), then Oracle Service Bus uses Base64 encoding for the payload. |
|
Disable message tracing for a business service |
Clear the Enabled check box next to Message Tracing. |
|
Enabling and Disabling Result Caching |
Selecting Enabled activates result caching for the business service. You must also ensure that result caching is enabled globally. See Section 27.2.11, "Enabling Result Caching Globally." When you deselect the Enabled option and click Update to disable result caching for a business service, all results cached for that business service are flushed. |
Use the Operational Settings page to set the aggregation interval for a specific service. The aggregation interval is the period over which aggregated statistics are computed for display in the Administration Console. The default aggregation interval setting is 10 minutes.
If you have not already done so, click Create to create a new session or click Edit to enter an existing session. See Section 3.1, "Using the Change Center."
Select Resource Browser > Business Services or Proxy Services.
Click the service name.
Select the Operational Settings tab.
In the Aggregation Interval field, select the length of the aggregation interval in hours and minutes, then click Update.
If your selection for hours exceeds 1, then the default selection for minutes is always zero. However, if your selection for hours is 0 or 1, then you can configure intervals in terms of minutes.
Click Update to commit the updates in the current session.
To end the session and deploy the configuration to the runtime, click Activate under Change Center.
Use this page to view the monitoring details of specific services, shown in Table 26-9, and the Service Metrics shown in Table 26-11.
Table 26-10 Service Metric Information
| Property | Description |
|---|---|
|
Service Name |
The name and path of the service. |
|
Service Type |
The parent service type: proxy service or business service. |
|
Display Statistics |
To display monitoring statistics for the service for the period of the current aggregation interval, select Current Aggregation Interval. The Current Aggregation Interval view displays a moving statistic view of the service metrics. To display monitoring statistics for this service for the period since you last reset statistics, select Since Last Reset. The Since Last Reset view displays a running count view of the metrics. |
|
Server |
Select a server from the list to display metrics for that server. If a cluster exists, cluster-wide metrics are displayed by default. Select an individual Managed Server to display metrics for that server. If you display metrics for an individual Managed Server in a cluster, the SLA Alert Count will be N/A (only cluster-wide SLA Alert Counts are displayed). |
|
Aggregation Interval |
If you have selected Current Aggregation Interval in the Display Statistics field, the current aggregation interval set for monitoring this service, in terms of hours and minutes. You set this interval on the Operational Settings page. See Section 26.10, "Setting the Aggregation Interval for a Service." |
|
Reset Statistics |
If you have selected Since Last Reset in the Display Statistics field, you can reset the monitoring statistics for this service. Click Reset Statistics at the bottom of the page. |
| Property | Description |
|---|---|
|
SLA Alert Count |
|
|
Pipeline Alert Count |
For proxy services only:
|
|
Min Response Time |
If you have selected Current Aggregation Interval in the Display Statistics field, the minimum response time this service has taken to execute messages within the period of the current aggregation interval. If you have selected Since Last Reset in the Display Statistics field, the minimum response time this service has taken to execute messages within the period since you last reset statistics. |
|
Max Response Time |
If you have selected Current Aggregation Interval in the Display Statistics field, the maximum response time this service has taken to execute messages within the period of the current aggregation interval. If you have selected Since Last Reset in the Display Statistics field, the maximum response time this service has taken to execute messages within the period since you last reset statistics. |
|
Overall Avg. Response Time |
If you have selected Current Aggregation Interval in the Display Statistics field, the overall average time (in milliseconds) this service has taken to execute messages within the period of the current aggregation interval. If you have selected Since Last Reset in the Display Statistics field, the overall average time this service has taken to execute messages within the period since you last reset statistics. |
|
Message Count |
If you have selected Current Aggregation Interval in the Display Statistics field, the total number of messages that this service has executed within the period of the current aggregation interval. If you have selected Since Last Reset in the Display Statistics field, the total number of messages that this service has executed within the period since you last reset statistics. |
|
Error Count |
If you have selected Current Aggregation Interval in the Display Statistics field, the number of error messages that this service has executed within the period of the current aggregation interval. If you have selected Since Last Reset in the Display Statistics field, the number of messages with errors that this service has executed within the period since you last reset statistics. |
|
Failover Count |
For business services only: If you have selected Current Aggregation Interval in the Display Statistics field, the number of failovers that this service has attempted within the period of the current aggregation interval. If you have selected Since Last Reset in the Display Statistics field, the number of failovers that this service has attempted within the period since you last reset statistics. |
|
Success Ratio |
If you have selected Current Aggregation Interval in the Display Statistics field, the success ratio of this service within the period of the current aggregation interval. If you have selected Since Last Reset in the Display Statistics field, the success ratio of this service within the period since you last reset statistics. For example, if the service has executed 9 out of 10 messages successfully, then the success ratio is 90%. |
|
Failure Ratio |
If you have selected Current Aggregation Interval in the Display Statistics field, the failure ratio of this service within the period of the current aggregation interval. If you have selected Since Last Reset in the Display Statistics field, the failure ratio of this service within the period since you last reset statistics. For example, if the service has failed to execute 1 out of 10 messages, then the failure ratio is 10%. |
|
WS Security Errors |
If you have selected Current Aggregation Interval in the Display Statistics field, the number of messages with WS security errors that this service has executed within the period of the current aggregation interval. If you have selected Since Last Reset in the Display Statistics field, the number of messages with WS security errors that this service has executed within the period since you last reset statistics. |
|
Validation Errors |
For business services: N/A is displayed. For proxy services: If you have selected Current Aggregation Interval in the Display Statistics field, the number of messages with validation errors that this service has executed within the period of the current aggregation interval. If you have selected Since Last Reset in the Display Statistics field, the number of messages with validation errors that this service has executed within the period since you last reset statistics. |
|
Hit Count |
For business services only: Hit Count displays the number of times a business service result cache has been used. |
|
Hit Ratio |
The sum of Hit Count and Message Count. |
|
Min Throttling Time |
For business services only: If you have selected Current Aggregation Interval in the Display Statistics field, the least amount of time that messages have spent in a throttling queue within the period of the current aggregation interval. If you have selected Since Last Reset in the Display Statistics field, the least amount of time that messages have spent in a throttling queue within the period since you last reset statistics. |
|
Max Throttling Time |
For business services only: If you have selected Current Aggregation Interval in the Display Statistics field, the maximum amount of time that messages have spent in a throttling queue within the period of the current aggregation interval. If you have selected Since Last Reset in the Display Statistics field, the maximum amount of time that messages have spent in a throttling queue within the period since you last reset statistics. |
|
Average Throttling Time |
For business services only: If you have selected Current Aggregation Interval in the Display Statistics field, the average amount of time that messages have spent in a throttling queue within the period of the current aggregation interval. If you have selected Since Last Reset in the Display Statistics field, the average amount of time that messages have spent in a throttling queue within the period since you last reset statistics. |
Use this page to view the service monitoring information, shown in Table 26-10, and the Operations metrics for WSDL-based services, shown in Table 26-12.
Table 26-12 Operations Metrics
| Property | Description |
|---|---|
|
Operation Name |
The name of the operation associated with this service. |
|
Message Count |
If you have selected Current Aggregation Interval in the Display Statistics field, the total number of messages that this operation has executed within the period of the current aggregation interval. If you have selected Since Last Reset in the Display Statistics field, the total number of messages that this operation has executed within the period since you last reset statistics. |
|
Error Count |
If you have selected Current Aggregation Interval in the Display Statistics field, the number of messages with errors that this operation has executed within the period of the current aggregation interval. If you have selected Since Last Reset in the Display Statistics field, the number of messages with errors that this operation has executed within the period since you last reset statistics. |
|
Min Response Time |
If you have selected Current Aggregation Interval in the Display Statistics field, the minimum response time this operation has taken to execute messages within the period of the current aggregation interval. If you have selected Since Last Reset in the Display Statistics field, the minimum response time this operation has taken to execute messages within the period since you last reset statistics. |
|
Max Response Time |
If you have selected Current Aggregation Interval in the Display Statistics field, the maximum response time this operation has taken to execute messages within the period of the current aggregation interval. If you have selected Since Last Reset in the Display Statistics field, the maximum response time this operation has taken to execute messages within the period since you last reset statistics. |
|
Avg. Response Time |
If you have selected Current Aggregation Interval in the Display Statistics field, the overall average time this operation has taken to execute messages within the period of the current aggregation interval. If you have selected Since Last Reset in the Display Statistics field, the overall average time this operation has taken to execute messages within the period since you last reset statistics. |
Use this page to view the service monitoring information, shown in Table 26-10, and the Pipeline metrics for proxy services that have pipelines, shown in Table 26-13.
| Property | Description |
|---|---|
|
Component Name |
The name of the component. |
|
Message Count |
If you have selected Current Aggregation Interval in the Display Statistics field, the total number of messages that this component has executed within the period of the current aggregation interval. If you have selected Since Last Reset in the Display Statistics field, the total number of messages that this component has executed within the period since you last reset statistics. |
|
Error Count |
If you have selected Current Aggregation Interval in the Display Statistics field, the number of messages with errors that this component has executed within the period of the current aggregation interval. If you have selected Since Last Reset in the Display Statistics field, the number of messages with errors that this component has executed within the period since you last reset statistics. |
|
Min Response Time |
If you have selected Current Aggregation Interval in the Display Statistics field, the minimum response time this component has taken to execute messages within the period of the current aggregation interval. If you have selected Since Last Reset in the Display Statistics field, the minimum response time this component has taken to execute messages within the period since you last reset statistics. |
|
Max Response Time |
If you have selected Current Aggregation Interval in the Display Statistics field, the maximum response time this component has taken to execute messages within the period of the current aggregation interval. If you have selected Since Last Reset in the Display Statistics field, the maximum response time this component has taken to execute messages within the period since you last reset statistics. |
|
Avg. Response Time (msecs) |
If you have selected Current Aggregation Interval in the Display Statistics field, the overall average time this component has taken to execute messages within the period of the current aggregation interval. If you have selected Since Last Reset in the Display Statistics field, the overall average time this component has taken to execute messages within the period since you last reset statistics. |
Use this page to view the service monitoring information, shown in Table 26-10, and the Action metrics for proxy services that have pipelines, shown in Table 26-14.
| Property | Description |
|---|---|
|
Node |
A hierarchical display of the nested actions. |
|
Count |
If you have selected Current Aggregation Interval in the Display Statistics field, the number of invocations within the period of the current aggregation interval. If you have selected Since Last Reset in the Display Statistics field, the number of invocations within the period since you last reset statistics. This is different than the number of messages since an action can be invoked many times per message. |
|
Avg. Time |
If you have selected Current Aggregation Interval in the Display Statistics field, the average execution time per invocation within the period of the current aggregation interval. If you have selected Since Last Reset in the Display Statistics field, the average execution time per invocation within the period since you last reset statistics. |
|
Total Time |
If you have selected Current Aggregation Interval in the Display Statistics field, the total execution time within the period of the current aggregation interval. If you have selected Since Last Reset in the Display Statistics field, the total execution time within the period since you last reset statistics. |
Use this page to view the service monitoring information, shown in Table 26-10, and the Endpoint URIs metrics for business services, shown in Table 26-15. For more information, see "Managing Endpoint URIs for Business Services" in the Oracle Fusion Middleware Administrator's Guide for Oracle Service Bus.
Table 26-15 Endpoint URIs Metrics
| Property | Description |
|---|---|
|
Endpoint URI |
The endpoint URL associated with this business service. |
|
Message Count |
If you have selected Current Aggregation Interval in the Display Statistics field, the total number of messages executed by this endpoint URI within the period of the current aggregation interval. If you have selected Since Last Reset in the Display Statistics field, the total number of messages executed by this endpoint URI within the period since you last reset statistics. |
|
Error Count |
If you have selected Current Aggregation Interval in the Display Statistics field, the number of messages with errors executed by this endpoint URI within the period of the current aggregation interval. If you have selected Since Last Reset in the Display Statistics field, the number of messages with errors executed by this endpoint URI within the period since you last reset statistics. |
|
Min Response Time |
If you have selected Current Aggregation Interval in the Display Statistics field, the minimum response time this endpoint URI has taken to execute messages within the period of the current aggregation interval. If you have selected Since Last Reset in the Display Statistics field, the minimum response time this endpoint URI has taken to execute messages within the period since you last reset statistics. |
|
Max Response Time |
If you have selected Current Aggregation Interval in the Display Statistics field, the maximum response time this endpoint URI has taken to execute messages within the period of the current aggregation interval. If you have selected Since Last Reset in the Display Statistics field, the maximum response time this endpoint URI has taken to execute messages within the period since you last reset statistics. |
|
Avg. Response Time |
If you have selected Current Aggregation Interval in the Display Statistics field, the overall average time this endpoint URI has taken to execute messages within the period of the current aggregation interval. If you have selected Since Last Reset in the Display Statistics field, the overall average time this endpoint URI has taken to execute messages within the period since you last reset statistics. |
|
Status |
The status of the business service endpoint URI. For single server domains or for an individual Managed Server in a cluster: Online or Offline. For cluster-level statistics: Online, Offline, or Partial, when that particular URI is offline on at least one of the Managed Servers in the cluster. |
|
Action |
Click the Mark Endpoint Online icon to mark an offline URI, Online. This action is enabled only if the URI has an Offline or Partial status. To enable this action, a business service must be enabled for taking URIs offline and its service and global-level monitoring operational settings must be enabled. See Section 26.9, "Configuring Operational Settings for Business Services." Note: If successful, the action is immediate. However, reflecting that its endpoint URI status is now online takes one monitoring aggregation cycle, which might take as long as 1 minute and a half. |
The Server Health page includes the following:
On the Server Health tab header, a Shutdown icon and numeric indicator which shows the number of servers that are shutdown, may be present:
Click the icon to filter the servers displayed using the Shutdown Health criteria and SHUTDOWN State criteria.
The number indicates the number of shutdown servers.
A pie chart that depicts the health of the servers in the domain. You can click the area in the chart that corresponds to the server to display more details.
The Log Summary. To display the log, click the numeric link that displays the number of messages for a given severity. For example, Alert:1, click the number 1. See Section 26.20, "Viewing Details of Domain Log Files."
Fields that display server information, depending on your customized settings for the Server Summary table. For example, server name, health, cluster name, computer name, the state of the server, and the length of time the server has been running. To learn more about these fields, see Table 26-16.
By default, the Dashboard refresh rate is No Refresh. To change the Dashboard refresh rate interval, see Section 27.3, "Setting User Preferences."
Caution:
By selecting a dashboard refresh rate interval other than the default (No Refresh), the browser refreshes the Dashboard at regular intervals. This prevents your session from timing out, even without you interacting with the Administration Console.Oracle recommends that you use the Dashboard refresh rate feature with caution. You should never leave an Administration Console session unattended. While your Administration Console session is active others can gain access to it from your computer, without re-authentication.
A Table Customizer icon. See Section 2.2, "Customizing Table Views."
To restrict the number of items in the list or locate specific servers:
Click the Open icon to display additional search filters. If you specify multiple search criteria, only results that match all the criteria will be returned.
Filter by health status. From the Health list, select to restrict servers to the specified health status level, then click Search.
Select the or above check box to restrict your search to the specified server health status level or above (listed from the most inclusive to the most restrictive level): OK, Warning, Overloaded, Critical, and Fatal.
Filter by server. From the Server list, select All or the name of the server, then click Search.
Filter by cluster name. From the Cluster Name list, select All or the name of the cluster associated with the server, then click Search.
Filter by computer name. From the Machine Name list, select All or the name of the computer associated with the server, then click Search.
Filter by state. From the State list, select All or the state of the server: RUNNING, FAILED, or SHUTDOWN, then click Search.
Click View All to remove the search filters and display all servers.
The Server Health page displays the following information for each server, shown in Table 26-16, depending on the filter settings you have specified.
Table 26-16 Server Summary Details
| Property | Description |
|---|---|
|
Server |
The name of the server. The name is a link to the View Server Details page. See Section 26.17, "Viewing Server Details." |
|
Health |
The health status of the server:
|
|
Cluster Name |
The name of the cluster associated with this server. |
|
Machine Name |
The name of the computer associated with this server. |
|
State |
The state of the server:
|
|
Uptime |
The length of time this server has been running. |
The objects displayed on this page are WebLogic Server entities. To learn more about these entities, see the Oracle Fusion Middleware Oracle WebLogic Server Administration Console Online Help.
This page displays a summary of domain log file entries, including the information shown in Table 26-17.
To customize the display of domain log file information, see Section 26.19, "Customizing Your View of Domain Log File Entries."
To display details of a specific log file, select the option for the appropriate entry, then click View. See Section 26.20, "Viewing Details of Domain Log Files."
To customize the view of domain log file entries:
Click Customize this table. Additional fields are displayed.
You can click the Customize this table link at any time to close this table and retain the original settings.
In the Filter fields, do the following:
In the Time field, select the time interval for which you want to view log entries.
In the Start Time field, enter a start time in the format MM/DD/YYYY HH:MM:SS. For example, enter 10/25/06 08:39:48. You use the Start Time and End Time fields to specify a window of time for which you want to view log entries.
In the End Time field, enter a end time in the format MM/DD/YYYY HH:MM:SS. For example, enter 10/25/06 13:20:51. You use the Start Time and End Time fields to specify a window of time for which you want to view log entries.
In the Criteria text box, specify a filtering criteria (a text string). The filtering criteria is specified as a string in the WLDF Query Language. The query language supports Boolean operators: AND, OR, and NOT, and relational operators. For more information on query syntax, see "WLDF Query Language" in Oracle Fusion Middleware Configuring and Using the Diagnostics Framework for Oracle WebLogic Server.
In the Columns field, select the columns you want to display:
Select a column name from the Available field.
Click the arrow to move this column name to the Chosen field.
Repeat until you have listed all the column names you want to display in the Chosen field.
In the Chosen field, you can use the Up and Down arrows to reorder the column names as required.
In the Number of rows displayed per page field, select the number of log entries you want to display on a single page.
In the Maximum Results Returned field, select the maximum number of log entries you want to display in total or select Show All to display all of them.
Do one of the following:
To save the new settings, click Apply.
To discard your changes and retain the original settings, click Reset.
Use this page to view details of domain log file entries, shown in Table 26-18.
Table 26-18 Domain Log Details
| Property | Description |
|---|---|
|
Message |
A description of the event or condition. |
|
Date |
Displays the time and date when the message originated, in a format that is specific to the locale. The Java Virtual Machine (JVM) that runs each WebLogic Server instance refers to the host computer operating system for information about the local time zone and format. |
|
Subsystem |
Indicates the subsystem of WebLogic Server that was the source of the message; for example, Enterprise Java Bean (EJB) container or Java Messaging Service (JMS). |
|
Message ID |
A unique six-digit identifier. All message IDs that WebLogic Server system messages generate start with BEA- and fall within a numerical range of 0-499999. |
|
Severity |
Indicates the degree of impact or seriousness of the event reported by the message:
|
|
Machine |
The DNS name of the computer that hosts the server instance. |
|
Server |
The name of the WebLogic Server instance on which the message was generated. |
|
Thread |
The ID that the JVM assigns to the thread in which the message originated. |
|
User ID |
The user ID under which the associated event was executed. |
|
Transaction ID |
Present only for messages logged within the context of a transaction. |
|
Context ID |
Context information to correlate messages coming from a specific request or application. |
|
Detail |
A description of the event or condition. |
|
Cause |
The cause of the message. |
|
Action |
The action that should be taken. |
Use this page to view the alert rules information shown in Table 26-19.
Table 26-19 Alert Rules Information
| Property | Description |
|---|---|
|
Name |
The name assigned to this alert rule. The name is a link to the Alert Rule General Configuration page. See Section 26.24, "Viewing Alert Rule Configurations." |
|
SLA State |
The status of the alert rule: Enabled or Disabled. |
|
Description |
This field is hidden by default. A description of the alert rule. |
|
Severity |
The severity of the alert that will be triggered by this rule: Normal, Warning, Minor, Major, Critical, or Fatal. |
|
Aggr. Interval |
The length of the aggregation interval in terms of hours and minutes. |
|
Expiration Date |
The date when this alert rule is no longer in effect. |
|
Stop Processing |
Displays Yes or No. |
|
Frequency |
The frequency of this alert:
|
|
Options |
This column includes the following functionality:
|
To locate alert rules:
Select Resource Browser > Business Services or Proxy Services.
Click the service name.
Select the SLA Alert Rules tab.
To locate a specific alert rule for this service, scroll through the pages. Use the page controls above or below the table. Go to a page by selecting the page number or by using the arrow buttons to go to the next, previous, first, or last page.
You can use this page also to do the following:
To configure monitoring for this service, select the Operational Settings tab. See Section 26.8, "Configuring Operational Settings for Proxy Services" and Section 26.9, "Configuring Operational Settings for Business Services."
To add a new alert rule, click Add New. See Section 26.23, "Creating and Editing Alert Rules."
The tasks in creating and editing alert rules include:
Section 26.23.1, "Configuring General Information for Alert Rules"
Section 26.23.3, "Reviewing the Alert Rule Configuration"
Note:
When a service is created from another service, alert rules are maintained in the following way:When a proxy service is created from a business service or a business service is created from a proxy service, the alert rules, if any, are removed.
When a proxy service is created from another proxy service or a business service is created from another business service, the alert rules, if any, are retained.
To configure general information for alert rules:
If you have not already done so, click Create to create a new session or click Edit to enter an existing session. See Section 3.1, "Using the Change Center."
Select Resource Browser > Proxy Services or Business Services.
Click the service name.
Select the SLA Alert Rules tab and click Add New.
In the Rule Name field, enter a name for the alert rule. This is a required field.
In the Alert Summary field, enter a short description of the alert rule. This text is also used as the subject line for an email message if this alert rule is configured with an email alert notification, and can contain no more than 80 characters. If you do not provide an alert summary, the default text, Oracle Service Bus Alert, will be used instead.
In the Rule Description field, enter a description for the alert rule.
In the Alert Destination field, enter the name of the alert destination resource or click Browse to display the Select Alert Destination page. Select an alert destination from the list and click Submit.
By default, the alert will always go to the Administration Console. To configure and select other alert destination resources, see Section 6.2, "Adding Alert Destinations" and Section 6.1, "Locating Alert Destinations."
In the Start Time field, enter a start time in the format HH:MM. For example, enter 09:00 AM. You use the Start Time and End Time fields to specify a window of time during which the rule is active on each day prior to the expiration date. For example, between 9am and 5pm every day.
In the End Time field, enter an end time in the format HH:MM. For example, enter 05:00 PM. You use the Start Time and End Time fields to specify a window of time during which the rule is active on each day prior to the expiration date. For example, between 9am and 5pm every day.
The alert rule is active daily during the start time you specified until the end time you specified, until the rule expires.
In the Rule Expiration Date field, enter an expiration date in the format MM/DD/YYYY. For example, enter 12/31/2010. The rule expires at 11:59 pm on the specified date. If you do not specify a date, the rule never expires.
In the Rule Enabled field, keep Yes as the default to ensure that this rule is enabled, or select No to disable this rule.
In the Alert Severity field, select one of the following:
Normal
Warning
Minor
Major
Critical
Fatal
In the Alert Frequency field, select one of the following settings, shown in Table 26-20.
Table 26-20 Alert Frequency Setting
| Property | Description |
|---|---|
|
Every Time |
If you select this option, the actions included in the alert rule are executed every time the alert rule evaluates to The number of times an alert rule is evaluated depends on the aggregation interval and the sample interval associated with that rule. If the aggregation interval is set to 5 minutes, the sample interval is 1 minute. Rules are evaluated each time 5 samples of data are available. Therefore, the rule is evaluated for the first time approximately 5 minutes after it is created and every minute thereafter. |
|
Notify Once |
If you select this option, the actions included in the rule are executed the first time the rule evaluates to |
Select Yes for the Stop Processing More Rules option to abort executing further rules after one of the rules associated with a service evaluates to true. Use this option to stop evaluating subsequent rules when there are multiple rules associated with a particular service. Keep No as the default to continue processing rules.
This option behaves like the Stop Processing More Rules option in the Rules Wizard in Microsoft Outlook.
After you finish
Click Next to display the New Alert Rule - Conditions Configuration page. Continue in Section 26.23.2, "Defining Alert Rule Conditions."
Use this page to define conditions for the alert rule. You must specify at least one condition. If you specify multiple conditions, you must use the And/Or operators to combine them.
In the Select Aggregation Interval for the Condition field, select the number of hours and minutes to set the aggregation interval for this condition. The aggregation interval determines the frequency at which the condition is tested. The condition is tested each time the monitoring subsystem aggregates enough samples of data to constitute 1 aggregation interval.
For example, if you select an aggregation interval of 1 hour, the condition is tested each time an hour's worth of data is available. The first time the condition is tested is at the end of the first hour. After that, the condition is tested every 10 minutes because the sampling interval for an aggregation interval of 1 hour is set to 10 minutes.
You start by defining a simple expression. Two or more simple expressions can be combined to form a complex expression. To define a complex simple expression, do the following:
In the first field, select Count, Minimum, Maximum, Average, or Status.
In the next field, select an operand.
Depending on whether you select Count, Minimum, Maximum, Average, or Status in the first field, the list of the operands varies. For example, if you select Minimum, Maximum, or Average, the Response Time operand is available. Use this operand to set the response time in milliseconds (msec). The operands available also depends on the configuration of the service itself. The number of operands varies according to whether a service has pipelines, route nodes, operations, and so on.
For information on how to generate alerts based on endpoint URI status, see "Managing Endpoint URIs for Business Services" in the Oracle Fusion Middleware Administrator's Guide for Oracle Service Bus.
When you select Count, this field displays the operands shown in Table 26-21.
Table 26-21 Count Operand Details
| Property | Description |
|---|---|
|
Cache Hit Count |
For business services that use result caching, Cache Hit Count increments each time the cache is used to return a response to a client. |
|
Error Count |
The error count gets incremented when message processing returns a failure. |
|
Failure Ratio (%) |
The ratio of errors encountered to the total number of messages successfully processed over the specified aggregation interval. |
|
Message Count |
The total number of messages processed. |
|
Success Ratio (%) |
The ratio of messages successfully processed to the total number of messages encountered over the specified aggregation interval. |
|
Failover count |
For business services only: The failover count. |
|
<Request Pipeline>.Error Count |
For proxy services only: The number of erroneous messages processed by the request pipeline. |
|
<Request Pipeline>.Message Count |
For proxy services only: The number of messages processed by the request pipeline. |
|
Validation Error Count |
For proxy services only that have a validate action in the pipeline: The number of validation errors. |
|
WSS Error Count |
Available depending on the transport for the service (such as with HTTP): The number of Web Service Security (WSS) erroneous messages processed. This counter is only available for WSDL-based services and is updated when a WSS error is encountered. |
In the next field, select the desired comparison operator: =, !=, > or <.
In the next field, enter the value to compare against.
Click Add.
To define a complex expression:
Repeat steps a - e in step 2 to define a simple expression.
Repeat steps a - e again to define another simple expression.
Select the check box for each of the two expressions.
Click And or Or to combine the expressions into a complex expression.
The Split option is available after you combine multiple expressions. This option is used to split complex expressions back into separate simple expressions.
After you finish
Click Prev to return to the General Configuration page. Or, click Last to display the New Alert Rule - [service name] page. Continue in Section 26.23.3, "Reviewing the Alert Rule Configuration."
Use this page to review the configuration data that you have entered for this alert rule. If necessary, you can click Edit to make changes to the configuration before you save the alert rule.
Do any of the following:
To make a change to one of the configuration pages, click the Edit icon for the appropriate page.
To return to the previous page, click Prev.
To create the alert, click Save. The alert rule is created and saved in the current session.
To disregard changes, click Cancel.
To end the session and deploy the configuration to the runtime, click Activate under Change Center.
Use this page to view alert rule configuration details, shown in Table 26-22.
Table 26-22 Alert Rule - General Configuration
| Property | Description |
|---|---|
|
Rule Name |
The name of the alert rule. |
|
Rule Description |
A description of the alert rule. |
|
Alert Summary |
A short description of the alert rule. This text is also used as the subject line for an email message if this alert rule is configured with an email alert notification. |
|
Alert Destination |
The path and name of the alert destination resource that contains the destination address for alert notifications. This field is a link to the View Alert Destination - General Configuration page. See Section 6.4, "Editing Alert Destinations." |
|
Start Time (HH:MM) |
The start time for this alert rule. |
|
End Time (HH:MM) |
The end time for this alert rule. |
|
Rule Expiration Date (MM/DD/YYYY) |
The date when this alert rule no longer applies. |
|
Rule Enabled |
An indicator of whether this alert rule is enabled. |
|
Alert Severity |
The severity of the alert raised as a result of this alert rule:
|
|
Alert Frequency |
The frequency of the alert:
|
|
Stop Processing More Rules |
An indicator of whether the alert stops processing more rules. |
The page displays the Conditions information shown in Table 26-23.
To edit alert rules:
If you have not already done so, click Create to create a new session or click Edit to enter an existing session. See Section 3.1, "Using the Change Center."
Locate the alert rule. See Section 26.22, "Locating Alert Rules."
Click the alert rule name.
To make a change to the fields on the configuration pages, click the Edit icon for the appropriate page or the Edit button at the bottom of the page. See Section 26.23, "Creating and Editing Alert Rules" for descriptions of the pages and fields.
Do any of the following:
To go to the next page, click Next.
To return to the previous page, click Prev.
To go to the summary page, click Last.
To commit the updates in the current session, click Save.
To disregard changes and return to the SLA Alert Rules page, click Cancel.
To end the session and deploy the configuration to the runtime, click Activate under Change Center.
To delete alert rules:
If you have not already done so, click Create to create a new session or click Edit to enter an existing session. See Section 3.1, "Using the Change Center."
Locate the alert rule. See Section 26.22, "Locating Alert Rules."
Click the Delete icon in the Options field of the alert rule you want to delete. The alert rule is deleted in the current session.
To end the session and deploy the configuration to the runtime, click Activate under Change Center.