Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
SOAP Webhook can be used as a source in a template. The WSDL (Web Services Description Language) file bundled with Adeptia Connect is generally used to define a SOAP Webhook acting as a source in a template. However, there can be a situation when you may want to use your own WSDL file to create a SOAP Webhook and define the request and response parameters based on your requirement.
In Adeptia Connect, you have an option to create and use a SOAP Webhook according to your need. You can use your own WSDL file to create a SOAP Webhook before or during the creation of a template. If you have already created one using your WSDL file and published it as a Template, you will be able to select it from the designated drop-down box (Select Web Service Provider). You can also create a new one by uploading your WSDL file and use that as a source even when you are in the middle of creating a template.
Follow the steps below to create and use a SOAP Webhook as a source in a template.
Info |
---|
For steps previous to the step 1 being discussed below, refer to Creating a Template. |
- Select SOAP WebHook as a source application.
- Select the Webhook type as Simple or Advanced.
- When Simple configuration is selected:
- Select Enable SSL check box if you want the SOAP Provider service to offer a SSL security.
Select a port in the Select Port field.
Tip If you want to publish the SOAP provider Webhook to a custom port instead of the default port, refer to this document. Note These two fields are available only when you have selected the Simple as a Webhook type.
- Advance Advanced Webhook type allows you to use a predefined Webhook or define a new one by using your own WSDL file. When Advance Advanced configuration is selected:
Select a pre-defined SOAP Provider in the Select Web Service Provider field. You can also create a new provider by clicking .
Note When you create a new SOAP Provider from Template wizard:
- The field Publish as will not be available and by default, the SOAP Provider will always be published as a Template.
- By default, the SOAP provider will be created in a published state.
Select the SOAP operation corresponding to the selected provider.
Tip The list displays all the available operations corresponding to the selected provider. The operations which have already been used in other templates will be grayed out.
- Click Next.
Select the Apply Security Policy check box.
Note This screen appears only when you have selected Webhook type as Simple. - Select a pre-defined security policy in the Select Security Policy to apply field. You can also create a new security policy by clicking .
- Click Next to complete the steps that follow to create the template.
Note |
---|
These two options are available only when the template is in active state and Webhook type is Simple. |
Info | |||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Below are the examples of a Webhook URL and the location of WSDL file associated with that Webhook.
The table below explains the components of this URL for different cases:
|
Panel | ||||
---|---|---|---|---|
| ||||
What's newBest practicesTraining guidesFrequently asked questionsAdeptia Connect APIsAdeptia security report |