Deploying FA

You run a .jar installation file to deploy Genesys Frontline Advisor.

You can deploy FA on a Red Hat Linux or a Windows platform, and with Oracle or MS SQL databases.

Roadmap

1. [+] Install the databases that correspond to the Advisors products you will deploy.
   1. Advisors Genesys Adapter metrics database
   2. Advisors Platform database
   3. Advisors Cisco Adapter database (if you use ACA)
   4. Metric Graphing database
2. Create the Advisors User and the Object Configuration User in Configuration Server.
3. [+] Install the Platform service (Geronimo) on all servers on which you will deploy one of the Advisors components.
   • Contact Center Advisor
   • Workforce Advisor
   • Frontline Advisor
   • Contact Center Advisor–Mobile Edition
   • Resource Management Console
4. Install each adapter you will use (AGA and ACA).
5. Install the Advisors components for your enterprise in the following order:
   • Contact Center Advisor
   • Workforce Advisor
   • Contact Center Advisor – Mobile Edition
   • Frontline Advisor
   • SDS and Resource Management
6. Make any required configuration changes.

<tabber>

Procedure=

1. Copy the installation file to the Advisors home directory. [+] Show additional information for Linux environments Ensure the Advisors Platform service has been installed. The Advisors Platform service hosts the FA application. Open the shell. Start the installer locally or from a remote desktop. To run the installer remotely, use SSH with X11 forwarding enabled: ssh -X root@<host> As root, copy the fa-server-installer-<version>.jar file to the /home/advisors directory. cp ./fa-server-installer-<version>.jar /home/advisors

2. Launch the installation file. [+] Show Steps for Linux As root, navigate to the Advisors home directory: cd /home/advisors As root, run the FA installer. The page format of this document might cause a line break in the following command, but you must enter it on one line in the command prompt window: ./jdk1.7.0_<version>/bin/java -jar fa-server-installer-<version>.jar [+] Show Step for Windows Do one of the following: Open a command line window, and enter the following command: java -jar fa-server-installer-<version>.jar Double-click the fa-server-installer-<version>.jar file in the release bundle. Double-clicking might not work due to system settings, but using the command line terminal should always work. For 64-bit systems, if double-clicking to launch the installer, please ensure that the Java instance associated with the jar file type is 64-bit. Running the installer with a 32-bit Java instance will create a Windows service with the wrong executable.

3. On the Destination Directory screen, accept the default directory, or specify a different directory. The installation directory for Frontline Advisor server must be the same as the directory where Advisors Platform has been installed.

4. Configure FA to run as a single instance, or in distributed mode. [+] Show Steps for single instance installation If you are installing a single instance of Frontline Advisor, select the Run as a single instance option. This is the default setting. On the Hierarchy Source Details screen, enter either: The name of the tenant in the Genesys Configuration Server in which the monitoring hierarchy resides, and the path to the hierarchy root folder. In a Cisco environment, the path should look like: Agent Groups\\<Your Cisco Group Name> The name of a Person folder in Configuration Manager, and the path to that Person folder. Selecting this option restricts the hierarchy view that is loaded at startup (or reloaded using the reload feature) to the team of agents belonging to that person (supervisor). To add more than one tenant or person, check the Add Another? check box, and complete the required details. [+] Show Steps for distributed mode installation If you are installing multiple FA instances for use in distributed mode, and this instance is one of those, select the Run as a cluster member option. On the Distributed Mode - Rollup Engine screen, select one of the two options: Enable Rollup Engine—Enable the rollup engine if you intend the FA instance you are installing to be responsible for data aggregation. When installing Advisors Platform to support the FA instance on which the rollup engine will be enabled, you must install the Administration workbench. Warning Enable the rollup engine for only one of the FA instances in a cluster. Disable rollup engine—Disable the rollup engine if you intend the FA instance you are installing to be responsible for presentation only. When installing Advisors Platform to support the FA instance on which the rollup engine will be disabled, do not install the Administration workbench.

5. On the Database Type screen, select either the SQL Server or the Oracle option – whichever you use for Advisors platform database(s). The screens that follow are dependent on your selection: [+] Show Step for SQL Server On the Genesys Advisor Platform Database screen, specify the parameters for the Advisors platform database: Database server—The host name or IP address of the database server. When using numerical IP v6 addresses, enclose the literal in brackets. Database port number—The database server’s port number. Database name—The unique name of the database instance. Database user—The Advisors user with full access to the Advisors platform database. Database user password—The password created and used for the Advisors platform database. [+] Show Steps for Oracle On the Oracle setup type screen, select the Basic option. On the Genesys Advisor Platform Database screen, specify the parameters for the Advisors platform database: Database server—The host name or IP address of the database server. When using numerical IP v6 addresses, enclose the literal in brackets. Database port number—The database server’s port number. SID—The unique name of the database instance. Database user—The Advisors user with full access to the Advisors platform database. Database user password—The password created and used for the Advisors platform database. [+] Show Steps for Oracle RAC On the Oracle setup type screen, select the RAC connectivity setup option. On the Genesys Advisor Platform Database screen, specify the parameters for the Advisors platform database: Database schema and Database schema password—The database schema and password created and used for the Platform database. Locate file—Enter the location of the file that contains the advanced database connection string. If you do not know how to correctly build the advanced database connection string, contact your database administrator. The installation wizard applies the specified advanced connection string when configuring the data sources.

6. On the Failure Notification Configuration screen, specify the e-mail settings for system-level notifications: Application from address—The default sender of the notification message; for example, faadmin@genesys.com Application to address—The default recipient of the notification message; for example, faadmin@genesys.com Subject—The default subject line for notification messages; for example, Frontline Advisor Message

7. After you deploy FA, you must modify the Apache configuration file (httpd.conf). See Deploy and Configure Apache.

|-| Start the FA Service=

To start the Frontline Advisor service from the command prompt, you must set the MaxPermSize parameter to 256 in the setenv.bat file. The FA log generates errors or exceptions if you start the service with the default setting of 128.

1. Follow the Advisors Platform instructions to install the Windows service.

2. Each time the service is started, the Monitoring Hierarchy Loader runs.

3. Start the service and refresh a few times to make sure the service stays running.

4. Check the Platform log file if you experience problems. It may take up to 45 minutes to fully start depending on the number of agents and the complexity of the hierarchy.

|-| Troubleshooting=

The following Table shows parameter validation errors that you may encounter at the end of installation.

Installation Error Message	Cause
[java] Failed to connect to the database using connection URL: [java] jdbc:sqlserver://192.168.xx.yy:nnn;DatabaseName=ys_fadb;user=sa; password=very_secure_pwd;selectMethod=cursor [java] The following exception was thrown: com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host 192.168.xx.yy, port nnn has failed. Error: "Connection refused. Verify the connection properties, check that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port, and that no firewall is blocking TCP connections to the port.	Wrong database server name / IP address or port number
[java] Failed to connect to the database using connection URL: [java] jdbc:sqlserver://192.168.xx.yy:nnnn;DatabaseName=NotAPlatformDB; selectMethod=cursor;user=sa;password=very_secure_pwd [java] The following exception was thrown: com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host 192.168.xx.yy, port nnnn has failed. Error: "connect timed out. Verify the connection properties, check that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port, and that no firewall is blocking TCP connections to the port."	Wrong database name
[java] Exception while connecting: Login failed for user 'badUserId'. [java] url used: jdbc:sqlserver://192.168.xx.yy:nnnn;DatabaseName=ys_fadb;selectMethod=cursor; user=badUserId;password=very_secure_password	Wrong database user name or password
[loadfile] Unable to load file: java.io.FileNotFoundException: C:\ (The system cannot find the path specified)	Produced in error and can be ignored.