Jump to: navigation, search

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.
  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.
  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
    • Pma you-are-here-arrow.png Frontline Advisor
    • SDS and Resource Management
  6. Make any required configuration changes.

1. Copy the installation file to the Advisors home directory.
[+] Show additional information for Linux environments
2. Launch the installation file.
[+] Show Steps for Linux
[+] Show Step for Windows
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
[+] Show Steps for distributed mode installation
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
[+] Show Steps for Oracle
[+] Show Steps for Oracle RAC
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.

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.


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.
This page was last modified on August 24, 2018, at 07:05.

Feedback

Comment on this article:

blog comments powered by Disqus