To ensure correct work of BI server, the Apache HTTP Server web server must be installed at the path that contains no spaces. The user, under whom Apache HTTP Server is started, must have read and write permissions for the installation folder.
IMPORTANT. Bitness of the installed BI server and the Apache HTTP Server web server must match: a x64 BI server version cannot be installed with x32 Apache HTTP Server version, and vice versa.
After installing Apache HTTP Server execute the following actions:
Complete the web server configuration file: S\conf\httpd.conf, where S is a path to the folder with installed Apache HTTP Server.
In the Listen directive, specify the path and the port where the BI server will be available. Make sure that the specified port is not busy with another application.
For example:
Listen localhost:80
According to these settings, the BI server is available at the following path: http://localhost:80/axis2/services/PP.SOM.Som.
NOTE. If the Listen directive has already been specified, it is not required to add it again.
If required, change BI server settings in the configuration file S\conf\extra\pp.conf, where S is a path to the folder with installed Apache HTTP Server. The configuration file contains the following directives:
LoadModule. The module to load. The path to the mod_axis2.dll module. The file is located in the install directory of Foresight Analytics Platform.
Axis2RepoPath. The path to the folder with installed Foresight Analytics Platform. The path must be specified in double quotation marks, direct slashes must be replaced with backward slashes. The path cannot end with a backward slash.
Axis2LogFile. The path to the file that will store the BI server log. The path must be specified in double quotation marks, direct slashes must be replaced with backward slashes. The specified file must exist at the specified path. The user, under whom Apache HTTP Server is started, must have read and write permissions for this folder.
Axis2LogLevel. Method of BI server log keeping. Available values:
critical. Only critical errors are recorded to the log.
error. Errors and critical errors are recorded to the log.
warning. Warnings and all types of errors are recorded to the log.
info. Information messages, warnings, and all types of errors are recorded to the log.
debug. Information and debug messages, warnings, and all types of errors are recorded to the log.
user. User messages and all types of errors are recorded to the log.
trace. Information, trace and debug messages, warnings, and all types of errors are recorded to the log.
Axis2ServiceURLPrefix. URL prefix for BI server. The "services" value must be specified.
Axis2MaxLogFileSize. Maximum size of the log file (in megabytes).
<Location>. A group of directives that control BI server end point. The following value must be specified:
<Location /axis2>
SetHandler axis2_module
</Location>
Example of the pp.conf file:
LoadModule axis2_module "C:/Foresight/Foresight Analytics Platform 9.2/mod_axis2_[version].dll"
Axis2RepoPath "C:/Foresight/Foresight Analytics Platform 9.2"
Axis2LogFile "C:/Foresight/Foresight Analytics Platform 9.2/logs/axis2.log"
Axis2LogLevel warning
Axis2ServiceURLPrefix services
Axis2MaxLogFileSize 100
<Location /axis2>
SetHandler axis2_module
</Location>
ThreadStackSize 524288
NOTE. It is required to specify the installed Apache HTTP Server version instead of the [version] value. Supported versions are 2.2 and 2.4, file name contains the values 2_2 or 2_4, respectively. By default, if the version is not specified, the mod_axis2.dll path will refer to mod_axis2_2_2.dll.
NOTE. If a firewall is used, the following operations are required to ensure correct performance of the Apache HTTP Server: open access to the port specified in the Listen directive, and allow data exchange in the network.
See also:
Installing BI Server on Windows OS | Checking BI Server Performance