Changes between Version 7 and Version 8 of OnyxDeployment


Ignore:
Timestamp:
01/04/11 21:57:26 (14 years ago)
Author:
jeff.lusted
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • OnyxDeployment

    v7 v8  
    11== Deploying an Onyx Questionnaire ==
    22
    3 This details what is required to deploy our onyx questionnaire. The first few paragraphs outline some of the major prerequisites and some minor complications in deploying across development and production environments.
     3This details what is required to deploy our onyx questionnaire. The first few paragraphs outline some of the major prerequisites and some minor complications in deploying across development and production environments.[[BR]]
     4
     5These notes are open for discussion or improvement.
    46
    57=== The Onyx Questionnaire and the PMI Lookup ===
    68Onyx uses a web service to access the Patient Master Index (the PMI). This web service is provided by the pmi-lookup. The Onyx questionnaire is currently installed alongside the pmi-lookup; ie: within the same instance of tomcat.[[BR]]
    79
    8 This seems sensible as we have only one questionnaire at the moment, and we don't know what it would entail to run more than one questionnaire at the same time. These ideas will have to be worked out in time. For the moment, we are sticking to using one tomcat instance.
     10This seems sensible as we have only one questionnaire at the moment, and we don't know what it would entail to run more than one questionnaire at the same time. These ideas will have to be worked out in time. For the moment, we are sticking to using one tomcat instance. This is almost certainly more secure as the Obiba interface for the web service is not encrypted at present.
    911
    1012There is a development and a production version of the pmi-lookup. The production version uses an !SqlServer table function invocation in JDBC to retrieve demographic data. For testing Onyx in a situation where !SqlServer is not available, the development version uses a !MySql database.
     
    2628=== Deploying PMI Lookup Production Version ===
    2729The version 1.0 artifact is located at http://mvn.briccs.org.uk/org/bru/briccs/briccs-pmi-lookup/production-1.0/briccs-pmi-lookup-production-1.0.war
     30
     31   1. Unzip war file into $BRICCS_WEBAPPS/briccs-pmi-lookup-production-1.0
     32   1. Locate config file at $BRICCS_WEBAPPS/briccs-pmi-lookup-production-1.0/WEB-INF/classes/pmi-lookup-config.properties
     33   1. Edit the config file for database, user and password. There are appropriate templates in the config file.
     34   1. Locate and edit log4j properties file at $BRICCS_WEBAPPS/briccs-pmi-lookup-production-1.0/WEB-INF/classes/log4j.properties
     35   1. Place a context file for deployment within the tomcat tree: $CATALINA_HOME/webapps/patient-lookup.xml
     36   1. Deploy within tomcat using manager commands of some sort.