Administrator Guide : Managing network connections : Network listening names (Com.Listen)
  
Network listening names (Com.Listen)
The network name of a server is a network listening name that consists of a communication protocol and a server name (port number). This combination identifies the server in the network. The network name is defined with the Com.Listen parameter in the solid.ini file.
The syntax of the Com.Listen parameter and the network listening name is the following:
[Com]
Listen = network_listening_name, network_listening_name, ...
where
network_listening_name = protocol_name [options] server_name | none
▪protocol_name depends on the operating system and type of network, see Communication protocols. If you are using Open SSL to encrypt the network connection, protocol_name must be tls.
▪server_name depends on the communication protocol:
– In TCP/IP or TLS protocol, server_name is a service port number, such as 2315.
– In other protocols, server_name is a name, such as soliddb or chicago_office.
▪none means that all listening ports are disabled. The value none cannot be set with ADMIN COMMAND 'par'.
▪[options] can be any combination of the following:
Option
Description
Protocol
-4
Specifies that solidDB® listens to IPv4 protocol only.
TCP/IP or TLS
-6
Specifies that solidDB® listens to IPv6 protocol only.
In Windows environments, this option is mandatory if IPv6 protocol is used.
TCP/IP or TLS
-iip_address|
host_name
solidDB® listens for client connections on only the specified IP address or host name.
Listening to specified IP address or host name is useful in multi-homed systems that support many TCP/IP interfaces or have multiple IP addresses.
For example, the following diagram shows two scenarios. In each case, the solidDB® process is running on a computer that has two IP addresses.
In the first scenario, when the -i parameter is not used, both Client A and Client B can connect to solidDB®.
In the second scenario, the -i parameter sets a specific IP address for connections, and so Client B, which is not attempting to connect on the specified IP address, cannot connect to solidDB®.
This diagram is described in the surrounding text
Host name can be used instead of IP address, for example:
[com]
Listen = tcp -ilocalhost 1313
TCP/IP or TLS
-ofilename
Turns on the Network trace facility and defines the name of the trace output file
See Troubleshooting a problem for details.
All
-plevel
Sets the highest level at which the clients can use the solidDB® Ping facility.
For example, if the server side is set to -p3, clients applications can run the Ping facility at levels 1, 2, and 3, but not at 4 and 5.
All
-t
Turns on the Network trace facility
See Troubleshooting a problem for details.
All
Notes
▪A server may use an unlimited number of network names.
▪All components of network names are not case-sensitive.
▪When a database server process is started, it publishes the network names that it starts to listen to. This information is also written to the solmsg.out file.
▪Network names must be unique within one host computer. For example, you cannot run two servers that are both listening to the same TCP/IP port in one host. However, it is possible that the same port number is in use in different hosts.
▪A server cannot listen for both TCP/IP and SSL connections on the same TCP port.
Example: solid.ini entry
[Com]
Listen = tcpip 1313, nmpipe soliddb
The example contains two network names which are separated by a comma. The first one uses the protocol TCP/IP and the service port 1313; the other one uses the Named Pipes protocol with the name soliddb. The tcpip and nmpipe are communication protocols, while 1313 and soliddb are server names.
Factory value for a network name
If the Listen parameter is not set in the solid.ini file or if the value is empty, solidDB® listens to the following network names by default:
Platform
Com.Listen factory values
Windows
NmPipe SOLID ShMem SOLID TCP/IP 1964
Linux and UNIX
UPipe SOLID TCP/IP 1964
See also
Viewing supported protocols for the server
Viewing network names for the server
Adding and modifying a network name for the server
Removing network name from the server
Managing network connections