Install Proxy for Kudu

This page explains how to install the Proxy in conjunction with Kudu.

Requirements

1. Proxy needs to be run on the connectathon intranet
2. Kudu may be on the extranet
3. Install Jboss version 4.2.x (Jboss Installation Instructions) and Mirth (see Mirth Installation Instructions) 1.7.x on Proxy System

On the Kudu system

• Install Mirth2EVSDaemon on Kudu
• Make sure that you have the directories mirth/template and mirth/channels in data directory of the event.

cd ~/webapp/data/NAME_OF_EVENT
mkdir mirth
mkdir mirth/template
mkdir mirth/channels
sudo chown -R www-data:www-data mirth

• Install Mirth Channel template: the template file is named : [ByPassForEVSTemplate.xml] and shall be stored at the following location on the Kudu system:

 ~/webapp/data/NAME_OF_EVENT/mirth/template

• Configure postgresql to allow user "gazelle" from the proxy system to access the kudu database (the one used for the current event). You need to have a similar line into your pg_hba.conf file.

host    DBNAME gazelle  IP_PROXY_SYSTEM/1      trust

On the Proxy system

• Install the Mirth API project in the opt directory of the Proxy system (follow the MirthAPI Tutorial on the Mirth page)
• Create a directory channels_data where all the channels to import on the Mirth server will be stored
• Script to upload the channels from the Kudu system:

cd MirthAPI
mkdir channels_data
...
... 
wget "http://KUDU_SYSTEM_NAME/NAME_OF_EVENT/mirth_channels_admin.php?submit=Create%20All%20Channels"
rm channels_data/*.xml
scp "KUDU_SYSTEM_NAME:/home/USERNAME/webapp/data/NAME_OF_EVENT/mirth/channels/*.xml" channels_data
cd dist 
java -jar MirthAPI.jar deleteAll connectionConfig.xml 
java -jar MirthAPI.jar importChannels connectionConfig.xml ../channels_data
java -jar MirthAPI.jar deployAll connectionConfig.xml 
java -jar MirthAPI.jar startAll connectionConfig.xml

You should now have all your channels deployed and started on the Proxy system.