Also known as GAX, Genesys Administrator Extension is a web-based User Interaction Layer component that provides user-friendly interfaces to help users perform complex operations while at the same time preventing user error. GAX provides an interface to the Configuration Layer, Management Layer, and other Genesys solutions.
Supported Operating Systems and Databases
For information about the operating systems and relational database management systems (RDBMSs) that Genesys Info Mart supports, see the Supported Operating Environment Reference Guide.
Genesys Info Mart can operate only with the Genesys components that are listed in Compatibility with Genesys Software. Other Genesys software components that you might have in an environment with Genesys Info Mart must be compatible with Interaction Concentrator 8.x.
For specific interoperability requirements, see the Genesys Interoperability Guide.
Software and Database Requirements
This section discusses the following considerations:
The Genesys Info Mart Server requires approximately 20 MB of hard disk space and a sufficient amount of disk space for local log files. It requires a minimum of 1 GB of additional RAM, depending on the configuration options that are set to define the data chunk size.
Genesys Info Mart Manager, the web-based management GUI that is implemented as a plug-in for Genesys Administrator Extension (GAX), requires negligible hard-disk space on the GAX host. Genesys Info Mart Manager requires no additional installations on client hosts and no additional RAM.
The following software must be installed on the Genesys Info Mart Server host to support Genesys Info Mart 8.x:
- Java Development Kit (JDK) or Server Java Runtime Environment (Server JRE) — Genesys Info Mart uses the Server Java Virtual Machine (JVM) that is part of the JDK or Server JRE packagings of Java. (The non-Server JRE packaging of Java does not include the Server JVM.)
You must install the JDK or Server JRE on the server on which you plan to install the Genesys Info Mart Server. Several Genesys Info Mart software components use Java. Note that Genesys Info Mart operates with 32-bit or 64-bit versions of Java. For the Java versions that Genesys Info Mart supports, see the Supported Operating Environment Reference Guide.
Periodically check that the daylight saving time (DST) definitions and other time zone information for your Java version are current and correct.
Genesys Info Mart uses Java TimeZone functionality to populate calendar data. Therefore, it is important to keep your Java TimeZone information up to date, particularly if DST rules change. Genesys recommends that you use the latest Oracle Java SE platform JDK or JRE release. If this is not feasible, use the Java Timezone Updater Tool to update your JRE time zone data, then rebuild your calendar data as described in Changing calendar settings during runtime in the Genesys Info Mart Operations Guide.
You must modify your PATH and JAVA_HOME environment variables so that Genesys Info Mart can locate the Server JVM. The PATH and JAVA_HOME environment variables that you modify depend on the operating system and user account under which the Genesys Info Mart Server runs.For specific information about installing the JDK or Server JRE and modifying the environment variables, see Preparing the Genesys Info Mart Server Host.
- Java Database Connectivity (JDBC) driver — Genesys Info Mart Server and the ETL jobs use JDBC to access all databases. For specific information about installing the appropriate JDBC driver for your environment, see Preparing the Genesys Info Mart Server Host.
Genesys Info Mart supports Transport Layer Security (TLS) connections and client-side port definition, to provide secured connections to the Configuration Layer and Management Layer — specifically, to Configuration Server and Message Server. Genesys supports these security features on all the operating systems that Genesys Info Mart supports.
Genesys Info Mart also supports mutual TLS and compliance with Federal Information Processing Standards (FIPS).
On Windows platforms, support for TLS is integrated into the operating system, and there are no additional requirements to enable Genesys Info Mart to support it. On UNIX-based platforms, you must install the Genesys Security Pack on the Genesys Info Mart host (see Security components).
Compatibility with Genesys Software
For general requirements on interoperability with the Genesys Configuration Layer, see the Genesys Interoperability Guide.
The following table provides release requirements for the Genesys software components with which Genesys Info Mart operates directly or for which Genesys Info Mart requirements are different from the minimum requirements for Interaction Concentrator 8.x. For requirements for various other Genesys software components that you may have in an environment with Genesys Info Mart, refer to the Interaction Concentrator 8.x documentation.
For each component, the table provides the minimum release number with which Genesys Info Mart release 8.5 is compatible in a non–SIP Cluster deployment.
| Management Layer:
||Genesys Info Mart supports:
|User Interaction Layer:
|| Genesys Info Mart requires this component only if you want to use the Genesys Info Mart Manager management GUI. |
Genesys Info Mart Manager and GAX interoperability requirements are reciprocal:
| Interaction Concentrator
|| The minimum Interaction Concentrator release is not sufficient to prevent significant data-quality or transformation issues. Genesys strongly recommends that you observe the following additional requirements:
There are additional minimum requirements for specific functionality. For recommendations for each Genesys Info Mart release, see the ICON version recommendations in the Genesys Info Mart 8.5 Release Note.
|T-Server release 7.6||
eServices/Multimedia Interaction Server release 7.5 or higher
| For Genesys intelligent Workload Distribution (iWD) and other deployments that have routing strategies that repeatedly move a multimedia interaction into and out of the same interaction queue or workbin, Genesys recommends that you use Interaction Server release 188.8.131.52 or higher and that you configure your deployment to suppress Interaction Server reporting events and notifications for this kind of routing strategy activity. However, be aware that suppressing Interaction Server reporting events for a strategy means that there will be no user data from that strategy to use for reporting, so some expected user data metrics might be missing. For more information about selectively suppressing reporting on strategy activity, see the Interaction Server 8.1.x Release Note and the Universal Routing 8.1 Business Process User’s Guide.
|Outbound Contact Server (OCS) release 7.6|| For information about how to configure Genesys Info Mart and other contact center objects to store reporting data for Outbound Contact campaign activity, see Enabling Reporting on Outbound Contact Activity.
In order for Genesys Info Mart to collect data from the Outbound Contact Server (OCS) Push Preview mode, you must be using OCS release 8.1.502.17 or later, and Interaction Server release 8.5.104.05 or later.
| Routing components:
|Genesys Voice Platform (GVP) release 7.6||For more information, see Genesys Voice Platform Support.|
|Orchestration Server (ORS) release 8.1.400.26||ORS is required to enable Callback. For more information, see the Callback Solution Guide.|
Genesys Security Pack 8.0
|This component is required for UNIX platforms only, for deployments in which you want to use the TLS protocol to secure the connections among Genesys Info Mart, Configuration Server, and Message Server. For more information, see Security Pack installation in the Genesys Security Deployment Guide.|