Installing the web application

Start

To install service.monitor, follow the steps below:

  1. Optionally, you can first adjust the name of the WAR file monitor##<version>.war. The name is used in the URL — without the ## section — through which the application is called (e.g. https://<yourserver>/monitor).

  2. Make sure that the Tomcat service is started.

  3. Then copy the WAR file into the %TOMCAT%\webapps folder. The file will now be unpacked automatically.

  4. 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.

  5. 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

  1. Create a folder on the system that contains the customised configuration values and is referred to below as data.dir. Within the new folder, also create a folder called license.

  2. Copy the %TOMCAT%\webapps\application.properties file to data.dir.

  3. In the %TOMCAT%\webapps\custom-application.properties file, change the configuration value from data.directory.location to the newly created folder data.dir.

Specify licence file

Copy the licence file to data.dir\license. The validity of the licence file is checked when the servlet container is started.

If you are not in possession of a licence file, please contact the con terra Support.

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.dir.

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].

Configure internal user

security.user.admin.pw

Password for the internal dafault user monitor.

It is strongly recommended to set a new password for the internal default user monitor for operation. The user 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.

Configure 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, another section follows below.

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.

Parameters according to protocol data

monitoring.logging.cleanup.enabled

Definition of whether log data should be deleted for each individual request in the internal data storage.

Allowed Values: true, false

monitoring.logging.interval

Specify the number of days for which log data about individual requests is retained.

Aggregated result data is kept forever.

Mail-Server

mail.host

Mail server host.

mail.port

Mail server port.

mail.user

Name of SMTP user.

mail.password

Password of SMTP user.

mail.sender

Sender address.

SMS configuration

service.monitor supports sending SMS messages via external providers using the SMTP protocol (e.g. http://www.ecall.ch/).

sms.email.server

If this method is used, service.monitor sends e-mails to the broadcast server specified here. This address must usually be on a white list at the service provider that allows the conversion from mail to SMS. The SMS option is not available in the web interface if this field is left empty.

Configuration of Simple Network Messaging Protocol (SNMP)

snmp.address

Please enter the IP/ host and port of the central SNMP management server to which the trap messages are to be sent.

Please empty the field if no such server is operated and the option is not to be offered in the user interface.

Example: hostname/162

Database setup

Part of the delivery is an SQL script schema.sql which can create the necessary tables, indices etc. in the database. (resources\sql\sm-db)

Configure database connection for Tomcat (JNDI)

In the event that the Tomcat is to establish the database connection and jndi was configured above instead of jdbc, two further configuration steps are necessary.

  1. Adjust server.xml
    You will find prepared XML sections under resources\tomcat-jndi-resources. Adjust the correct information about user, password and database connection URL. Copy this section into the file %TOMCAT%\conf\server.xml add the element GlobalNamingResources.

  2. Adjust context.xml
    Replace the file %TOMCAT%\webapps\monitor\##<version>.war\META-INF\context.xml by the file %TOMCAT%\webapps\monitor\##<version>.war\META-INF\jndi\context.xml.

Monitoring of Esri Enterprise Geodatabases

For monitoring Esri Enterprise Geodatabases (EGDB) it is necessary to take further manual steps:

  1. Add an arcobjects.jar to the classpath of the service.monitor. This must have the same version as the EGDB you want to monitor.

  2. Add a Java system variable to the start parameters of your servlet container that points to your ArcGIS instance, e.g.: -Djava.library.path="c:\Program Files\ArcGIS\Server\bin".

  3. Make sure that suitable JDBC drivers are available to connect to the EGDB, for Oracle the Oracle Instant Client must be installed.

Weitere Konfigurationshinweise