Pre-Installation Checklist

This page lists requirements you must complete before installing Genesys App Automation Platform (GAAP). It is recommended you print this page (click the link in the Table of Contents to the left of this page to generate a PDF) and have the installer sign off on each requirement.

After you install GAAP, be sure to complete the post-installation configuration.

On-site installation requirements

Task	Completed and tested by
A dedicated desktop/laptop computer has been made available for the GAAP consultant to perform the installation. This computer must be able to access all servers required.

Remote installation requirements

Task	Completed and tested by
Remote access has been set up and tested, and details have been forwarded to the GAAP consultant.
The GAAP consultant has been provided with third-party software (for example, a VPN client) required to connect remotely.

Genesys and GVP requirements

Task	Completed and tested by
The GVP, ASR and TTS versions has been made available, as per the Hardware and Software Specifications page.
If TTS or ASR is required, it has been installed, configured, and fully tested.
Genesys GVP has been installed, configured, and has successfully handled test calls (including ASR and TTS, if required) to confirm it is fully functional.
A Genesys resource has been made available to configure GVP to route calls to GAAP after the installation in order for basic testing to be completed.
A Genesys resource has been made available to troubleshoot any GVP issues encountered.
Genesys routing and required attached data (if applicable) has been configured to support the requirements.
Externally accessible DID test numbers has been made available and configured to allow the GAAP consultant to dial into the environment.
If using multimodal functionality, Genesys ORS has been installed and configured.

Microsoft SQL Server requirements

Important

This section is only required if you want to use Microsoft SQL Server for the database layer.

Task	Completed and tested by
The Microsoft SQL Server 2008/2012 R2 database environment is ready and has been tested for the GAAP consultant to access and install GAAP.
Microsoft SQL Server has been configured and tested to allow TCP/IP connections and to allow non-Windows users (SQL Server authentication).
Microsoft SQL Server Management Studio has been installed on at least one GAAP server per environment (for example, one for the test environment and one for the production environment).
Two databases (fish_core and fish_reports, for example) have been created and the following steps applied to each database: The ALLOW_SNAPSHOT_ISOLATION setting set to ON. For example: alter database fish set ALLOW_SNAPSHOT_ISOLATION ON; alter database fishreports set ALLOW_SNAPSHOT_ISOLATION ON; A SQL server authentication user has been created and the allocated account also has ownership of both databases. You can confirm these settings by connecting to the database using SQL Server Management Studio. In the left panel, navigate to Security > Logins. Right-click the appropriate user and select Properties > User Mapping. Ensure db_owner is enabled for both databases.
To accommodate future migration of the reports schema, Genesys recommends that the transaction log file(s) are configured to be at least as big as the data file(s), and that both are set to auto-grow. The size of these files should be monitored periodically and regular backups scheduled in order to better manage the transaction log(s).

Oracle requirements

Important

This section is only required if you want to use Oracle for the database layer.

Task	Completed and tested by
The Oracle 11g/12c database environment is ready and has been tested for the GAAP consultant to access and install GAAP.
Oracle SQLDeveloper has been installed on at least one GAAP server per environment (for example, one for the test environment and one for the production environment).
Two databases (fishcore and fishreports, for example) have been created as follows: Oracle 11g CREATE BIGFILE TABLESPACE fishcore DATAFILE 'fishcore.dbf' SIZE 20M AUTOEXTEND ON; CREATE BIGFILE TABLESPACE fishreports DATAFILE 'fishreports.dbf' SIZE 20M AUTOEXTEND ON; CREATE USER C##fishcore IDENTIFIED BY yourpasswordhere DEFAULT TABLESPACE fishcore; CREATE USER C##fishreports IDENTIFIED BY yourpasswordhere DEFAULT TABLESPACE fishreports; GRANT "RESOURCE" TO C##fishcore; GRANT "RESOURCE" TO C##fishreports; GRANT "CONNECT" TO C##fishcore; GRANT "CONNECT" TO C##fishreports; GRANT CREATE ANY VIEW TO C##fishcore; GRANT CREATE ANY VIEW TO C##fishreports; GRANT INSERT ANY TABLE TO C##fishcore; GRANT INSERT ANY TABLE TO C##fishreports; GRANT UNLIMITED TABLESPACE TO C##fishcore; GRANT UNLIMITED TABLESPACE TO C##fishreports; GRANT SELECT_CATALOG_ROLE to C##fishcore; GRANT SELECT_CATALOG_ROLE to C##fishreports; GRANT SELECT ANY DICTIONARY to C##fishcore; GRANT SELECT ANY DICTIONARY to C##fishreports; Oracle 12c CREATE BIGFILE TABLESPACE fishcore DATAFILE 'fishcore.dbf' SIZE 20M AUTOEXTEND ON; CREATE BIGFILE TABLESPACE fishreports DATAFILE 'fishreports.dbf' SIZE 20M AUTOEXTEND ON; CREATE USER fishcore IDENTIFIED BY yourpasswordhere DEFAULT TABLESPACE fishcore; CREATE USER fishreports IDENTIFIED BY yourpasswordhere DEFAULT TABLESPACE fishreports; GRANT "RESOURCE" TO fishcore; GRANT "RESOURCE" TO fishreports; GRANT "CONNECT" TO fishcore; GRANT "CONNECT" TO fishreports; GRANT CREATE ANY VIEW TO fishcore; GRANT CREATE ANY VIEW TO fishreports; GRANT INSERT ANY TABLE TO fishcore; GRANT INSERT ANY TABLE TO fishreports; GRANT UNLIMITED TABLESPACE TO fishcore; GRANT UNLIMITED TABLESPACE TO fishreports; GRANT SELECT_CATALOG_ROLE TO fishcore; GRANT SELECT_CATALOG_ROLE TO fishreports; GRANT SELECT ANY DICTIONARY TO fishcore; GRANT SELECT ANY DICTIONARY TO fishreports;
A SYS user has executed the following command in Oracle: ALTER SYSTEM SET open_cursors = 600 scope=both;

Server requirements

Task	Completed and tested by
The servers have been built as per the Hardware and Software Specifications page.
All server details—such as hostnames and IP addresses for all relevant servers, including GVP, GAAP, and the database environment—have been provided to the GAAP consultant.
Login information has been provided to the GAAP consultant for all relevant computers and servers, including Active Directory (if used) and database servers.
Administrative privileges on the GAAP server(s) have been configured to allow the GAAP consultant to install, test, and troubleshoot.

Project-specific requirements

Task	Completed and tested by
Test data for the GAAP consultant to test the IVR application after installation has been provided, including (if applicable) valid card payment details for testing of the payment gateway and all other web services.
All third-party components required as part of the solution have been installed, configured, tested, and available to integrate before the installation of GAAP.

Firewall requirements

The following table lists the main firewall rules that are required for GAAP to function. Some customers might have additional requirements. Additionally:

• The port numbers referenced in the table below reflect common configuration as documented elsewhere in this guide. You must update these port numbers if your environment uses non-default port numbers.
• This table does not include standard firewall requests for scenarios such as remote desktop – it is assumed that the customer has already enabled these rules.

Rule	Ports	Completed and Tested by
Communication from the customer site to the GAAP FTP server for downloading installation files. Server details are: Host Name: ftp.speechstorm.com Port Number: 22 File Protocol: Secure FTP (SFTP) Username: Will be supplied by Genesys Password: Will be supplied by Genesys Important Access to the FTP site does not need to originate from the GAAP servers, but you must have a method of transferring files from the FTP site onto the GAAP servers.	22 for Secure FTP (SFTP)
Inter-Communication between all GAAP servers	80, 8080–8089 for HTTP traffic 443, 8443-8449 for HTTPS traffic
Communication between Genesys environment and all GAAP VUI servers	80, 8080–8089 for HTTP traffic 443, 8443-8449 for HTTPS traffic
Communication between ASR and TTS environment and GAAP servers	80, 8080–8089 for HTTP traffic 443, 8443-8449 for HTTPS traffic
Communication between database environment and GAAP servers	The SQL Server Port: Usually 1433, but to be confirmed by the customer.
Communication between all GAAP servers and customer integration/backend systems	Ports to be confirmed by the customer.
Communication between all GAAP servers and customer SMTP server (see post-installation configuration for more details).	Ports to be confirmed by the customer.
Communication between all GAAP servers and customer SNMP Manager (see post-installation configuration section for more details). Important This is optional and only required if you want to use the trap-sending functionality provided by GAAP.	Ports to be confirmed by the customer.
Communication between all GAAP servers and customer SYSLOG/Centralized Logging server (see post-installation configuration section for more details). Important This is optional and only required if you want to use the SYSLOG functionality provided by the Log4j component within GAAP.	Ports to be confirmed by the customer.