SOAP service integration with WSDL-generated classes
Key Takeaway
Put the WSDL file in your cartridge's webreferences2 folder, run a pipeline to generate the classes, and call the SOAP service through the initServiceClient, createRequest, execute and parseResponse callbacks.
B2C Commerce can call SOAP web services by reading a WSDL file from your cartridge and generating script classes from it. Your code then calls the SOAP operations through those generated classes. You wrap the calls in the web service framework, so rate limits, circuit breakers, timeouts and logging apply to the SOAP call like any other service.
How a SOAP integration fits together
A SOAP integration has two parts. The first part is a service configuration in Business Manager, made up of a service, a profile and a credential, with the SOAP service type. The second part is script code.
SOAP support lives in the dw.ws package, mainly in the Port, WebReference2 and WSUtil classes. The SOAP service type uses dw.ws.WebReference2 underneath. Unlike the HTTP and FTP service types, the SOAP service type needs extra code to get the port.