OmiLab Integrated Virtual Environment
Olive is a Microservice Framework made available by OMiLAB.
The main idea behind is that the functionality of the system is composed by different (web-)services, running in their own processes and communicating with each other using standard network protocols. This approach brings the advantage of absolute technology independence. The only requirement for services is that they can communicate in HTTP using standardized JSON messages (OMiLAB Generic Interface).
More informations about the concepts behind the Olive Framework can be found in the Springer book: "OMiLAB: An Open Collaborative Environment for Modeling Method Engineering".
Use one of the following packages to easily deploy and test the Olive framework in your local machine:
|1.Olive Core Framework|
|1.1 Olive-Portable for Windows|| All-in-one portable package, |
only for Windows operating system
|1.2 Olive-Portable Docker|| All-in-one portable package |
using Docker Compose
|2.Project Specific Olive Framework|
|2.1 BIMERR||Core Olive Framework + KBSimulation + KPIDashboard + Celonis + ModelWiki||BIMERR_v1.3||OMILAB Olive portal||Olive_Portable_x86_win_v1.3_BIMERR.7z|
|2.2c CALIBRaiTE_v1.7||Core Olive Framework + KBSimulation + KPIDashboard + ModelWiki||CALIBRaiTE_v1.7||OMILAB Olive portal||Olive_Portable_x86_win_v1.7_CALIBRaiTE.7z|
|2.3 complAI||Core Olive Framework + Camunda Workflow Engine + Model Questionnaire + Model Signature||complAI_v1.2||OMILAB Olive portal||Olive_Portable_x86_win_v1.2_complAI.zip|
|2.4 Change2Twin||Core Olive Framework + Scene2Model + Annotation Service||Change2Twin_v1.0||OMILAB Olive portal||Olive_Portable_x86_win_v1.0_change2twin.7z|
|2.5 EIS 2020||Core Olive Framework + Twitter Post||EIS2020_1.0||OMILAB Olive portal||Olive_Portable_x86_win_v0.1._EIS2020.zip|
|3.Olive Based Applications|
|3.1 Hello World||Simple Olive based application that show the models in ADOxx and provide a service that can be called via ADOScript||HELLOWORLD_1.0||Hello World Documentation||Hello World|
|3.2 KPI Design||The Renovation process KPI design tool is an application build with ADOxx, a meta-modelling platform that allows to define your own meta-model and automatically generate the modelling environment for you accordingly it.||BIMERR 1.2_A1.5||Renovation Process KPI Design Tool||KPI Dashboard|
|3.3 Process Simulation and Verification||Allow to perform the simulation and formal verification of a process model||SIMULATION_1.0||Documentation||Simulation and Verification|
|3.4 Knowledge Based Process Simulation||The simulation of a renovation process complements the monitoring by providing a forward-looking simulation of the renovation process and hence estimates the expected duration and execution time.||BIMERR 1.0||Simulation of Renovation Process||Knowledge Based Model Simulation|
|3.5 Process Model Wiki||The Model Wiki web application allow to generate xWiki pages from any model in the ADOxx modelling environment and as soon as the pages are generated allow to import any existing comments in the wiki back to the model.||OLIVE2XWIKI_V0.1||Collaborative Reflection of Renovation Process||Model2Wiki|
Olive PSM Single Services
Here you can download the single components of the Olive PSM framework for a customized deployment:
|1.1 Project and Service Manager (PSM)||0.6.2||Project and Service Manager||PSM.war|
|1.2 Activity Logging Service||0.2.5||ActivityLoggingService||Logging.war|
|1.4 Role Service||0.3.1||RoleService||Role.war|
|2.1 Text Service||0.3.5||TextService||TextService.war|
|3.1 LDAP Configuration||0.1||LDAP Configuration||Olive_Ldap_Schema.ldif|
|4.1 Microservice Controller REST Interface||1.0||Microservice Controller Rest||Micro-Service-Controller-Rest.war|
All the components of the Olive platform are released as individual .war files. In order to deploy them, simply download every war file and copy in the webapp folder of your Tomcat application server. By default every component is configured to work with localhost adresses and recognize the other components deployed in the same application server.
Please be aware that every component require its own database and custom configuration, both detailed in the Documentation section of the component. Usually the schema for the DB creation and the istructions and material for the custom configuration are available inside the INSTALL folder of every component.
Java 8 is required in order to correctly execute the Olive framework.
Have a look at the Installation Manual for more details on the installation process.
Have a look at the Service Development Manual in order to learn how to create your own service.
Olive is released as Open Source and its code is available in the following GitLab repository: https://git.boc-group.eu/olive
Instructions for the building processes are explained in the DevOp section of the documentation for every component.
The source code of the Olive Microservice Controller is available in the following GitLab reporitory: https://git.boc-group.eu/adoxx/microservice-controller-rest
The following tables specify the detailed hardware/software requirement to get the Olive Framework up and running on your system.
|Minimum Hardware Requirements|
- Server-class computer
- Dual-Core processor
- 2048 MB RAM minimum, depending on service number and simultaneous users (3072 MB or more are recommended)
- 5 GB free disk space, depending on number services and space requirements for pictures, modelling toolkits (more recommended)
- 1 Network card and a static and world-wide routed IP address
|Minimum Software Requirements|
The portal should work pretty much work on any operating system that supports Tomcat, Java and any kind of SQL server.
Although the system is only well-tested in the following environment:
- Ubuntu 18
- JRE 8
- Tomcat 8.5
- MySQL 5.7
- Windows 10
- JRE 8
- Tomcat 8.5
- MySQL 5.7
|Minimum Skill Required|
The following skills are required in order to deploy correctly Olive:
- Basic MySQL administration skills
- Basic Tomcat administration skills
- Basic Java knowledge
In case of problems and for more informations contact us at firstname.lastname@example.org.