Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

Requirements

  • a connection to the database which holds the transfer history has to be configured;
  • a JobScheduler with the Job Chains job chains that fill the transfer history tables of the database (not deployed with this setup).

Installation

There are two ways to install the JADE YADE Background Service History Viewer:

  • install the JADE YADE Background Service History Viewer with a preconfigured Jetty;
    • This is recommended for supported platforms.
    • For platforms with limited support the installer can still be used if available. However, the uses is responsible for required changes in the webservlet container start script (start.sh).
  • install the JADE YADE Background Service History Viewer in your own webservlet container
    • This is recommended for users who want to use their individual webservlet container.

After selecting the install path you are prompted to decide whether you want to install the JADE YADE Background Service History Viewer with a preconfigured Jetty or use and already installed servlet container.

Installation with a preconfigured Jetty

To install the JADE YADE Background Service History Viewer, check the checkbox. The text field to choose a path will disappear and a text field to enter the port for Jetty will be shown.

...

After the installation process has finished the new service will have been installed and be active. The name of the service will be "SOS JadeHistoryViewer" (Windows) or "jadehistoryviewer" (Linux) respectively.

Now you can use the JADE YADE Background Service History Viewer with your Browser under the address http://[HOSTNAME]:[PORT]/JadeHistoryViewer.

Installation in your own

...

Servlet Container

During the installation process you will be prompted to:

...

Use this option to install a newer version of the web application as well.

Configuration Files

The war file jadeHistoryViewer.war contains configuration files that are updated during setup.

PathFileUsage
WEB-INF/classeslog4j.propertieslog4j configuration to log with log4j
/WEB-INF/classeslogback.xmllogback configuration to log with logback
/WEB-INF/classeshibernate.cfg.xmldatabase configuration file

hibernate.cfg.xml

Panel

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE hibernate-configuration PUBLIC "-//Hibernate/Hibernate Configuration DTD 3.0//EN"
"http://www.hibernate.org/dtd/hibernate-configuration-3.0.dtd">
<hibernate-configuration>
<session-factory>
<property name="hibernate.connection.driver_class">org.mariadb.jdbc.Driver</property>
<property name="hibernate.connection.password">DBPASSWORD</property>
<property name="hibernate.connection.url">jdbc:mysql://DBHost:DBPort/DBName</property>
<property name="hibernate.connection.username">DBUSERNAME</property>
<property name="hibernate.dialect">org.hibernate.dialect.MySQLInnoDBDialect</property>
<property name="hibernate.show_sql">false</property>
<property name="hibernate.connection.autocommit">false</property>
<property name="hibernate.format_sql">true</property>
<property name="hibernate.temp.use_jdbc_metadata_defaults">false</property>
<property name="javax.persistence.validation.mode">none</property>
<mapping class="sos.ftphistory.db.JadeFilesDBItem"/>
<mapping class="sos.ftphistory.db.JadeFilesHistoryDBItem"/>
</session-factory>
</hibernate-configuration>

This configuration will be updated with the credentials specified during the setup routine.

log4j.properties

  • The below setting for ${PATH_SET_BY_SETUP} is replaced by the installer with the path of the target directory

...

This configuration is used by log4j for logging and storing the log files in the location defined by the ${PATH_SET_BY_SETUP} property.

logback.xml

  • The below setting for ${PATH_SET_BY_SETUP} is replaced by the installer

...