Release Number | AIX | HP-UX PA | HP-UX IPF | Linux | Solaris | Windows |
---|---|---|---|---|---|---|
8.1.300.22 [06/22/16] – Hot Fix | X | X | X | X | ||
8.1.300.20 [02/19/15] – Hot Fix | X | X | ||||
8.1.300.19 [08/01/14] – Hot Fix | X | |||||
8.1.300.18 [02/11/14] – Hot Fix | X | X | X | X | X | X |
8.1.300.16 [01/27/14] – Hot Fix | X | |||||
8.1.300.14 [07/03/13] – General | X | X | X | X | X | X |
8.1.200.14 [07/26/13] – Hot Fix | X | X | ||||
8.1.200.13 [02/21/13] – General | X | X | X | X | X | X |
8.1.200.11 [11/21/12] – General | X | X | X | X | X | X |
8.1.100.21 [10/08/12] – Hot Fix | X | |||||
8.1.100.20 [09/07/12] – Hot Fix | X | |||||
8.1.100.19 [08/09/12] – Hot Fix | X | |||||
8.1.100.18 [06/28/12] – Hot Fix | X | |||||
8.1.100.17 [06/21/12] – Hot Fix | X | |||||
8.1.100.15 [05/22/12] – General | X | X | X | X | X | X |
8.1.100.14 [04/06/12] – General | X | X | X | X | X | X |
8.1.000.14 [08/23/12] – Hot Fix | X | |||||
8.1.000.13 [11/24/11] – General | X | X | X | X | X | X |
8.1.000.10 [07/13/11] – General | X | X | X | X | X | X |
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 Solution Control Server (SCS).
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 Genesys Customer Care representative if you have any questions.
This product includes software developed by Eric Young (eay@mincom.oz.au).
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents, above.
This is a hot fix for this product. This release does not contain new features or functionality.
Note: Support of Genesys Security Pack on UNIX version 8.5.100.12 or higher was added to this release on December 16, 2016.
This release includes the following corrections and modifications:
SCS is now more robust when processing malformed messages. SCS now properly rejects messages with a size that does not correspond to the message content. Previously, SCS sometimes terminated when receiving such a message. (MFWK-17543 [MFWK-17307])
If Solution Control Servers are configured as an HA pair, after the host restarts, only the primary controlling SCS requests Local Control Agent to start those applications for which Autostart is set to true. As a result, the status of those applications no longer fluctuate between Initializing and Started. Previously in this scenario, both the primary and backup Solution Control Servers sent these requests, causing the status of applications to fluctuate. (MFWK-17525 [MFWK-17379])
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents, above.
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following correction or modification:
Solution Control Server now connects properly to the backup Configuration Server running in primary mode after a Configuration Server switchover caused by an unexpected stoppage of the primary Configuration Server. Previously in this scenario, SCS was unable to connect to the Configuration Server running in primary mode. (MFWK-16506)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents, above.
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following correction or modification:
In a distributed SCS environment, all active alarms are now cleared automatically if both of the following conditions are met:
Cancel Timeout
field in Configuration Manager, or Clearance Timeout field
in Genesys Administrator) is expired.distributed-sync-timeout
option is enabled in the
general
section of the SCS Application
object
and set to a value less than the clearance timeout.Previously in this scenario, if the distributed_sync_timeout
option was enabled in the distributed SCS instances, the active alarms were
not automatically cleared when the clearance timeout expired. To clear the
alarms, you had to either manually clear the active alarms periodically, or
set up a scheduled alarm clearance script and clear the active alarms using
the mlcmd.exe
utility that is part of SCS.
(MFWK-15870)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents, above.
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following correction or modification:
Solution Control Server can now be started with a configuration file by
specifying a configuration file in the optional -f <configuration
file name>
command-line parameter. Previously, in only 8.1.3
releases, SCS could not be started in this way.
Note: This issue was caused by support of the ip-version
command-line argument that was added to SCS in release 8.1.300.14. This
current version removes SCS support for that argument, reverting back to
the ability to start SCS with a configuration file as it existed prior to
release 8.1.3.
(MFWK-15345, MFWK-15336)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents, above.
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following correction or modification:
SCS now attempts to reconnect to the management port of an application if the already established connection fails or if the first attempt to connect fails. Previously, in either of these scenarios, SCS sometimes did not attempt to reconnect, so that SCS and the application were unable to exchange management information. (MFWK-15344)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents, above.
There are no restrictions for this release. This section describes new features that were introduced in this release of Solution Control Server.
SCS now supports configuration objects encoded using UTF-8, including the processing and display of alarms with UTF-8 names and messages.
SCS now enables you to set the number of requests that it will process between pauses to scan its connection with Local Control Agent (LCA) and respond appropriately, thereby preventing the connection from closing because of expiration of the Automatic Disconnection Detect Protocol (ADDP) timeout.
SCS now uses the option ip-version
in an IPv6 dual-stack
environment, enabling it to connect and work with servers that use a mixed
IPv4/IPv6 configuration.
By default, SCS now enables automatic authentication of the server's
security certificate by the Windows TLS client socket. However, this might
cause the failure of existing TLS connections that do not have server
certificates. To prevent authentication errors on those existing TLS
connections, make sure that server certificates are used. Alternatively, you
can use the new option client-auth
to disable the default
behavior and restore pre-8.1.3 behavior.
The parameters of the mlcmd
command-line utility can now be
entered as either a name or a DBID. This restores the original syntax with
subsequent enhancements.
SCS supports new versions of operating systems, and a new virtualization platform. Refer to the Genesys Supported Operating Environment Guide for more information.
There are no corrections or modifications in this release.
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents, above.
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following correction or modification:
Solution Control Server (SCS) no longer terminates unexpectedly when it receives a message from a distributed SCS that has terminated. (MFWK-14167, ER# 324536461)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents, above.
There are no restrictions for this release. This release does not contain new features or functionality.
This release includes the following correction or modification:
You can now successfully import this version of SCS metadata in Genesys Administrator. The previous version of the metadata, 8.1.200.11, was malformed and could not be imported. (ER# 314552552)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents, above.
There are no restrictions for this release. This section describes new features that were introduced in this release of Solution Control Server (SCS).
You now have the option to install the Solution Control Server Utilities
(ccgs.pl
, gstuckcalls
and Stuck Calls detection
and deletion scripts, logmsg
, and mlcmd
) without
installing SCS. Previously, the utilities were installed automatically only
when you installed SCS.
You can now use the mlcmd
command-line utility to
report CPU usage for each thread of a given process of a given application,
and to store the results in an XML file for which you can set the path and
filename.
Two new transport options alarms-port
and
backup-alarms-port
enable the configuration of client-side ports
for the subscription connection from Solution Control Server to the primary
and backup log Message Servers, as follows:
alarms-port
Default Value: 0
(zero)
Valid Values: 0
to maximum number of operating system ports
Changes Take Effect: After restart
Specifies the port number of a client-side port for the subscription connection from SCS to the primary log Message Server.
backup-alarms-port
Default Value: 0
(zero)
Valid Values: 0
to maximum number of operating system ports
Changes Take Effect: After restart
Specifies the port number of a client-side port for the subscription connection from SCS to the backup log Message Server.
Solution Control Server now uses the option ip-version
in an IPv6 dual-stack environment when it is connecting to Local Control
Agent (LCA). This enables it to specify the version of IP (IPv4 or IPv6)
that the connection with LCA must use. (ER# 272754614)
This release also includes the following corrections and modifications:
Solution Control Server now reports the correct status of both the backup and primary servers in a high-availabilty (HA) pair in the following scenario:
disconnect-switchover-timeout
option expires.Previously in this scenario, SCS reported one server as Unknown
,
and did not change the status of the other server—it was incorrectly
reported as Running
.
(ER# 307203941)
In distributed mode, Solution Control Server no longer creates a duplicate alarm history log record for an alarm that was handled by another SCS instance and presented to this instance during synchronization of the distributed instances. (ER# 301592171)
A new option eliminates the race condition of HA scripts that sometimes occurs where both SIP Servers in an HA pair become primary for a brief period when they are started at almost the same time.
[general]
ha_service_unavail_primary
Default Value: true
Valid Values: true
, false
, on
,
off
, yes
, no
Changes Take Effect: Immediately
For applications in HA mode, set this option to false
to
prevent the application switching to primary when it is in Service
Unavailable
state. This prevents a race condition of the HA scripts,
in which both SIP Servers become primary for a brief period when they are
started at almost the same time.
(ER# 301340301)
Solution Control Server no longer generates license violation alarms for
MLSNMP/HA_REDUNDANCY
if these features are not requested and
are not present in the license file. Previously, SCS generated these alarms
whether the features were present or not. (ER# 263100776)
Solution Control Server now initializes the SNMP solutionsTable
correctly, and updates the table if the status of a Solution changes.
Previously, SCS would not populate the table at startup. (ER# 259173973)
Solution Control Server now writes logs to stderr
in only the
following situations:
stderr
is configured as the desired log output in the
options of SCS.Previously, the circumstances under which SCS wrote logs to stderr
were not consistent.
(ER# 24815091)
The Windows Event Viewer now displays correctly those events generated by Solution Control Server. Previously, the events were sometimes displayed incorrectly or not at all, and additional error messages would be generated on Windows for those missing events. (ER# 188334011)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents, above.
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:
In an environment where Solution Control Server is configured with multiple FlexLM servers, the high-availability redundancy (ha_redundancy) feature of SCS is no longer disabled dynamically in the following scenario:
This is existing behavior for other SCS features that require licensing, such as Management Layer Distributed Mode (MLDistributed) and Management Layer Simple Network Management Protocol (MLSNMP).
(ER# 299991552)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents, above.
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:
In a high-availability (HA) configuration, Solution Control Server (SCS)
now automatically starts applications configured with the autostart
option (in the sml
section) set to true
when the
SCS HA pair is restarted. Previously, a race condition sometimes occurred
when the HA pair was restarted, and these applications were not started
automatically. (ER# 306151742)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents, above.
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:
Solution Control Server no longer creates multiple redundant network connections to the SNMP managed application. This problem occurred only rarely in the past. (ER# 302106786)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents, above.
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:
Solution Control Server (SCS) no longer terminates unexpectedly when Configuration Server is restarted while SCS is starting up. Previously in this scenario, but only rarely, SCS unexpectedly terminated. (ER# 301189780)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents, above.
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:
Each Solution Control Server in a distributed environment can now be assigned to monitor up to 250 hosts and their applications. In this environment, Solution Control Server can handle the simultaneous failure of up to 50 hosts, while reflecting the actual runtime statuses of the hosts and affected applications in 15 seconds or less. (ER# 300117841, 300370017)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents, above.
There are no restrictions for this release. This section describes new features that were introduced in this release of Solution Control Server (SCS).
ccgs.pl
script—Graceful Call Center T-Servers stop
script.gstuckcalls
utility—To handle T-Server stuck calls.logmsg
utility—To send log messages on behalf of
applications to Message Server.mlcmd
utility—To generate Management Layer commands
to control Genesys Applications, Solutions, and Hosts.For more information about these utilities, refer to the Framework 8.1 Management Layer User's Guide.
This release includes the following corrections and modifications:
After a distributed SCS loses its connection with another distributed SCS,
it changes the status of all hosts controlled by the other SCS, and of the
applications running on those hosts, to UNKNOWN
. Previously,
the first SCS changed only the status of the hosts controlled by the other
server, but not the status of the applications on those hosts.
(ER# 298749711, 282999050)
SCS now correctly sends an e-mail message to those recipients specified in
the cc:
field. Previously, if the number of recipients in the
cc:
field exceeded the number of recipients in the
To:
field by two or more, SCS replaced the recipients specified
in the cc:
with those specified in the To:
field.
(ER# 214199948)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents, above.
There are no restrictions for this release. This section describes new features that were introduced in this release of Solution Control Server.
Solution Control Server now supports TLS on its connections with LCA.
Solution Control Server now supports heartbeat detection functionality used by Local Control Agent (LCA) to detect unresponsive Genesys applications.
Alarm Detection and Alarm Reaction scripts now identify the affected configuration object by name or by DBID. This ensures seamless XML import and export of Alarm Detection and Alarm Reaction script definitions.
Audit logs now contain Host and Tenant extended attributes.
Access to the mlcmd.exe
utility is now restricted to authorized
users. In addition, the parameters have been updated to use a name instead of a
DBID, and a new parameter created to clear all active alarms raised by an
application.
Solution Control Server now supports new operating systems. Refer to the Genesys Supported Operating Environment Reference Guide for more information.
This release also includes the following corrections and modifications:
Log messages sent using the logmsg
utility now have the correct
Application Type prefix. Previously, the prefix was based incorrectly on an
internal enumerator instead of using the value of the -atype
parameter of the utility. (ER# 292331582, 291828497)
Solution Control Server now clears an alarm if the corresponding Alarm Condition has been deleted. Previously, Solution Control Server would not clear the alarm. (ER# 291609493, 286679286)
Solution Control Server now attempts to restore lost connections with servers that are managed through Simple Network Management Protocol (SNMP). (ER# 291609471, 286681999)
The status of unmonitored Application
configuration objects
such as Database Access Points and Resource Access Points is now reported
as UNKNOWN
, which is consistent with end-user applications
for which a status of UNKNOWN
is reported as a blank space.
Previously, these unmonitored applications were reported as
STOPPED
instead. (ER# 284874013)
Solution Control Server now sends its current status and the mode in which it is running to Local Control Agent (LCA) when its status or run mode changes, and when it reconnects to LCA. Previously, it did not send changes in its status or run mode to LCA after reconnecting. As a result, both Solution Control Servers in a high-availability (HA) pair sometimes ran in the same mode.(ER# 280729861, 236638896)
Solution Control Server no longer generates the log event Unable to
execute Reaction
when executing an Alarm Reaction of type
Application Option Change
. (ER# 273075412)
Each Solution Control Server in a distributed environment now properly send
notifications to its clients, and as a result, SCI now reports the correct
status of the distributed Solution Control Servers. Previously, in some
cases, the status of a running distributed Solution Control Server was
reported as Initialized
instead of Running
.
(ER# 240702830)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents, above.
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:
In an environment where Solution Control Server is configured with multiple FlexLM servers, the high-availability redundancy (ha_redundancy) feature of SCS is no longer disabled dynamically in the following scenario:
This is existing behavior for other SCS features that require licensing, such as Management Layer Distributed Mode (MLDistributed) and Management Layer Simple Network Management Protocol (MLSNMP).
(ER# 305515171)
Solution Control Server now clears an alarm if the corresponding Alarm Condition has been deleted. Previously, Solution Control Server would not clear the alarm. (ER# 291909831 [286679286])
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents, above.
There are no restrictions for this release. This section describes new features that were introduced in this release of Solution Control Server.
Solution Control Server can now try to start an application of type
Third Party Server
with a state UNKNOWN
, including
when executing a Start a specified application
Alarm Reaction.
Default behavior in this case is to not try to start the application, but a
user can change this by using the following new configuration option in the
general
section of the Third Party Server
-type
Application object:
forced-start-enabled
Default Value: false
Valid Values: true
, false
Changes Take Effect: Immediately
Specifies if Solution Control Server is to try to start an application of
type Third Party Server
with a state of UNKNOWN
.
When set to false
(the default), Solution Control Server will
not try to start the application. When set to true
, Solution
Control Server will try to start the application, even if the state of the
application is UNKNOWN
.
(ER# 281774747)
Note: Following the initial Hot Fix release of this version of Solution Control Server on the Solaris platform, Solution Control Server 8.1.000.13 was tested on the AIX, HP-UX PA, HP-UX IPF, Linux, and Windows platforms. On January 4, 2012, the release type for all platforms changed from Hot Fix to General.
This release includes the following correction and modification:
Solution Control Server, on UNIX platforms, no longer exits unexpectedly
when attempting to carry out the Execute OS Command
Alarm
Reaction in the following scenarios:
(ER# 282284107)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents, above.
There are no restrictions for this release. This section describes new features that were introduced in the initial 8.1 release of Solution Control Server.
Solution Control Server now supports IPv6.
Solution Control Server now supports new operating systems. Refer to the Genesys Supported Operating Environment Reference Guide for more information.
Solution Control Server now supports new virtual operating systems. Refer to the Genesys Supported Operating Environment Reference Manual for more information.
This release includes the following corrections and modifications that were made between release 8.0 or earlier releases and the initial 8.1 release:
Solution Control Server now monitors changes in its own runmode in the
same manner as it monitors those of other Applications. When its mode changes,
it generates Standard-level Log Event 00-05151 (Application's runmode
changed to Backup
) or 00-05150 (Application's runmode
changed to Primary
) as appropriate. It also generates the Trace-level
log event 43-10610 (Application [name]: Runmode changed to [new mode]
from [old mode]
).
Previously, Solution Control Server generated these log events for other Applications, but not for itself.
(ER# 255184851)
This section provides corrections and updates for issues found in currently released documentation for this product. The changes described here will be included in future published versions of the document.
The Framework 8.1 Configuration Options Reference Manual is missing the description of the following configuration option:
distributed_sync_timeout
Default Value: 0
Valid Values: 0
or any positive integer
Changes Take Effect: Immediately
Specifies a time interval, in seconds, after which a distributed Solution
Control Server sends to other Solution Control Servers a request for the
status of objects controlled by them, while also sending the statuses of
objects that it controls. This enables all Solution Control Servers in the
configuration to synchronize object statuses and report them accordingly.
If this option is set to zero (0
, the default) or is not
defined, synchronization attempts are not sent in a timely manner.
Set this option in the general
section of each Solution Control
Server Application
object.
Notes:
60
seconds to
reduce network traffic.In the Framework 8.1 Deployment Guide, in the procedure entitled "Starting Solution Control Server manually", the following note appears in step 1 and is repeated in step 2:
Note: | If you are operating on a dual-stack machine, and dual stack is enabled,
add the following start-up parameter on the command line:-transport-ip-version 6,4 This specifies what internet protocol versions you are using, in this case IPv4 and IPv6. |
Unless you are using SCS versions 8.1.300.14 or 8.1.300.16, ignore this note. This option was added in SCS 8.1.300.14, but SCS stopped supporting it in release 8.1.300.18.
The Framework 8.1 Management Layer User's Guide contains the incorrect name of a configuration option on page 52, as follows:
autorestart
option
for each application, as described in the following procedures.The next published version of the User's Guide will contain the following corrected sentence:
autostart
option
for each application, as described in the following procedures.In addition, the Framework 8.1 Configuration Options Reference Manual is missing the description of this option, a common configuration option, as follows:
autostart
Default Value: false
Valid Values: true
, false
Changes Take Effect: After restart of the application
Specifies if SCS can start this application automatically every time SCS
establishes a connection with LCA, and if LCA does not report this application
as Started
.
Note: This option is set in the sml
section of the
Annex of the Application
object.
The next published version of the Reference Manual will contain this option and its description.
(MFWK-15180)
This section provides the latest information on known issues and recommendations associated with this product.
A solution might display a status of STARTED
before all its
applications have started. (ER# 62658371)
SCS terminates unexpectedly when the Alarm for the log event (43-)10401:
SC Interface [app name] disconnected, socket=[socket number], client's
host=[client's host] client's tenant=[ client's tenant]
is created.
(MFWK-17951)
Found In: 8.1.000.10 | Fixed In: |
If you use a tool other than Windows certificate services to generate the
TLS security certificate and then import the certificate to Windows manually,
the CERT_TRUST_REVOCATION_STATUS_UNKNOWN
validation error will
occur and the TLS connection to the Genesys server will fail.
Workaround: Set the client-auth
option to 0
(zero) to disable server authentication in the SCS TLS socket. Refer to
the Framework 8.1 Configuration Options Reference Manual for a full
description of this option and how to use it.
(MFWK-14166, ER# 324547671)
Found In: 8.1.300.14 | Fixed In: |
If one or more secure (using TLS) connections between LCA and SCS are configured incorrectly, SCS might stop responding if a connection cannot be upgraded in secure mode. (MFWK-17602)
Found In: 8.1.100.14 | Fixed In: |
When viewing logs through the Windows Event Viewer, events generated by Solution Control Server may be displayed incorrectly or not at all.
Workaround: In the registry entry
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Application\SCServer
,
change SCServer
to the name of the Solution Control Server
application as configured in the Configuration Database.
(ER# 188334011)
Found In: 7.1.100.05 | Fixed In: 8.1.200.11 |
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.
HP Compaq Tru64 Alpha is no longer supported.
Discontinued As Of: 8.1.000.10 |
IBM AIX 5.1 and 5.2 32/64-bit are no longer supported.
Discontinued As Of: 8.1.000.10 |
Red Hat Enterprise Linux (RHEL) AS 3 is no longer supported.
Discontinued As Of: 8.1.000.10 |
Solaris SPARC 8 is no longer supported.
Discontinued As Of: 8.1.000.10 |
Information in this section is included for international customers.
There are no internationalization issues for this product.
Additional information about Genesys Telecommunications Laboratories, Inc. is available on our Customer Care website. The following documentation also contains information about this software. Please consult the Framework 8.1 Deployment Guide first.
Framework 8.1 Deployment Guide provides instructions for installing and configuring Framework 8.1 components, and for starting and stopping Framework 8.1 components either using the Management Layer or manually.
Framework 8.1 Genesys Administrator Help describes how to use Genesys Administrator in either an enterprise or multi-tenant environment.
Framework 8.1 Management Layer User's Guide describes the concepts, terminology, and procedures relevant to the Management Layer.
Framework 8.0 Solution Control Interface Help describes how to use Solution Control Interface.
Framework 8.1 Configuration Options Reference Manual describes configuration options for Framework 8.1 components.
Framework 8.1 Combined Log Events Help describes log events that Genesys server applications generate and that Genesys Administrator and Solution Control Interface display.
Genesys 8.1 Security Deployment Guide describes Genesys security features and detailed instructions for deploying them. These features provide secure data transfer between Genesys components, protection against unauthorized access, and protection against data loss in case of component failure.
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.