Use the information on this page to install an Apache Web Server instance to direct http requests to the appropriate server. It is recommended to install Apache Web Server on a separate box.
You do not require a second Apache instance on the XML Generator server (local files are not produced). You can install a single Apache instance on a standalone server that points to the Advisors IP addresses and ports.
In a Frontline Advisor distributed mode configuration, the Apache HTTP configuration can be configured on any FA instance.
You can configure Apache to support HTTPs; to do so, you must:
Generate the SSL security certificate and private key.
Both procedures are described on the Configure Apache to Support HTTPS tab below.
1. To enable Apache Web Server serving different modules in the Advisors interface (for example, Administration, Contact Center Advisor, Workforce Advisor), edit the httpd.conf file as described below. The httpd.conf file is located in the conf folder of the Apache Web Server installation.
Locate the following lines in the httpd.conf file:
Locate the following entry and add a # to comment out Require all denied and to add Require all granted: <Directory /> AllowOverride none #Require all denied Require all granted</Directory>
Locate the following entry near line 133 and add a # to comment it out: #ServerAdmin
Add the following line: ProxyRequests Off
Add the lines shown below (see Platform and Advisors Modules below) to the bottom of the file and change the IP addresses or host names, as necessary. The format of this page might cause lines to wrap, but it is very important that each entry is on a single line in your httpd.conf file. You can comment out or exclude lines to proxy passes that are not installed.
The trailing slash must appear at the end of each line, as indicated below. If it is omitted, users might see a 404 or Not Found error, get no response when clicking, or see empty white screens in the Advisors interface. Errors can typically be seen in the Geronimo log if DEBUG is enabled. For example, ProxyPass /admin/ ajp://192.168.40.234:8009/admin will generate an error. Should this happen, the solution is to fix the httpd.conf and restart Apache.
If you need to access external applications through the Advisors interface, you should have lines for each of those applications.
For example, ProxyPass /APEX/ http://www.cra-arc.gc.ca/formspubs/menu-eng.html.
# Genesys Resource Management Console Web Application ProxyPass /rmc/ ajp://192.168.40.234:8009/rmc/
# FA ProxyPass /fa/ ajp://192.168.40.234:8009/fa/
# Contact Center Advisor Mobile Edition
ProxyPass /ma/ ajp://192.168.40.234:8009/ma/
Remove, or comment out, the ProxyPass /admin/ ajp://192.168.40.234:8009/admin/ statement on FA presentation-only instances. If you use a load balancer, do not direct requests to the /admin/ context to FA presentation-only instances.
If there is no Administration workbench module installed on the FA Platform server, add the following re-directs before ProxyPass /fa/ ajp://192.168.40.234:8009/fa/. This allows you to access the FA Administration module from the CCAdv/WA Platform server:
ProxyPass /fa/Admin ajp://192.168.40.234:8009/fa/Admin
Note that there is no slash at the end of the preceding statement; while this is different from most other ProxyPass statements, it is correct syntax for the fa/Admin statement.