It's your choice how you run the daemons.
The list I made was my personal opinion only, and there may be as many as there are users of global.
I however recommend you to run the daemons as batch files during the startup phase of global to see that everything is working properly. When you have got everything in place, and working you install them as a service on the server.
The reason why I wan't to have the daemons running as batch files is that sometimes they appear to be working properly when they in fact are "chewing air" only. After a restart of the daemon it will work properly again.
I have never got any DB problems if a daemon has failed during updating, and yes... if you want to run them as a service you should have them running on the same server as the PDMS databases.
It's your choice how you run the daemons.
The list I made was my personal opinion only, and there may be as many as there are users of global.
I however recommend you to run the daemons as batch files during the startup phase of global to see that everything is working properly. When you have got everything in place, and working you install them as a service on the server.
The reason why I wan't to have the daemons running as batch files is that sometimes they appear to be working properly when they in fact are "chewing air" only. After a restart of the daemon it will work properly again.
I have never got any DB problems if a daemon has failed during updating, and yes... if you want to run them as a service you should have them running on the same server as the PDMS databases.
