If an application relies heavily on SOAP Web Services to pull data and construct pages based on this data it receives, how is the best way to determine and handle it if the soap web service is not functional ?
Is it possible for the WSDL to be available but the web service be down? I am told that this is possible.
History to understand the project and my concerns:
- This application was built because we have a 3rd party vendor service-now.com supplying us with IT management.
- The problem is that service-now's web based interface is not accessible and we cannot provide a non-accessible service to our end users. Once we learned about their web service provisions, I rebuilt the self service service-now module entirely in php using soap and interacting with their web services to perform CRUD on their data. This way we have a better looking interface and its accessible.
My concern though lies in what to do and how to nicely handle the errors when the web service goes down.
I have coded an interface defining all interaction with the web service and I coded a client class which implements this interface. All methods in the client class are within try/catches so I know when something went wrong with requesting data or pulling data from this web service.
But, what about preemptively checking to see if the web service is down before presenting the user with the login page. This is what I really want to get it.