SOAP and WSDL Activities

Use the SOAP group to expose or call WSDL-defined services over HTTP(S) or JMS. Studio derives operation and message schemas from a WSDL resource so SOAP payloads can be mapped as structured workflow data.

Available activities

Activity	Purpose
WSDL	Defines an inline or remotely located WSDL and exposes its operations and schemas
SOAP Request	Calls a WSDL operation and maps the SOAP response back to workflow data
SOAP Receiver	Exposes an inbound SOAP operation that starts a workflow
SOAP Reply	Returns the successful response for an inbound SOAP request
SOAP Fault	Returns a SOAP 1.1 or SOAP 1.2 fault from an inbound flow

Call a SOAP service

1. Add a WSDL resource and load the service definition.
2. Add SOAP Request and select the WSDL, service, binding, and operation.
3. Configure the HTTP(S) or JMS transport required by the binding.
4. Map workflow data to the generated request schema.
5. Map the generated response and fault data to downstream activities.

Expose a SOAP operation

1. Add SOAP Receiver as the event source.
2. Select one WSDL operation and configure its transport.
3. Map the incoming request into the workflow.
4. End each successful path with SOAP Reply.
5. Use SOAP Fault for contract-compliant error responses.

Recommended practices

• Keep the WSDL stable after consumers integrate; review generated schema changes before updating it.
• Match the SOAP version and transport declared by the selected binding.
• Return a SOAP fault rather than an unrelated HTTP or workflow error body.
• Protect credentials and client certificates through resources and managed secrets.
• Test namespace-heavy and optional elements because their mapped JSON representation can be easy to misinterpret.