How to execute RoboServer at command line using an alternate configuration file

When you execute RoboServer from the command prompt in Linux or Windows, it uses the configuration settings in the RoboServer.conf file. You can edit that RoboServer.conf file to change the settings, such as allocating more RAM using wrapper.java.maxmemory.

What happens if you want to run multiple instances of RoboServer with different settings? For example, what if you want one instance that runs only Management Console with 1 GB of memory allocated, and another instance that listens on port 50000 with 4 GB of memory allocated? To do that, you need to have multiple copies of the .conf file, each with different settings. On Windows, ServiceInstaller.exe allows you to specify a configuration file when establishing RoboServer as a Windows service, but the RoboServer command itself doesn't allow you to specify a configuration file.
To run RoboServer with a different configuration file, do the following:

1. Duplicate the RoboServer.conf file located in the bin subdirectory of the Kapow Katalyst installation directory. For our example, we'll name the copy "RoboServerModified.conf". Edit the new copy to make any needed changes to settings.

2. Run the appropriate command, depending on your platform.

   • On Linux, use the wrapper command.
     If you're working in the bin directory, the command would be the following:

     ./wrapper -c RoboServerModified.conf wrapper.app.parameter.1=-service wrapper.app.parameter.2=socket:50000

     Additional parameters can be added or removed as needed. For example, wrapper.app.parameter.3=-MC could be added to start the Management Console.

   • On Windows, use the ServiceInstaller.exe command:

     .\ServiceInstaller.exe -c RoboServerModified.conf
wrapper.app.parameter.1=-service wrapper.app.parameter.2=socket:50000