OpenEdge Management and OpenEdge Explorer: Configuration
OpenEdge Management and OpenEdge Explorer: Configuration
OpenEdge Management and OpenEdge Explorer: Configuration
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Configuring DataServers<br />
3–6<br />
Table 3–1: ODBC DataServer broker properties (4 of 4)<br />
Advanced Features<br />
Property Description<br />
Maximum client instances The maximum number of client connections<br />
that the broker can support concurrently.<br />
The default value of 512 that is set for this<br />
parameter is high enough to ensure that the<br />
number of client connections is unlimited.<br />
Realistically, however, the system-level<br />
resources needed to support an unlimited<br />
number of clients might be exhausted before<br />
this limit is reached. If you see broker log<br />
entries that contain Exception Messages for<br />
"out of space" or "OutOfMemory" you might<br />
need to reduce the maximum number of client<br />
connections to a more reasonable value. Note,<br />
however, that lowering this value can cause<br />
some client requests to be rejected ("Exceeded<br />
Max Clients"). Configuring (<strong>and</strong> starting)<br />
multiple brokers to h<strong>and</strong>le higher client loads<br />
alleviates the problem.<br />
Priority weight (0-100)<br />
(dynamic property)<br />
An integer value between 0 <strong>and</strong> 100 that<br />
influences the share of the workload that the<br />
selected broker receives. The larger the value,<br />
the heavier the load that is distributed to the<br />
broker. Using the Priority weight value, the<br />
NameServer distributes client requests to the<br />
same DataServer service across all DataServer<br />
brokers. The default value is 0.<br />
You can update this property dynamically.<br />
Any changes will affect all current <strong>and</strong> new<br />
brokers.<br />
Registration retry (in seconds) After registering with its controlling<br />
NameServer, the DataServer broker<br />
periodically sends "keep-alive" messages to<br />
the NameServer to let the NameServer know<br />
that the broker is still active. The Registration<br />
retry value is the number of seconds that pass<br />
between "keep-alive" messages. The default<br />
value is 30.