Changes between Version 4 and Version 5 of PetriNetSagas
- Timestamp:
- Feb 7, 2021, 8:10:27 PM (4 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
PetriNetSagas
v4 v5 19 19 20 20 The setup assumes a Linux environment. If you work under macOS or Windows details might differ from the here presented instructions. 21 It is recommended to prepare a local installation of Docker and docker-compose, as it greatly eases setup of the required service components. 21 It is highly recommended to prepare a local installation of Docker and docker-compose, as it greatly eases setup of the required service components for the microservice infrastructure. 22 It is however not necessary to do so on the same machine the (sample) code is to be run. 22 23 Note, that under Windows Docker needs to run in Linux-image compatible mode, as some key images are only available for the Linux platform. 23 24 24 25 A working Java JDK (e.g. OpenJDK) needs to be present with support for at least Java 11! 26 The utility `curl` is also recommended to test things out. 25 27 26 28 The deployment requires a microservice environment (that can be supplied by just one machine for testing purposes) with the following applications: … … 32 34 33 35 If you do not use the Docker-based setup please refer to the respective projects websites on information on how to set these up. 34 To set up all the dependencies it is sufficient to navigate to the folder "service_environment" and issue the command {{{docker-compose up -d}}}. 36 37 Download the Example package (BookStoreExample.zip) (see above) 38 To set up all the dependencies it is sufficient to navigate to the folder "docker" and issue the command {{{docker-compose up -d}}} from within that directory. 39 If you have installed docker on another machine, make sure direkt connection between your machine and the docker machine is possible, and ports `2181`, `9092`, `3306`, `8099` and `9411` are not firewalled. 35 40 Depending on your local setup you might need to supply elevated permissions (e.g. by using {{{sudo}}}) to the docker-compose command. 36 41 The service infrastructure can be tore down again with the command {{{docker-compose down}}} from within the same directory.