Define the process on how new Partners can deploy ther partner recommender in a hosted environment #5
Description
The PartnerWizard solves the problem of creating a partner recommender without programming. The source code is automatically generated from the configuration and available for download.
However, the question remains where the partner recommender can be deployed in case an institution does not have a proper environment or does not want to invest a huge effort. An ad-hoc deployment on the stable federated recommender might not be a good solution, due to potential attacks and fraudulent behaviour.
So we need to define a process involving technical and manual efforts on how a partner recommender can be deployed. The process could involve
- deploying the Partner Recommender using a standard tomcat on their own environment
- deploying the Partner Recommender using some commercial hosting service (like the Amazon Cloud)
- deploying the Partner Recommender on the EEXCESS infrastructure (sandbox, devleopment system etc.)
This process should be described after the Maven artefact has been created.