Prerequisites for Genesys Administrator Extension Modules
Contents
[hide]This section describes prerequisites to be met before installing or using the functional modules of Genesys Administrator Extension. These are in addition to the basic prerequisites listed here, and are specific to the corresponding module.
Solution Deployment
Before using Solution Deployment to deploy Solutions to local and remote hosts, you must ensure that the following prerequisites are met:
- Hosts are set up and running at the remote locations, and are running Local Control Agent (LCA) and Genesys Deployment Agent (GDA). Use the instructions in Genesys Administrator Extension Help.
ImportantStarting from Local Control Agent 8.5.100.31, GDA is no longer installed and supported as part of Management Framework and therefore all functionality using GDA (including the installation of IPs) is deprecated.
- The following configuration options are defined on the Options tab of the Genesys Administrator Extension server Application object in the asd section:
- silent_ini_path
- local_ip_cache_dir
Refer to Configuration Options for more information about these options.
- An appropriate SQL client is installed for solution definitions that include <os:execSQL> commands. You can use the following clients for each database type:
- Oracle—SQL*Plus
- Microsoft SQL Server—sqlcmd
- PostgreSQL—psql
Operational Parameter Management
For the deployment of Parameter Groups, ensure that you have write permissions to the Transactions folder of the tenant on which the Parameter Group is deployed. You must also have write privileges for the Voice Platform Profiles folder to deploy the Voice application and/or write privileges for the Routing Scripts folder to deploy Genesys IRD or SCXML routing strategies.
There are no additional prerequisites for using Operational Parameter Management in Genesys Administrator Extension. However, ensure that your Interaction Routing Designer (IRD) routing strategies reference the Transaction objects correctly.
Operational Parameter Management works together with routing strategies, SCXML routing strategies, GVP voice applications, and Genesys Business Rules.
Audio Resource Management
- Internet Explorer does not support playing an audio file directly. You have to download the file and playback the file locally. Firefox cannot play µ-law and A-law audio codecs. Only PCM Audio codecs can be played in Firefox.
- If you will be converting audio file formats, you must install SoX (Sound Exchange) before doing any conversions. Use the procedure under the appropriate tab below.
Before using ARM on Linux, you must do the following:
1. Add the configuration option section [arm] and define the following configuration options on the Options tab of the Genesys Administrator Extension server Application object:
[+] Show options [arm]
See Configuration Options for a detailed description of these options. | ||||||
2. If you will be converting audio file formats, you must install SoX (Sound Exchange) before doing any conversions. For Linux, Genesys Administrator Extension supports SoX version 14.3.1 or higher.
[+] Show procedure Procedure: Installing SoX Purpose: To install SoX to enable conversion of audio resources to µ-law, a-law, and gsm formats. This procedure can be run at any time before or after Genesys Administrator Extension is installed. Steps
Important The user of the host on which the GAX application is running must be configured to read and execute the sox binary. | ||||||
3. Now you are ready to set up the ARM Runtime Web Server on Linux. [+] Show procedure Procedure: Setting up the ARM Runtime Web Server on Linux Purpose: To set up the target storage for Audio Resource Management by setting up a shared directory on an Apache web server on a Red Hat Enterprise Linux host. On this host, it creates a shared directory from which audio files are retrieved by Audio Resource Management, and to which Genesys Administrator Extension writes audio resource files as they are uploaded by users. The shared directory is accessible from the Genesys Administrator Extension host and is referred to as target storage. Important The ARM Runtime Web Server is sometimes referred to as an ARM HTTP Proxy.Prerequisites
Steps
Important Ensure that the user of the host on which the GAX application is running is configured to read and write these directories. GAX treats all directories as local. If the target directory and the sub-directories reside physically on a remote host and are used as network directories, or mapped as a local drive, the user must have network access configured.
|
Before using ARM on Windows, you must do the following:
1. Add the configuration option section [arm] and define the following configuration options on the Options tab of the Genesys Administrator Extension server Application object:
[+] Show options [arm]
See Configuration Options for a detailed description of the configuration options. |
2. If you will be converting audio file formats, you must install SoX (Sound Exchange) before doing any conversions. For Windows, GAX supports SoX version 14.3.1 or higher.
[+] Show procedure Procedure: Installing SoX Purpose: To install SoX to enable conversion of audio resources to µ-law, a-law, and gsm formats. This procedure can be run at any time before or after Genesys Administrator Extension is installed. Steps
|
3. Now you are ready to set up a Network File System for ARM. [+] Show the procedure Procedure: Setting up ARM Runtime Web Server on Windows Purpose: To set up a Network File System (NFS) to share data between Genesys Administrator Extension and the ARM Runtime Web Server. Important The ARM Runtime Web Server is sometimes referred to as an ARM HTTP Proxy.Prerequisites
Steps
|