Changes between Version 5 and Version 6 of UnifiedLogger

Timestamp:

07/16/2019 10:21:29 AM (7 years ago)

Author:

jdalbey

Comment:

add apache deployment

UnifiedLogger

@@ -24 +24 @@
 UnifiedLogPath = webapps/dynamicdata/
 }}}
-The only option is to specify the path to the folder in which the output CSV file is to be created.  This will change between dev and production systems; the production system will expect the file to exist on the apache server.
+The only option is to specify the path to the folder in which the CADcomments.log input file exists, and the output CSV file is to be created.  ''Perhaps this isn't necessary; I can't think of a situation where this would change.''
 
 === Packaging ===
@@ -63 +63 @@
 In CPTMS, display the CMS layer, open a CMS dialog and enter a message "SLOW TRAFFIC".  Click "Send" and wait five seconds.  Observe an entry for CMS Activated to appear in the monitor.   Update the CMS message results in a "CMS Updated" entry in the unified log.  Clearing a CMS message results in a "CMS Deactivated" entry in the unified log.
 
+=== Deploying on Apache Server ===
+Copy `unifiedlogger.zip` and `unifiedlogmonitor.html` to `webapps` folder on `W:` drive.[[BR]] Copy `loggingservice.cfg` to `config` folder (at same level as `webapps` folder).[[BR]] Start the application: `python webapps/unifiedlogger.zip`
+
 === Running as a background service ===
 ''TBD: Explain how to start the service as a unix daemon.  Explain start, stop, restart.  Explain which files are reset, etc.''