| Release Number | AIX | HP-UX | Linux | Solaris | Tru64 UNIX | Windows |
|---|---|---|---|---|---|---|
| 7.6.001.05 [10/20/09] – Hot Fix | X | |||||
| 7.6.001.04 [10/08/09] – Hot Fix | X | |||||
| 7.6.001.03 [12/18/08] – General | X | X | X | X | X | X |
| 7.6.001.01 [10/07/08] – Hot Fix | X | X | ||||
| 7.6.001.00 [02/14/08] – General | X | X | X | X | X | X |
| 7.6.000.03 [10/10/07] – 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.genesyslab.com for more details.
This release note applies to all 7.6 releases of Solution Control Server (SCS).
Genesys follows applicable third-party redistribution policies to the extent that Genesys solutions utilize functionality of commercial or non-commercial third parties. For specific information on any third-party software used in this product, see the Read Me.
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 section, above.
This is a hot fix for this product. This release contains no new features or functionality.
This release includes the following correction and modification:
Solution Control Server now continues trying to reconnect to the active Configuration Server in a Configuration Server high availability (HA) pair. Previously, Solution Control Server sometimes stopped trying to reconnect if the previous attempt failed. (ER# 235719610)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents section, above.
This is a hot fix for this product. This release introduces the following new feature and functionality:
This release does not include any corrections and modifications.
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents section, above.
There are no restrictions for this release. This release contains no new features or functionality.
This release includes the following corrections and modifications:
Solution Control Server (SCS) no longer attempts to establish a connection
with its backup SCS. Previously, after a number of switchovers caused by
network outages, the primary SCS sometimes improperly tried to establish a
connection to its backup SCS. This incorrect behaviour caused the primary
SCS to consider the status of the backup SCS to be STOPPED
because the backup SCS was (properly) rejecting all connection requests.
(ER# 167459402)
Synchronization of Application status and run modes between Distributed Solution Control Servers has been improved. Previously, an SCS that switched to Primary mode did not send to other Distributed Solution Control Servers any information about changes that occurred during the switchover. As a result, the other Distributed Solution Control Servers did not have the correct status and run mode of all Applications. (ER# 194549701)
If a network outage causes both Message Servers in a high-availability (HA) pair to run in Primary mode, SCS will now always switch one of them into Backup mode after the connections are restored.
Previously, both Messages Servers continued running in Primary mode if both of the following conditions were true:
disconnect-switchover-timeout had been configured
in SCS.disconnect-switchover-timeout had expired.(ER# 211724541)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents section, above.
This is a hot fix for this product. This release contains no new features or functionality.
This release includes the following corrections and modifications:
For applications that started in the ServiceUnavailable
state, Solution Control Server now sends to Local Control Agent (LCA) the
parameters of the Configuration Server currently operating in Primary Mode.
Previously, Management Layer sometimes failed in its attempt to automatically
restart a terminated application that had been running in ServiceUnavailable
state only, because the incorrect Configuration Server
parameters were used.
(ER# 200230268)
Solution Control Server no longer terminates when processing an E-mail Alarm Reaction if the e-mail template contains one or more fields longer than 255 characters. (ER# 200255949)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents section, above.
There are no restrictions for this release. This release contains no new features or functionality.
This release includes the following corrections and modifications that were made between the initial 7.6 release and this release:
Distributed Solution Control Servers now correctly handle the switchover of redundant servers when one server is running in primary mode, and a redundant server starts, also in primary mode. Now, the first server stays in primary mode, and the redundant server switches over to backup mode. Previously, the first server sometimes switched over to backup mode, and the redundant server stayed in primary mode. (ER# 154825826)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents section, above.
There are no restrictions for this release. This section describes new features that were introduced in the initial 7.6 release of Solution Control Server.
Solution Control Server now supports the autostart option for third-party
applications. Hosts on which third-party applications reside must be running Local Control
Agent version 7.6.000.01 or later.
This release includes the following corrections and modifications that were made between release 7.5 or earlier releases and the initial 7.6 release:
Starting with this release, in a distributed Solution Control Server (SCS) environment, a clearance alarm reaction is now executed only by one SCS—the SCS that actually generated this alarm. If there are one or more SCSs in the distributed environment running an earlier version, the alarm clearance reaction may be executed multiple times. (ER# 104066141)
The following new log event is now generated by SCS in a distributed environment if an active alarm is cleared but the configured clearance reaction is not executed by SCS because the active alarm was generated by another distributed SCS responsible for alarm clearance reaction execution:
10514|TRACE|GCTI_SCS_EXEC_REACTION_IGNORED |Reaction '%s' ignored by this SCS
(ER# 104066141)
The ADDP connection between SCS and Message Server now works correctly.
Previously, the ADDP connection to Message Server (both Log Message Server and dedicated Message Server)
could only be established if the log output of type network set in the SCS configuration.
Also, the ADDP connection could only be established with the one instance of Message Server
regardless of the number of Message Servers configured in the SCS connections.
(ER# 60310062)
When operating in a high-availability environment, the SNMP functionality is now available in SCS when simultaneous switchovers of both SCS and Configuration Server redundant pairs occur. (ER#s 149108231, 143785654)
SCS now correctly applies startup timeout settings for starting applications configured with the autostart options. Previously, SCS ignored the startup timeout settings after its initialization and applications were started immediately. (ER# 113834987)
SCS no longer becomes unstable when processing the errors occurred during alarm email transmitting. (ER# 113524336)
This section provides the latest information on known issues and recommendations associated with this product.
SCS may stop responding if any log spool files (*.qsp)
are deleted while SCS is running. To avoid this problem, do not delete
*.qsp files. (ER# 7501901)
A solution may display a status of STARTED before all its
applications have started. (ER# 62658371)
| Found In: 7.1.100.05 | 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.
UNIX domain socket mode connections with SNMP Master Agent are no longer supported.
| Discontinued As Of: 7.5.000.08 |
Information in this section is included for international customers.
There are no known limitations or restrictions for internationalization.
Additional information on Genesys Telecommunications Laboratories, Inc. is available on our Technical Support website. The following documentation also contains information about this software. Please consult the Framework Deployment Guide first.
Framework 7.6 Deployment Guide provides instructions for installing and configuring Framework 7.6 components, and for starting and stopping the Framework 7.6 components either using the Management Layer or manually.
Framework 7.6 Management Layer User's Guide describes the concepts, terminology, and procedures relevant to the Management Layer.
Framework 7.6 Solution Control Interface Help describes how to use Solution Control Interface.
Framework 7.6 Configuration Options Reference Manual describes configuration options for Framework 7.5 components.
Framework 7.6 Combined Log Events Help describes log events that Genesys server applications generate and that Solution Control Interface displays.
Genesys 7.6 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.