Upgrading to the latest Genesys Administrator Extension for Management Framework 8.1.1 or higher

Purpose

• To upgrade from an earlier release of GAX to the latest release for Management Framework 8.1.1 or higher.

Start

1. Stop the instance of GAX that you want to upgrade.
2. Ensure that Management Framework, Configuration Server, and Genesys Administrator are all upgraded to versions that are compatible with the latest version of GAX before proceeding (refer to Prerequisites for Genesys Administrator Extension Modules).
3. This step applies only to instances that use GAX Application object of type Genesys Generic Server.

Create and configure the configuration objects that are required for the latest version of GAX by using Genesys Administrator to perform the following steps:

1. Open your existing GAX Application object of type Genesys Generic Server in edit mode.
2. Click the Options tab.
3. Click Export to save your configured GAX options to a file on your local file system of type CONF/CFG.
4. Create and configure a new Server Application object for Genesys Administrator Extension of type Genesys Administrator Server by following Step 4 of Creating the necessary configuration objects for Genesys Administrator Extension.
1. Ensure that you follow the steps that pertain to the use of Management Framework Configuration Server 8.1.1, or higher.
2. Replicate any configuration that you wish to add to your newly created Application object by referring to the GAX Application object of your previous version.
3. Click the Options tab.
4. Click Import and specify the CONF/CFG file that you previously created. Select No to not overwrite any existing options.
5. (Optional) Create a DAP that points to the Log Database (refer to Step 3 of Creating the necessary configuration objects for Genesys Administrator Extension. Set the role of the DAP to auditing. Enable auditing by setting the value of the general/auditing option to true. Add the DAP to your GAX connections. On the Options tab of the DAP, in the GAX section, configure the role option with the value auditing.
4. On the target machine, run the GAX installer for the release to which you want to upgrade. The installer copies the binary file to the Tomcat instance that was defined during installation and copies all of the required files to the target directory. For more details, refer to the Installing Genesys Administrator Extension server on a Linux host or Installing Genesys Administrator Extension server on a Windows Server 2008 host.
5. Remove or deactivate all old GAX objects. You can use only one GAX Application object to point to one physical GAX instance. If you want more than one GAX Application object to point to a single machine, you must install separate physical GAX instances on the same machine, each with a separate, independent, Tomcat installation.
6. Execute all of the applicable database upgrade scripts, if necessary. To determine if you have to apply any database scripts, check the resources/sql_scripts folder in the target directory of the installation.

Note: GAX database schema version numbers are not necessarily synchronized with the version numbers of plug-ins, nor will they necessarily match the GAX release number. For example, your version of GAX might be 8.1.201.54 and your database schema version might be 8.1.201.25.

Perform one of the following steps, depending on whether you are using Oracle or Microsoft SQL:

• (Oracle only) Run all of the database upgrade scripts from the previous version. To determine if you have to apply any database scripts, check the resources/sql_scripts folder in the target directory of the installation.

  For example, if you have release 8.1.201.25 running and you intend to upgrade to release 8.1.300.XX, you must execute the following SQL scripts:

  • gax_core_upgrade_db_8.1.201.25_to_8.1.300.XX_ora.sql
  • (For Solution Deployment only) gax_asd_upgrade_db_8.1.201.15_to_8.1.300.XX_ora.sql
  • (For Operational Parameter Management only) gax_opm_upgrade_db_8.1.201.15_to_8.1.300.XX_ora.sql
• (Microsoft SQL only) Run all of the database upgrade scripts from the previous version. To determine if you have to apply any database scripts, check the resources/sql_scripts folder in the target directory of the installation.

  For example, if you have release 8.1.201.25 running and you intend to upgrade to release 8.1.300.XX, you must execute the following SQL scripts:

  • gax_core_upgrade_db_8.1.201.25_to_8.1.300.XX_mssql.sql
  • (For Solution Deployment only) gax_asd_upgrade_db_8.1.201.15_to_8.1.300.XX_mssql.sql
  • (For Operational Parameter Management only) gax_opm_upgrade_db_8.1.201.15_to_8.1.300.XX_mssql.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. If you are installing GAX for the first time or upgrading from release 8.1.x to 8.1.3, when you execute the SQL upgrade scripts, make sure that the scripts are properly committed. If your client application has auto-commit switched off, you might have to add the following line(s) to the scripts. For Oracle: commit; For MS SQL: BEGIN TRANSACTION;COMMIT TRANSACTION;

(Optional) You can delete the previous GAX Application object after you have verified that the new release is working correctly.

End

Install GAX

Refer to the Installing Genesys Administrator Extension server on a Linux host or the Installing Genesys Administrator Extension server on a Windows Server 2008 host.