Configuration Server Connector Service

The Configuration Server Connector Service maintains a physical connection to the Genesys Configuration Server. The Configuration Server Connector Service needs to be created manually in iWD Manager.

In addition to the options described in Service Details, the following properties are configurable for the Configuration Server Connector Service:

startAutomatically

Indicates whether the service should be started automatically after the configuration deployment.

logLevel

The Service log level. This should be set to Default unless otherwise instructed by Genesys Technical Support. See "Service Log Levels" for a description of each log level. Depending on the setting of this property, additional logging properties might be available. Refer to "Logging Service" for descriptions of these common properties.

reconnectionAttempts

Exception handling: 

The maximum number of attempts to connect to Configuration Server, before connecting to the backup server.

reconnectionPeriod

Exception handling:

The time, in seconds, between individual reconnection attempts.

protocolTimeout

Exception handling: 

The timeout of the Genesys Configuration Server protocol; specifies the number of milliseconds that the connector waits for Configuration Server to respond to the request.

eventBufferSize

Performance tuning:

The number of Configuration Server events that can be queued up in memory, until they are processed by the service.

addpTimeout

Used to configure local and remote timeouts (respectively) for Advanced Disconnect Detection Protocol (ADDP). In Configuration Manager or Genesys Administrator, you should enable ADDP on the connection to Interaction Server on the Connections tab of your iWD Runtime Node application.

addpRemoteTimeout

Used to configure local and remote timeouts (respectively) for Advanced Disconnect Detection Protocol (ADDP). In Configuration Manager or Genesys Administrator, you should enable ADDP on the connection to Interaction Server on the Connections tab of your iWD Runtime Node application.