/monitor web application

Start

To install service.monitor, follow the steps below:

Optionally, you can first adjust the name of the WAR file monitor.war.
Make sure that the Tomcat service is started.
Then copy the WAR file into the %TOMCAT%\webapps folder. The file will now be unpacked automatically.

Alternatively, you can use the Tomcat Manager to install the WAR file. If the Tomcat service is started, you can usually reach the Tomcat Manager at http://<yourserver>:8080/manager/html.
When Tomcat unpacks the file, it will then attempt to start the web application. Due to missing configuration this initial start will fail.

Create data directory location

Create a folder on the system that is going to contain the customised configuration values and is referred to below as data.directory.
Copy the %TOMCAT%\webapps\monitor\WEB-INF\classes\application.properties file to data.directory.
In the %TOMCAT%\webapps\monitor\WEB-INF\classes\custom-application.properties file, change the configuration value from data.directory.location to the newly created folder data.directory.

Configuring application.properties

All changes that need to be adjusted to the installation system or infrastructure are made in the application.properties file in the data.directory.

You need to adjust the following parameters. See the Common configuration page for an overview of the most commonly used parameters.

Internal account

security.user.admin.pw: Password for the internal default account monitor.

It is strongly recommended to set a new password for the internal default account monitor for operation. This is part of the built-in authentication procedure, which is the default after installation. A new password hash can be generated using the script resources\tools\createPassword.bat or resources\tools\createPassword.sh from the command line. The call is createPassword.bat SHA-512 <password>. Copy the output value of the tool into the file as a configuration value.

Public base URL

basehost.url: The public base URL for external communication without the context name.

Please also make sure to specify the correct protocol, e.g. https://[public.domain.tld].

Database connection

db.use

Specifies whether a direct database connection (JDBC) or a container-managed database connection (JNDI) is established.

In the case of JDBC, the other parameters described here must be configured. In the case of JNDI, follow the section JNDI.

Allowed Values: jdbc, jndi

db.type: Type of database.

Allowed Values: postgresql, oracle, oracle10, sqlserver
db.jdbc.url: Database connection URL.
db.jdbc.username: Name of db user.
db.jdbc.password: Password of db user.

Mail server

mailing.host: Mail server host.
mailing.port: Mail server port.
mailing.user: Name of SMTP user.
mailing.password: Password of SMTP user.
mailing.sender: Sender address.