8.5.0 Stat Server Migration Guide
Contents
Stat Server 8.5.0 General Changes
- Stat Server supports multiple Interaction Servers that handle the same Tenant.
- Stat Server supports the EventHint panic signal from Interaction Server. Refer to the eServices Reference Manual for more information about this feature.
- Stat Server supports Interaction Server Proxy.
- Stat Server supports direct connection to the database.
- Stat Server features a more robust DND model implementation for voice.
- Stat Server processes network messages (client and server) in a separate thread.
- Stat Server supports a higher number of concurrent client connections (on most platforms).
- Stat Server no longer supports Genesys suite-wide deployment wizards. All deployment wizards migrate to Genesys Administrator Extension (GAX):
- Resource Capacity Editor of GAX covers all the functionality that was covered by the Recourse Capacity Wizard.
Compatibility with Framework Components
Stat Server 8.5 interoperates successfully with the following Framework components:
- Configuration Server, releases 6.5 through 8.5
- Local Control Agent, releases 6.5 through 8.5
- Message Server, releases 6.5 through 8.5
- DB Server, releases 6.5 through 8.1
- T-Server, release 6.5 through 8.5
- Solution Control Server, release 6.5 through 8.5
However, to access all of the features that are available in a particular release, Genesys recommends that you operate Stat Server within the same family of Framework components in which it was released, or the latest available component release. Otherwise, some documented features may not be available to you.
Configuration Option Changes
| Current Option Name |
Section | Type of Change |
Release # in Which Change Occurred |
Details |
|---|---|---|---|---|
| debug | [db-direct-connection] | Added | 8.5.0 | Controls advanced debugging information on interactions with a database in the direct connection mode. |
| enable | [db-direct-connection] | Added | 8.5.0 | Enables direct database connection. |
| identity-in-login-table | [statserver] | Added | 8.5.0 | Applicable only for Oracle. Enables Stat Server to fill the APP_DBID field in LOGIN table. This option is required for Stat Server to operate with an Oracle Real Application Clusters (RAC). |
| verbose | [db-direct-connection] | Added | 8.5.0 | Controls the verbosity level of Stat Server log messages about SQL statement and other database-related activities. |
Migrating from Stat Server 8.1.2 with Connection to DB Server, to Stat Server 8.5.0 with Direct Database Connection
Prerequisites:
- A Database Access Point (DAP) properly configured for connection to the database with initialized Stat Server tables.
- Installed and properly configured related DBMS client software.
Migration steps:
- Install Stat Server 8.5.0.
- In the Stat Server application object, under Options / Application Options (GAX), in the [db-direct-connection] section set the enable option to on. Default value for the enable option is off.
- Optional. Set the verbose option in the db-direct-connection section to a value from 1 to 4 to produce more verbose log output on Stat Server database-related activities.
For DB2, you can install the IBM Data Server Runtime Client.
For SQL Server, you can install Microsoft Data Access Components (which includes ODBC), but this should not be necessary as Windows ships with ODBC.Migrating LOGIN table from 8.1.2 to 8.5.0 for Oracle
In general, Stat Server tables upgrade is not required, because Stat Server 8.5 works properly with tables from previous releases. If you use Oracle RAC environment, you must upgrade the LOGIN table using the upgrade script, which adds extra fields.
Using the Oracle sqlplus client, run the script sql_scripts/oracle/upgrade_850_login_oracle.sql, which will upgrade the table for use with Stat Server 8.5.0, and migrates existing data. This script creates two additional fields, ID and APP_DBID. Note that for existing data, the APP_DBID field will simply be set to 0.
- Running the script login_oracle.sql creates the table, and deletes previously existing data from it.
- Before you begin, back up your original LOGIN table, because running this script will reinitialize it, removing any old data from this table.
In the Stat Server application object, under Options / Application Options (GAX), in the [statserver] section set the identity-in-login-table option to on. This setting is not on by default.