Oracle Application Server 10.1.3.4, Руководство пользователя

Страница: 107 / 170

Configuring the Daemon for High Availability
Advanced Features of OracleAS Adapter for IMS/DB 8-3
■
singleClient : Each client receives a dedicated server process. The account in which
a server process runs is determined either by the client login information or by the
specific server workspace.
This mode enables servers to run under a particular user account and isolates
clients from each other (because each receives its own process). However, this
server mode incurs a high overhead due to process startup times and may use a
lot of server resources (because it requires as many server processes as concurrent
clients).
■
multiClient : Clients share a server process and are processed serially. This mode
has low overhead because the server processes are already initialized. However,
because clients share the same process, they may impact one another, especially if
they issue lengthy queries.
The number of clients that share a process is determined by the Clients per server
limit (the maximum number of concurrent clients a server process for the current
workspace accepts).
■
reusable : This is an extension of the single client mode. Once the client processing
finishes, the server process does not die and can be used by another client,
reducing startup times and application startup overhead.
This mode does not have the high overhead of single client mode because the
servers are already initialized. However, this server mode may use a lot of server
resources (because it requires as many server processes as concurrent clients).
The other modes can be set so that the server processes are reusable by setting the
number of times a process can be reused with the
Reuse limit
value (the
maximum number of times a particular server process can be reused or how many
clients it can serve before it is retired). Reuse of servers enhances performance
because it eliminates the need to repeat initializations. However, reuse runs a risk
of higher memory leakage over time. The default value for the
Reuse limit
field
is
None
, indicating that no reuse limit is enforced.
Set the server mode in the Server Mode tab of the daemon workspace editor as shown
in the following figure: