As of February 1, 2012, Genesys is no longer an affiliate of Alcatel-Lucent; any indication of such affiliation within Genesys products or packaging is no longer applicable. Please see the Genesys website at http://www.genesys.com for more details.
This release note applies to all 8.1 releases of Interaction Server.
Genesys follows applicable third-party redistribution policies to the extent that Genesys solutions utilize third-party functionality. For additional information about third-party software used in this product, see the Read Me. Please contact your Customer Care representative if you have any questions.
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix release of this product. The following new feature was introduced in this release of Interaction Server:
assignedUpdateSql
query parameter
to correctly provide the assigned-to agent
ID; for example:
update inbound set status = 'assigned', assignedto=?'PartyAgentId' where interactionid=?'InteractionId'
There are no corrections or modifications in this release.
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix release of this product. No new features were introduced in this release of Interaction Server.
This release includes the following correction and modification:
This version exposes two new options that can be added to the settings
section
of the Web Service Capture Point:
soap-accept-timeout
sets a timeout, in seconds, for the Web Service Capture Point to accept a SOAP request.
soap-receive-timeout
sets a timeout, in seconds, for reading request data from the accepted client’s connection.
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following correction and modification:
This release corrects the way that Interaction Server processes RequestChangeProperties
when
the property IsOnline
appears in the list of AddedProperties
.
Now Interaction Server updates the value of the property according to the request.
Previously Interaction Server treated the property as unchangeable and responded to the request
with EventError,
regardless of the value of the option ignore-read-only-on-change.
(ESR-8825)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following correction and modification:
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-8376)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following corrections and modifications:
Interaction Server now properly returns the interaction
on first receiving RequestPull
in most instances of the following scenario:
RequestChangeProperties
for an interaction.
RequestPull
for the same interaction via the system view.
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following corrections and modifications:
This release correctly trims UTF-8 strings, taking encoding into account, when storing them in database fields on submit and change properties operations. This release also tolerates incorrect encoding that may occur in submissions from clients. Previously, in such cases, Interaction Server became unresponsive or terminated unexpectedly. (ESR-8250)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following corrections and modifications:
Corrections in this release prevent Interaction Server from abnormal termination when it receives messages with a KVList structure that is 65536 (0x10000) bytes long. (ESR-8230)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. The following new features were introduced in this release of Interaction Server:
settings
section,
provide two ways of handling delays in responses to database requests:
either cancelling the request, or posting a warning log message.
database-request-timeout
Valid values: Any integer from 0–1800
Default: 0
Takes effect: Immediately
Specifies, in seconds, the maximum allowable delay after which certain database requests are cancelled, and an error is returned to the client. With the default value of 0, there is no timeout.
In particular: When the value is greater than zero, Interaction Server cancels any database request
that is blocking a reply to an Interaction Server client
and is taking longer to execute than the specified timeout.
Interaction Server also sends a Database request timed out
error to the client in question
and prints the standard "alarmable" message (log message ID 25037) in its logs.
database-request-warning-timeout
Valid values: Any integer from 0–1800
Default: 0
Takes effect: Immediately
Specifies, in seconds, the maximum allowable delay for a database transaction after which a standard "alarmable" log message with a warning (log message ID 25051) is printed in the log. The database request is not canceled in this case. With the default value of 0, there is no timeout.
Note: If a request is cancelled by the timeout set by the
database-request-timeout
option, this option does not apply.
This release includes the following corrections and modifications:
Interaction Server no longer exits unexpectedly when it receives improperly structured messages from clients such as Universal Routing Server. (ESR-8003)
Interaction Server no longer sends incomplete EventTakenFromQueue
messages that ICON cannot unpack.
Previously, ICON was unable to unpack this event when it did not include attr_party_type.
(ESR-7751)
The JMS Capture Point template (JMSCapturePoint.xml) has been modified so that the template
can be imported into Genesys Administrator without errors.
Previously, the presence of the jms-additional-context-attributes
section
produced an error when attempting to import.
(ESR-7775)
Interaction Server no longer permits routing of interactions that have not been fully submitted,
preventing a situation in which EventTakenFromQueue
is generated before EventInteractionSubmitted.
(ESR-7619)
If a client application sends a message that cannot be recognized, Interaction Server disconnects it. Previously in this situation, Interaction Server entered a 100-percent CPU loop and stopped processing interactions. (ESR-8066)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following corrections and modifications:
This release corrects a memory leak issue in the JMS Integrated Capture Point. This issue caused slow memory consumption in the JVM, leading to an OutOfMemoryError and eventually causing Java to exit. (ESR-7854)
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. The following new features were introduced in this release of Interaction Server:
As part of this feature, the
allow-multiple-agent-connections
option
has the added possible value force-logout.
With this value,
if an agent that is already logged in tries to log in on an additional connection,
Interaction Server closes any previous connections of the agent and logs the agent in on a new connection.
settings
section:
delayed-logout-timeout
Specifies, in seconds, the maximum amount of time that logout or other state adjustment actions are postponed for a disconnected agent. With the default value of 0, the disconnected agents are logged out immediately.
incremental-login-request-timeout
Specifies, in milliseconds, the maximum allowable delay between login related requests for a recovering agent in a suspended state. If this delay is exceeded, the agent’s state is adjusted to
not suspended,
and this is reflected in the corresponding reporting events.
delayed-logout-panic-threshold
Specifies the minimum number of agents simultaneously logging out (due to a proxy disconnecting) that triggers a panic signal. Interaction Server checks this value against the number of proxy agent clients at the time that the proxy disconnects.
enable-place-in-queue-reason
false
true, false
When this option and the option
delay-updates
are both set to true
, Interaction Server provides a reason for
an interaction being returned to the queue and then going into the strategy again. Interaction Server adds or updates
the key LastPlaceInQueueReason
with the system name of the reason that was used when returning the interaction to the queue.
The possible related reasons are: Rejected, Expired, RouteTimeout, HandlingTimeout, PartyDisconnect, RouteRejected, RouteFailed,
LicenseCut, AgentDeleted, PlaceDeleted, TenantDeleted, LoggedOut, ForcedDisconnect, EspForcedLogout, AgentForcedLogout,
DelayedLogoutTimeout, HoldRequest
. (ESR-7395)
This release also includes the following corrections and modifications:
Interaction Server no longer exits unexpectedly in rare occurrences in which the waiting period for the response from the Third-Party Server to the External Service request expired simultaneously with the receiving of that response. (ESR-7721)
After losing and regaining its connection to DB Server, Interaction Server submits interactions to Universal Routing Server (URS) without delays. (ER# 240735125, ESR-4356)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following corrections and modifications:
This release is built with the 8.1.200.04 Stat Server library, which corrects an issue with processing large datastream packages. Previously, datastream packages with key-value lists of more than 64K caused the MCR Java Extensions in Stat Server to exit. (ESR-7635)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix release of this product. No new features were introduced in this release of Interaction Server.
This release includes the following corrections and modifications:
Interaction Server no longer discards notification messages to JMS integrated Capture Points when the connection to the Message Queue is terminated. (ESR-7531)
Interaction Server now distributes the EventPartyRemoved
event correctly when it receives the RequestRouteCall
request with Type 7 (route reject). (ESR-7533)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix release of this product. No new features were introduced in this release of Interaction Server.
This release includes the following correction and modification:
The EventWorkbinContentChanges
notification is now correctly distributed to all agent applications that are subscribed to workbin notifications when a Media Server client moves an interaction out of a workbin into another queue by using the RequestChangeProperties
request. Previously, these notifications were not sent, which affected Integrated Capture Points. In particular, JMS Capture Point in iWD compatibility mode, which internally generates RequestChangeProperties
request when it processes CompleteTask
, CancelTask
or RestartTask
requests.
(ESR-7349)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix release of this product. No new features were introduced in this release of Interaction Server.
This release includes the following correction and modification:
Interaction Server no longer exits if the section log-filter-data,
containing valid option values,
is present in the Interaction Server application object.
This issue was platform-dependent, occurring on Linux only.
(ESR-7189)
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. The following new features were introduced in this release of Interaction Server:
This release also includes the following corrections and modifications:
If a logged-in agent attempts a second login at a different Place,
Interaction Server issues the correct 14 - Agent already logged in
error message.
Previously, it issued the message 12 - Place is already occupied.
(ER# 237680715)
Interaction Server no longer exits when Configuration Server becomes unavailable during Interaction Server startup or a tenant is removed from the Interaction Server application during startup. (ER# 299589181, 285040713)
When a primary Configuration Server exits and a backup Configuration Server becomes primary, Interaction Server now correctly connects to the backup server's secure port. (ER# 245371031)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix release of this product. No new features were introduced in this release of Interaction Server.
This release includes the following correction and modification:
This release corrects a memory leak issue in the JMS Integrated Capture Point. This issue caused slow memory consumption in the JVM, leading to an OutOfMemoryError and eventually causing Java to exit. (ESR-7853)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix release of this product. No new features were introduced in this release of Interaction Server.
This release includes the following correction and modification:
Interaction Server now correctly detects the Backup Universal Routing Server (URS) that is running in primary mode after the Primary URS initializes in primary mode and changes its mode to backup as forced by the Local Control Agent (LCA). (ER# 321415514)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix release of this product. No new features were introduced in this release of Interaction Server.
This release also includes the following corrections and modifications:
This release fixes an issue with a backup Universal Routing Server (URS) reporting its switchover to primary in certain situations. The situations in question are caused by the sequence in which Genesys components shut down (in particular, when Local Control Agent [LCA] shuts down before URS does). Previously, in such situations, Interaction Server considered the primary URS (the only one running out of a primary/backup pair) to be in backup mode; now the URS that is still running is considered primary as soon as its primary/backup partner disconnects. (ER# 320298341)
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. The following new feature was introduced in this release of Interaction Server:
max-submitted-interactions
as set in the Annex of a primary Universal Routing Server (URS)
or in the Annex of a strategy object associated with a primary URS
now applies to a backup URS as well.
This release also includes the following corrections and modifications:
In this release, reporting event sequence numbers of any size are correctly saved in the Event Logger tables (rpt_interaction, rpt_esp, rpt_agent, and rpt_custom). Previously, Interaction Server did not save numbers greater than 2147483647 (2^31-1). (ER# 319518931)
The way that Interaction Server generates event sequence numbers has been modified so that duplicate sequence numbers no longer occur incorrectly in the rpt_interaction and rpt_esp tables of the Event Logger. (ER# 318884861)
Note: There are cases where a single reporting event, by design, generates multiple records in these tables. Such records will necessarily have the same sequence number as the original reporting event.
The max-submitted-interactions
option now works correctly in all scenarios.
Previously, it did not work correctly after URS was restarted or a routing strategy was reloaded.
(ER# 317797761)
Interaction Server no longer deadlocks on the AIX platform when multiple updates are made to the same Person object in a rapid succession (such as might be done by an automated tool). (ER# 318385539)
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. No new features were introduced in this release of Interaction Server.
This release also includes the following corrections and modifications:
In this release, when an interaction has been placed in a queue by request from an agent desktop,
Interaction Server acknowledges this action to the desktop
without waiting for the interactions
database to finish updating.
Previously, in cases in which the database response was delayed, Stat Server received premature notification that
desktop capacity had been freed, before it actually was.
This sometimes caused increased loading on the desktop, because URS could possibly route a new interaction to the desktop
while the desktop was still waiting for confirmation from Interaction Server that it was free of the old interaction.
(ER# 308023018, 311215936)
Note: Because of this modification, it may occur that a custom desktop
receives an acknowledgement to RequestPlaceInQueue
before it receives the
acknowledgement to a preceding RequestChangeProperties,
if
the desktop issues new requests without waiting for a response to the previous request.
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix release of this product. No new features were introduced in this release of Interaction Server.
This release also includes the following corrections and modifications:
In the following scenario:
outbound-message-type
is set to text.
outbound-message-type.
(ER# 309948997)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix release of this product. The following new feature was introduced in this release of Interaction Server:
InboundMessage
parameter.
InboundMessage
parameter. OutboundMessage
parameter. InboundMessage
parameter as there is no original inbound message in this case.
This release also includes the following corrections and modifications:
In a scenario in which Interaction Server disconnects from Configuration Server while reading the configuration, it now reads the whole configuration again after its connection to Configuration Server is restored. (ER# 282801236)
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. The following new features were introduced in this release of Interaction Server:
Configurable ability to hold, pull, or move an interaction that has been assigned to an agent.
Ability for Interaction Server to filter reporting events by media type.
New Web Service Integrated Capture Point, with SSL support.
Documentation describing how to generate Web Service clients for popular development environments.
SSL support for the JMS Integrated Capture Point, for secure authentication and communication with the JMS Provider.
Interaction Server connection to database in a role other than as a schema owner.
More flexible configuration for handling timeouts, per interaction and media type.
Support for Oracle 11g RAC databases.
Three new configuration options enable you to suppress Interaction Server reporting events
and notifications related to routing strategy activity
(for example, EventTakenFromQueue, EventTakenFromWorkbin,EventPartyAdded, EventWorkbinContentChanged
).
To hide events from strategy processing,
default
section on the Annex
tab
(or Advanced View) of the strategy Script
object. If there is no default
section,
you must create one.
hide-activity
and give it the value true.
This eliminates reporting on actions such as taking the interaction from the staging area and sending it for routing to the strategy.
Two additional new options, hide-strategy-esp-activity
and hide-strategy-change-activity
,
are included in the settings
section of the Interaction Server Application
object.
Set the values of these options to true
to block distribution of related events
for the strategies that have the hide-activity
option set to true
.
For complete descriptions of these options, see the eServices 8.1 Reference Manual.
This release includes the following corrections and modifications:
Interaction Server behavior with respect to port selection has changed.
Interaction Server now always connects to the port that is assigned on its Connections tab.
The port that is assigned in the ESP Server's esp-server-port
option no longer,
in any circumstances, controls the port to which Interaction Server connects.
(ER# 283717542)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix release of this product. No new features were introduced in this release of Interaction Server.
This release includes the following correction and modification:
This release resolves an issue with Interaction Server exiting when a tenant was deleted from the configuration at runtime. This occurred because the following were processed simultaneously:
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix release of this product. No new features were introduced in this release of Interaction Server.
This release includes the following correction and modification:
Interaction Server now recognizes the Oracle error code ORA-00001: unique constraint violated,
even when
this error code is preceded by other error codes, and correctly returns EventError Duplicate interaction id
to the client. Previously, because the error code ORA-00001 was masked by other error codes,
Interaction Server returned EventError Database Failure
to the client,
and as a result, the client continued to resubmit interactions that were already in the database.
This issue applies to Oracle databases only.
(ER# 303601140)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix release of this product. No new features were introduced in this release of Interaction Server.
This release includes the following correction and modification:
Interaction Server no longer terminates unexpectedly when a value for a custom property defined in the Interaction Custom Properties
Business Attribute is submitted in Unicode. Previously, when Interaction Server was not able to convert the data from Unicode to the default code page, it terminated unexpectedly.
(ER# 301104934)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix release of this product. No new features were introduced in this release of Interaction Server.
This release includes the following corrections and modifications:
Interaction Server no longer adds (0=1)
as an AND
condition
into the select WHERE
clause for a synthetic queue.
Previously, in this scenario, no interactions were retrieved from the queue. This problem exists only in releases 8.1.000.27 through 8.1.000.29.
(ER# 299859494)
Interaction Server now uses the for update with cs
clause in the select request that is part
of the Pull
transaction on DB2. Also, the db-select-for-update
option in the
settings section of Interaction Server allows changes to this clause.
Note: This option must have a valid DB2 syntax; otherwise, Pull
transactions will fail.
The statement must also lock the records for the subsequent update
statements.
(ER# 299414173)
Interaction Server no longer fails if the packed key-value list in the message contains an incorrect pair count. Previously, Interaction Server might fail if such a corrupted protocol packed was received. (ER# 299318756)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix release of this product. No new features were introduced in this release of Interaction Server.
This release includes the following corrections and modifications:
Interaction Server no longer terminates unexpectedly with a stack overflow error when an External Services Protocol (ESP) server loaded with ESP requests disconnects. (ER# 296568220)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix release of this product. No new features were introduced in this release of Interaction Server.
This release includes the following corrections and modifications:
Interaction Server no longer terminates unexpectedly while processing a SubmitNew
third-party server request. This problem exists only in release 8.1.000.27.
(ER# 297899283)
Interaction Server now correctly limits the number of interactions an agent can receive through routing by strategy as defined by the capacity rules. Previously, an agent could receive more than the configured maximum capacity of interactions. This problem exists only in release 8.1.000.27. (ER# 297780673)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix release of this product. This section describes new features that were introduced in this release of Interaction Server.
This release includes the following corrections and modifications:
In the JMS Capture Point application,
the values of username
and password
from the settings
section are
no longer passed to the context provider.
If the context provider requires authentication, a username and password can be configured using
the options java.naming.security.principal
and java.naming.security.credentials
in the
new optional jms-additional-context-attributes
section of the JMS Capture Point application.
More generally, any option configured in the jms-additional-context-attributes
section
is passed to the context provider.
(ER# 297221673)
In this release, Interaction Server correctly opens a listening port when it switches from backup to primary mode, even when it is not connected to Configuration Server or undergoes some difficulty in reading the full configuration from Configuration Server. (ER# 296173482)
While processing a JMS Capture Point interaction, if Interaction Server receives a message from its database
concerning a uniqueness constraint violation,
it now issues the correct Duplicate interaction id
error message.
Previously, it rolled back the interaction and resubmitted it repeatedly.
(ER# 297166089)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix release of this product. No new features were introduced in this release of Interaction Server.
This release includes the following corrections and modifications:
Interaction Server no longer exits when the employee ID of a logged-in Agent is changed. Instead, the agent is logged out. (ER# 295718894)
The JMS Capture Point now passes a username and password when obtaining the context of a connection. See below for an issue associated with this correction. (ER# 295802756)
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. No new features were introduced in this release of Interaction Server.
This release includes the following corrections and modifications:
Interaction Server no longer exits when handling interactions that contain Unicode data in child key-value lists of user data in which the individual Unicode values exceed 32KB. (ER# 293796377)
The Installation Package for Windows now allows you to choose either Interaction Server or T-Server application type, as in 8.0.x and previous releases. (ER# 285801309)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix release of this product. No new features were introduced in this release of Interaction Server.
This release includes the following corrections and modifications:
Interaction Server no longer rapidly consumes memory while a JMS Capture Point is not able to read messages from a queue. (ER# 287852992)
Interaction Server no longer fails to switch over completely after several primary/backup switches while under a heavy load. (ER# 263968187)
This release alters Interaction Server's behavior so that the statistic current in processing
is
no longer produced with a negative value.
Previously, this may have happened when either of the following happened
while an interaction was being distributed by a strategy:
Interaction Server no longer undergoes memory growth when it cannot connect to the notifications queue in a JMS Capture Point. (ER# 287045321)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix release of this product. No new features were introduced in this release of Interaction Server.
This release includes the following corrections and modifications:
This release addresses several related issues that arose when Interaction Server reconnected to DB Server. (ER# 250203203, 280849313)
Interaction Server no longer exits when reconnecting to Configuration Server and Configuration Server proxy. (ER# 284415821)
This release addresses several issues that arose when Interaction Server reconnected to Universal Routing Server (URS). (ER# 281588410, 229831359, 287933241, 288021293)
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This section describes new features that were introduced in the initial 8.1 release of Interaction Server.
This release includes the following corrections and modifications that were made between Release 8.0 or earlier releases and the initial 8.1 release:
When Interaction Server connects to a backup ESP server that is running in primary mode and has an ESP port configured, it now connects to the ESP port. Previously Interaction Server connected to the default port in this scenario. (ER# 256029884)
Interaction Server no longer exits when reconnecting to Configuration Server and Configuration Server proxy
when the SetStrategyState
object is used in a strategy.
(ER# 266256745)
If Interaction Server is configured with a Java Message Service (JMS) capture point, and the message queue provider becomes unavailable, Interaction Server no longer consumes memory rapidly until the provider is back online. (ER# 284128764)
This section provides the latest information on known issues and recommendations associated with this product.
When Stat Server is configured in Hot Standby mode,
Interaction Server must have connections to both Primary and Backup Stat Servers.
Interaction Server does not track dynamic changes in the list of applications
included in the Connection Tab
of the configuration object type
Application_Cluster
. (ESR-7742)
Workaround: To make Interaction Server aware of these changes, remove this Application
Cluster
object from Connections
of the Interaction Server
object in Configuration
, and then add it back to Connections
.
Found In: 8.1.400.16 | Fixed In: |
If a value for a custom property defined in the Interaction Custom Properties
Business Attribute is submitted in
Unicode and Interaction Server is not able to convert the data from Unicode to the default code page, Interaction Server terminates
unexpectedly. Such unexpected termination might happen, for example, if a Subject
is defined as a custom property and a
Unicode value is submitted for it (for example, by Social Media Server) and the value cannot be encoded in the default code page
configured for the computer hosting the Interaction Server application. (ER# 301104934)
Interaction Custom Properties
if its value is expected to be submitted in Unicode.
Found In: 8.1.200.21 | Fixed In: 8.1.200.32 |
The Interaction Server Database Access Point (DAP) must have its Case Conversion
attribute (on the
DB Info
tab) set to any
or upper.
Setting it to lower
causes an error when Interaction Server initializes. To avoid this problem, use
version 8.0.300.00 or higher of DB Server.
Interaction Server does not support client-side port configuration with DB Server because it requires multiple connections to DB Server, for performance reasons. With client-side port configuration it is limited to one connection only.
Interaction Server does not support case-sensitive databases. All Interaction Server databases must be created as case-insensitive.
If a tenant is removed from the Interaction Server application at runtime, Interaction Server might exit. (ER# 302904558, 302811976)
Found In: 8.1.000.28 | Fixed In: 8.1.000.36 |
If Configuration Server becomes unavailable during Interaction Server startup or a tenant is removed from the Interaction Server application during startup, Interaction Server might exit. (ER# 299589181, 285040713)
Found In: 8.1.000.28 | Fixed In: 8.1.300.06 |
The following applies to version 8.1.000.21 only:
When an LDAP (Lightweight Directory Access Protocol) initial context factory
is used, the username and password that are provided in the settings of the
JMS Capture Point are passed to the initial context factory. This may lead to
exceptions in the LDAP context factory and prevent the JMS Capture Point from
starting. (ER# 297221673)
Found In: 8.1.000.21 | Fixed In: 8.1.000.27 |
The Installation Package for Windows does not allow you to choose the application type, but installs the software as Interaction Server application type. If you want to install Interaction Server with the T-Server application type, use the following workaround:
InteractionServer_810.apd
template to create
one with the Interaction Server application type.
InteractionServer_710.apd
template to create one with the T-Server application type.
templates
directory of the product CD.
startServer.bat
file, ordinarily found
in Program Files\GCTI\eServices 8.1.0\Interaction Server\<Interaction Server application name>,
and edit the -app
parameter to point to the Application with T-Server type
that you created in Step 1.
For example, if you have the following line after installation:
interaction_server.exe -host cfghost -port 2020 -app IxnServer_ixn_type
you can change it to:
interaction_server.exe -host cfghost -port 2020 -app IxnServer_tserver_type
Found In: 8.1.000.13 | Fixed In: 8.1.000.19 |
When connecting to a backup ESP server that has no port with an ESP ID present in its configuration,
Interaction Server connects to the port that is assigned in its connection
instead of the port that is assigned in the ESP Server's esp-server-port
option.
(ER# 283717542)
Found In: 8.1.000.13 | Fixed In: 8.1.200.21 |
In some scenarios, on Interaction Server or DB Server switchovers, the same XML inbound message can be processed more than once.
Interaction Server issues EventError Database error
for these interactions and rolls them back to a message queue,
but at the same time it places them in the interactions
table.
Since the messages are still in a message queue, Interaction Server pulls them one more time and submits them again. (ER# 263120407)
Found In: 8.0.200.11 | Fixed In: |
Interaction Server fails to switch over completely after several primary/backup switches under heavy load. The status looks correct in Solution Control Interface (SCI), but Interaction Server fails to switch over. (ER# 263968187)
Found In: 8.0.200.11 | Fixed In: 8.1.000.17 |
When a primary Configuration Server exits and a backup Configuration Server becomes primary, Interaction Server connects to the backup server's default port rather than its secure port. (ER# 245371031)
Found In: 8.0.100.18 | Fixed In: 8.1.300.06 |
On the Windows platform, Interaction Server exits, generating a Dr. Watson report, after making a large number of unsuccessful attempts to connect to DB Server. In this scenario on Solaris, Interaction Server simply stops attempting to connect to DB Server. (ER# 250203203)
Found In: 8.0.100.18 | Fixed In: 8.1.000.16 |
Interaction Server submits interactions to Universal Routing Server (URS) with a delay after losing and regaining its connection to DB Server. (ER# 240735125, ESR-4356)
Found In: 8.1.100.07 | Fixed In: 8.1.400.16 |
Some calculated statistics may display negative numbers for eServices Java Extension statistics
because of slow query execution time during the initialization phase of Interaction Server.
As a workaround, locate the index create index interactions_queue_stat_idx on interactions(tenant_id, queue, media_type, type, delivered_at)
in the isdb_<db_type>.sql
script for Interaction Server and apply it to the interactions
table.
Contact Genesys Technical Support for details.
(ER# 273170080)
Found In: 7.6.101.18 | Fixed In: 8.1.000.19 |
It is not possible to lock a snapshot with more than 1000 interactions in Oracle.
The Interaction Server option max-interactions-per-snapshot
has a maximum value of 2000
,
but Oracle has a limitation of 1000
. If using an Oracle database, be aware of this Oracle limitation.
(ER# 204795083)
Found In: 7.6.101.15 | Fixed In: |
In rare cases under heavy loads, Interaction Server might not switch to primary mode during switchover. This problem is intermittent; it occurs if switchovers are performed simultaneously with short intervals between switchovers. (ER# 172356768)
Workaround: Restart both primary and backup Interaction Servers.
Found In: 7.6.000.15 | Fixed In: 8.1.000.19 |
When the option delay‑updates
is set to true
,
and the external_id
is changed during the current handling session,
requests to get properties based on external_id
may fail if the database was not updated with the new value. (ER# 168597976)
Workaround: Use the User Data ForceDatabaseUpdate
key in RequestChangeProperties
.
Found In: 7.6.000.15 | Fixed In: |
Under heavy loads, extra interactions may be submitted to Universal Routing Server in the following situations:
(ER# 166786271)
Found In: 7.6.000.15 | Fixed In: |
In rare cases when multiple clients are manipulating the same interaction simultaneously,
the following statistics may be miscalculated: queue-current in processing, queue-current length, queue-current waiting processing,
tenant-current in processing,
and tenant-current waiting processing.
(ER# 180485806)
Found In: 7.5.000.19 | Fixed In: |
Interaction Server does not issue any warning when it sees an invalid value
for option max-submitted-interactions
(in the Annex
tab of a Strategy
object)
and max-submission-rate
(in section Interaction Server Name
of the Annex
of
Universal Routing Server). Interaction Server uses the default value zero
if the value submitted is invalid; this disables submission to Universal Routing Server.
(ER# 107154166, 107154168)
Found In: 7.5.000.10 | Fixed In: |
Setting an interaction custom property to an empty string value effectively removes this property from attached data in the interaction when Interaction Server uses an Oracle database. (ER# 105650427)
Found In: 7.5.000.10 | Fixed In: |
Interaction Server may freeze under the following condition: If a Tenant is added/removed in the Interaction Server Application when Interaction Server has not yet finished reading the configuration of its existing Tenants. (ER# 34221195)
Workaround: Restart Interaction Server after making Tenant changes.
Found In: 7.2.000.07 | Fixed In: |
In the rare situation where both Configuration Server and Interaction Server are running without a network connection between them, Interaction Server does not react to the deletion or addition of objects in Configuration Manager. (ER# 101751)
Found In: 7.1.000.03 | Fixed In: |
Interaction Server does not support interaction level logging. (ER# 74418)
Found In: 7.0.000.09 | Fixed In: |
This section documents features that are no longer supported in this software. This cumulative list is in release-number order with the most recently discontinued features at the top of the list. For more information on discontinued support for operating environments and databases, see "Discontinued Support" in the Genesys Supported Operating Environment Reference Guide.
IBM DB2 9.1 is no longer supported.
Discontinued As Of: 8.1.4 |
IBM DB2 8.x is no longer supported.
Discontinued As Of: 8.1.4 |
IBM AIX 5.3 is no longer supported.
Discontinued As Of: 8.1.4 |
Microsoft Windows 2003, and 32-bit for all platforms, are no longer supported.
Discontinued As Of: 8.1.3 |
Solaris 8 and Solaris 9 are no longer supported.
Discontinued As Of: 8.1.3 |
AIX 5.1 and AIX 5.2 are no longer supported.
Discontinued As Of: 8.1.0 |
Information in this section is included for international customers.
There are no internationalization issues for this product.
Additional information on Genesys Telecommunications Laboratories, Inc. is available on our Customer Care website. The following documentation also contains information about this software. Please consult the eServices 8.1 Deployment Guide first.
eServices 8.1 Deployment Guide describes deployment procedures for all eServices components. It also contains a high-level description of the eServices system, its architecture, and a list of new features in the current release.
eServices 8.1 User's Guide provides overall information about and recommendations on the use and operation of Genesys eServices.
eServices Social Media Solution Guide describes deployment and use of the Genesys Social Messaging product.
eServices 8.1 Reference Manual provides a reference listing of all configuration options and of field codes used in standard responses.
eServices 8.1 Web API Client Developer's Guide describes the structure of the Web API, explains the Simple Samples, and describes procedures for customizing them.
For a listing of classes, methods, fields, and constants of the Web API portion of the Web API Server component, see:
eServices (Multimedia) 8.0 Selected Conceptual Data Models for the UCS Database describes a portion of the Universal Contact Server (UCS) database.
8.1 Universal Contact Server Manager Help is a guide to the Universal Contact Server Manager user interface.
eServices 8.1 Knowledge Manager Help is a guide to the Knowledge Manager user interface.
Universal Routing 8.1 Interaction Routing Designer Help is a guide to Interaction Routing Designer, including the portion of it that designs interaction workflows and business processes for eServices.
Universal Routing 8.1 Business Process User's Guide contains step-by-step instructions for using Interaction Routing Designer to design interaction workflows. It also describes the sample business processes supplied with eServices.
Genesys Desktop 7.6 Help is a guide to using the Genesys Desktop.
Genesys Events and Models Reference Manual includes a set of basic interaction models, showing the components involved and the event messages sent among them. For authoritative description of the event messages, see the next item.
The API References of the Platform SDK, which provide the authoritative
information on methods and functions for each SDK, including requests
and events. The class Message
includes all event and request messages.
Genesys 8.1 Security Deployment Guide describes the deployment and configuration of some of the security features provided in Genesys software.
Product documentation is provided on the Customer Care website, the Genesys Documentation website, and the Documentation Library DVD (produced monthly).
Note: For the DVD, the New Documents on this DVD page indicates the production date for that disc. Due to disc production schedules, documentation on the Genesys Documentation website may be more up-to-date than what is available on disc immediately after a product is released or updated. To determine the version of a document, check the version number that is located on the second page in PDFs or on the About This File topic in Help files.