This is the administration system for VIPS. It relies on a PostgreSQL database.
The DDL files for this database are not in this repository, but can be obtained
by a request to NIBIO.
\ No newline at end of file
# VIPSLogic
Tor-Einar Skog, NIBIO
Last update: 2021-02-03
## Overview
VIPSLogic is the administration and business logic system of VIPS. Its main functionalities are:
* Batch running of models
* Caching/storing results from batch runs
* Database of field pest observations
* Management of organizations, users, farmer's fields, crops, pests and weather data sources
* Messaging / subscription services
* Web services to support VIPS's own public web pages and 3rd party clients
No models are deployed in VIPSLogic. It depends on web services from VIPSCore/VIPSCoreManager to run the models. However, for each model available in the VIPSCore/VIPSCoreManager system VIPSLogic needs a preprocessor to compile the model specific input data.
VIPSLogic is the source of data for most clients, including VIPSWeb, the standard public web page for a VIPS system.
![How VIPSLogic fits into the whole VIPS architecture](./docs/illustrations/VIPS_whole_architecture.png"All VIPS system parts")
## Technical description
### Environment that VIPSLogic is confirmed to work within
* Operating system: Ubuntu Linux >= 18.0.4
* Database: PostgreSQL >= 10 + PostGIS >= 2.4
* Java: OpenJDK >= 11
* Java EE application server: Wildfly >= 16
## License
VIPSLogic is licensed under the [NIBIO Open Source License](https://nibio.no/licenses), which is basically the [GNU Affero GPL v3 license](https://www.gnu.org/licenses/agpl-3.0.en.html).
Whether you deploy using Docker or Wildfly (or another JEE server), the context path of the app is always /VIPSLogic. However, the app is designed to be accessible at the root level. So you always need to proxy it behind e.g. Apache or Nginx. Here's an example vhost for Apache:
