Resetting the Edamame Demo

<< Click to Display Table of Contents >>

Navigation:  Analyzing Data in s-Server > Running Demo Applications > The Edamame Demo >

Resetting the Edamame Demo

Previous pageReturn to chapter overviewNext page

After you finish running the Edamame demo (or before running it again), you should reset the demo so that it starts with clean data the next time.

If you've encountered difficulty in running the Edamame demo, you can use any of the four bullets to troubleshoot, but to completely reset the demo and start over with clean original data, do all four in sequence.

There are four steps to completely reset the demo environment:

1.Stop all the demo components. The easiest way to do this is to click the "Stop All Services" link on the demo web application. You can also individually click the stop buttons on the various components.

2.Reset the schema. This is only necessary if you have modified any of the demo objects. Click the "Reset Schema" link on the demo web application page. This reloads the SQL script that creates all the objects in the EDAMAME schema.

3.Undeploy the demo. Close the browser window containing the demo web application. Then go to the Tomcat web application manager page (http://localhost:8080/manager/html) and click Undeploy next to edamame.

4.Delete all log files. To clear out the log files that the SQLstream s-Server reads as demo inputs, type rm -f $SQLSTREAM_HOME/temp/*.log.

Make sure that log files are really removed - if files are still locked Tomcat will open new files with .log.1 extensions and the server will be reading from the wrong file. The files are owned by the user that Tomcat runs under.

To run the demo after resetting it by these steps, you will first need to re-do the Installing the Demo steps.