Release Advisory

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.

The 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 technical support representative if you have any questions.

For 8.1.4 releases, it is important that you take note of the following limitations:

• Genesys Administrator Extension (GAX) does not support wizards. You must use Genesys Administrator, Configuration Manager, or a solution definition to create ranges of certain configuration objects, such as DNs or IVR Ports. For objects in the Accounts menu, you can continue to use Bulk Change Sets to create ranges of objects.
• Setup Mode can install Primary and Backup Configuration Servers and a Database Server, but Solution Control Server must be installed and functioning to operate these servers in a high-availability (HA) configuration.

For releases before 8.1.201.30, if the [sml]autostart option is set to the value true for GAX, Solution Control Server attempts to start two instances of GAX. The two instances block each other. To avoid this scenario, a single line should be added to the gax_startup.sh script. This line checks to determine whether the specific Tomcat instance is already running. If it is, it will terminate the already running process.

Open the GAX startup script (gax_startup.sh). Add the line that starts with ps to the existing script, which is located in the Tomcat/bin directory:

-----
#!/bin/bash
export GAX_CMD_LINE_ARGS=$*
ps -ef | grep java | grep `pwd` | awk '{print $2}' | xargs -n1 kill -9
./startup.sh
-----

If you plan to delete a Tenant and all of its resources, you should first delete the Operational Parameter Management (OPM) and Audio Resource Management (ARM) resources. If you delete the Tenant first, these resources will be inaccessible through the GAX interface.

When using Genesys Administrator Extension and Genesys Administrator in a load-balanced environment, download the metadata for Genesys Administrator Extension and associate it with the corresponding Application Template object on only one of the Genesys Adminsitrator instances. Then, copy the content of the resources/metadata folder for that instance to the other instances of Genesys Administrator.

The following upgrade information was not included in the 8.1.101.00 version of the Genesys Administrator Extension 8.1 Deployment Guide:

To upgrade to the latest Genesys Administrator Extension (GAX), perform the following steps:

1. Stop the instance of GAX that you intend to upgrade.
2. Run the GAX installer for the version that you want to upgrade to on the target machine. The installer copies the binary file to the Tomcat instance that was defined during installation and also copies all required files to the target directory.
3. Run all upgrade scripts from the previous version of the database, if required. To determine if you need to apply any database scripts, check the resources/scripts folder in the installation target directory.
   
   If you are running version 8.1.001.31 and you intend to upgrade to version 8.1.101.14, you must execute two SQL scripts in order from lowest version to highest version. For example:
   
   
   • gax_upgrade_8.1.001.31_to_8.1.101.13.sql
   • gax_upgrade_8.1.101.13_to_8.1.101.14.sql
   
   Notes:
   
   • Files that have version numbers prior to the ones from which you upgraded do not have to be executed.
   • You must log in to the database schema as a GAX user and run the commands inside the SQL scripts as commands for the database.

(ER# 284144277)

Top of Page