root/his/trunk/README.txt

Revision 2594, 5.4 kB (checked in by wouter, 7 months ago)

Last part of migration from exist to sql for healthdocuments.

Line 
1 HIS is a hospital information system currently in development.
2
3 For more information see http://www.joiningtracks.org
4
5 --------------------------------------------------------------------------------
6 Environment setup
7 --------------------------------------------------------------------------------
8
9 1. Installing MySQL 5.0.x.
10
11    - Download MySQL 5.0.x from http://dev.mysql.com/downloads/mysql/5.0.html#downloads
12    - Install MySQL according to the installation instructions.
13
14   Development
15    - Create a new database called 'build_his'.
16      CREATE DATABASE build_his DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci;
17    - Create the MySQL user 'build'
18    - Grant user 'build' access to the 'build_his' database
19      GRANT ALL ON build_his.* to 'build'@'localhost' IDENTIFIED BY 'build';
20      GRANT ALL ON build_his.* to 'build'@'%' IDENTIFIED BY 'build';
21
22    - Create a new database called 'build_questionnaire'.
23      CREATE DATABASE build_questionnaire DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci;
24    - Grant user 'build' access to the 'build_questionnaire' database
25      GRANT ALL ON build_questionnaire.* to 'build'@'localhost' IDENTIFIED BY 'build';
26      GRANT ALL ON build_questionnaire.* to 'build'@'%' IDENTIFIED BY 'build';
27
28    - Change 'data/src/test/resources/test.properties'
29      with the right database connection parameters. For an overview of the parameters, see the previous item.
30      The following properties need to be changed (default value is displayed):
31         jdbc.url=jdbc:mysql://localhost:3306/his?useUnicode=true&characterEncoding=utf8&characterSetResults=utf8
32         jdbc.username=build
33         jdbc.password=build
34
35    - Change 'configuration/default/tomcat/conf/his.properties'
36      with the right database connection parameters. For an overview of the parameters, see the previous item.
37      The following properties need to be changed (default value is displayed):
38         jdbc.url=jdbc:mysql://localhost:3306/his?useUnicode=true&characterEncoding=utf8&characterSetResults=utf8
39         jdbc.username=build
40         jdbc.password=build
41
42   Production / local testing
43    - Create a new database called 'his'.
44      CREATE DATABASE his DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci;
45    - Create the MySQL user 'his-user'
46    - Grant users 'build' and 'his-user' access to the 'his' database
47      GRANT ALL ON his.* to 'his-user'@'localhost' IDENTIFIED BY 'password';
48      GRANT ALL ON his.* to 'his-user'@'%' IDENTIFIED BY 'password';
49      GRANT ALL ON his.* to 'build'@'localhost' IDENTIFIED BY 'build';
50      GRANT ALL ON his.* to 'build'@'%' IDENTIFIED BY 'build';
51
52    - Change 'configuration/production/tomcat/conf/his.properties'
53      with the right database connection parameters.
54      The following properties need to be changed (default value is displayed):
55         jdbc.url=jdbc:mysql://localhost:3306/his?useUnicode=true&characterEncoding=utf8&characterSetResults=utf8
56         jdbc.username=his-user
57         jdbc.password=password
58
59  
60 2. Installing LDAP
61
62    So to fully test the system, you will have to setup an LDAP directory
63    and configure his.properties file accordingly to match your setup.
64    Installing LDAP is not covered here. We currently use Apple Open Directory in the production environment.
65
66    - Change 'data/src/test/resources/test.properties'
67             'configuration/default/tomcat/conf/his.properties'
68             'configuration/production/tomcat/conf/his.properties'
69      to contain the right LDAP connection parameters.
70         ldap.url=ldap://localhost:389
71         ldap.baseDn=dc=kantoor,dc=obesitaskliniek,dc=nl
72         ldap.userDn=uid=helpdesk,cn=users,dc=kantoor,dc=obesitaskliniek,dc=nl
73         ldap.password=password
74
75 3. Installing the certificate for the communication with the Vecozo webservice.
76
77     We use one of the Vecozo webservices to verify and support the creation of new patients in the system.
78     To make a secure connection to the Vecozo webservice we need to do some configuration.
79
80     - Open the 'vecozo/src/main/resources/vecozo-client.properties'
81     Change the following properties to:
82     webservice.endpoint.uri=https://uri.to.the.secure.webservice/webservice/
83     truststore.location=/location/to/certificate.extention
84     truststore.password=thepasswordofthecertificate
85
86     Make sure you use secured http (https://) connection instead of a regular http connection (http://)
87
88 --------------------------------------------------------------------------------
89 Running HIS
90 --------------------------------------------------------------------------------
91
92 * Deployment / Development mode
93
94         You have to specify a Java System property called "config.directory" and give
95         it the value of the directory on the filesystem where the configuration files
96         are located. Typically, this is done by using the -D option on the
97         commandline. When using the StartSite convenience runner, this property is set
98         to the development configuration directory for you automatically.
99
100         There are three means to configure Wickets configuration mode and they are
101         tested in the order given.
102
103        1) A system property: -Dwicket.configuration
104        2) servlet specific <init-param>
105        3) context specific <context-param>
106
107         The value might be either "development" (reloading when templates change)
108         or "deployment". If no configuration is found, "development" is the default.
109
110         ~
111
112         By default, HIS internal frontend will run in "deployment" mode, as configured
113         via option 2, in web.xml. The StartSite runner sets a system property.
Note: See TracBrowser for help on using the browser.