Scenario 7: The Web-Services-Workflow-Request-Not-Yet-Received-by-Waveset Scenario

Scenario Description

These scenarios cover those cases where the Waveset GUI is not used to launch provisioning. Instead, the user interface is provided by an application that internally calls to Waveset using the SPML or other custom web service interface. Here the user session related to the user going through the UI is managed by way of the calling application. For Waveset, the requests are all launched as the “soapadmin” subject.

In such a use case, this failure scenario covers the case where the request by way of the Waveset endpoint has not been received yet and the targeted node fails.

Without Session Persistence

User experience: A transparent failover. The SOAP administrator's credentials are passed in for each SOAP request, either over the wire or within Waveset through a Waveset.properties setting. As long as the node which was to receive this SOAP request has not received the request before going down, the failover is transparent with or without session persistence.

Recovery steps: No action needed. The SOAP request is sent to a live node that executes it.

With Session Persistence

User experience: Same as in the Without Session Persistence mode.

Recovery steps: Same as in the Without Session Persistence mode.