...
Requirements
- The user has to install a webserver where the web application will be hosted.
We recommend the use of jetty, because it is a lightweight webservlet container easy to set up and with few configuration expenses.
The web application will work on other servlet containers, too. - Deployment of the necessary libraries
Libraries which are used by the web application are integrated in the war file, therefore it runs independently to any JobScheduler instance. - a database connection
A database connection to the database which holds the transfer history has to be configured. - a JobScheduler with the Job Chains to fill the transfer history tables of the database
Installation
There are two ways to install the JADE Background Service History Viewer.
...
- configure the path to where the war file of the webapplication will be stored.
- configure the credentials for the database connection to the database holding the data of the transfer history.
- add the jobscheduler, which has to perform the JADE Job Chains to fill the database with the transfer history data.
The war file will be stored in the configured path and holds the configured database connection credentials.
...
| Pfad | Datei | Verwendung |
|---|
| /WEB-INF/classes | log4j.properties | log4j configuration to log with log4j |
| /WEB-INF/classes | logback.xml | logback configuration to log with logback |
| /WEB-INF/classes | hibernate.cfg.xml | database 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">scheduler</property>
<property name="hibernate.connection.url">jdbc:mysql://wilma:3305/scheduler</property>
<property name="hibernate.connection.username">scheduler</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>
|
log4j.properties example
| Panel |
|---|
| borderColor | grey |
|---|
| borderWidth | 1 |
|---|
| borderStyle | solid |
|---|
|
# Set the log level of the root logger to WARN
log4j.rootLogger=DEBUG, consoleAppender, fileAppender
# Direct log messages to the console
log4j.appender.consoleAppender=org.apache.log4j.ConsoleAppender
log4j.appender.consoleAppender.layout=org.apache.log4j.PatternLayout
log4j.appender.consoleAppender.layout.ConversionPattern=%5p [%t] (%F:%L) - %m%n
# Direct log messages to a file
# Set the file appender to a rolling file appender with a date configuration
log4j.appender.fileAppender=org.apache.log4j.DailyRollingFileAppender
# Set the type of the pattern layout to EnhancedPatternLayout to display local timezone
log4j.appender.fileAppender.layout=org.apache.log4j.EnhancedPatternLayout
# Set the pattern layout
log4j.appender.fileAppender.layout.ConversionPattern=%-5p [%d{yyyy-MM-dd HH:mm:ss,SSS Z}]: [%t] (%F:%L) - %m%n
# Set the output file an its path
log4j.appender.fileAppender.File=${java.io.tmpdir}/JadeHistory.log
# Set the append to true, should not overwrite
log4j.appender.fileAppender.Append=true
# Set the immediate flush to true
log4j.appender.fileAppender.ImmediateFlush=true
# Set the threshold to debug mode
log4j.appender.fileAppender.Threshold=debug
# Set the date pattern when the rollover should happen (daily at midnight)
log4j.appender.fileAppender.DatePattern='.'yyyy-MM-dd
|
...