Page tree

Versions Compared

Key

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





Table of Contents
minLevel2
stylenone
classfixedTableOfContents

HTML
<script src="https://cdnjs.cloudflare.com/ajax/libs/mathjax/2.7.5/MathJax.js?config=TeX-MML-AM_HTMLorMML"></script>
<script type="text/x-mathjax-config">
MathJax.Hub.Config({
  messageStyle: "none",
  tex2jax: {
    inlineMath: [["\\(", "\\)"]],
    displayMath: [["\\[", "\\]"]],
    ignoreClass: "nostem|nolatexmath"
  },

  asciimath2jax: {
    delimiters: [["\\$", "\\$"]],
    ignoreClass: "nostem|noasciimath"
  },

  TeX: { equationNumbers: { autoNumber: "none" } }
});
//jQuery('#title-heading').hide();
jQuery('#title-heading').css('display','none'); </script>

<style>
h1.with-breadcrumbs {display: none !important}
</style> 








Productswitcher






Ahd

Averbis Health Discovery: Installation Manual 5.12


Apm

Averbis Patent Monitor: Installation Manual 5.9


Aid

Averbis Information Discovery: Installation Manual 5.13


Overview

This document describes the installation of

Prod
. If you are upgrading please refer to the Upgrade Guide.

Installation Types

There are two different ways to install

Prod
:

  • Docker - Install the application as docker containers.
  • Native - Install the application manually from an archive file.

System Requirements

Prod
requires the following system environment:

  • RAM >= 16 GB*

  • HDD > 100 GB

  • 64-bit x86 quad core processor

  • Operating System: Current versions of Windows Server or Linux (RHEL/SuSE/Ubuntu LTS)

A docker based installation additionally requires:

For a native installation you also need to provide

  • Application Server: Apache Tomcat >= 7.0.29 with at least 8GB of RAM

  • Database: MySQL >= 5.5.58

  • Oracle Java 1.8


Info

16GB RAM are the minimum requirements. When using multiple projects and multiple pipelines, additional memory may be required.


Installation with Docker

This guide describes how to deploy

Prod
using Docker

Tip

The Docker based installation is the recommended installation variant if a Docker runtime environment is available or can be installed. Compared to native installation, the effort for installation and upgrades is considerably reduced.


Info

This guide covers the Docker deployment of

Prod
on a single server. Running
Prod
on a cluster like Docker Swarm or Kubernetes is not supported yet.

Prerequisites

The following prerequisites must be installed on the target system:

Installation Steps

The installation steps are essentially as follows:

  1. Download a docker-compose.yml file
  2. Optional: Adjust the docker-compose.yml file according to your memory requirements
  3. Start the 
    Prod
    docker containers using Docker Compose

Download a docker-compose.yml file

Averbis provides a docker-compose.yml file for every

Prod
 version. It is used to configure and orchestrate the docker images that make up the
Prod
 application. The docker-compose.yml file is packaged as a PRODUCT_NAME-VERSION-docker.zip archive and can be downloaded from the Averbis Download Portal.


Extract the archive to the hard disk. We recommend to store the docker-compose.yml file in a folder named after the application, e.g. information-discovery or health-discovery

Tip

It's a best practice to extract the docker-compose.yml file in a directory named after the application, e.g. information-discovery or health-discovery.


Info

The following code samples are showing the file and directory structure for Information Discovery but can easily applied to Health Discovery and Patent Monitor as well.


The folder structure should look something like this:

Code Block
languagebash
~/information-discovery$ ls
docker-compose.yml information-discovery-5.12.2-docker.zip

An example docker-compose.yml file is shown below:

Expand
titleExample docker-compose.yml


Code Block
languageyml
linenumberstrue
version: '3.5'
services:
  database-id:
    container_name: mysql-id
    image: registry.averbis.com/mysql/mysql:1.4.0
    environment:
      MYSQL_ROOT_PASSWORD: getaccess
      MYSQL_DATABASE: aif
      MYSQL_USER: aif
      MYSQL_PASSWORD: getaccess
      innodb_buffer_pool_size: 512m
      innodb_log_file_size: 256m
      innodb_log_buffer_size: 256m
    volumes:
      - dbVol-id:/var/lib/mysql
    networks:
      - id_network
    logging:
      driver: "json-file"
      options:
        max-size: "50m"
        max-file: "3"
  gcm-id:
    container_name: gcm-id
    image: registry.averbis.com/information-discovery/gcm-id:5.12.0
    environment:
      TOMCAT_XMS: 1g
      TOMCAT_XMX: 2g
    volumes:
      - gcmVol-id:/home/tomcat/tomcat/connector-manager-home
      - gcmLogVol-id:/home/tomcat/tomcat/logs
      - ./update-folder-gcm:/home/tomcat/updateResources:z
    networks:
      - id_network
    healthcheck:
      test: ["CMD", "curl", "-f", "http://localhost:8080/connector-manager/testConnectivity"]
      interval: 30s
      timeout: 5s
      retries: 3
      start_period: 30s
    logging:
      driver: "json-file"
      options:
        max-size: "50m"
        max-file: "3"
  solr-id:
    container_name: solr-id
    image: registry.averbis.com/information-discovery/solr-id:5.12.0
    environment:
      SOLR_XMS: 512m
      SOLR_XMX: 512m
    volumes:
      - solrDataVol-id:/opt/solr/server/solr/solrCores
      - solrTermsVol-id:/opt/solr/server/solr/terms
      - solrLogVol-id:/opt/solr/server/logs
      - ./update-folder-solr:/opt/solr/updateFolder:z
    networks:
      - id_network
    healthcheck:
      test: ["CMD", "curl", "-f", "http://localhost:8983/solr/#/terms"]
      interval: 30s
      timeout: 5s
      retries: 3
      start_period: 30s
    logging:
      driver: "json-file"
      options:
        max-size: "50m"
        max-file: "3"
  aif-id:
    container_name: information-discovery
    image: registry.averbis.com/information-discovery/information-discovery:5.12.0
    ports:
       - "127.0.0.1:8080:8080"
    environment:
      TOMCAT_XMS: 1g
      TOMCAT_XMX: 10g
    depends_on:
       - database-id
       - solr-id
    volumes:
      - sharedDirectoryDataVolume-id:/home/tomcat/tomcat/shared/pipelines
      - productLogVol-id:/home/tomcat/tomcat/logs
      - ./update-folder-id:/home/tomcat/updateResources:z
      - ./licenses:/home/tomcat/tomcat/shared/licenses:z
    networks:
      - id_network
    healthcheck:
      test: ["CMD", "curl", "-f", "http://localhost:8080/information-discovery"]
      interval: 30s
      timeout: 5s
      retries: 3
      start_period: 1m
    logging:
      driver: "json-file"
      options:
        max-size: "50m"
        max-file: "3"
networks:
  id_network:
    driver: bridge
    name: id_network
    ipam:
      driver: default
      config:
        - subnet: 172.24.0.0/16
volumes:
  dbVol-id:
    driver: "local"
  gcmVol-id:
    driver: "local"
  gcmLogVol-id:
    driver: "local"
  solrDataVol-id:
    driver: "local"
  solrLogVol-id:
    driver: "local"
  solrTermsVol-id:
    driver: "local"
  sharedDirectoryDataVolume-id:
    driver: "local"
  productLogVol-id:
    driver: "local"
        




Connect to the Averbis Docker Registry

Besides the docker-compose.yml file, you need to load the 

Prod
docker images to your local computer. Averbis operates a docker registry that hosts the required docker images. To access the images you need to log on to the Averbis docker registry using your Averbis credentials:

Code Block
languagebash
sudo docker login registry.averbis.com
Username: myuser@mydomain.com
Password: *********


Login Succeeded

Start
Prod

Start the

Prod
 docker containers using the docker-compose command from within the directory that contains the docker-compose.yml file. This will fetch the required docker images from the Averbis docker registry and start the
Prod
 docker containers.

Code Block
languagebash
sudo docker-compose up -d

The startup of

Prod
 may take a couple of minutes. The current status of the 
Prod
docker containers can be viewed using the following command:

Code Block
languagebash
sudo docker ps

The output should look something like this:

Code Block
languagebash
linenumberstrue
CONTAINER ID        IMAGE                                                                       COMMAND                  CREATED             STATUS                PORTS                                 NAMES
d33afb081313        registry.averbis.com/information-discovery/information-discovery:5.12.0   "bash /home/gcmuser/…"   2 days ago          Up 2 days (healthy)   127.0.0.1:8080->8080/tcp, 13377/tcp   information-discovery
82b27d2168dc        registry.averbis.com/information-discovery/gcm-id:5.12.0                  "bash /home/gcmuser/…"   2 days ago          Up 2 days (healthy)   8080/tcp, 13377/tcp                   gcm-id
52fe02b70a13        registry.averbis.com/information-discovery/solr-id:5.12.0                 "docker-entrypoint.s…"   2 days ago          Up 2 days (healthy)   8983/tcp                              solr-id
f6c41afdb0c7        registry.averbis.com/information-discovery/mysql:1.4.0                  "docker-entrypoint.s…"   2 days ago          Up 2 days             3306/tcp                              mysql-


Aid

As soon as all

Prod
docker containers have been started (Status healthy) you can log on to the web interface at http://localhost:8080/information-discovery as an administrator with user name admin and password admin.


Ahd

As soon as all

Prod
docker containers have been started (Status healthy) you can log on to the web interface at http://localhost:8080/health-discovery as an administrator with user name admin and password admin.


Apm

As soon as all

Prod
docker containers have been started (Status healthy) you can log on to the web interface at http://localhost:8080/patent-monitor as an administrator with user name admin and password admin.


Warning

Before using

Prod
in production it is highly recommended to change the administrator password.

Stop
Prod

The Information Discovery docker containers can be stopped using the following command:

Code Block
languagebash
sudo docker-compose stop

Native Installation

This chapter describes the native installation type of

Prod
. The native installation variant is intended for environments in which no Docker environment is available and cannot be installed. This installation variant requires an external MySQL database and a Tomcat Application Server with Java 8 on the target system. 

Tip

In order to be able to perform a native installation of 

Prod
, knowledge of MySQL and Apache Tomcat is strongly recommended.

Prerequisites

The following prerequisites have to be fulfilled before installing

Prod
:

Database

To run

Prod
you’ll need an external MySQL database. The following database configuration settings are required to be made in the [mysqld] section of your MySQL configuration file my.cnf:


[mysqld]
character-set-server=utf8mb4
innodb_buffer_pool_size=2G
innodb_file_format=barracuda
innodb_file_per_table=true
innodb_large_prefix=true
innodb_log_file_size=1G
innodb_log_buffer_size=500M
max_allowed_packet=1G

Please create an empty database named aif and a database user with read and write access to that database. The database tables are created automatically during the first start of the application.

File System Resources

Prod
requires several resources such a property files, resource and temporary files to be accessible on the file system. Please create the following directories:

  • aifHome contains configuration files which are shipped along with

    Prod
    . Read access is required for this directory.

  • aifSharedResources contains resource files for the application. Read and write access is required.

  • aifWorkingDirectory is used to store temporary files. Read and write access is required for this directory.

  • connectorBaseDirectory is used to store connector configuration files. Read and write access is required for this directory.

Apache Tomcat Server

Prod
requires an existing Apache Tomcat Server environment. This section describes the configuration that is needed to run
Prod
:


Setenv Script

Please create a configuration script named setenv.sh on Linux or setenv.bat on Windows with the following content and place it in the Tomcat bin directory.

Linux:

export CATALINA_OPTS="$CATALINA_OPTS -server -Dfile.encoding=UTF-8 -Xms1G -Xmx8G -XX:+HeapDumpOnOutOfMemoryError"

Windows:

set CATALINA_OPTS=%CATALINA_OPTS% -server -Dfile.encoding=UTF-8 -Xms1G -Xmx8G -XX:+HeapDumpOnOutOfMemoryError


Warning

In order to run the text analysis pipelines that come with

Prod
Tomcat requires at least 8GB of memory. When running multiple text analysis pipelines in parallel, additional memory may be required.


HTTP Connector Configuration

Please make sure that the Tomcat HTTP Connector configuration in the Tomcat server.xml configuration file is using the following settings:

  • URIEncoding="UTF-8" Use UTF-8 as URI character encoding.

  • maxPostSize=-1 Disable the maximum size limit for POST requests.

Info

More detailed information about the Tomcat HTTP Connector can be found at Apache Tomcat HTTP Connector Reference

An example connector configuration in the server.xml configuration file could look like this:

<Connector port="8080" protocol="HTTP/1.1"
  URIEncoding="UTF-8"
  maxPostSize="-1"
  redirectPort="8443"
/>


Info

A complete server.xml configuration file with example values can be found in the appendix.


JNDI Resources

Tomcat needs to provide JNDI access to the database and to the file system. Please configure the following JNDI resources in the Tomcat server.xml configuration file:

  • jdbc/aifDB

<Resource name="jdbc/aifDB" factory="org.apache.tomcat.jdbc.pool.DataSourceFactory"
  auth="Container" type="javax.sql.DataSource" maxWait="5000" minIdle="0" initialSize="2"
  maxActive="15" maxIdle="15" driverClassName="com.mysql.jdbc.Driver"
  url="jdbc:mysql://localhost:3306/aif?serverTimezone=Europe/Berlin"
  username="user" password="password"/>


Warning

Please adjust the serverTimezone parameter in the jdbc connection url to your local timezone.


  • resource/aifHome

<Environment name="resource/aifHome" type="java.lang.String"
  value="_PATH_TO_AIF_HOME_" />
  • resource/aifSharedResources

<Environment name="resource/aifSharedResources" type="java.lang.String"
  value="_PATH_TO_AIF_SHARED_RESOURCES_" />
  • resource/aifWorkingDirectory

<Environment name="resource/aifWorkingDirectory" type="java.lang.String"
  value="_PATH_TO_AIF_WORKING_DIRECTORY_" />


Info

More detailed information about Tomcat JNDI resources can be found in the Tomcat JNDI Resources HOW-TO


MySQL Connector

Averbis is not allowed to ship the MySQL Connector/J for legal reasons. You can download the MySQL Connector/J for your MySQL database version at https://dev.mysql.com/downloads/connector/j/. Please provide the mysql-connector-java-VERSION.jar file within your Tomcat lib directory.

Logging

is using log4j2 for logging. Please put a log4j2.xml logging configuration file in your Tomcat lib directory to enable logging.


Info

A sample log4j2.xml logging configuration for log4j2 can be found in the appendix.

Installation Steps

The application is shipped as an archive which includes the following components:


Ahd
  • health-discovery.war

  • connector-manager.war

  • resources.zip

  • solr-distribution.zip


Apm
  • patent-monitor.war

  • connector-manager.war

  • resources.zip

  • solr-distribution.zip


Aid
  • information-discovery.war

  • connector-manager.war

  • resources.zip

  • solr-distribution.zip


The deployment overview of these components is shown in the figure below:

Extract Resources

Extract the resources.zip archive into the directory that is referenced in the JNDI resource resource/aifHome. The archive contains the configuration files health-discovery.properties.dist and connector-manager.properties.dist. Please remove the .dist extension of those files.


Info

If you are using different directories for resource/aifHome and resource/aifSharedResources please put health-discovery.properties and connector-manager.properties in resource/aifHome and all other files and directories in resource/aifSharedResources.


Application Configuration 

Prod
can be configured to your specific installation environment using property files. Most parts of the configuration can be used as shipped. The following parameters need to be configured manually:


connector-manager.properties

  • connector.base.dir contains the path to the connectorBaseDirectory. The connector manager needs read and write access to this directory

Start Solr Server

Prod
comes with a dedicated Apache Solr search platform that is contained in the solr-distribution.zip archive. It has been enhanced with Averbis specific functionality that is leveraged by
Prod
. Therefore it is not possible to use a stock Apache Solr instance alternatively.


Please extract the solr-distribution.zip archive into a directory named solr and run the following command to start the Solr server:

Linux:

./solr/server/bin/solr start -f -s ./solr/solr-home

Windows:

solr\server\bin\solr.cmd start -f -s ..\..\solr-home


Info

You can verify that Solr has been started successfully by opening the Solr web interface at http://localhost:8983/solr


Warning

Please make sure that the Solr server is available before proceeding with the next steps.

Deploy to Tomcat

Deploy connector-manager.war and health-discovery.war to your running Tomcat instance.

Ahd

Deploy connector-manager.war and health-discovery.war to your running Tomcat instance.


Apm

Deploy connector-manager.war andpatent-monitor.war to your running Tomcat instance.


Aid

Deploy connector-manager.war and information-discovery.war to your running Tomcat instance.


Info

You can verify a successful deployment by opening the the connector manager test connectivity page at http://localhost:8080/connector-manager/testConnectivity and the 

Prod

login page.


Ahd

URL for login: http://localhost:8080/health-discovery.


Apm

URL for login: http://localhost:8080/patent-monitor.


Aid

URL for login: http://localhost:8080/information-discovery.


Post-Installation Steps

After you install

Prod
please perform these steps:


Login to
Prod


Ahd

Open the

Prod
login page at http://localhost:8080/health-discovery and login as administrator with user name admin and password admin.


Apm

Open the

Prod
login page at http://localhost:8080/patent-monitoringand login as administrator with user name admin and password admin.


Aid

Open the

Prod
login page at http://localhost:8080/information-discoveryand login as administrator with user name admin and password admin.


Change the Administrator Password


Warning

Before using

Prod
in production it is highly recommended to change the administrator password.


Upgrade

Follow the guidelines in this chapter in order to do an upgrade of your existing

Prod
installation. Depending on your installation type please follow the instructions for upgrading a docker installation or a native installation.


Info

While this manual is the general guideline to follow for an upgrade of

Prod
, some version specific information may be additionally available in the 
Prod
release notes. Please use them as a complement to this guide.


Compatibility between Versions

Prod
promises various levels of backwards-compatibility between versions:

  • PATCH versions are always backwards-compatible

  • MINOR versions are always backwards-compatible

  • MAJOR versions may contain breaking changes

For further details about versioning see https://semver.org/

Upgrading a Docker Installation

Please execute the following steps to upgrade your Docker based 

Prod
 installation:

Stop
Prod

Stop the 

Prod
 docker containers by executing the following command from with the directory that contains the docker-compose.yml file:

Code Block
languagebash
sudo docker-compose stop

Update docker-compose.yml File

Create a backup copy of the existing docker-compose.yml file and replace it with the docker-compose.yml file that comes with the latest 

Prod
 version.

Tip

If you have made any manual changes to the docker-compose.yml file please make sure to include these in the new file version.


Start
Prod

Start the upgraded version of 

Prod
 by running the following command:

Code Block
languagebash
sudo docker-compose up -d

This completes the upgrade procedure of docker based 

Prod
 installations.

Upgrading a Native Installation

Preparation

Please stop your

Prod
instance before starting the upgrade:

Ahd
  • Undeploy health-discovery.war from Tomcat

  • Undeploy connector-manager.war from Tomcat

  • Stop Solr Server:


Apm
  • Undeploy patent-monitor.war from Tomcat

  • Undeploy connector-manager.war from Tomcat

  • Stop Solr Server:


Aid
  • Undeploy information-discovery.war from Tomcat

  • Undeploy connector-manager.war from Tomcat

  • Stop Solr Server:

       Linux:

  • solr/server/bin/solr stop -all -s ./solr/solr-home

    Windows:

    solr\server\bin\solr.cmd stop -all -s ..\..\solr-home

Backup

Before upgrading to a new

Prod
version it is highly recommended to make a backup first. If things go wrong, you can at least go back to the old version. Please make a backup of:


  • The Database

  • The solr-home directory

  • The aifHome directory

  • The aifSharedResources directory

  • The connectorBaseDirectory directory

Upgrading Resources and Configurations

Extract the resources.zip archive as described in section Extract Resources and replace existing files. Merge any changes that have been made to the health-discovery.properties and connector-manager.properties files to health-discovery.properties.dist and connector-manager.properties.dist. Then remove the .dist extension of health-discovery.properties.dist` and connector-manager.properties.dist.

Upgrading Solr

Extract the solr-distribution.zip archive into your existing solr directory and replace existing files. After that you can restart the Solr Server. See Start Solr Server

Deploy Upgrade to Tomcat

Deploy connector-manager.war and health-discovery.war to your running Tomcat instance. See Deploy to Tomcat

Appendix

server.xml

<?xml version='1.0' encoding='utf-8'?>
<!--
  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.
-->

<Server port="8005" shutdown="SHUTDOWN">
  <Listener className="org.apache.catalina.startup.VersionLoggerListener" />
  <Listener className="org.apache.catalina.core.AprLifecycleListener" SSLEngine="on" />
  <Listener className="org.apache.catalina.core.JasperListener" />
  <Listener className="org.apache.catalina.core.JreMemoryLeakPreventionListener" />
  <Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener" />
  <Listener className="org.apache.catalina.core.ThreadLocalLeakPreventionListener" />

  <GlobalNamingResources>
   <Environment description="Averbis Integration Framework resources directory"
     name="resource/aifHome" type="java.lang.String" value="/aifHome"/>

   <Environment description="Averbis Integration Framework resources directory"
     name="resource/aifSharedResources" type="java.lang.String" value="/aifSharedResources"/>

   <Environment description="Averbis Integration Framework resources directory"
     name="resource/aifWorkingDirectory" type="java.lang.String" value="/aifWorkingDirectory"/>

   <Resource auth="Container" driverClassName="com.mysql.jdbc.Driver"
     factory="org.apache.tomcat.jdbc.pool.DataSourceFactory"
     type="javax.sql.DataSource" maxActive="100" maxIdle="30"
     maxWait="30000" name="jdbc/aifDB" username="user" password="password"
     url="jdbc:mysql://localhost:3306/aif?serverTimezone=Europe/Berlin" />

   <Resource name="UserDatabase" auth="Container"
     type="org.apache.catalina.UserDatabase"
     description="User database that can be updated and saved"
     factory="org.apache.catalina.users.MemoryUserDatabaseFactory"
     pathname="conf/tomcat-users.xml" />
  </GlobalNamingResources>

  <Service name="Catalina">
    <Connector port="8080" protocol="HTTP/1.1" maxPostSize="-1"
      URIEncoding="UTF-8" redirectPort="8443" />
    <Connector port="8009" protocol="AJP/1.3" redirectPort="8443" />
    <Engine name="Catalina" defaultHost="localhost">
      <Realm className="org.apache.catalina.realm.LockOutRealm">
        <Realm className="org.apache.catalina.realm.UserDatabaseRealm"
          resourceName="UserDatabase"/>
      </Realm>
      <Host name="localhost"  appBase="webapps" unpackWARs="true" autoDeploy="true">
        <Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs"
          prefix="localhost_access_log." suffix=".txt" pattern="%h %l %u %t &quot;%r&quot; %s %b" />
      </Host>
    </Engine>
  </Service>
</Server>

log4j2.xml

<?xml version="1.0" encoding="UTF-8"?>
<Configuration status="INFO" strict="true" monitorInterval="30">
  <Properties>
    <Property name="tomcatBaseLogDir">/var/log/tomcat7</Property>
    <Property name="averbisLogSubDir">averbis-logs</Property>
    <Property name="filenameAll">${tomcatBaseLogDir}/${averbisLogSubDir}/all.log</Property>
    <Property name="filenameAif">${tomcatBaseLogDir}/${averbisLogSubDir}/aif.log</Property>
    <Property name="filenameMsi">${tomcatBaseLogDir}/${averbisLogSubDir}/msi.log</Property>
    <Property name="filenameAep">${tomcatBaseLogDir}/${averbisLogSubDir}/aep.log</Property>
    <Property name="filenameAmlp">${tomcatBaseLogDir}/${averbisLogSubDir}/amlp.log</Property>
    <Property name="filenameMoskito">${tomcatBaseLogDir}/${averbisLogSubDir}/moskito.log</Property>
    <Property name="filenameSwagger">${tomcatBaseLogDir}/${averbisLogSubDir}/swagger.log</Property>
    <Property name="filenameGcm">${tomcatBaseLogDir}/${averbisLogSubDir}/gcm.log</Property>
    <Property name="filenameAsp">${tomcatBaseLogDir}/${averbisLogSubDir}/asp.log</Property>
    <Property name="filenameSolr">${tomcatBaseLogDir}/${averbisLogSubDir}/solr.log</Property>
    <Property name="defaultPattern">%d %p %C %M %L >> %m%n</Property>
  </Properties>
  <Appenders>
    <Appender type="Console" name ="STDOUT">
      <Layout type="PatternLayout" pattern="${defaultPattern}"/>
    </Appender>
    <Appender type="File" name="fileAll" fileName="${filenameAll}">
      <Layout type="PatternLayout" pattern="${defaultPattern}"/>
    </Appender>
    <Appender type="File" name="fileAif" fileName="${filenameAif}">
      <Layout type="PatternLayout" pattern="${defaultPattern}"/>
    </Appender>
    <Appender type="File" name="fileMsi" fileName="${filenameMsi}">
      <Layout type="PatternLayout" pattern="${defaultPattern}"/>
    </Appender>
    <Appender type="File" name="fileAep" fileName="${filenameAep}">
      <Layout type="PatternLayout" pattern="${defaultPattern}"/>
    </Appender>
    <Appender type="File" name="fileAmlp" fileName="${filenameAmlp}">
      <Layout type="PatternLayout" pattern="${defaultPattern}"/>
    </Appender>
    <Appender type="File" name="fileMoskito" fileName="${filenameMoskito}">
      <Layout type="PatternLayout" pattern="${defaultPattern}"/>
    </Appender>
    <Appender type="File" name="fileSwagger" fileName="${filenameSwagger}">
      <Layout type="PatternLayout" pattern="${defaultPattern}"/>
    </Appender>
    <Appender type="File" name="fileGcm" fileName="${filenameGcm}">
      <Layout type="PatternLayout" pattern="${defaultPattern}"/>
    </Appender>
    <Appender type="File" name="fileSolr" fileName="${filenameSolr}">
      <Layout type="PatternLayout" pattern="${defaultPattern}"/>
    </Appender>
    <Appender type="File" name="fileAsp" fileName="${filenameAsp}">
      <Layout type="PatternLayout" pattern="${defaultPattern}"/>
    </Appender>
    </Appenders>
    <Loggers>
      <Logger name="de.averbis.integration" level="INFO" additivity="false">
        <AppenderRef ref="STDOUT" />
        <AppenderRef ref="fileAll"/>
        <AppenderRef ref="fileAif"/>
      </Logger>
      <Logger name="de.averbis.extraction" level="INFO" additivity="false">
        <AppenderRef ref="STDOUT" />
        <AppenderRef ref="fileAll"/>
        <AppenderRef ref="fileAep"/>
      </Logger>
      <Logger name="de.averbis.msi" level="WARN" additivity="false">
        <AppenderRef ref="STDOUT" />
        <AppenderRef ref="fileAll"/>
        <AppenderRef ref="fileMsi"/>
      </Logger>
      <Logger name="de.averbis.amlp.feature" level="WARN" additivity="false">
        <AppenderRef ref="STDOUT" />
        <AppenderRef ref="fileAll"/>
        <AppenderRef ref="fileAmlp"/>
      </Logger>
      <Logger name="net.anotheria" level="WARN" additivity="false">
        <AppenderRef ref="STDOUT" />
        <AppenderRef ref="fileAll"/>
        <AppenderRef ref="fileMoskito"/>
      </Logger>
      <Logger name="moskito" level="WARN" additivity="false">
        <AppenderRef ref="STDOUT" />
        <AppenderRef ref="fileAll"/>
        <AppenderRef ref="fileMoskito"/>
      </Logger>
      <Logger name="org.moskito" level="WARN" additivity="false">
        <AppenderRef ref="STDOUT" />
        <AppenderRef ref="fileAll"/>
        <AppenderRef ref="fileMoskito"/>
      </Logger>
      <Logger name="springfox" level="WARN" additivity="false">
        <AppenderRef ref="STDOUT" />
        <AppenderRef ref="fileAll"/>
        <AppenderRef ref="fileSwagger"/>
      </Logger>
      <Logger name="com.google" level="INFO" additivity="false">
        <AppenderRef ref="STDOUT" />
        <AppenderRef ref="fileAll"/>
        <AppenderRef ref="fileGcm"/>
      </Logger>
      <Logger name="org.apache.solr" level="INFO" additivity="false">
        <AppenderRef ref="STDOUT" />
        <AppenderRef ref="fileAll"/>
        <AppenderRef ref="fileSolr"/>
      </Logger>
      <Logger name="de.averbis.search" level="INFO" additivity="false">
        <AppenderRef ref="STDOUT" />
        <AppenderRef ref="fileAll"/>
        <AppenderRef ref="fileAsp"/>
      </Logger>
      <Logger name="de.averbis.textanalysis" level="INFO" additivity="false">
        <AppenderRef ref="STDOUT" />
        <AppenderRef ref="fileAll"/>
        <AppenderRef ref="fileAsp"/>
      </Logger>
      <Logger name="org.springframework.orm.jpa.JpaTransactionManager" level="ERROR" additivity="false">
        <AppenderRef ref="STDOUT" />
        <AppenderRef ref="fileAll"/>
      </Logger>
      <Root level="INFO">
        <AppenderRef ref="STDOUT" />
        <AppenderRef ref="fileAll"/>
      </Root>
    </Loggers>
</Configuration>