Oracle Application Software 10.1.3.4 User Manual

Configuring the Daemon for High Availability

Advanced Features of OracleAS Adapter for IMS/DB

A one-client server can be reused after its (single) client has disconnected. Reuse of 
servers enhances startup performance because it avoids the need to repeat 
initialization.

This parameter is not available if the Limit server reuse parameter is not selected.

This parameter is not available if the server mode value is singleClient.

■

:  Select this to limit the number of clients that 

a server can accept for the current workspace process.

If this is not selected, the number of clients is unlimited.

If Limit concurrent clients per server is selected, in the field next to the check box, 
enter the maximum number of clients that a server process for the current 
workspace accepts. The default for this field is None, indicating that the number 
of clients for each server is unlimited. This field is available if the server mode 
value is multiClient or multiThreaded.

■

: Set the priority for servers. For example, a workspace for 

applications with online transaction processing can be assigned a higher priority 
than a workspace that requires only query processing. The lower the number, the 
higher the priority. For example, workspaces with a priority of 1 are given a 
higher priority than workspaces with a priority of 2.

: This is unavailable if Use default server priority is selected.

■

: Sets the priority to 0. There is no specific priority for 

this workspace. Clear this check box to set a priority in the Specify Server Priority 
parameter.

■

: Select this to kill all servers started by that daemon 

when a daemon is shutdown, even if they are active. Select this if you want the 
servers for the workspace to remain active, even after the daemon has been shut 
down. If selected, it is the responsibility of the system operator or manager to 
ensure that the servers are eventually killed. This must be done at the system level.

■

: The number of server processes that are 

prestarted for this workspace when the daemon starts up. These are available for 
use by new client processes with minimal initialization time. Instead of starting a 
new server process each time one is requested by a client, the daemon 
immediately allocates (to the client) a server from a pool of available servers. 
When the number of available server processes drops lower than the value 
specified in the Minimum number of available servers field, the daemon again 
starts server processes until the specified number of available servers is reached. 
The default for this parameter is 0, meaning that no servers are prestarted for this 
workspace.

■

: The minimum number of server processes in the 

prestarted server's pool before the Oracle Connect daemon resumes creating new 
server processes (up to the number specified in the Initial number of servers field 
value, described earlier). If this parameter is set to a value greater than the Initial 
number of servers field value, the daemon considers the value to be the same as 
the value specified in the Initial number of servers field. In this case, a new server 
process is started and added to the pool each time a server process is removed 
from the pool and allocated to a client). The default for this parameter is 0, which 
means that new servers are created only when there are no other available servers.

■

: The number of sub-tasks for a server that are prestarted for 

this workspace when the daemon starts up. In addition to setting up a pool of 
server processes as described earlier, you can set additional server processes as