Maintenance - probably an obvious question

[John Fligg]

When you have a new version ready to supply to your customers, I assume you must stop the ervice running and then transfer the exe to the server and restart the server?

Also if there are any file changes presumably it would be best for me to perform this function at a universal time when people arte not using the service as I would also have to run FM3 against all the data folders. Yes I know FM3 handles itself but for a better user experience I think it better and perhaps safer to have an external program loop round the data folders/files and run RTFM against all the files.

Has anyone addressed this and come up with an international time that might be best to do this maintenance. I am in the UK and had been thinking about 6am. The trouble is I have Australian clients so 6am here is 6pm there.

Just curious how anyone handles taking the service down with people potentially using it.

John

[Bruce]

I think you'll find that even with "global use", there are plenty of dead-time to do updates in.

We don't update ClarionShop a lot, but when we do we usually don't think too hard about it. Just wait till early morning, see if anyone is connected, and if not just stop it for a few minutes.

NT6 has a couple features which are leaning towards making this easier. The performance monitor control template let's you see easily how many current sessions there are. Also a large array of "traffic" is being created as the program runs, so with some creative graphing you should be able to identify the best times. I still need to do an example of the creative bit, but the data is being collected (into ram at this stage.)

cheers
Bruce