About These Wizards
Link to 8.0 Wizard Advisory
Known Issues and Recommendations
This Wizard Advisory contains general information about the Framework Wizards, including any limitations or restrictions.
This Wizard Advisory contains information concerning the Wizards on the Management Framework 8.1 CD.
The Framework Wizards support installation, configuration, and dynamic modification of contact center objects. The Wizard also initiates the application deployment process by pre-configuring an application, customizing and copying a relevant installation package, and reminding users to run the setup and the executable of the application.
Before deploying any application with Configuration Wizards from any Genesys CD, always make sure that Configuration Wizards have already been installed from the CD that you are using for deployment. If you are not sure, run Wizard Setup from the CD. This procedure:
Genesys follows applicable third-party redistribution policies to the extent that Genesys solutions utilize third-party functionality. For specific information on any third-party software used in this product, see the Read Me. Please contact your technical support representative if you have any questions.
Top of Page
Please note the following information about the Framework Wizards:
The information in this advisory is needed to correctly configure Genesys Framework. Read this advisory before running the Framework Wizards.
Starting with release 8.0, Wizard Manager now supports the inactivity timeout
feature, in which a user must be reauthenticated after a user-defined period
of inactivity. The value of the Configuration Manager configuration option
inactivity-timeout also applies to Wizard Manager.
Before using the Wizard Manager, make sure Configuration Server, with its corresponding DB Server, is running. Configuration Manager is not required for the Wizards to operate. To start Configuration Manager from the Wizard Manager, you need to install it separately.
Do not create a
Person configuration object with an empty
password field or delete the predefined password value from
Person Properties dialog box.
The rationale for not doing this is given in the following scenario:
Personconfiguration object with an empty
passwordfield or delete the predefined password value from the default
Person Propertiesdialog box.
Personthat does not have a configured password to log into the Genesys Wizard Manager.
As a result, the installation script for the server cannot read the
configuration parameters from the
GCTISetup.INI file. The
installation script then reports an error and exits without completing the
Configuration Import Wizard now supports the use of international characters when importing Agents from LDAP or Active Directory.
When using LDAP for external authentication, Configuration Import Wizard
now ignores any LDAP attributes with binary data to prevent control
characters appearing in the output
(MFWK-12778, ER# 280529074)
In Configuration Import Wizard, you can now import very large data files
without interruption by setting
SOAP timeout value on the
Load Data page of Configuration Import Wizard. This option
value can be set to a value from 1 second to 2,000,000 million seconds
(approximately 23 days), with a default value of 500 seconds.
Before using the Configuration Import Wizard to import Agents, set the
Application object's configuration option
1. This ensures that these
Agents are added to the
Users Access Group, and have the
appropriate access privileges.
When using Configuration Conversion Wizard to check the data in your Configuration Database for correct business logic, you can:
Backfrom the shortcut menu.
When using Configuration Conversion Wizard on the Windows Vista platform, you can now enter connection parameters in the Wizard. Previously, you could only enter those parameters directly in the configuration file.
If you are converting a DB2 configuration database from 7.6, use Configuration Conversion Wizard version 8.1.000.03 instead of 8.1.000.02. If you use version 8.1.000.02, the conversion fails and the following error message generated:
SQL20112N – A SAVEPOINT cannot be set because a SAVEPOINT already
exists and nested SAVEPOINTS are not supported and the conversion will not
Before using the Configuration Conversion Wizard (CCW) with an Informix database, make sure that the locale settings at the DB Server host and at the client machine that is running CCW are the same. If the settings are not the same, CCW will not connect to the Informix database.
Starting with version 8.1.3, you can now use Configuration Conversion Wizard
(CCW) to convert:
You cannot use the Configuration Conversion Wizard to import or export a
database if the Wizard detects the database as being an
UTF-8>. In this case, the Import and Export
options are disabled in the Wizard. (MFWK-14161, ER# 324404411)
When upgrading a database, Configuration Conversion Wizard 8.1.3 now sends
schema reload request to pick up the most recent locale
update. This request is sent when the Wizard is reviewing the database to
be upgraded. In addition, the current locale version is displayed along
with the database version on the database information page of the Wizard.
After the new locale is loaded, the new locale version is also displayed.
Previously, Configuration Conversion Wizard did not send the request, nor did it display the locale version information.
(MFWK-14015, ER# 320974487)
Configuration Conversion Wizard version 220.127.116.11 and later now properly
creates new Genesys Administrator and Genesys Administrator Server
Application objects. Previous versions of the Wizard sometimes
created these objects with incorrect database IDs (DBID). (MFWK-13793,
Top of Page
This section provides the latest information on known issues and recommendations associated with these Wizards:
Wizards are not localized. However, when operating with a localized version of Configuration Server and/or on a localized version of Windows, Wizards display part of the text in the local language. As a result, the Wizard screens contain text partially in English and partially in the local language.
When configuring Host objects for the Windows server hosts, do not specify
Windows as the
OS Type. Instead, select a specific version of
the Windows operating system.
The Configuration Wizards do not work on the following operating systems:
When importing a large data file using the XML Import Wizard, part of the
Configuration Import Wizard, the following error message may be displayed
in error when the import completes successfully:
during conversion. See log for details. Unspecified error. This
error can be ignored.
In addition, the Wizard does not provide any indication that the import was completed successfully, either in the dialog box or in the log.
The result of a comparison of two databases using the Comparison Wizard (part of the Configuration Import Wizard) cannot be successfully imported into either database. (MFWK-11741, ER# 235253211)
If the Configuration Database contains corrupted password fields resulting from, for example, improper manual updating of the database, and these fields contain characters that cannot be represented properly by Genesys Administrator, attempting to launch Genesys Administrator against this database would cause an error. To prevent this from occurring, examine any database fields that you may have modified manually, and correct their values.
Warning: Do not manually make any changes to the Configuration Database. Use only the tools provided in Genesys software.
You cannot use Configuration Wizards to modify predefined or create new
Time Zone configuration objects. When such modifications are
required, use Genesys Administrator or Configuration Manager.
(MFWK-9671, ER# 75851016)
If Configuration Server terminates unexpectedly, all Configuration Server requests posted by the Configuration Wizards between the time the termination occurred and the time the disconnect was detected fail. Although the failure is properly reported to each Wizard, some Wizards do not process these cases correctly. This may cause the Wizard to stall or behave incorrectly after the connection to the server has been restored.
To minimize the time interval during which failure can occur, enable Automatic Disconnect Detection Protocol (ADDP) on the connection between Wizard Manager and Configuration Server. ADDP will ensure the timely detection of the disconnection from Configuration Server. To enable ADDP, do the following in the
Application configuration object used to log in to Configuration
Server (usually, the
default Application Object):
(MFWK-10030, ER# 107854372)
If you want to use Configuration Wizards to create an Application for T‑Server for Cisco CallManager, keep the following in mind:
Switching Officesof the
Cisco CallManagertype starting with release 6.5.000.12. This means that you must have Configuration Server release 6.5.000.12 or later in order to run Configuration Wizard for T‑Server for Cisco CallManager. Check the release number of your Configuration Server and upgrade if necessary.
Switching Officetypes (for example,
CfgLocale_db2.sqlfor the DB2 DBMS). Do NOT execute any initialization scripts (such as
init_single_db2.sqlfor a Single-Tenant Configuration Database on the DB2 DBMS).
If Configuration Wizard is invoked from Configuration Manager, Configuration Wizard screens and their contents are not minimized when the user is locked out of the system because of inactivity. Refer to the Framework 8.x Security Deployment Guide for more information about the Inactivity Timeout feature.
The Database Initialization Wizard sometimes processes the database initialization scripts incorrectly, so the databases may not be initialized properly.
Workaround: Use the DBMS client for your DBMS to manually run the scripts. Refer to the product-specific Deployment Guide for detailed instructions to manually initialize databases.
(MFWK-12683, ER# 274331519; MFWK-12675, 274222203; MFWK-12140, 250706471; MFWK-12222, 254161078)
When converting a database, Configuration Conversion Wizard (CCW) can create new configuration objects, the names of which might conflict with the names of existing configuration objects. In these cases, the new objects do not appear in Genesys Administrator.
For example, starting in release 8.1.1, CCW creates two new
Genesys Administrator and
Genesys Administrator Server, during database conversion. If
objects with these names already exist in the Configuration Database,
the new objects will not appear in Genesys Administrator.
Workaround: Before running the Wizard, rename any existing objects for which the conflict will occur. Then, after running the Wizard, rename or delete the new objects and change the original objects back to their original names.
(MFWK-13296, ER# 296585821)
Configuration Server does not export Campaign objects that contain Campaign
Groups into XML correctly. If Campaign Groups exist, they are stored in XML
as obsolete entities
CampaignGroupInfo that cannot be imported.
This issue appears to have been introduced in release 7.5 and affects both
import and export methods, using SOAP or the Configuration Server internal
and export feature (
in Configuration Server. (MFWK-14427)
Top of Page