Maintenance Notice - PDF Generation
Dynamic PDF generation for web-based content is temporarily unavailable. This maintenance affects dynamic PDF files that are generated from either the HTML-based page or manual that you are viewing. Links that normally allow this functionality have been hidden, and will reappear as soon as the feature is restored.


Note: Access to static files, including PDF files that are not dynamically generated from our web-based content, is unaffected.

Jump to: navigation, search

Deploying FAAA

You run a .jar installation file to deploy Genesys Frontline Advisor/Agent Advisor. The fa-server-installer-<version>.jar file installs both Frontline Advisor and Agent Advisor dashboards; you use Role-Based Access Control (RBAC) privileges to control which dashboard each user can see and use.

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

Deployment 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 servers where it is required for Advisors components.
  4. Install each adapter you will use (AGA and ACA).
  5. Register the Stat Servers that you plan to use with Advisors.
  6. 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
  7. Make any required configuration changes.

<tabber>

Procedure=

Procedure: Deploying Frontline Advisor and Agent Advisor


Steps

  1. Review the General Prerequisites and prerequisites specific to Frontline Advisor deployment before beginning deployment.
  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. Use the information provided on the Installation Screens tab on this page to assist you to complete the remaining deployment screens.
  5. After you deploy FA, you must modify the Apache configuration file (httpd.conf). See Deploy and Configure Apache.

|-| Installer Screens=

[+] Distributed Mode Configuration
[+] Distributed Mode - Rollup Engine
[+] Failure Notification Configuration
[+] Genesys Advisor Platform Database
[+] Genesys Advisor Platform Database - Advanced
[+] Hierarchy Source Details
[+] RDBMS Type And JDBC Connectivity
[+] SCS Integration


|-| 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.
This page was last edited on August 24, 2018, at 13:54.

Feedback

Comment on this article:

blog comments powered by Disqus