OpenEdge Management and OpenEdge Explorer: Configuration
OpenEdge Management and OpenEdge Explorer: Configuration
OpenEdge Management and OpenEdge Explorer: Configuration
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Configuring AppServers <strong>and</strong> AppServer Internet Adapters<br />
5–30<br />
3. Click Server Pool Control. The Server Pool Control page for that instance appears <strong>and</strong><br />
displays the following information:<br />
• Initial number of servers to start —The value referenced when the AppServer<br />
broker starts AppServers.<br />
• Minimum servers — The minimum number of AppServers that must be<br />
simultaneously running before the AppServer broker starts additional servers. The<br />
broker strives to maintain this specified minimum. If at any time the number of<br />
servers falls below the specified minimum, the broker automatically starts the<br />
additional servers needed to maintain the minimum.<br />
If you set a trim value that requires trimming the number of servers to below the<br />
number specified for this field, a message appears.<br />
• Maximum servers — The maximum number of AppServer processes that can be<br />
running simultaneously. Add requests you initiate that will exceed the specified<br />
maximum are not fulfilled.<br />
• Licensed servers — The total number of licensed servers.<br />
• Active servers — The number of AppServers currently running.<br />
• Busy servers — The number of AppServers h<strong>and</strong>ling ABL client requests.<br />
• Locked servers — The number of AppServers servicing a bound connection. (This<br />
state applies to a stateless AppServer.)<br />
• Available servers — The number of AppServers available to h<strong>and</strong>le broker<br />
requests.<br />
A server pool summary provides details about the following:<br />
• PID — The process identifier for this AppServer. Click the PID number to display a<br />
detail page that provides specific information about this server process <strong>and</strong>, as<br />
necessary, to kill the process. See the section about killing an AppServer process in<br />
<strong>OpenEdge</strong> <strong>Management</strong>: Servers, DataServers, Messengers, <strong>and</strong> Adapters for more<br />
information.<br />
• State — The current execution state of the agent.<br />
• Port — The TCP/IP port number used by the agent.<br />
• nRq — The number of messages sent to the agent.<br />
• nRcvd — The number of messages received by the agent.<br />
• nSent — The number of requests sent by the agent.<br />
• CPU Use — The percentage of CPU user <strong>and</strong> system time consumed by a process.<br />
• Memory Use — The amount of virtual memory (in Kbytes) consumed by a process.<br />
• Started — The time stamp indicating when the agent started.<br />
• Last Change — The time stamp indicating when the agent last changed execution<br />
state.