Simple Object Access Protocol (SOAP) is a standard protocol specification for message exchange based on XML. Communication between the web service and client happens using XML messages.
On Adeptia Connect, you can connect an application to any other application or service that supports SOAP APIs. For example, you can send stock prices from your Google Spreadsheet to an application that supports SOAP APIs.
SOAP is supported only at Destination only.
Field (Account) Information
While configuring the Source or Destination of a Transaction, you find an Account option to configure your application with Adeptia Connect. Using Account configuration, you need to specify the location from where the data is to be accessed. In this process, provide the details of the application account to grant permission to access data.
Specify the following information for SOAP:
- Type a unique SOAP account name.
- Select the location of your Web Services Description Language (WSDL) file. WSDL is an XML-based interface definition language that is used for describing the functionality offered by a web service.
- On Local Disk: Select this option if your WSDL file is on a local computer or on a LAN network.
- Over HTTP: Select this option if your WSDL file is at an HTTP location.
- Browse to and select the WSDL file.
- Select WSDL file references other files check box if your uploaded WSDL file is referring to other files. On selecting this check box, File References field appears.
- Upload your referential WSDL or XSD file(s) in a single zip file only. Also just keep the folder structure of the zip file as per the references made by the WSDL or XSD file(s).
If you have selected Over HTTP option then type the HTTP URL of the WSDL file, the endpoint URL of the SOAP web service.
- Click Process WSDL to fetch the information from the uploaded WSDL file.
The information about the service, binding, and endpoint URL are automatically populated.- Service Name: Service is defined as a collection of network endpoints or ports. If there is only one service name in the uploaded WSDL file, it will appear as default selected in the Service Name automatically. However, if there are multiple service names in the WSDL file then you need to select the service from the drop-down list.
- Binding Name: Bindings defines the message format and protocol details for a web service. If there is only one binding in the WSDL file then it will appear as default selected in the Binding Name automatically. However, if there are multiple bindings in the WSDL file then you need to select the binding from the drop-down list.
- Endpoint URL: The operations and messages are described abstractly and then bound to a concrete network protocol and message format to define an endpoint. It is the URL where the web service will eventually hit.
- Service Name: Service is defined as a collection of network endpoints or ports. If there is only one service name in the uploaded WSDL file, it will appear as default selected in the Service Name automatically. However, if there are multiple service names in the WSDL file then you need to select the service from the drop-down list.
- If a web service you are accessing is secure then define the security settings. Select Enable client authentication check box to authenticate both server and client identity.
- On selecting the check box, you need to select the Keystore.
- Select authorization used in the web service. By default authorization is disabled, however, you may choose basic authorization for a web service. Basic authorization is a widely used protocol for simple username/password authentication.
- Click Save.
Actions
The Web Services operation performs a specific request action against a URL endpoint. Whenever the destination application or service uses SOAP APIs, the actions are displayed according to the uploaded WSDL. It may vary with different WSDL files.
When applicable, type the SOAP header content that you want to include in the request.
