The Unipoole Service is the intelligence and processing engine of all data communication between the Unipoole Client and Sakai. This is a deployable project.
Unipoole Service Architecture
Highlevel Overview
This diagram illustrates on a very high level how unipoole, unipoole clients, and sakai fit together. A unipoole server will host the Unipoole-Service, and the Admin tool. The admin tool communicates with the Unipoole-Service using REST calls. When a client is created using the Admin tool, the bulk of the work is actually done on the Unipoole-Service (initiated with a REST call from the Admin Tool). Unipoole-Service communicates to a single sakai server via SOAP Webservice calls. (take note there is NOT a load balancer between Unipool-Service and Sakai) When a student connects to sakai the user will connect to a Load Balancer which in turn works with a selected sakai instance. When a student uses the Unipoole client (desktop or mobile) the client connects directly to the Unipoole Service using REST calls. The unipoole client never directly communicates with Sakai.
git clone https://github.com/Unipoole/unipoole-service.git
cd unipoole-service
mvn clean installIf the Maven build is successful there will be a unipoole-service.war archive in the target folder of the build. This archive can be deployed to your Tomcat instance.
Please note: If you deploy to more then one instance only one instance can have the property creator.content.manage.modules set to true.