Jump to: navigation, search

delivery-protocol

Section: logger-settings
Default Value: eventlog
Valid Values: mq-series, msmq, eventlog, jms, odbc
Changes Take Effect: After restart of Interaction Server
Modified: 8.5.100.15

Specifies the delivery protocol to be used for Event Logging. The valid value odbc was added in release 8.5.1.

reconnection-pause

Section: logger-settings
Default Value: 5000
Valid Values: 100-300000
Changes Take Effect: Immediately
Introduced: 8.5.100.15

Specifies, in milliseconds, the time between repeated attempts to connect to the database, test database integrity, initialize database values, or reconnect to the database when a connection is lost.

odbc-string

Section: logger-settings
Default Value: No default value
Valid Values: Any valid ODBC connection string
Changes Take Effect: After restart of Interaction Server
Introduced: 8.5.100.15

Configuring a connection string is described on the ODBC Connection page of the eServices Deployment Guide. Consult the description of the connection-string option.

connection-string

Section: logger-settings
Default Value: No default value
Valid Values: Any valid ODBC connection string
Changes Take Effect: After restart of Interaction Server
Introduced: 8.5.100.17

Configuring a connection string is described on the ODBC Connection page of the eServices Deployment Guide.

reconnection-pause

Section: settings
Default Value: 5000
Valid Values: 100-300000
Changes Take Effect: Immediately
Introduced: 8.5.100.18

Specifies, in milliseconds, the time between repeated attempts to connect to the database, test database integrity, initialize database values, or reconnect to the database when a connection is lost.

queue-size

Section: settings
Default Value: 20000
Valid Values: 50-65535
Changes Take Effect: Immediately
Introduced: 8.5.100.18

Specifies the maximum number of requests that can be stored in the queue of requests to the database.

odbc-string

Section: settings
Default Value: No default value
Valid Values: Any valid ODBC connection string
Changes Take Effect: After restart of Interaction Server
Introduced: 8.5.100.18

Configuring a connection string is described on the ODBC Connection page of the eServices Deployment Guide. Consult the description of the connection-string option.

dbprotocol

Section: settings
Default Value: odbc
Valid Values: odbc
Changes Take Effect: After restart of Interaction Server
Introduced: 8.5.100.18

To enable an ODBC connection, this option must be present, with its value set to odbc. This option has no other use.

connections

Section: settings
Default Value: 5
Valid Values: 1-50
Changes Take Effect: After restart of Interaction Server
Introduced: 8.5.100.18

Specifies the number of concurrent connections to the database.

connection-string

Section: settings
Default Value: No default value
Valid Values: Any valid ODBC connection string
Changes Take Effect: After restart of Interaction Server
Introduced: 8.5.100.18

Configuring a connection string is described on the ODBC Connection page of the eServices Deployment Guide.

blob-chunk-size

Section: settings
Default Value: 1024
Valid Values: 1024-65535
Changes Take Effect: After restart of Interaction Server
Introduced: 8.5.100.18

Specifies, in kilobytes, the amount of data to be read from a BLOB in each iteration.

8.5.100.18

Interaction Server Release Notes

Release Date Release Type Restrictions AIX HP-UX PA HP-UX IPF Linux Solaris Windows
11/26/14 General X X X X

Helpful Links

Releases Info


Product Documentation

eServices

Genesys Products

List of Release Notes

New in This Release

There are no restrictions for this release. This section describes new features that were introduced in this release of Interaction Server.

  • Support for MS SQL Server 2012 Cluster
  • Support for Oracle 12g RAC
  • Support for Windows Server 2012 Hyper-V
  • Support for functionality that enables new features and enhancements of Orchestration Server (ORS).
  • Support for UTF-8 on Windows as well as on other platforms. On Windows, this support requires Interaction Server to connect to its database using ODBC (not DB Server).
  • The way that Interaction Server communicates with its database has been modified to optimize performance (limited to Windows and Linux only with IBM DB2, MSSQL and Oracle). The following new options were added:



    Corrections and Modifications

    This release also includes the following corrections or modifications:


    Interaction Server now provides standard-level messaging to indicate that all Capture Points are working as expected. (ESR-6010)


    Interaction Server now sends the correct EventTakenFromQueue message to Interaction Concentrator (ICON). (ESR-8534)


    Interaction Server now delays checking out licenses if there are errors encountered after checking out any non-feature license. (ESR-8234)


    If DB Server disconnects just when a database transaction is about to start, this particular interaction continues to be available for further requests. (ESR-8185)


    Now Interaction Server supports a mechanism for removing attached data keys, based on the response from ESP servers. (ESR-8070)


    This release corrects the limitation with the use of the Web Service Capture Point on Linux hosts that occurred when the number of open client connections to Interaction Server came close to or exceeded 1024. Previously, the Web Service Capture Point stopped working in such cases. (ESR-8382)

Feedback

Comment on this article:

blog comments powered by Disqus
This page was last modified on November 23, 2016, at 15:27.