Operational settings let you configure things like monitoring, alerts, reporting, logging, message tracing, and business service result caching. You can specify operational settings for all services, at the service and global level, and use the global settings to turn on and off monitoring, SLA alerts, pipeline message reporting, and pipeline message logging. The available settings are described in the following sections.

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. The service state must also be enabled. 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.

When you enable or disable monitoring at the global level, it enables or disables monitoring for all services that have individually been enabled for monitoring. If monitoring for a particular service has not been enabled, you must first enable it and set the aggregation interval for that specific service before the system starts collecting statistics for that service.

Enable or disable these settings at the global level in conjunction with the settings at the service level to effectively enable or disable them. The operational settings at the global level supersede the operational settings at the service level. The following settings must be enabled at the global level in order to be enabled for a specific service:

• Monitoring

• SLA Alerting

• Pipeline Alerting

• Reporting

• Logging

• Result Caching

• Automatic Service Migration

• JavaScript Timeout

• Comment Logging Enabled

When you configure an operational setting at the global level (also called global settings), it affects all applicable services in the domain. Most settings must be enabled at both the service and global levels in order to take effect at runtime. Use the Global Settings tab of the Service Bus home page to update settings at the global level.

Figure 9-1 The Global Settings Tab

Description of "Figure 9-1 The Global Settings Tab"

To configure operational settings at the global level:

1. In the Target Navigator, expand SOA and then select service-bus.

   The Service Bus Dashboard appears.

2. Click the Global Settings tab.

   The Service Bus settings for the domain appears.

3. To enable a setting, select its check box; to disable a setting, clear the check box.

   Each global setting is described in Table 9-1

4. To revert all unapplied changes back to the saved settings, click Revert.
5. When you are done configuring operation settings, click Apply to save your changes to the runtime.

1. Do one of the following:

   • To search for services across the domain, in the Target Navigator expand SOA and select service-bus.

   • To search for services in a Service Bus project, in the Target Navigator expand SOA, expand service-bus, and select the name of the project in which to search.

2. Click the Operations tab.
3. Specify the search criteria to use to locate the services who settings you want to modify.

   You can specify the following criteria, all of which are optional except Type:

   • Type: Select from the list of available options, which includes all services, both business and proxy services, business services, proxy services, pipeline, or split-joins.

   • Name: Enter the name of the services to locate.

   • Path: The path (project name and folder names, if any) to the services to locate. If you are on the Service Bus Project Operations tab, the path is already filled in for you.

4. Click Search.

   A list of services matching your criteria appears in the Operations table, as shown below. For more information about these settings, see Available Operational Settings and the online help provided with Fusion Middleware Control.

   Figure 9-2 Operations Page

   
   Description of "Figure 9-2 Operations Page"
5. To configure operational settings, continue to Enabling and Disabling Operational Settings for Multiple Services

1. Perform a search for services, as described in Searching for Services to Configure Their Operational Settings.
2. For any service in the results list, select a check box to enable the corresponding operational setting, or clear a check box to disable the operational setting.
3. To enable or disable an operational setting for all the services in the list, select or clear the check box in the column header for that setting.

   For information about the settings and notations in the Operations list, see Available Operational Settings and the online help provided with Fusion Middleware Control.

4. To revert all unapplied changes back to the saved settings, click Revert.
5. When you are done configuring operation settings, click Apply to save your changes to the runtime.

In addition to enabling and disabling operational settings from the Operations page of the Service Bus or Service Bus Project page, you can also enable and disable settings for a service from its Properties page. For most services, you can also configure the operational settings in more detail, such as setting logging and monitoring levels.

For information about configuring specific operational settings, see Available Operational Settings and the online help provided with Service Bus. The following figure shows the Properties page for a service.

Figure 9-3 Service Bus Service Properties

Description of "Figure 9-3 Service Bus Service Properties"

To enable or disable operational settings for a single service:

1. Perform a search for services, as described in Searching for Services to Configure Their Operational Settings.
2. In the Operations table, click the service you want to configure.

   The Properties page for that service appears.

3. To enable a setting, select the Enabled check box for that setting.
4. To disable a setting, clear the Enabled check box for that setting.
5. To revert all unapplied changes back to the saved settings, click Revert.
6. When you are done configuring operation settings, click Apply to save your changes to the runtime.

1. Perform a search for services, as described in Searching for Services to Configure Their Operational Settings.
2. In the Operations table, click the service you want to configure.

   The Properties page for that service appears.

3. In the Aggregation Interval field under Monitoring, select the number of hours or minutes for the interval.

   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.

4. When you are done configuring operation settings, click Apply to save your changes to the runtime.

1. Perform a search for services, as described in Searching for Services to Configure Their Operational Settings.
2. In the Operations table, click the pipeline or split-join you want to configure.

   The Properties page for that service appears.

3. In the Monitoring Level field under Monitoring, do the following:

   • For a pipeline, select Service, Pipeline, or Action to indicate the level.

   • For a split-join, select Service, Branch, or Activity to indicate the level.

4. To revert all unapplied changes back to the saved settings, click Revert.
5. When you are done configuring operation settings, click Apply to save your changes to the runtime.

1. Perform a search for services, as described in Searching for Services to Configure Their Operational Settings.
2. In the Operations table, click the service you want to configure.

   The Properties page for that service appears.

3. Next to Message Tracing, select Enabled.
4. From the Tracing Detail Level list, select the level of detail from among the following:

   • Terse: Display the date, time, service type, service name, and URI.

   • Headers: Display terse information along with the XML representation of the message metadata.

   • Full: Display the headers information along with the raw payload, including attachments if any.

5. If you selected Full from the Detail Level list, do the following:

   • In the Payload Tracing Unit field, specify the maximum size (in kilobytes) for the message payload.

   • In the Default Encoding field, specify the default encoding for logging the payload.

     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.

     Note:

     If you leave the Default Encoding field empty, Service Bus uses 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), Service Bus uses Base64 encoding for the payload.

   • Click Apply.

1. Perform a search for services, as described in Searching for Services to Configure Their Operational Settings.
2. In the Operations table, click the service you want to configure.

   The Properties page for that service appears.

3. In the SLA Severity field under SLA Alerting, select the level at which you want to start generating alerts.
4. To revert all unapplied changes back to the saved settings, click Revert.
5. When you are done configuring operation settings, click Apply to save your changes to the runtime.

1. Perform a search for services, as described in Searching for Services to Configure Their Operational Settings.
2. In the Operations table, click the service you want to configure.

   The Properties page for that service appears.

3. In the Pipeline Severity field under Pipeline Alerting, select the level at which you want to start generating alerts.
4. To revert all unapplied changes back to the saved settings, click Revert.
5. When you are done configuring operation settings, click Apply to save your changes to the runtime.

1. Set the Oracle WebLogic Server log levels, as described in To set Oracle WebLogic Server log levels:
2. Perform a search for services, as described in Searching for Services to Configure Their Operational Settings.
3. In the Operations table, click the service you want to configure.

   The Properties page for that service appears.

4. In the Logging Level field under Logging, select the level at which you want generate log entries.
5. To revert all unapplied changes back to the saved settings, click Revert.
6. When you are done configuring operation settings, click Apply to save your changes to the runtime.

Business service throttling is described in Configuring Business Services for Message Throttling. For information and instructions on configuring throttling, see Configuring Throttling for a Single Business Service.

Managing offline endpoint URIs is described in Monitoring and Managing Endpoint URIs for Business Services. For information and instructions on configuring endpoint URI handling, see Configuring Service Bus to Take Unresponsive Endpoint URIs Offline.