We are experiencing intermittent timeouts with calls to a variety of the Interplay web services. (We're primarily calling GetLatest, Search, Move, GetChildren, etc. on the Assets web service endpoint). In many cases, the timeouts are due to the syncronous response from the interplay service is taking longer than 60 seconds (a typical HTTP timeout) to respond.
While troubleshooting, I noticed there is an (undocumented) Health web service - that provides the quantity of Soap Requests, the Average Response Time and the Max Response Time for each operation on the Assets web service endpoint. I assume the response time numbers are in seconds - and they paint a similar picture - that many of our frequently used API calls average response time is > 60 seconds.
Assets web service endpoint: Http://interplaywshost/services/Assets?wsdl
Health web service endpoint: Http://interplaywshost/services/Health?wsdl
My questions are:
Is there any documentation on the Health Services that can help us understand the context (ex. are these month to date, year to date, are the timings in fact in seconds, etc.)? How can we reset the counters? (I noticed one of the APIs reports a MAX response time of greater than 4 hours; I'd like to re-baseline to get an accurate picture of the current system.)
Separately, is there any advice to what we can do to improve the slower operations? Ex. additional CPU/RAM horsepower, disk defrag, database indexing/optimization, etc.?
