1. Deployment
2. Clone riccardo branch of medco-deployment in the three servers and install dependencies. `sh $ cd ~ $ git clone https://c4science.ch/source/medco-deployment.git $ git checkout riccardo $ bash ~/medco-deployment/resources/utility-scripts/ubuntu_prereqs_setup.sh ` Notice that:
   • in medco-deployment/docker-images/i2b2-database/Dockerfile we added the following commands to allow TCP/IP connection and avoid an error during the data loading phase. `
   • hack postgresql docker image to allow transmart loading (allow TCP/IP connections during init phase) RUN sed -i "s/listen_addresses=''/listen_addresses='*'/g" /usr/local/bin/docker-entrypoint.sh `
   • medco-deployment/docker-images/i2b2-web/Dockerfile is set to swith to the fork/1.22.8-medco_dev branch of the shrine webclient. ` SHRINE_VERSION="fork/1.22.8-medco_dev" `
3. Follow the steps described in the section Deploying MedCo on Different Servers \(For Development\) to create the CA certificate and also to build and run the dockers.
4. Copy the generated group.toml to shrine-webclient/src/main/html/js-i2b2/cells/plugins/MedCo/gropu.toml (and push it on fork/1.22.8-medco_dev branch) so that the webclient can use it to compute the aggregate key.
5. Load the databases by executing the following script from only one server: ` sh $ ./loadData-3nodes-iccluster.sh ` Ask Joao for details of where to find this script.

ATTENTION: if the log file of the i2b2-server container returns an "insufficient permissions" error for table i2b2medco.medco_project_user_budget or i2b2medco.medco_hash_noise after a query is performed, manually grant all the privileges for the users "i2b2medco" and "postgres" in both tables.