The i-net Clear Reports server can execute report files (*.rpt) that have been designed with the i-net Designer or using the Ad Hoc reporting.

After installation and setup you can open the start page of the i-net Clear Reports server. The start page provides an overview of the available application modules. More modules can be added with additional plugins.

A login is required to access most of the application modules. By default, i-net Clear Reports uses the operating system/domain accounts for authentication. On Windows it uses Windows Authentication and on Linux/Unix/macOS it uses PAM authentication based on /etc/pam.d/reporting or /etc/pam.d/login.

This means that you should be able to login with your Windows / Linux / MacOS user if you click on the Login button or on the configuration.

You should configure the following topics first:

• permissions to the report server in the configuration manager dialog: Permissions
• datasource(s) for your database(s) in the Datasource manager
• Drive application if you want to store the report templates on the report server
• additional plugins, e.g. Task Planner

Afterwards you can create report templates using the i-net Designer (local installed or as remote designer), store it in the Drive and execute it using report server and HTML report viewer or any other supported output format.

It is recommended to create a backup job in the Maintenance module. The backup can automatically be run as a task using the Task Planner.

Anti Virus scans, such as the Windows Defender, are generally recommended. Live scans may, however, have a negative impact on the performance of i-net Clear Reports. The application produces many index and cache files that need to be created and read very fast.

If the performance degrades, especially while starting up the server, some technical folders should be considered to be excluded from the scans. The main index resides in the persistence sub-directory index and can be excluded. Due to its binary nature it is possible that it generates false-positive matches otherwise. The location of the persistence can be looked up in the Diagnostics module → Server Information.

It is strongly recommended not to include the report Drive into the scanning exception, as users may be allowed to store any files there.