cast-servercommand. Each machine should produce some output like the text below. The
cast-serverexecutable actually runs severs for both the languages supported by CAST. The numbers displayed by on the terminal are the process ids of the Java and C++ servers.
vonnegut:~ nah$ cast-server Java server: 1301 CPP server: 1302
To enable the server to find your compiled components you must do the following. For Java components your
CLASSPATH environment variable must include the directories and/or jars which contain the classes. For C++ components your component libraries (e.g.
libHelloWriter.so) must be in the library search path. The easiest way to do this is to set the environment variable
DYLD_LIBRARY_PATH on OS X) to include the directories which contain your libraries.
cast-clientwith a single argument, a cast file. E.g.
vonnegut:~ nah$ cast-client /usr/local/share/cast/config/comedian-architecture.cast CoSy Architecture Schema Toolkit. Release: 0.2.0 [starting [1/11]: stage.subarch_wm] [starting [2/11]: stage.subarch_tm] [starting [3/11]: funny.man] ...
The cast file contains a description of the system you wish to run. For more details on this file see configuration instructions. When a CAST system runs it passes through a series of synchronised steps. These are described in system architecture overview.
To shut down a running CAST system, CTRL-C the client. This will send the appropriate signals to the servers, halting execution and destroying the components. Once a system has been shut down, you can run the client again without restarting the servers.