Web Report Server repwebexe

The Report Manager web server generates PDF files on the fly: it prompts the user for the report name and parameters, runs the report and returns an Adobe PDF file, which can be displayed directly in the browser.

It is a true network and web report server with no license fees and multiprocessor support, a native binary for Windows and Linux. It has been deployed as CGI behind Apache or IIS for more than twenty years, and it is also a service with an HTTP API and a published Docker image.

It runs reports; it does not design them: you upload the .rep files you designed with any Report Manager designer. To design in the browser, with an AI copilot, see Reportman Server — it reads the same files. The three servers compared.

Run it self-hosted with Docker

The published image runs repwebexe -selfhosted and serves the web report server on port 8080. Start the service directly with:

docker run -d \
  -p 8080:8080 \
  -e REPORTMAN_HTTP_PORT=8080 \
  -v repweb_etc:/usr/local/etc \
  -v repweb_home:/var/lib/reportman \
  -v repweb_logs:/var/log/reportman \
  --name reportman-web \
  --restart unless-stopped \
  tonimartir/reportman-web:latest

Docker pulls the image on the first run. The admin panel is then available at http://localhost:8080/admin/login.

Good to know

• Port: set with REPORTMAN_HTTP_PORT (default 8080); publish the same port with -p.
• Persistent data (named volumes): repweb_etc → /usr/local/etc (dbxdrivers.conf, dbxconnections.conf), repweb_home → /var/lib/reportman (server configuration), repweb_logs → /var/log/reportman.
• Database clients included: PostgreSQL, MySQL/MariaDB, Firebird/Interbase, SQLite, MS SQL Server/Sybase (FreeTDS) and ODBC. Proprietary clients (Oracle, Db2) are added in a derived image.
• TLS / authentication: place a reverse proxy in front of the container.

Image on Docker Hub: tonimartir/reportman-web.

Documentation

See the documentation and choose the sections under Web Report Server.