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.genesys.com for more details.
Link to 8.0 Product Release AdvisoryThe following information applies to Genesys 8.1.x software and is important for you to note:
Genesys follows applicable third-party redistribution policies to the extent that Genesys solutions utilize third-party functionality. For additional information about third-party software used in this product, see the Read Me. Please contact your Customer Care representative if you have any questions.
The Universal Routing 8.1 Interaction Routing Designer Help file opened on Windows 64-bit operating systems may not display all the available document information correctly.
When running URS applications on Windows 64-bit operating systems, ensure that the folder in which the application is installed has Write access enabled, or point URS to another location to which it can write. The default location is the current working directory. You can archive the redirection with an additional -b command line parameter, followed by the full file name. (ER# 276581761)
The Log Library for each application looks for the common.lms file in the installation directory you
specified for that application. If you need to run the application from a different working directory, you must
either copy common.lms into the working directory or specify the command line
option -lmspath to indicate the directory in which
common.lms is located.
For application-specific messages, you must configure the messagefile configuration option
in the log section on the Options tab of the Application's Properties window and
specify the path to the application-specific *.lms file as the option value.
Genesys does not recommend installation of its components via a Microsoft Remote Desktop connection. The installation should be performed locally.
The installation script on UNIX cannot update configuration data for applications whose host computers contain
a period (".") in their names. Therefore, when configuring a Host object in the Configuration Database,
avoid using periods in the value for the Host Name property on the General tab.
If you have to use an IP address (such as 180.170.9.150) or a full host name including the domain name (such as server.genesyslab.com), expect to receive a warning during the installation of any application
on this host. The warning message tells you that the installation cannot find the specified object; as a result, the installation
script does not update the configuration data for this application. If you see this warning, continue with the installation.
After completing the installation, update the configuration data for an application you installed on this host as follows:
Properties window for the Application object in Configuration Manager.Working Directory, Command Line, and Command Line Arguments
on the Start Info tab.OK to save configuration updates.run.sh file to start the application, verify that the Working Directory, Command Line,
and Command Line Arguments are specified correctly in the run.sh file.
If you intend to use any Java extension statistics during a routing process, and you run Stat Server on a UNIX platform, remember that certain targets require attention to the names you give them; names for targets, such as Campaign Groups, Tenants, and Employee ID cannot use the Multi-Byte Character System (MBCS).