Starting and Stopping SQLstream s-Server
Starting the SQLstream s-Server
To start your SQLstream s-Server, double-click its desktop icon:
Or run the script named "s-Server", located in the bin directory:
If you have included $SQLSTREAM_HOME/bin in your PATH then you can just run
Note: $SQLSTREAM_HOME refers to the installation directory, such as /opt/sqlstream/5.1.0.XXX.
Note: On most Linux systems, one way to to add $SQLSTREAM_HOME to your system's path is by creating a script file in /etc/profile.d with lines of code similar to the following:
Confirming that SQLstream s-Server is running
To confirm that SQLstream s-Server is running, do one of the following:
•Check if s-Server appears in SQLstream s-Studio.
•Use jps -l to confirm that "AspenVJdbcServer" is running. (This is the actual name of s-Server.)
Start SQLstream s-Studio
Once the SQLstream s-Server is started, you can open SQLstream s-Studio by double-clicking its desktop icon or by running the SQLstream script from any directory. When you launch s-Studio, you will need to enter connection information for your installation of s-Server.
If the server is running, s-Studio should connect to it and its icon will appear in the left pane of s-Studio:
Use jps -l
SQLstream s-Server runs as a Java Virtual Machine called "AspenVJdbcServer"
To confirm that SQLstream s-Server is running, you can use the Java jps -l command. (See https://docs.oracle.com/javase/8/docs/technotes/tools/unix/jps.html for more detail on this command.) This command will produce something like the following if s-Server is running:
Stopping the SQLstream s-Server
To stop the SQLstream s-Server, type:
into the SQLstream s-Server terminal window. This will stop the server, create a checkpoint backup of the repository, and close the window.
If there are open client connections to the server (for example, if the user interface is running), the server will alert you and continue running.
If you need to stop the server in spite of open client connections, type:
into the SQLstream s-Server terminal window. This will force closure of the connections, then stop the server and create a checkpoint backup of the repository.
In the event that neither !quit nor !kill is able to stop the server, you can type Ctrl+C into the SQLstream s-Server terminal window. This will abort the server and shut down the repository, but will not create the checkpoint backup of the repository. When you next restart the server, it will restore the previous checkpoint backup, so any changes made to repository objects since then will be lost. Obviously, this option should only be used in extreme circumstances.
For more information on catalogs and checkpoints, see the topics Backups and Code Control in this guide.