NET Genium settings

Home / Support / Manuals / Administrator Guide /

NET Genium settings

1. NET Genium settings

Obrázek.png

  • NET Genium settings are available to all users with administrator privileges.

2. List of tabs in the settings dialog NET Genium

  • General – Setting general properties of NET Genium
  • E-mails – Email settings
  • Printing templates – Setting up print templates
  • Authorization – Permission settings
  • Passwords – Password settings
  • Colors – Color settings
  • Other – Setting other properties

2.1. “General” tab

Obrázek.png

2.1.1. Name

  • The name NET Genium displayed in the web browser tab.
  • The NET Genium name is stored in the server variable “#portal#”.

2.1.2. Version

  • The NET Genium version displayed in the header of the web browser and in the subject of all outgoing e-mail messages.

2.1.3. URL

  • NET Genium intranet address – the Enter-separated list of these addresses will be u sed when initializing NET Genium in multiple instances.
  • Internet address of NET Genium – the Enter-separated list of these addresses will be used in e-mail messages sent by the script and will ensure that the user can be redirected to NET Genium for specific records.

2.1.4. Time zone

  • The NET Genium time zone is automatically set to the time zone of the server on which NET Genium is hosted.
  • By selecting a specific time zone from the drop-down list, this setting can be changed to the desired value.

2.1.5. Date format

  • The date format affects the display of date data across the entire application.
  • The drop-down list contains the following options:
    • dd/mm/yyyy – day month Year
    • mm/dd/yyyy – month, day, year

2.1.6. Default map

  • The default map defines the default geographical center of all map data that does not contain any points on the map in the currently displayed data visualization. In other cases, the geographic center is calculated automatically from all points displayed on the map.
  • The default map controls the search for addresses stored in “TextBox” controls called “Find on map”, “Find on map” or “Find on map”.
  • The drop-down list contains the following options:
    • Czech Republic – address search offers map portals “maps.google.cz” and “www.mapy.cz”.
    • Slovakia – address search is offered by the map portal “maps.google.sk”.

2.1.7. Full-text catalog

  • Catalog for the full-text file attachment search function.
  • The drop-down list contains the following options:
    • None – File attachments are never searched while searching for values in lookup tables.
    • Windows Search – while searching for values in the look-up tables, file attachments are searched using the “Windows Search” full-text catalog. A detailed description of the configuration of the “Windows Search” full-text catalog is given in the separate Installing NET Genium on the web server manual.
    • Indexing Service – while searching for values in view tables, file attachments are searched using the “Indexing Service” in the catalog, the name of which is entered in the text field below the drop-down list of the full-text catalog. The “Indexing Service” was last available in the “Windows Server 2008” operating system, so we recommend replacing its use with the full-text catalog “Windows Search”. A detailed description of the configuration of the “Windows Search” full-text catalog is given in the separate Installing NET Genium on the web server manual.

2.2. “Emails” tab

Obrázek.png

2.2.1. Default sender of all messages

  • An email address that will be set as the default sender of all messages. Emails that have senders from another domain will be sent using the default sender of all messages.

2.2.2. System warnings

2.2.2.1. Service e-mail address

  • Administrator's email address for sending system messages. If the address is empty, no system messages will be sent.
    • E-mail messages with an empty sender (NG NO-RCPT will be inserted in the subject of the message:)
    • Reports of exceeding the maximum number of logged in users
    • Error messages in applications or when synchronizing records

2.2.3. Outgoing mail server

2.2.3.1. SMTP Server 1

  • The name or Internet address of the SMTP mail server used to send e-mail messages.
  • SMTP Server 1 is used to send e-mail messages through the following commands:
    • View page – New e-mail message
    • Button – Open the form for entering a new e-mail message
    • Script – Send email
    • Script – SENDMAILMESSAGE()
    • Script – SENDMAILINVITATION()
    • Script – SCHEDULEMAILMESSAGE()

2.2.3.2. SMTP Server 2

  • The name or Internet address of the SMTP mail server used to send e-mail messages.
  • SMTP Server 2 is used to send e-mail messages through the following commands:
    • Backup SMTP Server – all e-mail messages that fail to be sent the first time using SMTP Server 1 are forwarded for sending using SMTP Server 2. If SMTP Server 2 is not defined, or fails when sending a message using SMTP Server 2, the e-mail message is saved in the “SMTP” directory as an “eml” file, and “ResendEmlFiles.exe” tries to resend it, Which is typically run every 30 minutes using a scheduled task.
    • Script – SENDMAILMESSAGE2()
  • If neither SMTP Server 1 nor SMTP Server 2 is defined, all e-mail messages are stored in the “SMTP” directory in the form of “eml” files. The “ResendEmlFiles.exe” program, which typically runs every 30 minutes with a scheduled task, attempts to resubmit them. Messages successfully sent by “ResendEmlFiles.exe” are deleted from the “SMTP” directory, unsuccessful messages sent by “ResendEmlFiles.exe” will be sent a total of 48 times (which corresponds to attempts to send a message during a full day at 30 minute intervals), and then ignores these files in the “SMTP” directory. The list of unsuccessfully sent or already ignored messages is stored in the configuration file “SMTP/ResendEmlFiles.errors”.

2.3. “Print templates” tab

Obrázek.png

  • List of print templates stored in the “Templates” directory with the option to add or remove templates from this directory.
  • Print templates from this list are offered in “File” and “Button” controls.
  • Unused print templates are shown in italics.
  • A detailed description of print templates is given in the separate Print templates manual.

2.3.1. Statistics

  • Statistics display aggregated information about the use of printing templates across the entire application.
  • The “Statistics” link displays a detailed report of all controls that use this template, including the ability to open the settings for this control.

2.3.2. Add a template

  • Button for inserting a new print template in the “Templates” directory.

2.4. “Permissions” tab

Obrázek.png

2.4.1. User account administrator

  • List of user groups or users who:
    • they can set a new password for other users (except for users who have administrator privileges).
    • they can set up new user groups for other users (except for users who have administrator privileges).
    • they can set up new user groups for each permission group.
    • they can send a chat message to all users of the application (as well as users with administrator privileges).
    • sees all sessions in the list of online users (as well as users with administrator privileges). Other users see only one record for each user online, in terms of time the one with the latest user login date.

2.4.2. IP addresses allowed

  • List of allowed IP addresses from which it is possible to log in to the application if the user is a member of the selected user group.
  • The list of allowed IP addresses is used to set restrictions for users who are in the “Administrators” group and therefore have administrator privileges, including the administrator mode option. Administrator mode is then enabled only if the user accesses the application from specific IP addresses. If the user accesses from another IP address, the administrator mode option is removed, but the option to log in to the application remains enabled.
  • The list of allowed IP addresses is used to set restrictions for users who are not in the “Administrators” group. If the user accesses from another IP address, the option to log in to the application is removed.
  • The allowed IP address can take the following values:
    • 1.2.3.4 – access is allowed only for this specific IP address
    • 1.2.3 – access is allowed for all IP addresses where the first three parts agree, the value of the fourth part can be arbitrary
    • 1.2 – access is allowed for all IP addresses where the first two parts agree, the value of the third and fourth part can be arbitrary
    • 1 – access is allowed for all IP addresses where the first part agrees, the following three parts can be arbitrary

2.4.3. Public external functions

  • List of public external functions that are accessible even for unregistered users.
  • The definition of a public external function must contain only the identifier of the external function, ie the value of the “string id” parameter. A detailed description of external functions is given in the separate manual “External functions”, and also for the function “string ngef” in the separate manual “Server functions”.

2.4.4. Add IP address

  • Button for entering a new record of the allowed IP address.

2.4.5. Add external function

  • Button for inserting a new record of a public external function.

2.5. “Passwords” tab

Obrázek.png

2.5.1. Password strength required

  • The password strength setting determines how complex passwords must be when changing old passwords to new ones.
    • None – The password may be blank.
    • Weak – The password must be at least 5 characters long. The password expires every 12 months, and the new password may be the same as the previous one.
    • Fair – The password must be at least 8 characters long, and must contain at least 3 characters from the set {lowercase, uppercase, numbers, special characters}. The password expires every 12 months, and the new password cannot be the same as the previous one.
    • Strong – The password must be at least 12 characters long (administrator password at least 17 characters), and must contain all characters from the set {lowercase, uppercase, numbers, special characters}. The password expires every 12 months, and the new password cannot be the same as any of the previous passwords.
  • Special characters: – _ , . : ; ! @ # $ % ^ & * = + () {} [] < > / ? ' ` | §

2.5.2. Printing templates

  • Password required when editing print templates by a user who does not have administrator privileges. If the password is blank, print templates cannot be edited.
  • The website for editing print templ ates is located at “url-netgenium/templates”.

2.5.3. Restart

  • Password re quired when restarting NET Genium by a user who does not have administrator privileges. If the password is blank, NET Genium will not be restartable.
  • The NET Genium restart web site is located at “url-netgenium/restart”.

2.5.4. Synchronization

  • If the password is blank, it will not be possible to synchronize data from the re mote server with your NET Genium.

2.6. “Colors” tab

Obrázek.png

  • List of colors offered by the color designer when editing a value in “TextBox” controls with the “Show color designer in edit form” option checked.
  • If the color list is empty, the color designer offers a default color palette.

2.6.1. Add color

  • Button for inserting a new color record.

2.7. “Other” tab

Obrázek.png

2.7.1. E-Learning

  • The e-learning style setting determines what appearance will be used to visualize e-learning courses.
    • Style A – displays e-learning courses in pleasant blue and orange colors and contains pictorial navigation buttons.
    • Style B – is rather conservative and respects the color settings of NET Genium.

2.7.2. Logging

  • Logging is used to measure the processing time of database queries, scripts, view pages, edit form s and external functions.
    • Off – Server-side processing times are not measured.
    • To database – Processing times for database queries, scripts, view pages, edit form s and external functions are stored in the database. From this data it is possible to display aggregated statistics using the “Logging” button directly in the settings of the given control element, resp. its database query, as well as in the settings of the script, view page or edit form. Another option is to display these statistics on the reports page, where statistics of measurements of external functions are also available. A detailed description of the reports is given in a separate manual Reports.
    • To disk – Processing times for database queries, scripts, view pages, edit forms and external functions are stored on disk in the “Logs” directory.
    • To database and disk – Server-side processing times are stored in the database and on disk at the same time.
    • Logging to console – Processing times for preview pages and client-side edit forms are displayed in the console at the bottom of the web browser.
      • Data Transferring Time – communication time between client and server
      • Page Processing Time – server-side page processing time
      • Page Rendering Time – time of page rendering in the web browser
      • Total Waiting Time – total waiting time for the page to be viewed
    • Measure memory consumption – Monitoring the memory consumption of each database query that retrieves data.
      • Memory consumption is calculated as the difference of the allocated memory of the “w3wp.exe” process before and after the data is successfully retrieved from the database.
      • The “w3wp.exe” process serves the requests of all users of the web application, so the calculated value may be inaccurate and may also include the memory consumption of other requests.
      • The calculated value can also be negative if memory was freed by the Garbage Collector during data loading.
      • The measured value of memory consumption is available in reports when database logging is enabled, and on disk in the log file “Logs\yyyy-DD-mm.log” for those database queries whose memory consumption exceeds 1GB (the word “LastMemoryConsumption”).
    • Delete old logs in the database – Deleting all measured data in the database.
    • Delete old logs on the disk – Delete all measured data on the disk in the “Logs” directory.

2.7.3. Options

  • Enable automatic error reporting to NetGenium
    • Checking this box determines whether each error should be automatically sent to NetGenium Technical Support.
    • For each error in NET Genium, an error message will be displayed on a separate page, where you can manually send the error to NetGenium Technical Support.
  • Log usage of view pages
    • Checking this box determines whether the use of individual preview pages in the database should be logged in the “Settings” application:
      • Logging into the “Settings/Statistics” table – Visited view page, User, Date
      • Logging into the table “Settings/Statistics 2” – Visited view page, Number of visits
      • Logging into the table “Settings/Statistics 3” – Visited view page, User, Number of visits
    • View page logging is used to detect underused or unused view page s by users.
    • The opening of the same page by the same user is logged in the database only once an hour.
  • Enable sending lost passwords on the login page
    • Checking this box determines whether the “Forgot Password” button should be displayed on the login page next to the “Login” button, which is used to send a forgotten password to the user's email address.
    • A forgotten password can only be sent once a day for each user.

3. Application “Settings”

3.1. Core application

  • NET Genium contains a default set of edit forms and their corresponding view pages, which are essential for the correct functioning of the entire application. These edit forms are located in the “Settings” application.
  • The “Settings” application cannot be deleted or moved to another application group.
  • Modifications to edit forms and view pages in this application can be performed only by a single user with the highest permission level — the “Administrator” user with database ID 1.
  • The “Settings” application contains the following edit forms and their corresponding view pages:
    • User – database table “susers” with the list of users
      • Full name – the user’s full name
      • Surname – the user’s surname
      • First name – the user’s first name
      • Title – the user’s title
      • Login name – the user's login name
      • Password – the user’s password
      • Language – the user’s language setting (cs, de, en, fr, sk)
      • Windows account – the domain account name of the user in Active Directory, used to enable automatic login to NET Genium without entering a username and password
      • E-mail – the user’s email address
      • M-Password – password for the user’s Android mobile - device account
      • Rights group – foreign key to the permissions - group directory, defining the list of user groups of which the user is a member. Assigning a user to a rights group is the preferred method of granting permissions, though manual assignment of user groups is possible via the next control “User groups”.
    • User groups – list of user groups in which the user is a member. Manual assignment of user groups for each user individually is not the preferred method of permission assignment; the recommended method is selecting a rights group as described above.
    • User group – database table “susergroups” with the list of permission groups
      • User group – name of the user group
      • Description – description of the user group
    • Rights group – database table “srightsgroups” with the list of permissions groups
      • Rights group – name of the rights group
      • Description – description
      • User groups – list of user groups defining the rights group
    • Public holiday – database table “sholiday” listing current public holidays. Content is generated automatically according to the language settings of NET Genium.
      • Holiday name – name of the public holiday
      • Date – date of the public holiday
      • Half - day – checkbox for marking half - day public holidays (used mainly in Germany)
    • Layout – database table “slayout” with the list of graphic themes of NET Genium
      • Name – name of the layout
      • Save as active layout – checkbox for marking the layout as active and regenerating CSS
      • Font name
      • Text size
      • Font color
      • Header – Logo
      • Header – Background image
    • Invalid login – database table “sinvalidlogins” with invalid login attempts
      • Date – date of the invalid login
      • IP address – IP address from which the login attempt was made
      • Login name – login name that was used
    • Statistics – database table “sstatistics” with view - page usage statistics
      • View page – visited view page
      • User – login name of the user who visited
      • Date – date of visit
    • Statistics 2 – database table “sstatistics2”
      • View page – visited view page
      • Session – number of visits
    • Statistics 3 – database table “sstatistics3”
      • View page – the visited view page
      • User – the login name of the user who visited the page
      • Session – the number of visits
    • Synchronization – database table “ssynchro” with synchronization errors
      • Error date
      • Edit form – name of the form where the error occurred
      • Record ID – ID of the record involved
      • Error – error description

3.2. Optional applications

  • The “Install” directory contains a set of optional applications that can be imported into NET Genium.
  • Available optional applications:
    • API – management of API keys for external system access and SQL - query records available for download via API.
    • Applications – overview and management of applications installed in NET Genium.
    • Business Logins – storage of login credentials for external business systems.
    • DataGrid Settings – saving/loading individual datagrid settings.
    • E-learning – e-learning courses and materials.
    • E-mail – management of email templates and sent emails.
    • FileUpload – management of files uploaded to the server (used by FileUpload.exe).
    • Licenses – monitoring license usage over time.
    • Maps – map backgrounds and geographic data visualization.
    • Practical information – help and useful information for users.
    • Reset password – mass password reset and email delivery.
    • RUIAN – address lookup in the Czech territorial registry.
    • Services – monitoring services running via Windows Scheduler or console apps.
    • SMS – sending and receiving SMS.
    • Stats – application usage statistics and reports.
    • UNION – examples of SQL UNION queries.
    • Web – management of content published via NET Genium.

4. Configuration files

  • Configuration files contain data required for the correct operation of the web application but are not part of the database. They are located in “NETGenium\Config” as text files.
  • ActiveLayout.txt – database ID of the layout that will be used as the default, regardless of the active - layout setting in the database records of configured NET Genium layouts in the “Settings” application.
  • BlindFriendly.txt – when this file exists, view tables use a static toolbar displayed permanently under the view - table title instead of a dynamically displayed one.
  • ConnectionString.txt – the connection string to the NET Genium database.
  • Copyright.txt – placeholder HTML code for the copyright displayed in the navigation area. If the file does not exist, the text “© 20xx NetGenium” is shown.
  • CustomIcons.txt – a list of custom icons replacing default icons used in the application. Each line defines one icon in the format: “Images/Picker.gif:Images/Custom/Picker.svg”
  • DefaultLanguage.txt – two - letter code of the default language in which the “Settings” application is localized and which is assigned to users “Administrator” and “Anonymous” upon creation (“cs”, “de”, “en”, “fr”, “sk”).
  • Demo.txt – when this file exists, saving or deleting anything in the web application is disabled. The file may optionally contain a list of database tables (one per line) in which changes remain allowed. For example, “susers_vf” enables user customization of view tables.
  • DenyCookieless.txt – when this file exists, the web application requires cookies on the client side. Consequently:
    • SessionID will not be inserted into page URLs („…/netgenium/(S(33cipeb0js15bo1t1xhkupr4))/default.aspx”)
    • it will not be possible to log in within a single web browser under different user accounts in different tabs — the web browser merges individual sessions.
  • DenyExport.txt – when this file exists, exporting applications is disabled.
  • DenyLogin.txt – when this file exists, login to the application is restricted to the server desktop or the IP address “127.0.0.1”. The file may optionally contain a URL for redirecting unauthorized login attempts.
  • DenySynchro.txt – when this file exists, data synchronization is disabled.
  • Developer.txt – when this file exists, application errors are displayed in their raw form instead of user - friendly messages.
  • EncryptionKey.txt – encryption key used for encrypting “TextArea” and “RichTextBox” columns. If the file does not exist, a default encryption key is used.
  • ExecutionTimeout.txt – maximum request - processing time (in hours) used to extend the default limit of 5 hours, typically for long - running scripts. This influences the “executionTimeout” attribute in “Web.config”, which is updated automatically by “FinishUpdate.exe”.
  • Framework.txt – automatically generated file containing the detected .NET Framework version configured in the IIS application pool.
  • Framework4.txt – when this file exists, the update program “Update.exe” downloads NET Genium builds intended for .NET Framework version 4.
  • GoogleTranslationKey.txt – API key for Google Translation API used in rich text boxes for translation features.
  • GoogleTranslationLanguages.txt – semicolon - separated list of two - letter language codes available for translation in rich text boxes.
  • Holidays.txt – condition used to filter public - holiday records loaded into date pickers and into functions such as “ADDWORKDAYS”, “MEASUREWORKDAYS”, “MEASUREWORKHOURS”, or “jsMeasureWorkDays”. Example: “ng_country = 'USERDETAILS(ng_countryforholidays)'”
  • License.txt – NET Genium license key.
  • LoginByIdentity.txt – the presence of this file ensures that the NET Genium login window includes a checkbox enabling automatic user login through Windows Integrated Authentication, without the need to manually enter a username and password. For this purpose, the user must exist in Active Directory, and the user’s domain account name must be filled in within NET Genium in the users table (“susers”) in the “Windows account” column (“account”). The automatic login process performs only authentication, while authorization is handled by NET Genium — each user has an assigned list of user groups to which the user belongs. Along with creating the “LoginByIdentity.txt” file, it is necessary to configure the “LoginByIdentity.aspx” page in IIS so that it supports Windows Integrated Authentication; more details are provided in the separate guide Installing NET Genium on the web server.
  • LoginByMicrosoft.txt – he presence of this file ensures that the NET Genium login window includes a checkbox enabling automatic user login through Microsoft Integrated Authentication, without the need to manually enter a username and password. For this purpose, the user must exist in Azure Active Directory (Microsoft Entra ID), and the user’s email address must be filled in within NET Genium in the users table (“susers”) in the “E-mail” column (“email”). The automatic login process performs only user authentication, while authorization is handled by NET Genium — each user has an assigned list of user groups to which they belong. Along with creating the “LoginByMicrosoft.txt” file, NET Genium must be configured in the portal at “https://portal.azure.com”; more details are provided in the separate guide “Configuring user login via MS Entra.”
  • MaxRequestCount.txt – maximum number of requests per second from a single user and IP address. Increasing the default limit of 100 is relevant for anonymous web forms where all visitors share a single anonymous session.
  • MaxRequestLength.txt – maximum request size (in MB) used to increase the default limit of 50 MB, typically required for uploading large files using “File” and “Image” controls. This affects “maxRequestLength” and “maxAllowedContentLength” in “Web.config”, set by “FinishUpdate.exe”.
  • MetaTags.txt – list of HTML tags inserted into every edit form inside the <head> section.
  • NoFrames.txt – when this file exists, NET Genium runs in frameless mode — the header and navigation area become part of each page’s HTML.
  • NoScript.txt – text message inserted inside <noscript> in every edit form, displayed to users with JavaScript disabled. Example:
    “Dear users,
    Your browser unfortunately does not support JavaScript, which is required to display these pages correctly.
    Please enable it.
    Thank you.”
  • OCRServer.txt – URL of a remote NET Genium instance providing OCR services used with the “#ocrserver#” variable and functions “OCR2TEXT” or “OCR2FILE”.
  • ResponseHeaders.txt – list of HTTP headers (one per line, format “key: value”) added automatically to every response.
  • SecureCookies.txt – when this file exists, every cookie is assigned the “Secure” attribute. Use this only when SSL termination happens on a firewall (e.g., F5). When SSL is terminated in IIS, this file is not needed.
  • SessionTimeout.txt – session timeout in minutes after which inactive users are automatically logged out.
  • SingleLogin.txt – when this file exists, a user may have only one active session; older sessions are automatically logged out.
  • SimpleClick.txt – when this file exists, records in view tables open with a single click instead of the default double click.
  • SSL.txt – when this file exists, all HTTP requests are automatically redirected to HTTPS. The file may optionally contain a custom redirect URL.
  • SysLog.txt – IP addresses of SysLog servers (separated by semicolons) to which all log messages will be sent.
  • Tester.txt – when this file exists, “Update.exe” downloads testing versions of NET Genium intended for partners and developers. These versions may contain bugs or be unstable. See the Logging chapter.
  • UnderConstruction.txt – when this file exists, the web application becomes unavailable, and all requests are redirected to “UnderConstruction.aspx”. The file may optionally contain a custom message.
  • UnderConstruction2.txt – similar to the above, but only the “Administrator” login is allowed; all other users are redirected to “UnderConstruction.aspx”. A custom message may be included.
  • Version.txt – the current version number of NET Genium.
  • XFrameOptions.txt – value of the “X-Frame-Options” header inserted into every response. This header controls whether pages may be displayed in frames. Setting “*” allows framing from external domains.

5. File attachments

  • File attachments are stored on disk in the “Files” directory. Each file attachment has its original filename stored in the database in the “sfiles” table, while the actual file on disk is saved under a modified filename. The filename on disk (without extension) is defined as the ID of the file - attachment record in the “sfiles” table, and the file extension is preserved. For example, the first file attachment stored in NET Genium may appear as “1.pdf”.
  • File attachments are created by uploading a file using the “File” or “Image” controls in an edit form, by creating a file attachment through a server function in a script, and similar mechanisms.
  • The file - attachments directory can be redirected to a different location on disk using a configuration file named “Files” (without extension), which is stored directly inside the “Files” directory in the same way as other file attachments. The content of the “Files” configuration file defines the disk path to the alternative directory where file attachments should be stored.

6. Logging

6.1. Incident logging

  • Incident logging is handled by two primary operations:
    • Saving log messages to files on disk in the “NETGenium\Logs” directory
    • Simultaneously sending the same log messages to a “SysLog” server

6.1.1. Log files

  • Log messages are stored in the “NETGenium\Logs” directory in the following files:
    • Auth-year-month.log – List of successful and unsuccessful logins and logouts
    • Download-year-month.log – List of downloaded files
    • Errors.log – List of errors that occurred during user activity
    • Export-year-month.log – List of user - exported data
    • FinishUpdate.log – List of errors that occurred during application updates
    • Fulltext-year-month.log – List of errors during full - text searching of file attachments
    • ResendEmlFiles-year-month.log – List of SMTP communication commands executed when attempting to resend email messages queued on disk (in the “NETGenium\SMTP” directory)
    • RunScript-year-month.log – List of scripts executed through the “RunScript.exe” application
    • Scripts60sec-year-month.log – List of scripts that ran for more than 60 seconds
    • SMTP-year-month.log – List of successfully and unsuccessfully sent emails
    • System.log – List of informational messages related to application startup (often associated with application - pool starts or restarts)
    • UnsafeTags.log – List of original and sanitized HTML code that was cleaned when entering formatted text in “RichTextBox” controls
    • Version.log – List of database - structure changes related to new application versions
    • Warnings.log – List of warnings
  • The log - file directory can be redirected to another location on disk using a configuration file named “Logs” (without extension), which is stored directly inside the directory of the same name, in the same way as other log files. The content of the “Logs” file defines the disk path to the alternative directory where log files should be stored.

6.1.2. SysLog

  • Sending log messages can be configured for multiple SysLog servers simultaneously. The configuration is done using the “SysLog.txt” file located in the “NETGenium\Config” directory.
  • If the “SysLog.txt” configuration file exists and contains one SysLog server IP address or several SysLog server IP addresses separated by semicolons, all log messages will be automatically sent to the specified SysLog servers and stored in the “NETGenium\Logs” directory.
  • If the “SysLog.txt” configuration file is not present, logging is performed only into the files located in the “NETGenium\Logs” directory.
  • Messages sent to a SysLog server use the following format, with space as the separator between values: “date time server_domain_name application category event_type user_login_name user_ip_address message”
    • Category – Auth, Download, Errors, etc.
    • Event type – VERBOSE, NOTICE, WARNING, ERROR, FATAL

6.2. Web application performance logging

  • NET Genium logs the following events into the database:
    • Loading speed of edit forms – into the database table “stables_stats”
    • Loading speed of view pages – into the database table “sviewpages_stats”
    • Database query performance – into the database table “squerybuilder_stats”
    • External function performance – into the database table “sngef_stats”
  • Enabling or disabling logging is done in a dedicated dialog under “Modify NET Genium” on the “Other” tab:
    • Off – logging is turned off
    • To database – logging is performed only into the database
    • To disk – logging is performed only to disk in the “Logs” directory
    • To database and disk – logging is performed both into the database and to disk in the “Logs” directory
  • Aggregated statistics generated from database - logged events can be viewed using reports. More details are provided in the separate guide Reports.