Refreshing HTML Servers

Does anyone know of any best practices regarding how often HTML servers should be refreshed?

We are implementing the "Default Deny" security approach, and have some concerns regarding performing testing...security is ONLY update for users when the server is refreshed (not simply with a log out, log in - like Citrix). When an issue is identified, we can update the security configuration, but the user will not be able to test again until the server is refreshed, and then they log out and log in...

We are utilizing Xe, SP 19.

Regards,
Eric

Eric,

Do you know of or have a script/method of scheduling a recycle of the WAS? I'd sure like a copy of it or some help with setting up something like it.

Regards,
Doug

We just use a cron-like scheduler and do "net stop" and "net start" early every morning. Works fine.

The interval for refreshing security is in the JAS.INI [CACHE] section, item Security=nnnnn . Maybe for testing you could have this value low on a test web server to allow frequent refreshes. See KG SAR 950. I haven't tried this yet, but plan to soon as part of our implementation testing.

Gerard