documentation:software:webapi:setup
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| documentation:software:webapi:setup [2016/08/23 18:48] – jhardin | documentation:software:webapi:setup [2018/04/23 19:11] (current) – lee | ||
|---|---|---|---|
| Line 118: | Line 118: | ||
| Open command prompt, go to WebAPI folder, type | Open command prompt, go to WebAPI folder, type | ||
| - | set JAVA_HOME=C:/ | + | |
| //Make sure you point to a JDK, not a JRE. It is probably a good idea to stick to the same Java version that is running Tomcat// | //Make sure you point to a JDK, not a JRE. It is probably a good idea to stick to the same Java version that is running Tomcat// | ||
| - | mvn clean package -s / | + | |
| This will create the file WebAPI.war in the target subfolder. | This will create the file WebAPI.war in the target subfolder. | ||
| Line 136: | Line 136: | ||
| Reading the Tomcat logs, the following output should appear indicating that the tables have been created (in this example, we see an Oracle output): | Reading the Tomcat logs, the following output should appear indicating that the tables have been created (in this example, we see an Oracle output): | ||
| - | 2016-02-24 11: | + | |
| - | 2016-02-24 11: | + | 2016-02-24 11: |
| - | 2016-02-24 11: | + | 2016-02-24 11: |
| - | 2016-02-24 11: | + | 2016-02-24 11: |
| - | 2016-02-24 11: | + | 2016-02-24 11: |
| - | 2016-02-24 11: | + | 2016-02-24 11: |
| - | 2016-02-24 11: | + | 2016-02-24 11: |
| - | 2016-02-24 11: | + | 2016-02-24 11: |
| - | 2016-02-24 11: | + | 2016-02-24 11: |
| - | 2016-02-24 11: | + | 2016-02-24 11: |
| - | 2016-02-24 11: | + | 2016-02-24 11: |
| - | 2016-02-24 11: | + | 2016-02-24 11: |
| - | 2016-02-24 11: | + | 2016-02-24 11: |
| - | 2016-02-24 11: | + | 2016-02-24 11: |
| - | 2016-02-24 11: | + | 2016-02-24 11: |
| - | 2016-02-24 11: | + | 2016-02-24 11: |
| - | 2016-02-24 11: | + | 2016-02-24 11: |
| - | 2016-02-24 11: | + | 2016-02-24 11: |
| - | 2016-02-24 11: | + | 2016-02-24 11: |
| - | 2016-02-24 11: | + | 2016-02-24 11: |
| - | 2016-02-24 11: | + | 2016-02-24 11: |
| - | 2016-02-24 11: | + | 2016-02-24 11: |
| - | 2016-02-24 11: | + | 2016-02-24 11: |
| - | 2016-02-24 11: | + | 2016-02-24 11: |
| - | 2016-02-24 11: | + | 2016-02-24 11: |
| - | 2016-02-24 11: | + | 2016-02-24 11: |
| Line 169: | Line 169: | ||
| ---- | ---- | ||
| The webapi.source and webapi.source_daimon tables were created when you started the tomcat service with the WebAPI war deployed. | The webapi.source and webapi.source_daimon tables were created when you started the tomcat service with the WebAPI war deployed. | ||
| + | |||
| + | Here are the valid values for the daimon_type in the source_daimon table: | ||
| + | 0 = CDM, 1 = VOCABULARY, 2 = RESULTS, 3 = EVIDENCE | ||
| + | |||
| For this example it is assumed that the CDM and Vocabulary exist as a separate schema in the same database instance. | For this example it is assumed that the CDM and Vocabulary exist as a separate schema in the same database instance. | ||
| === WebAPI SOURCE and SOURE_DAIMON Inserts === | === WebAPI SOURCE and SOURE_DAIMON Inserts === | ||
| - | INSERT INTO ohdsi.source (source_id, source_name, | + | |
| - | INSERT INTO ohdsi.source (source_id, source_name, | + | INSERT INTO ohdsi.source (source_id, source_name, |
| - | + | INSERT INTO webapi.source_daimon (source_daimon_id, | |
| - | INSERT INTO webapi.source_daimon (source_daimon_id, | + | INSERT INTO webapi.source_daimon (source_daimon_id, |
| - | INSERT INTO webapi.source_daimon (source_daimon_id, | + | INSERT INTO webapi.source_daimon (source_daimon_id, |
| - | INSERT INTO webapi.source_daimon (source_daimon_id, | + | INSERT INTO webapi.source_daimon (source_daimon_id, |
| - | INSERT INTO webapi.source_daimon (source_daimon_id, | + | |
| Line 187: | Line 190: | ||
| //Note: IF using postgresql, the jdbc connection string is of the form// | //Note: IF using postgresql, the jdbc connection string is of the form// | ||
| - | jdbc: | + | |
| === Verify Configuration === | === Verify Configuration === | ||
| Line 193: | Line 196: | ||
| Once WebAPI is started, and the source/ | Once WebAPI is started, and the source/ | ||
| - | http:// | + | |
| This should result in the following output: | This should result in the following output: | ||
| - | [ | + | |
| {" | {" | ||
| [ | [ | ||
| Line 221: | Line 224: | ||
| ===Errors when calling sources URL=== | ===Errors when calling sources URL=== | ||
| ---- | ---- | ||
| - | The most likely error you will receive when accessing http:// | + | The most likely error you will receive when accessing |
| is the ohdsi_app_user does not have permission on relation ‘source’. | is the ohdsi_app_user does not have permission on relation ‘source’. | ||
| If no error is appearing in the logs at all, please confirm the Tomcat servlet engine is listening on port 8080. If it is on a different port, you will need to adjust the URLs above to the correct port. | If no error is appearing in the logs at all, please confirm the Tomcat servlet engine is listening on port 8080. If it is on a different port, you will need to adjust the URLs above to the correct port. | ||
documentation/software/webapi/setup.1471978091.txt.gz · Last modified: by jhardin
