Is there a supported method to lock out MRE and DevStudio users during a scheduled outage? I could disable the authentication method, but the error message is nondescript. I could also post an index.html page at the root of the site, but those who have bookmarked a page and DevStudio users would fly right by. Stopping the services gives an ugly EDASERVE message. Thoughts, ideas, sympathy?

This message has been edited. Last edited by: Kerry,

What we have is a maintenance page displayed by the Webserver in case it can't contact the Application Server.
So, if you have a planned maintenance, just turn off the AppServer and a nice page informs your users.

I'm not sure if this works for DevStudio.

This message has been edited. Last edited by: Computix,

It sounds like you're talking about blocking things during server maintenance on the Reporting Server (e.g. The WebFOCUS Client is still running). Otherwise you wouldn't get the "ugly EDSERVE message".

This being the case if you have ANY Reporting Server running anywhere (even on a Dev or Test environment), you could do something like this:

IBIC_server=UP_SERVER
IBIF_adhocfex = "\n-HTMLFORM BEGIN \n<B>Down for maitenance!</B>\n-HTMLFORM END "

This code can be added to:
WF Admin Console -> Configuration -> Custom Settings

UP_SERVER should be the name of the Reporting Server that is not down (e.g. EDASERVE).

What this does is it changes the server that is being used to the server is up. It then runs a report on that server which displays a message:
"Down for maintenance".

This report should override any request that has been sent to the server.

Please test this before implementing it. It is possible something like this might give an ugly message in DevStudio before you actually get to the point of running a report.

Matt,

What I have done is create a version of the WORP_Login.jsp file that displayes a message to the user and doesn't allow them to log in. However, it does contain a hidden log in button so I can log on and run tests. I can send you the modified .jsp file if you like.

Cheers,

Dan

great ideas. I'll try dlogan's and Dan's approaches and report back to the forum