Changes between Version 15 and Version 16 of ProdSimStartup

Timestamp:

08/24/2019 09:39:50 AM (7 years ago)

Author:

jdalbey

Comment:

put reset info in list

ProdSimStartup

@@ -11 +11 @@
 Decide which script you want to run ("full" or "practice"). Double-click on the correspondingly named `systemstart` .bat file.
 
-Observe a terminal window open and display webserver status messages.
-
 The CAD server GUI should appear displaying time 0:00:00.
 
 The Simulation Manager GUI should appear.
 
+A Web Browser should appear with three tabs.
+
 Optionally, start any CADClients, ideally on a different workstation.
-
-A Web Browser should appear with three tabs.
 
 Click "Start" button in Simulation Manager GUI. Observe the clock begin counting every second. In CADServer GUI, observe the timer running. Click on the "Traffic" tab to view the queue of traffic events. As events are processed, there will be a ten second delay and then the affected dots will change color in the CPTMS map (see below).
@@ -42 +40 @@
 ----
 == Reset log files ==
-On Apache server (W:) clear `activitylog/data.json `and `webapps/dynamicdata/CADcomments.log`
+On Apache server (W:)
 
-On Apache server (W:) in `webapps/dynamicdata` Copy `cms_messages_empty.json` to `cms_messages.json`
-
-On Apache server (W:) in `webapps/dynamicdata` Copy `har_messages_empty.json` to `har_messages.json`
+  * clear `activitylog/data.json ` 
+  * clear `webapps/dynamicdata/CADcomments.log`
+  * clear `unifiedlog.csv` 
+  * in `webapps/dynamicdata`  Copy `cms_messages_empty.json`  to `cms_messages.json`
+  * in `webapps/dynamicdata`  Copy `har_messages_empty.json`  to `har_messages.json`
 
 ----
@@ -55 +55 @@
  * Verify Apache is configured properly for running cgi's from cgi-bin.
 
-----
-Notes on switching from "Practice" script to "Full" script
 
-{{{
-config/traffic_model_config.properties 
-Events_File = config/vds_data/sample_data/atmsBatchEvents_practice.txt  to ..._production.txt
-
-webapps/sim_scriptname.json
-{"filename":"practice_script_2016.xml"}  to ... full_script...
-}}}
 ----
 === Troubleshooting Tips ===
@@ -71 +62 @@
  * make sure path is correct as described above.
  * make sure webserver is started in correct directory.
+ * refresh the cmsmonitor web page in the browser.
 
 === Add Ad hoc Incident ===