By Erick Otenyo, Alibaba Cloud Tech Share Author. Tech Share is Alibaba Cloud's incentive program to encourage the sharing of technical knowledge and best practices within the cloud community.
DHIS2 is a tool for collection, validation, analysis, and presentation of aggregate and patient-based statistical data, tailored to integrated health information management activities. It is a generic tool rather than a pre-configured database application, with an open meta-data model and a flexible user interface that allows the user to design the contents of a specific information system without the need for programming.
The DHIS2 database is designed ground-up with flexibility in mind. Data structures such as data elements, organisation units, forms and user roles can be defined completely freely through the application user interface. This makes it possible to adapt the system to a multitude of locale contexts and use cases that require routine data capture and analysis. This has allowed for DHIS2 to serve as management system in different domains such as logistics, labs and finance.
DHIS2 is an open source software under the BSD licence and thus can be obtained freely and run on any platform with a Java Runtime Environment installed.
The following are the key features and purpose of DHIS2
A typical informaton cycle in a DHIS2 system icludes:
In this tutorial, we will be covering on how to get DHIS2 up and running on an Alibaba Cloud Elastic Compute Service (ECS) Ubuntu 16.04 instance.
Before we deploy our DHIS2 instance, we need to fulfill the following requirements. We need to set up an Alibaba Cloud Elastic Compute Service (ECS) Linux server (Ubuntu 16.04) with atleast 4GB of RAM and basic configurations. You should also allocate administrator (sudo) privileges to a non-root user.
You can refer to this guide for setting up your Alibaba Cloud ECS instance. If you don't have an Alibaba Cloud account, you can sign up for free and enjoy $300 worth in Free Trial.
To deploy DHIS2 on our server, we will first need to install a few requirements and configure the Java Runtime Environment neccessary for DHIS2 to run.
We will need to install a Postgres/PostGIS database and thereafter install Java and setup the configurations.
It may be important to match the server timezone with the location which the DHIS2 server will be covering. The default time zone on the ECS instance may not correspond to the time zone of your DHIS2 location. To reconfigure the timezone, invoke the command below and follow the instructions displayed:
sudo dpkg-reconfigure tzdataThe DHIS2 server should not be run as a privileged user such as root. Therefore create a new dedicated user for running DHIS by invoking:
sudo useradd -d /home/dhis -m dhis -s /bin/falseThen set the password for the account by invoking:
sudo passwd dhisMake sure you set a strong password
Create a suitable directory for the DHIS2 configuration files that will also be used for apps in DHIS2, files and log files
sudo mkdir /home/dhis/configSet ownership of the directory to 'dhis' user created above
sudo chown dhis:dhis /home/dhis/configInstall PostgreSQL and the PostGIS extension by invoking:
sudo apt-get install postgresql-9.5 postgresql-contrib-9.5 postgresql-9.5-postgis-2.2Create a non-privileged PostgreSQL user called 'dhis' by invoking:
sudo -u postgres createuser -SDRP dhisGive a password for the new PostgreSQL user when prompted.
Create a database that will be used by the DHIS2 instance by invoking:
sudo -u postgres createdb -O dhis dhis2The PostGIS extension is needed for several GIS/mapping features to work. Create the PostGIS extension by invoking:
sudo -u postgres psql -c "create extension postgis;" dhis2PostgreSQL performance tuning is necesarry to achieve a high performing system in a production environment. Note this is not neccessary in terms of getting DHIS2 to run.
Open the postgresql.conf file for editing:
sudo nano /etc/postgresql/9.5/main/postgresql.confSet the following properties:
max_connections = 200
shared_buffers = 3200MB
work_mem = 20MB
maintenance_work_mem = 512MB
effective_cache_size = 8000MB
checkpoint_completion_target = 0.8
synchronous_commit = off
wal_writer_delay = 10000msFor an indepth explanation of the above properties, please refer the DHIS2 docs
The database connection information is provided to DHIS2 through a configuration file called dhis.conf. Create this file and save it in the configuration directory we created in Step 3:
sudo -u dhis nano /home/dhis/config/dhis.confInsert following lines to the file (update PostgreSQL dhis user password according what you set above):
# Hibernate SQL dialect
connection.dialect = org.hibernate.dialect.PostgreSQLDialect
# JDBC driver class
connection.driver_class = org.postgresql.Driver
# Database connection URL
connection.url = jdbc:postgresql:dhis2
# Database username
connection.username = dhis
# Database password
connection.password =xxxx
# Database schema behavior, can be validate, update, create, create-drop
connection.schema = update
# Encryption password (sensitive)
encryption.password = xxxxOracle Java will need to be installed manually. Create a directory to install Java:
mkdir /usr/java/cd /usr/java/Next we need to download oracle java from the Java download page.
Obtain the correct download link with 'Linux x64' from the above link and replace http://oracle-java-download-link in the command below with that link. It should look something like http://javadl.oracle.com/webapps/download/AutoDL?BundleId=235717_2787e4a523244c269598db4e85c51e0c
wget -O java-linux-x64.tar.gz http://oracle-java-download-linkAfter downloading, untar by invoking the following:
tar zxvf java-linux-x64.tar.gzTo install the Tomcat servlet container we will utilize the Tomcat user package. This lets us easily create a new Tomcat instance. Install the package by invoking:
sudo apt-get install tomcat7-userTo create a Tomcat instance for DHIS2 move to the dhis folder created earlier:
cd /home/dhis/Create Tomcat instance:
sudo tomcat7-instance-create tomcat-dhisSet ownership of the created folder to dhis user
sudo chown -R dhis:dhis /home/dhis/tomcat-dhis/Edit setenv.sh:
sudo nano /home/dhis/tomcat-dhis/bin/setenv.shAdd the following lines to the bottom of the file:
Please note that jre1.8.0_191 directory as below may change according to oracle java version downloaded.
export JAVA_HOME='/usr/java/jre1.8.0_191/'
export JAVA_OPTS='-Xmx2000m -Xms1000m'
export DHIS2_HOME='/home/dhis/config'The next step is to now download the DHIS2 WAR file and place it into the webapps directory of Tomcat.
You can download the DHIS2 version 2.30 WAR release as below (replace 2.30 with your preferred version if necessary):
wget https://s3-eu-west-1.amazonaws.com/releases.dhis2.org/2.30/dhis.warMove the WAR file into the Tomcat webapps directory. We want to call the WAR file ROOT.war in order to make it available at localhost directly without a context path:
sudo mv dhis.war tomcat-dhis/webapps/ROOT.warDHIS2 should never be run as a privileged user, so edit the startup.sh to use the dhis user we created earlier:
sudo nano /home/dhis/tomcat-dhis/bin/startup.shReplace everything in the file with the following lines:
#!/bin/sh
set -e
if [ "$(id -u)" -eq "0" ]; then
echo "This script must NOT be run as root" 1>&2
exit 1
fi
export CATALINA_BASE="/home/dhis/tomcat-dhis"
/usr/share/tomcat7/bin/startup.sh
echo "Tomcat started"DHIS2 can now be started by invoking:
sudo -u dhis tomcat-dhis/bin/startup.shTo monitor the behavior of Tomcat, the log is the primary source of information. The log can be viewed with the following command:
tail -f tomcat-dhis/logs/catalina.outAssuming that the WAR file is called ROOT.war, you can now access your DHIS2 instance at:
http://your.server.ip.address:8080
The Default login details are:
Username: adminPassword: districtDHIS2 can be stopped by invoking:
sudo -u dhis tomcat-dhis/bin/shutdown.shIn certain situations the server might reboot unexpectedly. It is preferable to have Tomcat start automatically when the server starts. To achieve that the first step is to create init scripts.
Create init scripts:
sudo nano tomcatEnter the following lines:
#!/bin/sh
#Tomcat init script
HOME=/home/dhis/tomcat-dhis/bin
case $1 in
start)
sudo -u dhis ${HOME}/startup.sh
;;
stop)
sudo -u dhis ${HOME}/shutdown.sh
;;
restart)
sudo -u dhis ${HOME}/shutdown.sh
sleep 5
sudo -u dhis ${HOME}/startup.sh
;;
esac
exit 0Move the script to the init script directory and make it executable by invoking:
sudo mv tomcat /etc/init.dsudo chmod +x /etc/init.d/tomcatNext make sure the tomcat init script will be invoked during system startup and shutdown:
sudo /usr/sbin/update-rc.d -f tomcat defaults 81Tomcat will now be started at system startup and stopped at system shutdown. If you later need to revert this you can replace defaults with remove and invoke the above commands again
Hooray ! If you were able to follow this tutorial up to this point, your DHIS2 instance should be up and running on your Alibaba Cloud Elastic Compute Service (ECS) Instance. We have done a basic setup to get us started with our DHIS2 server, but you might need further customization for DHIS2 to work as per your use case, mainly from the admin user interface. For that and more, you can refer to the official documentantion of DHIS2, which covers all the DHIS2 platform instructions in detail.
MVP #FridayFive: Alibaba Cloud IoT, Cybersecurity, and Blockchain
2,605 posts | 747 followers
FollowAlibaba Clouder - December 20, 2019
Nick - May 7, 2019
Alibaba Clouder - July 18, 2019
Nick - May 6, 2019
Nick - May 10, 2019
Nick - May 17, 2019
2,605 posts | 747 followers
Follow
ECS(Elastic Compute Service)
Elastic and secure virtual cloud servers to cater all your cloud hosting needs.
Learn More
OSS(Object Storage Service)
An encrypted and secure cloud storage service which stores, processes and accesses massive amounts of data from anywhere in the world
Learn MoreLearn More
More Posts by Alibaba Clouder