Configuring a reception application built with the C API
A reception application built with the C API can be configured with keywords in the configuration file.
Use the following keywords in the configuration file to configure a reception application built with the C API.
- ActiveConnections=nn
- The number of active connections that the reception process should handle.
- ActiveConnectionsSafety=nn
- The percentage of ActiveConnections that the number of actual connections permits must be reduced to a specific number before connections can be processed again. This is a threshold value.
- ConnectionsQueued=nn
- The approximate number of queued connections that the reception process will handle.
Example of a reception application build with the
C API receiving events over a SOCKET connection:
BufferEvents=YES
BufEvtPath=/tmp/eif_socket_recv.cache
TransportList=t1
t1Type=SOCKET
t1Channels=t_
t_ServerLocation=myserver.com
t_Port=5151
Example of a reception application build with the
C API receiving events over an SSL connection:
BufferEvents=YES
BufEvtPath=/tmp/eif_socket_recv.cache
TransportList=t1
t1Type=SSL
t1Channels=t_
t_ServerLocation=myserver.com
t_Port=5151
t_SSLKeystore=/my/other/location/gbkeys.kdb
t_SSLKeystorePW=password
t_SSLCipherList=SSL_RSA_WITH_3DES_EDE_CBC_SHA
t_SSLFIPSMode=OFF
Note: The procedure to configure a keystore for a reception
application is identical to that of a sender application.