IBM Enterprise Console manual Calculate the value for the EventSendThreshold keyword

2.Determine the number of gateways and the resulting number of events that they can send to the event server.

The example environment contains two gateways, where gateway A is responsible for Web commerce servers and gateway B is responsible for the secretaries’ systems. Divide the average capacity of the event server by the number of gateways:

120 ÷ 2 = 60

The resulting value of 60 indicates the average number of events each gateway can send without overwhelming the event server. Continue with step 3 to obtain the adjusted values for the gateway send rate.

3.Calculate the value for the EventSendThreshold keyword.

The EventSendThreshold keyword sets the maximum number of events per second that the gateway sends to the event server. Because gateway A forwards events from mission-critical systems, more gateway A events should be sent to the event server than gateway B events. Thus, the EventSendThreshold keyword for gateway A is set to 80 events per second. Gateway B has the EventSendThreshold keyword set to 40 events per second. In this way, more gateway A events get to the event server.

The sum of the values for gateway A and gateway B must be less than or equal to the 120 events that the event server can process:

80 + 40 ≤ 120

4.Determine the value for the BufferFlushRate keyword.

Any events above the value specified for the EventSendThreshold keyword are stored in the cache on the gateway. To regulate the number of events being sent to the event server, the BufferFlushRate keyword controls the number of events per minute to be sent from the cache, when the gateway recovers a lost connection to the event server.

For gateway A, the BufferFlushRate keyword is set to 5400 events per minute (90 events per second), and for gateway B the keyword is set to 3000 events per minute (50 events per second). Thus at peak traffic times, the event server is receiving 140 events per second from both gateways:

90 + 50 = 140

Although 140 events per second is greater than the average capacity of the event server (120 events per second), the event server has the capability to process excess events during brief, intermittent periods of time.

Tip: Remember to convert events per second to events per minute before setting the value for the BufferFlushRate keyword.

5.Modify the gateway ACP with the values calculated in step 3 and step 4.

6.Distribute the gateway ACP.

Depending on the number of gateways and endpoints in your environment, you need to carefully consider the rates you specify for the keywords. For instance, an improper configuration might have multiple gateways sending events at the same rate, thus flooding the event server at the same time. See “Configuration File” on page 97 for details about these keywords.

96IBM Tivoli Enterprise Console: Adapters Guide