Page Comparison

...

• LogFile

• MessagesRepositories

• Connectivity

• ServerSSLCertificate

• ServerSSLPrivateKey

• Performance

• Nexo

• PoiConfigurations

• Security Provider sections

  • OpenSSL

  Performance

  • HSM

• Nexo

• PoiConfigurations

LogFile

The log file was defined in previous versions using only the parameter LogFile. It is now a section which contains the following parameters:

...

The CryptographicProvider qualifies the provider that will provide the required resource. The parameters Type, Format and URI depends on the provider. They may be used or not. More information is given in the Cryptographic Providers section of this page. As of version 03.00.00, only OpenSSL and HSM’s are supported.

Performance

This section contains various parameters that will have an influence on the performance of the Gateway. If you are in doubt about the the consequences that a parameter value may have, contact the technical support.

MaximumConnections

Maximum number of concurrent connections the server will handle before queuing the other ones. Up to 10000 connections can be handle simultaneously by a single server. This parameter should be below 9000 to stay on the safe side. It is an operating system limit.

PendingConnectionQueueLength

Size of the queue if the MaximumConnections has been reached. If the queue is empty, the other connections will be refused.

ListeningMaximumWaitTime

Maximum number of microseconds the listening thread will be blocked before doing an house keeping cycle. Typically, 100000 microseconds is a sweet spot.

SocketSelectMaximumWaitTime

Maximum number of microseconds the socket event manager will be blocked before doing an house keeping cycle. Typically, 100000 microseconds is a sweet spot.

SSLTimeout

Maximum time in seconds the connection with a POI will be kept open without receiving any data. Passed this threshold, the connection with the POI will be terminated. In normal operation condition, 60 seconds is a prefered value.

ShutdownDelay

Maximum time in seconds that the server will wait for the currently active connections to terminate when it received a shutdown (HUP) event. Beyond this delay, any non normally closed connection will be terminated.

NexoMessageInitialBufferSize

Initial buffer size in bytes used to parse the received Nexo messages. This value shall be modified if recommended by the technical support.

NexoBuilderBufferSize

Buffer size in bytes used to build outgoing Nexo messages. This value shall be modified if recommended by the technical support.

NexoBuilderErrorMessagesBufferSize

Buffer size used to store error messages while building or parsing Nexo messages. This value shall be modified if recommended by the technical support.

# Maximum number of concurrent connections the server will handle before

# queuing the other ones.

MaximumConnections = 10

# Pending connections queue length. If MaximumConnections is reached, up to

# PendingConnectionQueueLength connections will be queued before rejecting

# them.

PendingConnectionQueueLength = 200

# Maximium wait time while listening for a new connection in microseconds.

ListeningMaximumWaitTime = 100000

# Time in seconds the server will wait before terminating

# active connections.

ShutdownDelay = 60

# Timeout in seconds of a connection with a POI.

SSLTimeout = 60

# Maximum wait time when waiting for an event on a socket.

SocketSelectMaximumWaitTime = 100000

# Nexo message initial input buffer size in bytes. This value shall not be

# lower than 2000 bytes.

NexoMessageInitialBufferSize = 48000

# Nexo Builder Buffer size in bytes. NexoBuilderErrorMessagesBufferSize bytes

# are reverved as the error message buffer.

NexoBuilderBufferSize = 48000

# How much space to reserve in the Nexo Builder Buffer for error messages.

# It must be lower than 3072.

NexoBuilderErrorMessagesBufferSize = 1024

Parameters that are no longer in the configuration file

...