|
[Com]
|
Description
|
Factory value
|
Access mode
|
|---|---|---|---|
|
Listen
|
Network (listening) name for a server.
The format of the network name is:
protocol_name [options] server_name
For example, Listen=tcp 2315
Note You can use tcpip instead of tcp.
The options and server_name arguments depend on the communication protocol. For details, see Managing network connections.
You can define several network listening names. When a solidDB database server process is started, it will publish at least one network name that distinguishes it in the network. The server can then start to listen to the network using the given network name.
Note The ADMIN COMMAND 'par com.listen=value' command does not replace existing network listening names; it appends new listening names to the existing list.
|
On Windows:
NmPipe SOLID, tcp 1964 On Linux/UNIX:
UPipe SOLID, tcp 1964 |
RW
|
|
MaxPhysMsgLen
|
Maximum length (in bytes) of a single physical network message.
Follow the value with K (to specify a value in KB).
For example: MaxPhysMsgLen=2K
Longer network messages are split into smaller messages of this size.
|
OS dependent
|
RW/
Startup |
|
OpenSSLLibPath
|
Path and name of the OpenSSL library that contains the TLS routines for encrypted connections to the server.
For example: OpenSSLLibPath=C:\SSLLibs\libssl-1_1.dll
The solidDB distribution does not include OpenSSL libraries; you can download the libraries from the following OpenSSL site: wiki.openssl.org/index.php/Binaries.
This parameter is required only if the environment is not set up to locate the OpenSSL libraries in $LD_LIBRARY_PATH (on Linux/UNIX), $LIBPATH on AIX, or %PATH% (on Windows).
If this parameter must be set, then General.CryptoLibPath must also be set, see CryptoLibPath.
The path must use the conventions of your operating system. For example, in Windows environments, if the path contains white space characters, the path must be enclosed in double quotation marks. If the server runs on a UNIX operating system, path separators must be slashes instead of backslashes.
|
|
RW/
Startup |
|
RConnectLifetime
|
Time (in seconds) that idle remote connections are kept open in the pool.
Whenever the connection is used, the timer starts from zero.
Valid values are integers from 0 to 3600.
This parameter is associated with server-maintained remote connections that are used to execute remote stored procedures in Advanced Replication.
|
60
|
RW
|
|
RConnectPoolSize
|
Number of remote connections in the connection pool.
These are the connections that are used to execute the remote procedure calls. For performance reasons, idle connections are kept open in the pool for the time that is specified by the RConnectLifetime parameter. If the pool becomes full, and there is call for a node that does not exist in the pool, then that call is blocked until there is room in the pool.
Valid values are integers from 1 to 1000.
This parameter is associated with server-maintained remote connections that are used to execute remote stored procedures in Advanced Replication.
|
10
|
RW
|
|
RConnectRPCTimeout
|
RPC timeout (in milliseconds) for remote connections.
This parameter is associated with server-maintained remote connections that are used to execute remote stored procedures in Advanced Replication.
|
0 (no timeout)
|
RW
|
|
ReadBufSize
|
Buffer size (in bytes) for the data read from the network.
Follow the value with K (to specify a value in KB).
For example: ReadBufSize=16K
|
OS dependent
|
RW/
Startup |
|
ServerCertificate
|
Path (optional) and file name of the certificate file (TLS).
This parameter is required only if you are encrypting solidDB connectivity by using the TLS protocol but not using the one-time, self-signed certificate that is generated by solidDB, see Securing communications with TLS.
The path (if specified) can be an absolute path or relative to the solidDB working directory and must use the conventions of your operating system. For example, in Windows environments, if the path contains white space characters, the path must be enclosed in double quotation marks. If the server runs on a UNIX operating system, path separators must be slashes instead of backslashes.
|
server.crt (in server working directory)
|
RW/
Startup |
|
ServerPrivateKey
|
Path (optional) and file name of the private key file (TLS).
This parameter is required only if you are encrypting solidDB connectivity by using the TLS protocol but not using the one-time, self-signed certificate that is generated by solidDB, see Securing communications with TLS.
The path (if specified) can be an absolute path or relative to the solidDB working directory and must use the conventions of your operating system. For example, in Windows environments, if the path contains white space characters, the path must be enclosed in double quotation marks. If the server runs on a UNIX operating system, path separators must be slashes instead of backslashes.
If the private key has a password, you can save the password in a file and specify the file name with the Com.ServerPrivateKeyPwdFile parameter, see ServerPrivateKeyPwdFile.
Note solidDB does not start if the private key is invalid.
|
server.key (in server working directory)
|
RW/
Startup |
|
ServerPrivateKeyPwdFile
|
Path and file name of a file that contains the password for the private key, see ServerPrivateKey.
The path (if specified) can be an absolute path or relative to the solidDB working directory and must use the conventions of your operating system. For example, in Windows environments, if the path contains white space characters, the path must be enclosed in double quotation marks. If the server runs on a UNIX operating system, path separators must be slashes instead of backslashes.
Note If the private key is password-protected, solidDB does not start under the following conditions:
▪ the password file is not configured in solid.ini,
▪ the password file is inaccessible,
▪ the password file contains the wrong password.
|
None
|
RW/
Startup |
|
SocketLinger
|
Controls the TCP socket option SO_LINGER.
If set to yes, the system attempts to deliver any buffered data when a close is requested.
If set to no, the system discards any buffered data when a close is requested.
The parameter affects all server-side connections, including Advanced Replication and HotStandby.
|
no
|
RW/
Startup |
|
SocketLingerTime
|
Time (in seconds) that the socket lingers after a close is requested.
If the time interval expires before the graceful shutdown sequence completes, an abortive shutdown sequence occurs (the data is discarded).
|
0 (system default, usually 1 second)
|
RW/
Startup |
|
TcpKeepAlive
|
(Linux and Solaris platforms only; on other platforms, the parameter has no effect)
If set to yes, when the client computer is rebooted, the connection status on the server side remains "ESTABLISHED".
This parameter controls the SO_KEEPALIVE socket option.
See also, TcpKeepAliveIdleTime, TcpKeepAliveProbeCount, and TcpKeepAliveProbeInterval.
|
no
|
RW/
Startup |
|
TcpKeepAliveIdleTime
|
(Linux and Solaris platforms only; on other platforms, the parameter has no effect)
Time (in seconds) before TCP sends the initial keepalive probe.
This parameter controls the TCP_KEEPIDLE socket option.
If the SO_KEEPALIVE option is enabled with the TcpKeepAlive parameter, TCP sends a keepalive probe to the remote system of a connection that has been idle for a period of time. If the remote system does not respond to the keepalive probe, TCP retransmits a keepalive probe for a certain number of times before a connection is considered to be broken.
See also, TcpKeepAlive, TcpKeepAliveProbeCount, and TcpKeepAliveProbeInterval.
|
7200
|
RW/
Startup |
|
TcpKeepAliveProbeCount
|
(Linux and Solaris platforms only; on other platforms, the parameter has no effect)
Maximum number of keepalive probes to send.
This parameter controls the TCP_KEEPCNT socket option.
If the SO_KEEPALIVE option is enabled with the TcpKeepAlive parameter, TCP sends a keepalive probe to the remote system of a connection that has been idle for a period of time. If the remote system does not respond to the keepalive probe, TCP retransmits a keepalive probe for a certain number of times before a connection is considered to be broken.
See also, TcpKeepAlive, TcpKeepAliveIdleTime, and TcpKeepAliveProbeInterval.
|
9
|
RW/
Startup |
|
TcpKeepAliveProbeInterval
|
(Linux and Solaris platforms only; on other platforms, the parameter has no effect)
Time (in seconds) to wait before retransmitting a keepalive probe.
This parameter controls the TCP_KEEPINTVL socket option.
If the SO_KEEPALIVE option is enabled with the TcpKeepAlive parameter, TCP sends a keepalive probe to the remote system of a connection that has been idle for a period of time. If the remote system does not respond to the keepalive probe, TCP retransmits a keepalive probe for a certain number of times before a connection is considered to be broken.
See also, TcpKeepAlive, TcpKeepAliveIdleTime, and TcpKeepAliveProbeInterval.
|
75
|
RW/
Startup |
|
Trace
|
If set to yes, trace information about network messages for the established network connection is written to the file that is specified with the TraceFile parameter.
|
no
|
RW/
Startup |
|
TraceFile
|
Name of file to which trace information about network messages is written (if the Trace parameter is set to yes).
The file is created in the current working directory of the server or client, depending on which end the tracing is started.
|
soltrace.out
|
RW/
Startup |
|
WriteBufSize
|
Buffer size (in bytes) for the data written to the network.
Follow the value with K (to specify a value in KB).
For example: WriteBufSize=2K
|
OS dependent
|
RW/
Startup |