You may install multiple instances of s-Server on a single host machine, in order for multiple developers to have their instances of s-Server on a multi-tenant deployment. You may also install multiple instances for testing, as well as for validation of federated/distributed deployment of Guavus SQLstream suite of products in a multinode cluster.
In order to run multiple instances of s-Server on the same system, you need to change the way you install a second instance of s-Server.
When you run the installer as root or with sudo privileges, the installer does several things that interfere with running a second instance with the same settings:
Only one instance of SQLstream s-Server can be set up to start/stop as a linux service. As a result, if you try to install a second instance with root privileges, the installer will overwrite earlier the installation of the linux service unless the installer is instructed not to install as a service.
So, to install a second instance using a super-user, you need to make changes in the steps below. You can also run this installer form the command line and pass in these properties. See Appendix: Command-line Installation for more details.
The Installation Directories page. Here, you need to change the installation directories. For example, you might change these to the following:
The Service/Daemon page. Here, you need to deselect the Create the s-serverd Service option:
To start this instance in the background, you will need to use a Linux command such as nohup. This command lets the instance continue to run in the background after the terminal is closed. See http://en.wikipedia.org/wiki/Nohup for more details.
Installing as a user without root privileges avoids these problems. First, when the installer is run without superuser privileges, it cannot be installed as a linux service. When you install as a regular user, the default location for trace logs is set relative to "installation directory" rather than
/var/log/sqlstream.
Having said all that, the problem with installing as a regular user is that you will need to create that user on your system first. Since installing with root privileges creates a new user, it may be advantageous to take the steps described above.
When you install an instance as a regular user, you will need to start it in the foreground through a terminal. To start this instance in the background, you will need to use a Linux command such as nohup. This command lets the instance continue to run in the background after the terminal is closed. See http://en.wikipedia.org/wiki/Nohup for more details.
For all instances, you need to make sure the following definitions are unique:
See the topic Configuring SQLstream in the SQLstream Adminstrator Guide for more information.