Installing OpenHMIS

General Notes:

This code base is expected to be built using Maven, and deployed to Tomcat.
We are using MySQL as a data store.
Although several core developers are using Eclipse, this is not a requirement to contribute.

Create a local build:

The instructions below explain how to set up a development environment capable of running the API endpoints. This section assumes you have already used git to download a local copy of the code base.

In order for those endpoints to function correctly, you must also create a local copy of the schema.

Install JDK 1.7.x

On Debian GNU/Linux 'testing' dist as of 2015-07-30, sudo apt-get install openjdk-7-jre openjdk-7-jdk should work.
Install Maven (3.x).

On Debian GNU/Linux 'testing' dist as of 2015-07-30: sudo apt-get install maven.
Install Tomcat 7.x. Note that there may be a more recent version of Tomcat, but as of 2015-06-22 Maven plugins do not appear to exist beyond Tomcat 7.

On Debian GNU/Linux 'testing' dist as of 2015-07-30, some combination of sudo apt-get install libtomcat7-java tomcat7 tomcat7-admin tomcat7-user tomcat7-common tomcat7-docs tomcat7-examples should do the trick. If you install the Tomcat server correctly, you can visit http://localhost:8080/ and see a message saying "It works" and giving details about Tomcat configuration paths, etc.
Install MySQL 5.x.

(Most Debian GNU/Linux systems already have the mysql-server and mysql-client packages installed.)

Create a Tomcat admin by editing <TOMCAT7_PATH>/conf/tomcat-users.xml.

    <tomcat-users>
            <role rolename="admin-gui"/>
            <role rolename="admin-script"/>
            <role rolename="manager-gui"/>
            <!-- We don't need 'manager-jmx' and 'manager-status' 
                 roles for this application, but feel free to
                 add them if you need them for other reasons. -->
            <role rolename="manager-script"/>
            <user username="admin" password="password" 
                  roles="admin-gui,admin-script,manager-gui,manager-script" />
    </tomcat-users>

On Debian GNU/Linux, TOMCAT7_PATH above is usually /var/lib/tomcat7. This path is also known as CATALINA_BASE in Tomcat-speak, and the corresponding CATALINA_HOME would be /usr/share/tomcat7.

Restart Tomcat

On many Unix-like systems, this will work:
```
    $> sudo service tomcat7 stop
    $> sudo service tomcat7 start
```
TODO 2016-07-13: The above might need to be updated for systemd-style shutdown and startup. It would be something like systemctl stop tomcat7.service; systemctl start tomcat7.service probably.

You could also try doing it manually:
```
    $> cd <CATALINA_HOME>   # (e.g., /usr/share/tomcat7)
    $> bin/shutdown.sh
    $> bin/startup.sh
```

Update Maven's settings by editing <MAVEN_PATH>/conf/settings.xml so that Maven will be able to use the Tomcat user in step 3.

On Debian GNU/Linux, MAVEN_PATH is /usr/share/maven.

The username and password must match those set in step 3. The ID must be TomcatServer.

    <settings ...>
            <servers>
                    <server>
                            <id>TomcatServer</id>
                            <username>admin</username>
                            <password>password</password>
                    </server>
            </servers>
    </settings>

Create the schema:

Database migrations are performed using Flyway. Note: you do not need to install anything for this to work. Flyway is automatically loaded and used by Maven.

Using your tool of choice, create an empty MySQL schema, and create a user with access to it.

The name of your schema is up to you; in this example we use openhmis. The username and password are likewise up to you; here we use openhmis_user and openhmis_password.

    $> mysql -u root -p
    (...enter database admin password...)
    mysql> create database openhmis;
    mysql> create user openhmis_user@localhost identified by "openhmis_password";
    mysql> grant ALL on openhmis.* to openhmis_user@localhost identified by "openhmis_password";

Create a local src/config/flyway.properties file with your database connection information

The schema name, username, and password entered in this file must match those created in the above step
```
    $> cp src/config/flyway.properties.example src/config/flyway.properties
    $> vi src/config/flyway.properties
```
To initialize and update the schema, run the following command in the top-level directory (the one containing the pom.xml file):
```
    $> mvn clean compile flyway:migrate
```
NOTE: If the above command gets an error that looks something like this...
```
    [ERROR] Failed to execute goal                          \
            org.flywaydb:flyway-maven-plugin:3.2.1:migrate  \
            (default-cli) on project api:                   \
            org.flywaydb.core.api.FlywayException:          \
            Validate failed. Migration Checksum mismatch for migration 010
```
...then you might need to run mvn flyway:repair and retry. (Flyway 3.0 set validateOnMigrate to true by default, as explained here, though Flyway 4.0 supposedly has a better fix so maybe you won't run into this problem anyway.)
Create the dev.properties file.
```
    $> cp src/main/resources/dev.properties.example src/main/resources/dev.properties
```
Open the new file and enter the database username and password that you created in steps 1 and 2. Note that the file has default values for client id and client key. Development deployments can just use those, but production instances will need to get new values; see the authentication documentation for more.

Import sample data (or real data, if you have some):

        mysql -u openhmis_user -p openhmis < src/main/resources/db/data/DATA.sql

Create your first admin user:

If you are setting up the OpenHMIS server for the first time, you'll see that you have a TMP_USER table in your database. If you don't, then do the following:

    $ mysql -u __YOUR_USER__ -p __YOUR_SCHEMA__
    Enter password: __YOUR_PASSWORD__
    
    mysql> \. src/main/resources/db/migration/V028__CREATE_TMP_USER.sql

Then, create an admin user with all permissions:

    mysql> insert into TMP_USER (externalID, canRead, canWrite, canAdmin, dateCreated, dateUpdated) values ('__YOUR_GMAIL_EMAIL__', 1, 1, 1, NOW(), NOW());

Note that the externalID column expects some identification from another external account. We generally expect this API to be set up with Google as the external authenticating party, in which case you would use a Google email address for the externalID, but you could set up OAuth with any other external authentication authority, too. See the authentication documentation for more.

Run the web service:

Ensure that Tomcat is running (generally you can do this by going to http://localhost:8080)
Using a Command Line Interface, navigate to the root directory of this code base. It should be the one containing pom.xml

Deploy using Maven if this is the first time you've ever deployed this code:

    $> mvn tomcat7:deploy

But if you have previously deployed this code with any tool, then you should instead redeploy using Maven:

    $> mvn tomcat7:redeploy

If successful, the output will end with a message similar to the example below:

    [INFO] tomcatManager status code:200, ReasonPhrase:OK
    [INFO] OK - Deployed application at context path /openhmis
    [INFO] ------------------------------------------------------------------------
    [INFO] BUILD SUCCESS
    [INFO] ------------------------------------------------------------------------
    [INFO] Total time: 4.488 s
    [INFO] Finished at: 2015-06-22T14:43:19-04:00
    [INFO] Final Memory: 20M/165M
    [INFO] ------------------------------------------------------------------------

If your web service is properly configured, http://localhost:8080/openhmis/api/v3/healthcheck should display "Your service is working with version <version>."
If the authentication has been set up successfully, then http://localhost:8080/openhmis/api/v3/healthcheck/authentication should display "You have a valid authentication token."
Once authentication works, if the schema is properly set up, http://localhost:8080/openhmis/api/v3/clients should yield a valid XML object.
You can check that regular event logging is happening in CATALINA_BASE/logs/catalina.out (e.g., /var/lib/tomcat7/logs/catalina.out). The default log level provides an informational log entry for every API endpoint request, in the following format:
- Authorizatation events start with AUTHN.
- A GET/PUT/DELETE of one object: GET|PUT|DELETE <endpoint>/<id>
- A GET that fetches multiple objects: GET <endpoint> (<number> results)
- A POST that creates a new object: POST <endpoint> (new id: <id>)

Continuous integration:

To set up continuous integration for a fork of this repository, follow the instructions at Travis. We've already added the .travis.yml file to this repo, so all you need to do is turn on CI for your fork, as described on that page.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

INSTALL.md

INSTALL.md

Installing OpenHMIS

General Notes:

Create a local build:

Create the schema:

Import sample data (or real data, if you have some):

Create your first admin user:

Run the web service:

Continuous integration:

Further reading, if this is a production server:

Files

INSTALL.md

Latest commit

History

INSTALL.md

File metadata and controls

Installing OpenHMIS

General Notes:

Create a local build:

Create the schema:

Import sample data (or real data, if you have some):

Create your first admin user:

Run the web service:

Continuous integration:

Further reading, if this is a production server: