Skip to main content

SOAP Sender Connector

SOAP sender connector enables the SOAP service to be opened on MIP with the given address, in accordance with the WSDL file (Web Services Description Language) specified by the user. The user provides the WSDL file of the target for which he wants to open the SOAP service. The WSDL file contains the description of the SOAP service and defines the service's functionality, input and output parameters, message formats, and communication methods. The user loads the WSDL file via Resources/WSDL Resources in the interface and selects WSDL via the SOAP Sender connector. This passes the definition of the SOAP service to the integration platform. SOAP sender connector opens the SOAP service on MIP with the given address, in accordance with the WSDL file specified by the user. After successful activation of the SOAP service, users can send requests to the specified address using the SOAP protocol and use the functionality provided by the SOAP service.

Required Connector Properties​

  • SOAP Address: The area where the address of the SOAP service to be opened via MIP is defined. It specifies the endpoint or resource location within the SOAP API. For instance, it might be represented as “/mip/api/getFile”.

  • WSDL Resource: WSDL (Web Services Description Language) is an XML-based document that defines the functionality, available methods, and communication details of a SOAP (Simple Object Access Protocol) web service. The WSDL file contains details about the operations (methods) offered by a web service, parameters for these operations, and communication details to be used for invoking these operations.

  • Synchronous Endpoint: Synchronous Endpoint is typically preferred for situations that require a quick response. When this option is used, a request sent by a client is processed immediately, and a response is expected to be received. This implies that operations are carried out instantly. Contrarily, if this feature is not selected, this Endpoint is named Asynchronous Endpoint, and in its usage, the client sends a request, but the response is not received immediately. The request is processed in the background by the server, and after some time, a response is communicated to the client. In this case, the client does not have to wait for the process and can proceed with other tasks.