SPEEDD prototype consists of two modules:
- runtime
- user interface (or dashboard)
Before the first use you should build the modules as described below.
Project speedd-runtime contains the code for the runtime platform for SPEEDD. The speedd-runtime module depends on a bunch of other projects (e.g. storm, kafka, etc.). The dependencies are available on the internet and will be resolved by maven.
Build the speedd-runtime module by performing the following:
- cd speedd-runtime
- mvn clean install assembly:assembly
Follow instructions for respective use cases:
In the following sections we assume that your current working directory is 'speedd-runtime'.
- cd scripts/traffic
- sudo ./start-speedd-runtime
- Open a new terminal and start the dashboard app following the instructions
- start sending input events by running ./playevents-traffic
- cd scripts/ccf
- sudo ./start-speedd-runtime
- Open a new terminal and start the dashboard app following the instructions
- start sending input events by running ./playevents-fraud
- Kill the topology by running 'sudo scripts/kill-speedd-runtime'
- Stop the UI by killing the process (or Ctrl-C in the terminal shell where the UI process has been started)
Note: It is important to stop the prototype running current demo scenario before running another demo scenario (for example, if the traffic management demo is running, it is important to stop it before running the credit card fraud demo).
For example, for traffic management:
- For input events: run 'scripts/traffic/show-in-events'
- For output events: run 'scripts/traffic/show-out-events'
- For actions: run 'scripts/traffic/show-actions'