Choice is yours , however in service you can set daemon as automatic startup by using adminstrative toolS > service option instead of handling with batch option start
I will try out both the options and decide whatever suits me well and the most important thing for me is that I do want to setup a network which could be easily rectified if some problem comes since I am the only one who has to look after all these things. But what I feel is instead of making so many daemon batch files for each project, why shouldn't we go for a single batch file and utilize it's services. Is there anything which is hidden behind the scene, Thomas, please put that thing in front if you feel something is going to stuck in future.
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.
Tback,
Totally agree with your pro-cons analysis. We are running a batch file on server and since most time I am the only one connect to it, I just minimize the dos windows.
Here I have something to say....Running daemon as a Batch file let's you run all the individual batch file one by one...which will makes you irritating sometimes since it is time-consuming too while on the other side if you just make a single batch file for all the projects or run it as a service you won't even need to start the service of your own as Vinayak said use the Windows Service for it to start-up.
The other thing is the system which we have made it as a server,which owns all the project databases and which is serving all the work-stations, here I want to ask if I can put all the Daemons here on the same system and suppose any of the daemon goes down,will it be going to make any problem with PDMS access from it by work-stations or any network problem,it doesn't seems to be so simple,any suggestions.
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.
Thanx Thomas....But If we go for Batch file option then,Is there any other way by which we can initiate all the batch files at one go rather than clicking them all one by one.
We are going to use the Windows Task Scheduler tool to manage our starts and stops for us. This way we can have different projects update at different scheduled times. This is running Global through batch files, not as daemon services.
