|
All SOAP components are based on existing WSDL files that can be selected from either within the Opensphere, the file system or remotely using an URL.
|
|
Web service components are up-and-running with just a few mouse clicks.
|
|
The web services simulation engine supports all available SOAP flavours including document-literal and rpc-encoded messages.
|
|
Transmission encryption using SSL mode can be easily configured.
|
|
The payload (SOAP Content) of the operation invocation and response can be freely customised within the inbuilt XML editor.
|
|
You can also use markers (for xyz) that are replaced by the value of project dependent substitution variables.
|
|
These markers can also be replaced by the corresponding data of a single row when the driving component for invoking operations is a row set.
|
|
Row sets can be defined as static data within an editor but they can also be the result of an SQL select statement that gets executed each time the web service client component is started.
|