I've run into this before. I was able to set up a task on the server to reload the manifold application at a specific time, then another task copy updated .map files and overwrite the ones serving the IMS. Again, this would fail if someone happened to hit the IMS during or just before a file got copied. To guard against this, I had another task that renamed the default.asp file to some other name, then renamed another asp file to default.asp that had a message saying "temporarily out of service". Once the copying was finished the default.asp file was renamed back and the proper default.asp file was renamed as well so people could access the IMS again. So in summary my task schedule was something like this: 1. Reload mapserver (see the default_admin.asp page created by manifold when you export to IMS) 2. Rename default.asp file to default_temp.asp (or whatever) 3. Rename default_maint.asp to default.asp 4. Copy the new .map files 5. Rename default.asp to default_maint.asp 6. Rename default_temp.asp back to default.asp
"The blessing in life is finding the torture you are comfortable with." - Jerry Seinfeld, 6/26/2013 |