The Application Server executable (ApplicationServer.exe in the Application Directory) accepts several command line arguments. Usually you will never need to use these command line arguments since the Setup Program takes care about them when creating the Windows Services, however for advanced installation scenarios and in some special situations those command line arguments may be very useful.
Command line argument |
Description |
--InstanceConfiguration or -i |
Defines the instance configuration file (*.icfg) to be used. This option is automatically set by the Application Server Setup or the Application Server Instance Setup. See chapter Instance configuration for more details. Example: ApplicationServer.exe -i"c:\Program files\Redbex\Application Server - Instance02\Instance02.icfg" |
--NoJobQueuing or -n |
Defines that the Application Server shall not que jobs. This argument should only be used for debugging purposes. |
--Testing or -t |
Defines that the Application Server should run a set of extended self tests on start up. This switch should only be used for debugging purposes. |
--InternalLogFile or -l |
Defines that the Application Server shall use the given file name as place where problems with the log configuration shall be written. This is useful if you want to use a custom nlog.config file. Parsing errors etc. will then be written to the given file. ApplicationServer.exe -l"c:\temp\InternalLog.txt |
Table 1: Command line arguments for the Application Server executable.
