Prev Next

Using Multiple Configurations

Using Multiple Configurations

The Sparx Systems Cloud Service can be run multiple times with different configurations by passing these additional arguments.



--config / -c

The argument following this will be interpreted as the path to the configuration file to read on startup. This allows a secondary instance of the cloud server to run on a different set of ports, use an altered logging level or different directories.

When multiple configurations are being used, you need to ensure that each instance reads a configuration file that specifies different paths. Otherwise only the first instance will start successfully.

By default this references SSCloudServices.config in the directory containing the service executable.

--path / -p

The argument following this will be interpreted as the absolute path to search for other resources. Changing this parameter changes where the configuration file is read from, along with all paths in the configuration file that specify %SERVICE_PATH%. Setting this to a directory other than the default is an easy way to separate multiple running instances of the cloud service.

--registry / -r

The argument following this will be interpreted as a registry path within HKEY_LOCAL_MACHINE where the models the cloud server provides are specified. Changing this parameter allows using different cloud servers to provide access to different models.

By default this is Software\Sparx Systems\SQLBridge.


This argument allows starting the SSCloudServices.exe as a standalone executable instead of requiring it to be launched as a Windows service.

This can be important if Windows firewall is blocking the service, as it will prompt to create a firewall exception.

Additionally, Wine by default closes services automatically when the last user process closes, but using the 'standalone' argument to run the server as an application will ensure that the service isn't terminated when no more user applications are running. Use the command line:

     wine SSCloudServices.exe standalone

Or, if you are launching from a terminal and want to close it:

     wine SSCloudServices.exe standalone & disown     or

     nohup wine SSCloudServices.exe standalone

(The 'disown' parameter and 'nohup' command both close the terminal but ignore the 'hangup' message that would otherwise disconnect Cloud Services again.)