System Settings of Foresight Analytics Platform are created:
In the settings.xml file.
In the system registry.
Names and purpose of subsections/registry parameters match the corresponding elements/attributes of the settings.xml file. For details about Foresight Analytics Platform settings see the System Registry Settings section.
When the web application or desktop application starts, the settings.xml file is searched. If the file is missing or does not contain required keys, settings are taken from the registry. If settings are missing in the registry, their default values are used.
NOTE. The settings.xml file has a higher priority than than the system registry.
When installing Foresight Analytics Platform, the settings.xml file and registry sections/parameters are not created. If any settings should be used, the corresponding parameters must be created manually.
All configured parameters are displayed in debug info. The registry key or section of the settings.xml file, from which parameters are loaded, can be tracked by means of the debug info applications, for example, DebugView - included in the Windows Sysinternals package of system applications.
Depending on the web application and BI server specificity of use, it can be necessary to set up timeouts for various nodes of the system being developed.
During the development of a project based on BI server of Foresight Analytics Platform, the user may require advanced features developed to extend the functionality of future systems:
Using state servers to create fault-tolerant systems.
Creating a fault-tolerant cluster based on several BI servers.
Using connection pool.
NOTE. On installing a BI server to Windows 7, Windows Server 2008 or Windows Server 2008 R2, the KB2533623 update installation may be required to provide correct work with OpenSSL libraries.
See also:
Installing BI Server on Windows OS | Installing BI Server on Linux OS