Installing ReportServer on Windows
In this best-practice guide we discuss step-by-step how to manually install ReportServer on a freshly set-up Windows 10 box. If you would rather use a preconfigured installation package, have a look at the installer packages available in our download page.
The instructions in this guide are valid both for ReportServer Community Edition and for ReportServer Enterprise Edition (see here for a detailed comparison).
Overview
ReportServer is a database backed Java web application. In order to install ReportServer we additionally need to install Java, a servlet container (in this guide we choose Tomcat) and a database (in this guide we choose MariaDB). Thus, a high-level overview of an installation of ReportServer consists of the following steps.
Obtaining the ReportServer Binaries
The binaries for ReportServer Community Edition are available from SourceForge. On SourceForge look for Files and then the bin directory. Beneath the bin directory you should find directories for the various versions of ReportServer. At the time of writing, the latest version is ReportServer 4.6.3. Download the latest version (the file should be named RS followed by the version number and the build number, followed by reportserver.zip). For example, RS4.6.3-6104-reportserver.zip denotes ReportServer version 4.6.3 build number 6104.
To obtain a trial version of ReportServer Enterprise Edition go to our download page and look for Binaries.
Download ReportServer (either enterprise or community). We will get back to this shortly.
Installing Java
For a smooth experience it is best to install e.g. Java 11. Note that Java 17 is also supported. You can download Java JDK 11 from here. If you are running on a 64-bit Windows (which is highly recommended when using ReportServer) you should ensure to download the 64-bit version of java. Scroll down the site and download the Java 11 JDK Windows x64 MSI Installer and run it. During the installation choose to set the Java HOME Path (check Screenshot).
Once the installation is complete let us ensure that java is running properly. For this open a command prompt (open the Cortana quick search and search for cmd). Then run the following command
java -version
You should see a response similar to the following
openjdk version "11.0.18" 2023-01-17 LTS OpenJDK Runtime Environment Zulu11.62+17-CA (build 11.0.18+10-LTS) OpenJDK 64-Bit Server VM Zulu11.62+17-CA (build 11.0.18+10-LTS, mixed mode)
If so, you have successfully installed a 64-bit Java. Let's proceed with installing Tomcat.
Installing Tomcat
In the following we install Apache Tomcat a web application server that is well suited to run ReportServer. We will install Tomcat in version 9. The easiest is to install the 32-bit/64-bit Windows Service Installer. You find the download page in the left navigation.
Once the installer is downloaded, run the installer and follow the setup. You will be asked to choose the Components for the installation. Here choose the Minimum setup which consists only of the Start Menu Items. In the next step you can adapt Tomcat's basic configuration, to locate the installed Java JRE and to define the installation directory. The default values are usually fine so simply proceed.
Once the installation has finished you are asked whether to start Tomcat. For the moment we do not yet start Tomcat, so disable the checkbox and hit Finish.
In a next step we need to configure Tomcat. For this open the tomcat management application Configure Tomcat which you can find in the start menu. Go to the Java tab. Here we need to adapt the the Java Options as well the memory settings. Go to the end of the Java options and add the following lines
-Drs.configdir=C:\Program Files\reportserver -Dfile.encoding=UTF8
The first one tells ReportServer that we are using an external configuration directory which will be C:\Program Files\reportserver. The second property tells Tomcat (and ReportServer) to use UTF8 encoding by default. As for the memory setting, set the initial memory pool to 512 MB and the maximum memory pool should be set to at least 1.5 GB. Click on Apply and then OK to close the configuration.
If you use Java 9 or newer, you need some extra configuration which can be done in the setenv.bat of your Tomcat environment. Specifically, the following configuration is needed, so create a setenv.bat in the C:\Program Files\Apache Software Foundation\Tomcat 9.0\bin Folder containing:
--add-opens=java.base/java.net=ALL-UNNAMED --add-opens=java.base/jdk.internal.ref=ALL-UNNAMED --add-opens=java.base/jdk.internal.reflect=ALL-UNNAMED --add-opens=java.base/java.lang.invoke=ALL-UNNAMED --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.base/java.lang.ref=ALL-UNNAMED --add-opens=java.base/java.lang.reflect=ALL-UNNAMED --add-opens=java.base/sun.reflect.generics.repository=ALL-UNNAMED -Djavax.net.ssl.trustStoreType=JKS -Dfile.encoding=UTF-8 -Djava.awt.headless=true
Next step is to install a database. ReportServer can be installed on DB2, MariaDB, MySQL, Microsoft SQL Server, Oracle or PostgreSQL. Here we choose MariaDB.
Installing MariaDB
You can find current installers for MariaDB on http://downloads.mariadb.org. Choose the latest stable version (at the time of writing 10.11.1 RC is the latest supported) and download the corresponding 64-bit MSI package.
Once downloaded, run the installer. Note that Windows may regard MariaDB as an Unknown Publisher in which case it will ask you twice whether you want to run the installer. Hit Run anyway to continue and follow the setup steps. Most of the standard options are fine so the only thing you need to change is the root password and you should select the checkbox next to Use UTF8 as default server's character set. The UTF8 option is on the bottom of the same page as the password.
MariaDB comes with a copy of HeidiSQL which provides a front end to the database. Once the installation has finished, open HeidiSQL and create a new Session. On the right side under Settings you 'll have to choose a Library that works (most likely libmysql.dll, if not, choose another one), then choose user root and the password that you provided during the installation and hit Open. You should now see your database.
To create the database for ReportServer, move the mouse to the left (Database) panel, right click and choose Create New -> Database. As name we choose reportserver and hit OK.
We will come back to the database in a bit to create the ReportServer tables. You may also want to create an additional user to be used by ReportServer that only has the privileges to work on the freshly created reportserver database. For the purpose of this guide, we assume that ReportServer will also use the root user.
Setting up ReportServer
Now that we have Tomcat and MariaDB set up, we can install and configure ReportServer. Let REPORTSERVER.zip denote the zip file that we downloaded in the very first step. Unzip the file.
Next, go to the Tomcat installation directory. If you haven't changed the directory during installation the directory should be
C:\Program Files\Apache Software Foundation\Tomcat 9.0
Here you should find a folder webapps that contains a single folder called ROOT. Remove the ROOT folder. Now move the extracted ReportServer folder into Tomcat's webapps directory and rename it to ROOT. Within the ROOT folder you should now have amongst others a folder called ddl and one called WEB-INF.
Next we create the ReportServer configuration directory. For this create the following directories
- C:\Program Files\reportserver
- C:\Program Files\reportserver\config
- C:\Program Files\reportserver\lib
The lib directory can hold additional jars (for example, additional JDBC drivers). The config directory can hold internal configuration files. For further information about the config dir see the chapter on the configuration dir in ReportServer's Configuration Guide.
In a next step we will copy default configuration files to the configuration directory. We will copy the following files to:
- C:\Program Files\reportserver\persistence.properties.example
- C:\Program Files\reportserver\reportserver.properties
- C:\Program Files\reportserver\logging-rs.properties
C:\Program Files\Apache Software Foundation\Tomcat 9.0\webapps\ROOT\WEB-INF\classes
Copy the files to C:\Program Files\reportserver and rename the file persistence.properties.example into persistence.properties. This file holds the database configuration which we setup next. For this open the file persistence.properties with a text editor (if no proper editor is installed try Notepad++ which is freely available from https://notepad-plus-plus.org/) and set up the following connection parameters (replace the password with the password you chose during the MariaDB installation).
hibernate.connection.username=root hibernate.connection.password=**** hibernate.dialect=net.datenwerke.rs.utils.hibernate.MariaDbDialect hibernate.connection.driver_class=org.mariadb.jdbc.Driver hibernate.connection.url=jdbc:mariadb://localhost:3306/reportserver
Initialize the ReportServer Database
ReportServer expects that its database is properly initialized. For this we need to run the DDL script for MySQL that is located in the ddl subdirectory of ReportServer (i.e., in C:\Program Files\Apache Software Foundation\Tomcat 9.0\webapps\ROOT\ddl). ReportServer supports various databases and in that directory you not only find the create script for MySQL (which is also the one needed for MariaDB) but also for all other supported databases. The files are named according to the following format:
reportserver-VERSION-schema-MySQL5_CREATE.sql
Besides a CREATE script there is also a DROP script, if you wish to clean up the database.
To set up ReportServer's database again open HeidiSQL and a connect to the reportserver database. Select the database by double clicking in the left panel on the reportserver database. Next chose Load SQL file from the File Menu and select the reportserver-VERSION-schema-MySQL5_CREATE.sql file. Once the file is loaded you should see the file in within HeidiSQL. Hit F9 (or select the blue play button from the toolbar) to run the script. Wait for the script to finish (this can take a few seconds). Once finished you can close HeidiSQL.
If you are not installing on MariaDB make sure to call commit to commit the inserts at the end of the DDL.
Setup Logging
By default, Tomcat will write its log entries into a file called catalina.out, which not only contains ReportServer specific entries but anything that involves Tomcat. To have a ReportServer specific log file, edit the file C:\Program Files\Apache Software Foundation\Tomcat 9.0\conf\logging.properties. Note that this step is optional and can be skipped in which case the standard Tomcat log structure will be used.
To have a ReportServer specific log file, the following changes need to be made to C:\Program Files\Apache Software Foundation\Tomcat 9.0\conf\logging.properties:
- add 5reportserver.org.apache.juli.FileHandler to handlers
- define handler specific properties
- tell tomcat to use the new handler for anything ReportServer specific
- adapt the log format to include a proper timestamp
A sample configuration could look as follows:
# Licensed to the Apache Software Foundation (ASF) under one or more
# contributor license agreements. See the NOTICE file distributed with
# this work for additional information regarding copyright ownership.
# The ASF licenses this file to You under the Apache License, Version 2.0
# (the "License"); you may not use this file except in compliance with
# the License. You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
handlers = 1catalina.org.apache.juli.AsyncFileHandler, 2localhost.org.apache.juli.AsyncFileHandler, 3manager.org.apache.juli.AsyncFileHandler, 4host-manager.org.apache.juli.AsyncFileHandler, 5reportserver.org.apache.juli.FileHandler, java.util.logging.ConsoleHandler
.handlers = 1catalina.org.apache.juli.AsyncFileHandler, java.util.logging.ConsoleHandler
############################################################
# Handler specific properties.
# Describes specific configuration info for Handlers.
############################################################
1catalina.org.apache.juli.AsyncFileHandler.level = FINE
1catalina.org.apache.juli.AsyncFileHandler.directory = ${catalina.base}/logs
1catalina.org.apache.juli.AsyncFileHandler.prefix = catalina.
2localhost.org.apache.juli.AsyncFileHandler.level = FINE
2localhost.org.apache.juli.AsyncFileHandler.directory = ${catalina.base}/logs
2localhost.org.apache.juli.AsyncFileHandler.prefix = localhost.
3manager.org.apache.juli.AsyncFileHandler.level = FINE
3manager.org.apache.juli.AsyncFileHandler.directory = ${catalina.base}/logs
3manager.org.apache.juli.AsyncFileHandler.prefix = manager.
4host-manager.org.apache.juli.AsyncFileHandler.level = FINE
4host-manager.org.apache.juli.AsyncFileHandler.directory = ${catalina.base}/logs
4host-manager.org.apache.juli.AsyncFileHandler.prefix = host-manager.
5reportserver.org.apache.juli.FileHandler.level = FINE
#5reportserver.org.apache.juli.FileHandler.maxDays = 90
5reportserver.org.apache.juli.FileHandler.directory = ${catalina.base}/logs
5reportserver.org.apache.juli.FileHandler.prefix = reportserver.
java.util.logging.ConsoleHandler.level = FINE
java.util.logging.ConsoleHandler.formatter = java.util.logging.SimpleFormatter
java.util.logging.SimpleFormatter.format = [%1$tc] %4$s: %2$s - %5$s %6$s%n
############################################################
# Facility specific properties.
# Provides extra control for each logger.
############################################################
org.apache.catalina.core.ContainerBase.[Catalina].[localhost].level = INFO
org.apache.catalina.core.ContainerBase.[Catalina].[localhost].handlers = 2localhost.org.apache.juli.AsyncFileHandler
org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/manager].level = INFO
org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/manager].handlers = 3manager.org.apache.juli.AsyncFileHandler
org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/host-manager].level = INFO
org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/host-manager].handlers = 4host-manager.org.apache.juli.AsyncFileHandler
org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/reportserver].level = INFO
org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/reportserver].handlers = 5reportserver.org.apache.juli.FileHandler
# For example, set the org.apache.catalina.util.LifecycleBase logger to log
# each component that extends LifecycleBase changing state:
#org.apache.catalina.util.LifecycleBase.level = FINE
# To see debug messages in TldLocationsCache, uncomment the following line:
#org.apache.jasper.compiler.TldLocationsCache.level = FINE
Starting ReportServer
We are finally ready to start Tomcat and thus ReportServer. Again open the Tomcat management application. In the general tab on the bottom you have buttons for starting and stopping Tomcat. Hit Start. If everything goes fine, Tomcat should show a progress bar and then switch to showing Service Status: Started. To ensure that everything worked (or to find out what does not) let us have a look at the log files. They are located in
C:\Program Files\Apache Software Foundation\Tomcat 9.0\logs
again assuming that you installed Tomcat in its default location. There you should now find a log file called reportserver.DATE.log which, if everything went fine should have content similar to the following:
26-Jan-2023 17:21:12.600 INFO [main] net.datenwerke.rs.EnvironmentValidator.startup
_____ _ _____ ______ _ _
| __ \ | | / ____| | ____| | | (_)
| |__) |___ _ __ ___ _ __| |_| (___ ___ _ ____ _____ _ __ | |__ _ __ | |_ ___ _ __ _ __ _ __ _ ___ ___
| _ // _ \ '_ \ / _ \| '__| __|\___ \ / _ \ '__\ \ / / _ \ '__| | __| | '_ \| __/ _ \ '__| '_ \| '__| / __|/ _ \
| | \ \ __/ |_) | (_) | | | |_ ____) | __/ | \ V / __/ | | |____| | | | || __/ | | |_) | | | \__ \ __/
|_| \_\___| .__/ \___/|_| \__|_____/ \___|_| \_/ \___|_| |______|_| |_|\__\___|_| | .__/|_| |_|___/\___|
| | | |
|_| |_|
Version: RS4.4.0-6084 2022-12-08-13-49-54
Code Version: 2022-12-08-12-41-21
Java Version: Azul Systems, Inc. OpenJDK 64-Bit Server VM 11.0.18+10-LTS (11)
VM Args: -Dcatalina.home=C:\Program Files\Apache Software Foundation\Tomcat 9.0 -Dcatalina.base=C:\Program Files\Apache Software Foundation\Tomcat 9.0 -Djava.io.tmpdir=C:\Program Files\Apache Software Foundation\Tomcat 9.0\temp -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.util.logging.config.file=C:\Program Files\Apache Software Foundation\Tomcat 9.0\conf\logging.properties -Drs.configdir=C:\Program Files\reportserver --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.io=ALL-UNNAMED --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED exit abort -Xms512m -Xmx1500m
Max memory: 1,500 MB
JVM Locale: en_US
rs.configdir: C:\Program Files\reportserver (OK)
### DB Config ###
hibernate.dialect: net.datenwerke.rs.utils.hibernate.MariaDbDialect (OK)
hibernate.connection.driver_class: org.mariadb.jdbc.Driver (OK)
hibernate.connection.url: jdbc:mariadb://localhost:3306/reportserver (OK)
hibernate.connection.username: root
hibernate.connection.password: **********
hibernate.default_schema:
Connection Test: OK
Schema Version: RS3.0-25
### Internal datasource metadata ###
Database name: MariaDB
Database version: 10.11.1-MariaDB
Driver name: MariaDB Connector/J
Driver version: 3.1.0
JDBC major version: 4
JDBC minor version: 2
JDBC URL: jdbc:mariadb://localhost:3306/reportserver?user=root&password=***
JDBC username: root
26-Jan-2023 17:21:12.636 INFO [main] net.datenwerke.rs.EnvironmentValidator.startup Validating database schema...
26-Jan-2023 17:21:31.434 INFO [main] net.datenwerke.rs.EnvironmentValidator.hibernateValidateSchema Schema validation completed
26-Jan-2023 17:21:35.373 INFO [main] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure try to bind: net.datenwerke.rs.saiku.server.rest.resources.InfoResource
26-Jan-2023 17:21:35.373 INFO [main] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure done binding: net.datenwerke.rs.saiku.server.rest.resources.InfoResource
26-Jan-2023 17:21:35.373 INFO [main] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure try to bind: net.datenwerke.rs.saiku.server.rest.resources.OlapDiscoverResource
26-Jan-2023 17:21:35.373 INFO [main] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure done binding: net.datenwerke.rs.saiku.server.rest.resources.OlapDiscoverResource
26-Jan-2023 17:21:35.373 INFO [main] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure try to bind: net.datenwerke.rs.saiku.server.rest.resources.StatisticsResource
26-Jan-2023 17:21:35.373 INFO [main] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure done binding: net.datenwerke.rs.saiku.server.rest.resources.StatisticsResource
26-Jan-2023 17:21:35.373 INFO [main] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure try to bind: net.datenwerke.rs.saiku.server.rest.resources.ExporterResource
26-Jan-2023 17:21:35.377 INFO [main] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure done binding: net.datenwerke.rs.saiku.server.rest.resources.ExporterResource
26-Jan-2023 17:21:35.377 INFO [main] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure try to bind: net.datenwerke.rs.saiku.server.rest.resources.Query2Resource
26-Jan-2023 17:21:35.377 INFO [main] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure done binding: net.datenwerke.rs.saiku.server.rest.resources.Query2Resource
26-Jan-2023 17:21:35.377 INFO [main] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure try to bind: net.datenwerke.rs.saiku.server.rest.resources.SessionResource
26-Jan-2023 17:21:35.377 INFO [main] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure done binding: net.datenwerke.rs.saiku.server.rest.resources.SessionResource
26-Jan-2023 17:21:35.377 INFO [main] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure try to bind: net.datenwerke.rs.saiku.server.rest.resources.BasicRepositoryResource2
26-Jan-2023 17:21:35.377 INFO [main] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure done binding: net.datenwerke.rs.saiku.server.rest.resources.BasicRepositoryResource2
26-Jan-2023 17:21:35.377 INFO [main] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure try to bind: net.datenwerke.rs.saiku.server.rest.resources.License
26-Jan-2023 17:21:35.377 INFO [main] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure done binding: net.datenwerke.rs.saiku.server.rest.resources.License
26-Jan-2023 17:21:35.377 INFO [main] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure try to bind: net.datenwerke.rs.saiku.server.rest.resources.DataSourceResource
26-Jan-2023 17:21:35.377 INFO [main] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure done binding: net.datenwerke.rs.saiku.server.rest.resources.DataSourceResource
26-Jan-2023 17:21:35.377 INFO [main] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure try to bind: net.datenwerke.rs.saiku.server.rest.resources.FilterRepositoryResource
26-Jan-2023 17:21:35.377 INFO [main] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure done binding: net.datenwerke.rs.saiku.server.rest.resources.FilterRepositoryResource
26-Jan-2023 17:21:35.377 INFO [main] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure try to bind: net.datenwerke.rs.saiku.server.rest.resources.SaikuI18nResource
26-Jan-2023 17:21:35.377 INFO [main] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure done binding: net.datenwerke.rs.saiku.server.rest.resources.SaikuI18nResource
26-Jan-2023 17:21:36.369 INFO [main] net.datenwerke.rsenterprise.main.service.RsEnterpriseModule.configureServlets SAP Crystal libraries not present
26-Jan-2023 17:21:45.705 WARNING [main] net.datenwerke.rs.configservice.service.configservice.ConfigServiceImpl.getConfigFailsafe Configfile scheduler/scheduler.cf could not be loaded. Default values are in effect.
26-Jan-2023 17:21:45.705 WARNING [main] net.datenwerke.rs.configservice.service.configservice.ConfigServiceImpl.getConfigFailsafe Configfile exportfilemd/pdfexport.cf could not be loaded. Default values are in effect.
26-Jan-2023 17:21:45.705 WARNING [main] net.datenwerke.rs.configservice.service.configservice.ConfigServiceImpl.getConfigFailsafe Configfile exportfilemd/pdfexport.cf could not be loaded. Default values are in effect.
26-Jan-2023 17:21:46.430 INFO [main] net.datenwerke.rs.saiku.service.saiku.ThinQueryServiceImpl. loaded thinqueryservice
26-Jan-2023 17:21:46.430 INFO [main] net.datenwerke.rs.saiku.service.saiku.ThinQueryServiceImpl. loaded thinqueryservice
26-Jan-2023 17:21:47.142 INFO [main] net.datenwerke.rs.core.service.i18ntools.RemoteMessageServiceImpl. Loading messages...
26-Jan-2023 17:21:58.073 INFO [main] net.datenwerke.rs.core.service.i18ntools.RemoteMessageServiceImpl. Available locales: de, hi, lo, pt, lt, hr, lv, hu, zh-CN, hy, uk, id, mk, mn, af, uz, ms, el, mt, en, is, it, my, es, et, eu, vi, ja, ne, ro, nl, no, be, fi, ru, bg, keys, bn, fr, jw, bs, ka, si, sk, sl, ga, gd, ca, sq, sr, kk, km, sv, ko, zh-TW, ta, cs, th, lb, tl, pl, da, tr
26-Jan-2023 17:22:16.830 INFO [Thread-12] net.datenwerke.rs.installation.ExecutePackagedScriptsTask.executeOnFirstRun Executing package scripts from: C:\Program Files\Apache Software Foundation\Tomcat 9.0\webapps\ROOT\pkg
26-Jan-2023 17:22:17.814 INFO [Thread-12] net.datenwerke.rs.installation.ExecutePackagedScriptsTask.executeOnFirstRun Executing package: C:\Program Files\Apache Software Foundation\Tomcat 9.0\webapps\ROOT\pkg\baseconfig-RS4.4.0-6084-2022-12-08-13-49-54.zip
26-Jan-2023 17:27:47.611 INFO [Thread-12] net.datenwerke.rs.core.service.jarextension.hookers.ReportServerExtenderHooker.initialize Start loading ReportServer extensions.
26-Jan-2023 17:27:47.627 INFO [Thread-12] net.datenwerke.rs.core.service.EnvironmentAfterStartupInformation.initialize
Application Server: Apache Tomcat/9.0.71
### PAM Configuration ###
Static PAM configuration: net.datenwerke.rs.authenticator.service.pam.UserPasswordPAMAuthoritative
Finalized PAM configuration: class net.datenwerke.rs.authenticator.service.pam.UserPasswordPAMAuthoritative
26-Jan-2023 17:27:51.941 INFO [Thread-12] net.datenwerke.rs.search.service.search.SearchServiceImpl.rebuildIndex Rebuilding search index...
26-Jan-2023 17:27:52.401 INFO [Thread-12] net.datenwerke.gf.service.lateinit.LateInitStartup$1.run Startup completed
The last line (Startup complete) indicates that ReportServer was properly started. You can now direct your browser to
http://127.0.0.1:8080/ReportServer.html
and log in to ReportServer via user root with password root which ReportServer created on the first start.
Happy Reporting
