This topic includes the following subtopics:
To start your SQLstream s-Server, 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
$SQLSTREAM_HOME refers to the installation directory, such as /opt/sqlstream/
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:
SQLSTREAM_HOME="/opt/sqlstream/18.104.22.16821/s-Server" export SQLSTREAM_HOME PATH=$PATH:$HOME/bin:$JAVA_HOME/bin:$SQLSTREAM_HOME/bin export PATH
To confirm that SQLstream s-Server is running, do one of the following:
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:
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:
6301 sun.tools.jps.Jps 2560 com.sqlstream.aspen.server.AspenVJdbcServer
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.
You can choose to run s-Server as a service. This is an option in the installer. Once s-Server is installed as a service, it will automatically start whenever the machine on which s-Server is running is started. You can also manually start, stop, and restart the s-Serverd service using standard Linux service commands.
The s-Serverd service can be found in: /etc/init.d/s-serverd
You can start, stop, restart, and check the status of s-serverd using the following standard Linux service commands:
|service s-serverd start||Starts service|
|service s-serverd stop||Stops service (equivalent to !kill)|
|service s-serverd restart||Stops then starts service.|
|service s-serverd status||Tells whether s-serverd is running|
You can specify a checkpoint for start, stop, and restart, using the following syntax:
service s-serverd stop <checkpoint name>
service s-serverd stop --with-checkpoint <checkpoint name>
Use the same syntax to set a checkpoint for restart. Note: If you do not specify a checkpoint when stopping, a default checkpoint will be used when the service stops. Once you establish a checkpoint, you can start the service at the same point by indicating the checkpoint name in the start command:
service s-serverd start <checkpoint name>
service s-serverd start --with-checkpoint <checkpoint name>