Server-side configuration of the Loupe Server is done using the Loupe Server Administration tool. This is automatically started at the end of the installation and if it detects that the server has not been configured yet it will automatically launch the initial configuration wizard. This will walk you through all of the required steps to get your server operational.
The Server needs a shared file storage area. For Standard edition the local file system can be used. For other installations, a network share or Azure Storage can be used. It has to be specified during the initial installation. For more information see Loupe Server Administration - Server Repository.
The Server requires a SQL Database for indexing session events and tracking the information displayed in the web interface. For more information on selecting an appropriate database server see Loupe Server Administration - SQL Server Requirements.
You can optionally set up Elasticsearch to do full text indexing for Loupe in place of the built-in Lucene.net support. This is recommended when possible. For more information see Loupe Server Administration - Elasticsearch Requirements.
If you would like to be able to view sessions in real time you can enable Live Sessions on the Server. This is designed for high performance monitoring of server applications in Loupe Desktop. It is disabled by default. See Loupe Server Administration - Live Sessions for how to enable and configure it.
If you want to take advantage of email notifications from the server you need to specify a mail server to use to send the messages. See Loupe Server Administration - Mail Server for how to configure one.
The Server will keep session summary information in its index indefinitely but to control the amount of total disk space it requires you'll want to set up the rules for when it should drop local detailed log files.
For details see Loupe Server Administration - Storage Limits.
All extensions are disabled by default, even ones that ship with Loupe itself.
In most cases enabling the extension doesn't immediately cause it to start performing actions on the server, it merely enables it to be configured.
For complete information see Loupe Server Administration - Extensions.