> #### Server Pool Control page content

> The Server Pool Control page, as shown in Figure 4–4, displays data relevant to your current AppServer workload, and allows you add or reduce the number of AppServers currently running.

> Figure 4–4: Server Pool Control page example

> For example, use this page to add agents when agent requests are high; you can add agents to the maximum number of agents that your license recognizes. Also, use this page to reduce the agent count during a lag in agent requests. Using the trim feature, you can reduce agents down to the minimum agents property setting.

> The Server Pool Control page is comprised of these sections:

> - An add/trim selection control that you use to specify which activity you want to perform. When you initiate a manual trim request, Fathom determines which server(s) to actually remove. See the "Adding or trimming AppServers" section for detailed steps.
> - Three distinct, server-related data summary tables that allow you to review relevant AppServer-pool specific data quickly:
> - Server pool initial configuration.
> - Servers state.
> - Server pool summary.

> The changes that you make through add/trim activities can affect the data displayed in these summary tables. The Server pool summary also allows you to kill a specific server process. See the "Killing an AppServer process" section for the detailed steps.

> The following information describes each section of the Server Pool Control page. For the detailed procedures on how to add or trim servers, see the "Adding or trimming AppServers" section for more information.

> ##### Server pool data initial configuration section

> The Server pool initial configuration section identifies AppServer broker configuration properties set in the `ubroker.properties` file. These values display in a read-only mode.

> Table 4–4 identifies and describes each field that displays in the Server pool data initial configuration section.

> Table 4–4: Server pool data initial configuration field definitions
> This displayed property field... | Identifies...
> --- | ---
> Initial number of servers to start | The value Fathom references when the AppServer broker starts AppServers.
> Minimum servers | The minimum number of AppServers that must be simultaneously running before the AppServer broker will start additional servers. The broker strives to maintain this specified minimum; if at any time the number of servers falls below the specified minimum, the broker will automatically start any additional servers needed to maintain this minimum. If you set a trim value that would require Fathom to trim the number of servers below the number specified for this field, Fathom displays a message.
> Maximum servers | The maximum number of AppServer processes that can be running simultaneously. Fathom will not fulfill add requests you initiate that exceed this specified maximum. Fathom will display a message to state this condition so that you can re-consider your request and, if necessary, initiate a new request.

> ##### Servers state section

> The Servers state section provides a snapshot of the total number of AppServers currently associated with a specific server state. The state details related to agents and the number of agents reported reflect real-time data. This data can fluctuate due to changes in the AppServers' workflow and changes you initiate using the add and trim option.

> Table 4–5 identifies and describes each field presented in the Serves state section.

> Table 4–5: Servers state field definitions
> This server state... | Identifies the number of AppServers currently...
> --- | ---
> Active | Running.
> Busy | Serving 4GL client requests.
> Locked | Servicing a bound connection. (This state applies to a stateless AppServer.)
> Available | Available to handle broker requests.

> ##### Server pool summary section and the kill process option

> The Server pool summary section provides:

> - Detailed data about each individual server in the AppServer pool associated with a specific AppServer broker. Table 4–6 identifies and describes each field displayed in the Server pool summary section.
> - Access to:
> - More data about a specific agent.
> - A control to terminate, or kill, the agent process.
> Use the PID field to access these features. Table 4–6 provides more information about PID.

> Table 4–6: Server pool summary field definitions
> This field identifies... | Identifies the...
> --- | ---
> PID | Process identifier for this Appserver. Click on the specific PID number to display a detail page that provides specific information about this server process and, as necessary, kill the process. See the "Killing an AppServer process" section for more information.
> State | Current execution state of the AppServer process.
> Port | TCP/IP port number that the AppServer process uses.
> nRq (Number of Requests) | Number of messages sent to the AppServer process.
> nRcvd | Number of messages received by the AppServer process.
> nSent | Number of requests sent by the AppServer process.
> CPU Usage | Percentage of CPU user and system time consumed by a process.
> Memory Usage | Amount of virtual memory (in Kbytes) consumed by a process.
> Started | Time stamp that indicates when the AppServer process started. If the broker is restarted for any reason, the PID and the Last Changed value might change.
> Last Changed | Time stamp that indicates when the AppServer process last changed execution state

Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095