30.11.2012 Views

OpenEdge Management and OpenEdge Explorer: Configuration

OpenEdge Management and OpenEdge Explorer: Configuration

OpenEdge Management and OpenEdge Explorer: Configuration

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Configuring WebSpeed Messengers <strong>and</strong> WebSpeed Transaction Servers<br />

7–34<br />

During the next interval, the request load diminishes somewhat. At the end of the interval, only<br />

20 agents are concurrently busy. The maximum number of busy agents for the interval remains<br />

at 30, since 30 were busy at the start of the interval. Thirty agents are running, <strong>and</strong> the maximum<br />

busy level is 30. No trimming occurs.<br />

Assume that all employees have to attend a company-wide meeting that begins midway through<br />

the interval. The highest number of agents busy at that same time was 20. At the end of the<br />

interval, there are 30 agents running, with zero agents currently busy. Since the maximum busy<br />

level is 20 (at the start of the interval), <strong>and</strong> the number of running agents is 30 (all are available<br />

since everyone is at the company meeting), the broker attempts to trim back the number of<br />

agents to 20.<br />

Assume that the company meeting ran for another half-hour, <strong>and</strong> the entire next interval elapsed<br />

without any requests. The maximum busy agents is zero, with 20 currently running. Since the<br />

Minimum Agent/Server Instances property value is set to 10, the broker attempts to trim back<br />

to 10 agents.<br />

Keep in mind that the lower you set the Agent/Server Auto-trim Interval value, the more quickly<br />

the broker reacts to a drop in the workload. Under a reasonably steady work load, the broker<br />

should trim the number of running agents to the number needed. However, if the workload<br />

fluctuates a great deal <strong>and</strong> the Agent/Server Auto-trim Interval is set too low, the broker may<br />

trim agents that it must then restart. As stated earlier, repetitive trimming <strong>and</strong> restarting causes<br />

the system to waste resources on unnecessary process management.<br />

To add or trim WebSpeed agents:<br />

1. Click Resources in the management console menu bar. The main resource types appear in<br />

the list frame.<br />

2. In the list frame, browse to <strong>and</strong> click the WebSpeed broker for which you want to add or<br />

trim agents. The Details page for that broker appears in the detail frame.<br />

3. If the WebSpeed broker is not started, click Broker Control. Then click Start<br />

WebSpeed.<br />

4. When the WebSpeed broker is running, return to the Details page.<br />

5. Click Agent Pool Control.<br />

6. Review the Agent pool initial configuration, the Agents state, <strong>and</strong> the Agents pool<br />

summary information.<br />

7. To add or trim agents, choose the corresponding option in the Add/Trim dropdown menu,<br />

<strong>and</strong> type the number of agents in the box provided.<br />

8. Click Submit.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!