Wizard Advisory

Contents

Introduction
About These Wizards
Known Issues and Recommendations

Introduction

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 Wizard Advisory contains general information about the Framework Wizards, including any limitations or restrictions.

This Wizard Advisory contains information concerning the Wizards on the following CDs:

• Management Framework 7.6
• Media 7.6

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:

• Upgrades, if necessary, the Wizards on your computer.
• Installs additional Wizard components specific to the applications distributed on the CD.
• Ensures that the Wizards you are using are compatible with the features and configuration requirements of the applications being deployed.

Use of Third-Party Software

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.

Top of Page

About These Wizards

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.

New features in the 7.6 release of Framework Wizards include the following:

• Wizards support all new features introduced in release 7.6 of corresponding applications.
• Wizards support upgrading of their corresponding applications from releases 6.5.x, 7.0, 7.1.x, 7.2, and 7.5 to release 7.6.
• Wizards can configure 6.5.x and 7.x versions of the applications. At deployment, the Wizard detects the version of the application by identifying the version of the installation package (IP) on the source CD. During upgrade of the application, the Wizard reads the version from the Application configuration object.

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.

Starting with release 7.5, the Common Wizard Component Set is no longer required. You now install configuration wizards from the appropriate product CD, and run the Wizards from a common Wizard Manager or Configuration Manager.

If you encounter an error starting with:

The required wizard module cannot be found on your computer. Corresponding Configuration Wizard may have been not installed, removed or corrupt. Try to install or reinstall the Configuration Wizard from the Product CD relevant to the configuration task you are trying to perform.

please ensure that the Configuration Wizard from the specific product CD is installed.

Example: To configure the Stat Server application with the Wizard, ensure that the Configuration Wizard has been installed from the Real-Time Metrics Engine CD, from which the Stat Server application is delivered.

(ER# 34930661)

Users who do not belong to the ADMINISTRATOR system group can now access Application-specific configuration wizards from Configuration Manager. Previously, only users who were members of the ADMINISTRATOR system group could access these wizards. (ER# 213417491)

When configuring a primary server in an HA pair for any T-Server using the common Application Wizard, the link to a backup server created in Configuration Manager (that is, without using the Wizard) is no longer removed. (ER# 169429171)

Do not create a Person configuration object with an empty password field or delete the predefined password value from the default Person Properties dialog box.

The rationale for not doing this is given in the following scenario:

1. You create a Person configuration object with an empty password field or delete the predefined password value from the default Person Properties dialog box.
2. You use the login parameters of a Person that does not have a configured password to log into the Genesys Wizard Manager.
3. You then use an application Wizard to configure a server application.

As a result, the installation script for this server cannot read the configuration parameters from the GCTISetup.INI file. The installation script then reports an error and exits without completing the setup.

In the Connection Protocol field, valid values are addp for pure 6.5 or 7.x components. Starting with release 7.5, Framework no longer supports backward compatibility of the Keep-Alive Protocol (KPL) for 6.5 clients. If you used KPL in a previous version of Genesys, consider using Advanced Disconnect Detection Protocol instead.

The Range of Agents Wizard for 7.6 now allows assignment of newly created agents to Access Groups. (ER# 155445129)

When creating a new Person using the Person Wizard in a 7.6 configuration environment, the default Access Group displayed on the Access Groups page is now updated consistently. (ER# 159610901)

Media Configuration Wizard 7.5, when used in a release 7.2 or earlier configuration environment, now completes the one-step configuration and deployment of the T‑Server in Hot Standby High Availability mode, which requires that HA Proxy operate in this mode. (ER# 109009033)

When deploying a pair of primary and backup applications with Configuration Wizards 7.5 in a release 7.2 or earlier configuration environment, the Wizard now completes the configuration if Network Log Server is selected on the Log Outputs page of the Log Wizard. (ER# 109009033)

Management Framework Deployment Manager (MFDM) supports remote deployment on these platforms only with the following versions of Windows Installer:

• Windows 2000 with Windows Installer 2.0 installed
• Windows XP with Windows Installer 3.0 installed (some special requirements are described below)
• Windows 2003 with Windows Installer 3.0 installed (some special requirements are described below)

Requirements for Windows 2003 and Windows XP:

• The source computer must be running MFDM.
• Disable the Windows firewall (and any other kind of firewall) for the source and target computers.
• The target computer for the remote deployment requires:
  • Windows Installer service started
  • Windows Management Instrumentation (WMI) service started and available for communication with the computer running MFDM
• Installers must use login accounts that have these permissions on the target host:
  • log on locally
  • access the target host over the network
  • install applications
  • launch batch jobs
• Install Windows Scripting Host (WSH) service version 5.6 on both target host and host where MFDM runs (default choice).
• Activate the WSH remote scripting option on target host via registry: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Script Host\Settings\Remote = 1
• When deploying applications on Windows 2003 or XP hosts, you must select the MFDM authentication option use the account of the currently logged-in user only. No other type of authentication is supported.

Requirements for Windows 2003 only:

• WMI Windows Installer Provider component installed and activated on Windows 2003. Activate this component from Add/Remove Windows Components > Management and Monitoring Tools > Details.

(ER# 91229)

Before deploying components on a host running a Windows operating system, set the option Every visit to the page in the Internet Explorer settings on both the computer where the Deployment Manager is installed and the target computer where the component will be deployed.

Note: To enable this setting:

1. In the Internet Explorer window, select Tools > Internet Options. This opens the Internet Options dialog box.
2. In the Temporary Internet files section in this dialog box, click the Settings button.
3. In the Settings dialog box, select Every visit to the page and click OK.

The Configuration Import Wizard is now located on the Management Framework CD, and does not require a separately-purchased license.

Starting with Configuration Import Wizard 7.1, you can now launch the Wizard from Configuration Manager.

You can now import configuration data from the Cisco CallManager switch using the CCM Extractor utility that comes with Configuration Import Wizard.

You can now use the Switch Configuration Synchronization Utility, which comes with Configuration Import Wizard, to synchronize configuration data before importing the data into the Configuration database.

Keep in mind that Configuration Conversion Wizard (CCW) converts predefined configuration objects according to the following rules:

• If a user has modified any parameters of a predefined configuration object in the original Configuration Database, CCW keeps the user-specified values while converting the object data to 7.6 database structures.
  
  CCW does not substitute the modified values with new default values for these objects.
• If a user has deleted any predefined configuration objects from the original Configuration Database, CCW creates a new similar object instead of maintaining the deletion while converting the object data to 7.6 database structures.
  The predefined object exists in the converted database even though you deleted it from the original database. The only exceptions to this rule are Alarm Condition objects, which are not re-created in the converted database.

When using Configuration Conversion Wizard to check the data in your Configuration Database for correct business logic, you can:

• Print the results of the business logic check by right-clicking on the results page and selecting Print from the shortcut menu.
• Return to the top of the results page from any report section by right-clicking on the results page and selecting Back from the shortcut menu.

Top of Page

Known Issues and Recommendations

This section provides the latest information on known issues and recommendations associated with these Wizards:

Wizards are not localized in release 7.x. 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: Windows 2000, Windows XP, or Windows Server 2003.

Management Framework Deployment Manager is not compatible with Windows hosts on which Microsoft update KB842773v2 (Windows Installer 3.1) is installed. (ER# 107148941)

Configuration Conversion Wizard does not support conversion of Informix database release 5.1.504�5.1.508.

For DB2 databases, Configuration Conversion Wizard supports migrating only release 6.0 and later.

The "Installation Package" screen in an application Wizard may falsely display the following warning:

Selected Source is a newer version of the CD. This Wizard can configure the newer version of the application incompletely or incorrectly. Although you can continue to deploy the application with this Wizard, it is strongly recommended that you install the newer Wizard before deployment from this CD.

This warning occurs if 6.5 Configuration Wizards (for example, a 6.5 solution Wizard) are installed after 7.x Wizards. Ignore the above warning if it is displayed in the described case. Always make sure you install the Configuration Wizards from the product CD used for the deployment of a given component. (ER# 61576)

SCS Deployment Wizard for Solution Control Server (SCS) does not allow you to specify license information. If your SCS requires a license, configure it manually. (ER# 59694)

You cannot use Configuration Wizards to modify predefined or create new Time Zone configuration objects. When such modifications are required, use Configuration Manager. (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.

Workaround:
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):

1. Add the connection to Configuration Server (the confserv Application Object).
2. Specify a reasonable ADDP Local Timeout.

(ER# 107854372)

If you want to use Configuration Wizards to create an Application for T‑Server for Cisco CallManager, keep the following in mind:

• Configuration Server supports Switching Offices of the Cisco CallManager type 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.
• If upgrading, execute the localization data script for your database type to update the supported Switching Office types (for example, CfgLocale_db2.sql for the DB2 DBMS). Do NOT execute any initialization scripts (such as init_single_db2.sql for a Single-Tenant Configuration Database on the DB2 DBMS).

The new Wizard Manager's Solution Reporting page launches Wizards starting only with the 7.0 version of the Reporting CD. Reporting options of the 6.5 solutions will be configured through the corresponding solution's pages.

Top of Page