Jump to: navigation, search

Prerequisites for Genesys Administrator Extension Modules

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.

Important
Unless specified otherwise, all commands that are entered on a command line in this section should be issued as a root user (command prompt of #) or as a regular user (command prompt of $).


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.
  • 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.

Important
Operational Parameter Management does not load strategies on DNs or upload applications to application servers. You must do this manually for all parameterized objects.

Audio Resource Management

Important
  • 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
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
3. Now you are ready to set up the ARM Runtime Web Server on Linux. [+] Show procedure

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
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
3. Now you are ready to set up a Network File System for ARM. [+] Show the procedure

Feedback

Comment on this article:

blog comments powered by Disqus
This page was last modified on 4 December 2017, at 00:17.