| Subcomponent Version | AIX | HP-UX | Linux | Solaris | Tru64 UNIX | Windows |
|---|---|---|---|---|---|---|
| 7.6.201.03 [12/18/09] – Hot Fix | X | |||||
| 7.6.201.02 [10/16/09] – Hot Fix | X | |||||
| 7.6.201.01 [02/20/09] – General | X | X | X | X | X | X |
| 7.6.200.08 [12/17/08] – General | X | X | X | X | X | X |
| 7.6.000.06 [02/29/08] – General | X | X | X | X | X | X |
This document applies to all 7.6 releases of the Protocol Manager Application Block for Java subcomponent that are specified in the Contents (above). For a list of other Java Platform SDK subcomponents, or to read about the Java Platform SDK in general, see the Platform SDK & Application Blocks for Java Release Note.
Note: Genesys follows applicable third-party redistribution policies to the extent that Genesys solutions utilize functionality of commercial or non-commercial third parties.
This is a hot fix for this product. This section describes new features that were introduced in this release of the Protocol Manager Application Block for Java.
This component has been updated to accommodate changes in the underlying libraries.
This release also includes the following corrections and modifications:
You can now initialize ProtocolManagementService with a user-defined receiver by using the constructor that includes a MessageReceiverSupport argument. (ER# 234146435)
This is a hot fix for this product. This section describes new features that were introduced in this release of the Protocol Manager Application Block for Java.
This component has been updated to accommodate changes in the underlying libraries.
Users can now configure the number of switchover attempts for the Warm Standby Application Block through Protocol Manager.
To use this new feature, the setWarmStandbySwitchovers property in ProtocolConfiguration class. The WarmStandbyConfiguration.setAttempts property is initialized automatically with this value when warm standby is used by the Protocol Manager Application Block. (ER# 233912293)
This release also includes the following corrections and modifications:
The Protocol Manager Application Block now creates warm standby endpoints correctly using an initialized endpoint name. Previously, data could be lost or unavailable after a warm standby reconnection. (ER#s 233617441, 233961492)
There are no restrictions for this release. This section describes new features that were introduced in this release of the Protocol Manager Application Block for Java.
This component has been updated to accommodate changes in the underlying libraries.
There are no corrections or modifications in this release.
There are no restrictions for this release. This section describes new features that were introduced in this release of the Protocol Manager Application Block for Java.
This component has been updated to accommodate changes in the underlying libraries.
With the addition of the UcsConfiguration class, the Protocol Manager Application Block for Java now supports the Contacts Platform SDK.
There are no corrections or modifications in this release.
There are no restrictions for this release. This section describes new features that were introduced in the initial 7.6 release of the Protocol Manager Application Block for Java.
This release includes the following corrections and modifications that were made between Release 7.5 or earlier releases and the initial 7.6 release:
The warm standby state is now checked before a TServerConfiguration or InteractionServerConfiguration object is unregistered. Previously, this could cause an IllegalStateException. (ER# 120478019)
Support for additional protocols has now provided. Previously, the Protocol Manager Application Block for Java was limited to the TServerConfiguration and InteractionServerConfiguration types. (ER# 120478001)
This section provides the latest information on known issues and recommendations associated with this product.
There are no known issues in this release.