Configuring Operational Settings for Business Services

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 Finding and Updating Operational Settings.

The run-time 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 run time. Additionally, the Service State must also be enabled. See Enabling Global Settings.

You can change and save monitoring configuration settings even if the service will be not be enabled at run time. 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.

  1. If you have not already done so, click Create to create a new session or click Edit to enter an existing session. See Using the Change Center.
  2. Select Resource Browser > Business Services.
  3. Click the business service name.
  4. The View a Business Service page displays the information shown in Table 23-8.

    Table 23-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 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 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 Viewing References to Resources.
    Description
    A description of the service, if one exists.

  5. Select the Operational Settings tab.
  6. You must be in an active session to configure business service operational settings shown in Table 23-9.

    Table 23-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 run time, so that only the responsive URIs are used for retry attempts and for processing subsequent requests.
    If you want 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 Viewing Business Services Endpoint URIs Metrics.
    If you want 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 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 run time, make sure the Enable Monitoring check box is selected.
    Disable SLA Alerting
    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 Alerting
    Select the Enabled check box. From the Enable Alerting at drop-down 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 run time. See 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 AquaLogic Service Bus in the AquaLogic Service Bus Operations Guide.
    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 run-time 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 run time, 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.