| Oracle® Communications Service Broker Configuration Guide Release 5.0 Part Number E15182-01 |
|
|
View PDF |
| Oracle® Communications Service Broker Configuration Guide Release 5.0 Part Number E15182-01 |
|
|
View PDF |
This chapter describes how to manage the Processing Tier using the Administration Console and Java MBeans:
Oracle Communications Service Broker provides some tier-layer functionality which is available only in the Processing Tier layer:
Monitoring: Runtime MBeans that provide statistics and notifications related to the tier performance rather than an individual Service Broker module. For more information, see "Monitoring Service Broker" in Oracle Communications Service Broker System Administrator's Guide.
Overload Protection: Protects Service Broker from failures during unexpected traffic peaks. For more information, see "Preventing System Overload" in Oracle Communications Service Broker System Administrator's Guide.
You can manage the Processing Tier functionality using the Tier Management node in the Domain Navigation pane.
The Monitoring tab enables you to define how Runtime MBeans and notifications operate in the Processing Tier level.
See "Configuring Service Broker Monitoring" for more information about configuring monitoring with the Administration Console.
Warning:
Thresholds that you define for notifications serve also as thresholds for key overload indicators. If you select a measurement (Runtime MBean and attribute) as a trigger for both notification and overload protection, the threshold value that you specify in the Monitoring tab is also regarded in the context of overload protection.The overload protection mechanism prevents Service Broker failures during traffic peaks. See "Preventing System Overload" in Oracle Communications Service Broker System Administrator's Guide for more information.
The Overload Protection Configuration screen lets you define key overload indicators that you identified, and for which you have defined thresholds using the Thresholds Crossed Notifications subtab of the Monitoring tab.
This section describes how to define key overload indicators and how to configure overload protection behavior, using the Service Broker Administration Console and Java MBeans:
To access the Overload Protection Configuration screen:
On the Domain Navigation pane, select OCSB > Processing Tier > Tier Management > Monitoring and Overload Protection. The Monitoring and Overload Protection screen is displayed in the Configuration pane.
Click the Overload Protection tab. This tab enables you to define key overload indicators and configure overload protection behavior.
The Overload Protection Configuration tab contains the subtabs described in Table 4-1.
Table 4-1 Overload Protection Subtabs
| Tab | Description |
|---|---|
|
Key Overload Indicators |
Enables you to configure gauges and counters that you identified as key overload indicators, to be valid key overload indicators. For more information, see "Configuring Overload Protection Method". |
|
Overload Protection Methods |
Enables you to configure how Service Broker responds to SIP and Diameter network entities that attempt to establish sessions during system overload |
Key overload indicators are counters and gauges (that is, attributes of any Runtime MBeans, including module-level Runtime MBeans and tier-level Runtime MBeans) that Service Broker monitors to observe system overload. Usually, key overload indicators are mission critical parameters.
System overload occurs when at least one key overload indicator crosses the upper threshold defined on the Thresholds Crossed Notifications subtab of the Monitoring tab of the Monitoring and Overload configuration screen (for more information, see "Configuring Service Broker Monitoring").
Note:
To enable Service Broker to observe system overload, you must setup thresholds of Runtime MBean attributes, which you define as key overload indicators, as follows:If a key overload indicator is a module-level Runtime MBean, you need to set up thresholds using the Monitoring tab of the appropriate module.
If a key overload indicator is a tier-level Runtime MBean, you need to set up thresholds using the Monitoring tab of the Monitoring and Overload configuration screen.
Table 4-2 describes the fields that you define for each key overload indicator.
Table 4-2 Key Indicators Parameters
| Name | Type | Description |
|---|---|---|
|
Name |
STRING |
Specifies a unique name of a key overload indicator |
|
MBean Instance Name |
STRING |
Specifies the object name of a Runtime MBean instance whose attribute was identified as key overload indicator. |
|
MBean Attribute Name |
INT |
Specifies the name of a Runtime MBean attribute (gauge or counter) that you identified as key overload indicator. |
When system overload occurs, Service Broker declines new sessions and responds to the network entities that attempted to establish new sessions.
The Overload Protection Methods subtab enables you to configure how Service Broker responds to attempts by SIP and Diameter network entities to establish new sessions.
Table 4-3 describes configuration parameters on the Overload Protection Methods subtab.
Table 4-3 Overload Protection Methods Parameters
| Name | Type | Description |
|---|---|---|
|
Enabled |
BOOL |
Specifies whether or not the overload protection mechanism is enabled. Possible values:
|
|
SIP Response Status Code |
STRING |
Specifies a SIP error that Service Broker returns to a SIP network entity when Service Broker declines an attempt to establish a session. |
|
SIP Retry-After |
STRING |
Specifies the value that Service Broker sets in the Retry-After header of the error response sent to the network entity. This value defines how long the network entity waits before it retries to establish a session. |
|
Diameter Response Result-Code |
STRING |
Specifies a response Result-Code AVP that Service Broker returns to a Diameter network entity when Service Broker declines the attempt to establish a session. |
Service Broker provides a set of MBeans that provide attributes and operations for configuring overload protection parameters through JMX. The hierarchy of the MBeans is shown on Figure 4-1.
The following sections provide reference information for the overload protection configuration MBeans.
OverloadProtectionMBean is a root MBean for overload protection configuration.
Created automatically
None
ObjectName getOverloadProtectionIndicators()
Returns a reference to the instance of OverloadProtectionIndicatorsMBean
ObjectName getOverloadProtectionMethods()
Returns a reference to the instance of OverloadProtectionMethodsMBean
OverloadProtectionIndicatorsMBean provides access to instances of OverlodProtectionIndicatorMBean. For each gauge or counter that you identified as a key overload indicator, you need to create a separate instance of OverloadProtectionIndicatorMBean.
Created automatically
None
ObjectName getOverloadProtectionIndicators()
Returns an array of references to instances of OverloadProtectionIndicatorMBean
ObjectName createOverloadProtectionIndicator()
Creates an instance of OverloadProtectionIndicatorMBean
ObjectName destroyOverloadProtectionIndicator()
Destroys an instance of OverloadProtectionIndicatorMBean
ObjectName lookupOverloadProtectionIndicator()
Returns a reference to a specified instance of OverloadProtectionIndicatorMBean
OverloadProtectionIndicatorMBean enables you to define a counter or a gauge (that is, an attribute of any Runtime MBean, including module-level Runtime MBeans and tier-level Runtime MBeans), that you wish to set as a valid key overload indicator.
OverloadProtectionIndicators.createOverloadProtectionIndicator()
Name
MbeanInstanceName
MbeanAttributeName
For more information on these attributes, see Table 4-2.
None
Overload ProtectionMethodsMBean enables you to specify how Service Broker responds to SIP and Diameter network entities that attempt to establish sessions during system overload.
Created automatically
Enabled
SipResponseStatusCode
SipRetryAfter
DiameterResponseResultCode
For more information on these attributes, see Table 4-3.
|
 Copyright © 2010, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
