PatientView Server Configuration
Patientview runs on tomcat and is written in java. Currently it uses java 8 and runs on tomcat 9.
RedHat 6 didn't support tomcat 7 so the servers have run using the EPEL release however when an issue occurred with the latest release version we were forced to run a source code version temporarily until the fixed version of tomcat came out. The server is split between two instances of tomcat. One run from source located in /opt/tomcat-importer
(tomcat 7.0.52) which runs the importer tasks and handles the rabbitmq queue of messages and the other which runs the main site and api. There is an nginx front end that routes traffic to the correct local ports. This has now changed to use two copies of tomcat 9.0.xxx located in /opt and /opt/apache-importer
folders and linked to a standard path as detailed below.
EPEL Setup - this has now been superceded
Patientview frontend is located in /opt/patientview
Patientview api and migration is located in /opt/lib/tomcat/webapps
Current Source configuration
Staging/Test
/opt/tomcat
(link to /opt/apache-tomcat-9.0.xxx
) is where the code is stored with the sub folder /opt/tomcat/webapps
containing the api
, manager
and migration
code.
/opt/patientview
contains the main frontend
code.
/opt/tomcat-importer
(link to /opt/apache-importer/apache-tomcat-7.0.52
) with /opt/tomcat-importer/webapps
containing the importer
code
Live
/root/apache-tomcat-9.0.xxx
contains the source code with the subfolder webapps containing the api
and {{migration}} code.
/opt/patieintview
contains the main frontend
code.
/opt/tomcat-importer
(link to /opt/apache-importer/apache-tomcat-9.0.xxx
) with /opt/tomcat-importer/webapps
containing the importer
code
ls /opt drwxr-xr-x. 3 tomcat-importer tomcat 4096 Jun 11 06:51 apache-importer drwxr-xr-x. 9 tomcat tomcat 4096 Jun 9 10:28 apache-tomcat-9.0.36 dlrwxrwxrwx. 1 tomcat tomcat 21 Jun 9 10:30 tomcat -> apache-tomcat-9.0.36/ lrwxrwxrwx. 1 root root 42 Jul 8 15:58 tomcat-importer -> /opt/apache-importer/apache-tomcat-9.0.36/