Running daemon as a service: + No-one needs to logged on to the computer where global is running if DBs are on the same machine. - If more daemons are added the multi project service(all daemons) must be stopped before starting again with the modified multids batch file. - You cannot stop/start individual daemons if using multi project service, unless you setup the service to show a output window and interact with the desktop. It's all or none.
I would not thrust that a daemon is working properly unless I see that it is processing data. If I would run it as a service I would let it show the output window, but then it is no longer any benefit from running it as a service as you would anyway end up with the same amount of windows.
Running daemons as a batch file: - Someone must be logged on to the machine where the dameons are running at all the time. + It is easy to start/stop individual daemons(You only need to run a batch file/close the window). + You can have the databases wherever you like in your network. Just set the project variables to point to the project folders. + The daemon is outputting all commands to the cmd window, so you can see what is happening. + Setting up a new daemon is easy. Just copy an old batch file and make necessary changes.
Running daemon as a service: + No-one needs to logged on to the computer where global is running if DBs are on the same machine. - If more daemons are added the multi project service(all daemons) must be stopped before starting again with the modified multids batch file. - You cannot stop/start individual daemons if using multi project service, unless you setup the service to show a output window and interact with the desktop. It's all or none.
I would not thrust that a daemon is working properly unless I see that it is processing data. If I would run it as a service I would let it show the output window, but then it is no longer any benefit from running it as a service as you would anyway end up with the same amount of windows.
Running daemons as a batch file: - Someone must be logged on to the machine where the dameons are running at all the time. + It is easy to start/stop individual daemons(You only need to run a batch file/close the window). + You can have the databases wherever you like in your network. Just set the project variables to point to the project folders. + The daemon is outputting all commands to the cmd window, so you can see what is happening. + Setting up a new daemon is easy. Just copy an old batch file and make necessary changes.
