Prerequisites

Before upgrading Genesys Administrator Extension, you must ensure that your system meets the prerequisites described in this section.

Management Framework

You must be running Management Framework 8.1.0 or later to support GAX.

If you are currently running a release of Management Framework earlier than 8.1.0, refer to Management Framework documentation to upgrade to the required release of Management Framework.

Genesys Administrator Extension

You must be running GAX 8.1.320.xx or higher to upgrade to GAX 8.5.x.

If you are currently running a GAX version older than 8.1.320, refer to the GAX chapter in the Genesys Migration Guide for instructions to upgrade to GAX 8.1.320.xx.

Computing Environment Prerequisites

Recommendation: To avoid issues with role assignments, you should upgrade the application, metadata, and the roles to the new type when you migrate to the latest version of GAX or perform a fresh install.

The computer on which you install GAX must be capable of acting as a web application server, and must be running one of the following:

• Red Hat Enterprise Linux 5.5 (64-bit) - Enterprise Edition, with Updates from RHN enabled
• Red Hat Enterprise Linux 6.0 (64-bit) - Enterprise Edition, with Updates from RHN enabled
• Red Hat Enterprise Linux 7.0 (64-bit) - Enterprise Edition, with Updates from RHN enabled

Or,

• Windows Server 2008 R2, with 64-bit applications running natively on a 64-bit operating system
• Windows Server 2012, with 64-bit applications running natively on a 64-bit operating system

The computer must also run the following:

• Java 6,7,or 8 Runtime (JRE) from Oracle. See the Genesys Administrator Extension Deployment Guide for information about obtaining and installing Java, if necessary.

GAX 8.5.x uses an embedded Jetty instance as the web application server; as a result, Tomcat is no longer a prerequisite to use GAX. For those who choose to use Tomcat instead of Jetty, GAX requires Tomcat 6.0.37 (or a later version from the Tomcat 6.0.x branch) or Tomcat 7. Refer to Migration Procedures for additional information.

In addition, each module of Genesys Administrator Extension might have additional prerequisites. Refer to the Genesys Administrator Extension Deployment Guide for more information.

Browser Requirements

Genesys Administrator Extension includes a web-based GUI with which you can manage Genesys applications and solutions. It is compatible with the following browsers:

• Microsoft Internet Explorer 9.x, 10.x, 11.x
• Mozilla Firefox 17 or higher
• Safari 6,7, or 8, on Macintosh systems
• Chrome

Genesys Administrator Extension supports all major browsers, but it is optimized for Chrome. If you use Microsoft Internet Explorer or Safari, refer to the Genesys Administrator Extension Deployment Guide for troubleshooting information specific to your browser.

Genesys Administrator Extension is designed to be viewed at a minimum screen resolution of 1024x768, although higher resolutions are recommended. If you are working in 1024x768 mode, maximize your browser to ensure that you can see all of the interface.

Required Permissions and Role Privileges

Genesys Administrator Extension uses a permission-based mechanism and a role-based access control system to protect your data. Before installing and using Genesys Administrator Extension, ensure that all users have the necessary access permissions and role privileges to do their work. The following are examples of scenarios that require permissions:

• A Tenant user must have write (Update) permission on his or her User object to set and save his or her User Preferences in Genesys Administrator Extension.
• To log in to Genesys Administrator Extension, a user must have Read permission on his or her User object, Read and Execute permissions on his or her Tenant object, and Read and Execute permissions on the Genesys

Administrator Extension client Application object. These permissions are usually assigned by adding the users to access groups.

There are no role privileges required to log in to GAX; however, GAX-specificfunctions may require additional role privileges to be enabled. Refer to the Genesys Administrator Extension Deployment Guide for more information about role privileges that are specific to Genesys Administrator Extension.

Deploying Multiple Instances of GAX with Shared Resources

You can install multiple instances of GAX to support both High Availability (HA) and load balancing. You can also install multiple instances of GAX to take advantage of the GAX plug-in architecture. Each instance of GAX can be deployed with a different combination of plug-ins.

In either scenario, the multiple instances of GAX share the same data resources, such as Configuration Server, the GAX database, and audio resources, but are executed independently by different users on different hosts.

Minimum Required Firewall Permissions and Settings for GAX Deployment

Your firewall must allow incoming connections on the http and https ports (for example, 8080, 80, 433, and so on, based on your setup). The application server can listen on more than one port at once.

You must allow outgoing connections to allow GAX to establish connections; however, you can restrict the connections to networks that contain the following components:

• GDA hosts
• Databases
• Genesys configuration layer servers: Configuration Server, Message Server, and Solution Control Server

Minimum Required File System Permissions and Settings for GAX Deployment

The GAX operating system user is the user that runs the GAX process. The GAX operating system user must have the following permissions:

• Write permission on the log file folder
• Read/write access to the folder configured for ARM (Audio Resource Management)

Enabling UTF-8 Encoding (for Oracle Databases)

Genesys Administrator Extension optionally supports UTF-8 character encoding for Oracle databases. This functionality requires Configuration Server 8.1.2 or later. For more information, refer to the Genesys Administrator Extension Deployment Guide.