Hi Rick,

We're going to be doing SQL maintenance in a couple of weeks in our production environment, and it just occurred to me that while I can set the WWC app to hold requests using the admin page, I don't quite get how that works in a REST service environment. Not to mention that my wwsession/wwrequest tables are also in SQL. Any recommendations or am I overthinking this in my usual way? 😃

TIA

It works the same for Rest services. You put the server into either Hold Requests (no requests except logged in admin requests), or Single Server mode so you can control operations one at a time.

You probably don't need the latter since you're using SQL Server and don't have to worry about EXCLUSIVE access. Once the server is on hold no requests go through - same for Html as REST requests.

The same admin urls work for that even in a REST service because they are handled by the connector.

+++ Rick ---

As expected, of course. 😃

I was more curious as to what response code/message goes back to the caller. I'll turn it on in my stage environment and see what the result is.

For any lurkers, enabling hold requests via the administration page results in a 500 server response along with the HTML that renders the standard maintenance page, which iirc is baked into the WW DLL and cannot be modified.