Our requirement is to implement SOAP Based Boomi Service adhering to the existing SOAP Based Web Service with 5 operations (currently implemented using Java + SpringBoots) so that consumer application just need to change new Boomi Service URL Endpoint in their system. This is to avoid a code change in consumer application.
When we implement a Operation in Boomi using Boomi Process, we can use the same message structure as request and response profile but process binds to a new operation generated automatically based on the “Operation Type” and “Object” defined in Web Services Server Operation configuration. So when calling existing WSDL pointing to Boomi SOAP Service URL (/ws/soap), gives operation mismatch error.
FYI, we do not have API Management License so can't make use of API Management.
Looking for some work around solution.