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, you have an option to create and use a SOAP Webhook according to your need in Adeptia Connect. You can use your own WSDL file to create a Webhook before or during the creation of a template.
If you have already created a Webhook using your WSDL file and publish 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 even when you are in the middle of creating a template.
Follow the steps below while you define the source application as 'SOAP WebHook' in a template.
For steps previous to the one being discussed below while creating a template, refer to Creating a Template.
- Select SOAP WebHook as a source application.
- Select the Webhook type as Simple or Advanced.
- Simple Webhook type will work as it was working before.
- Advanced Webhook type allows you to define a custom WSDL and other SOAP Properties to create a SOAP Provider.
- When Advanced configuration is selected:
- Select a pre-defined SOAP Provider from the drop-down list of Select Web Service Provider. You can also create a new provider by clicking .
- Only the WS Providers whose type is 'Webhook' is shown in Selection list. (Standalone providers wont be available for Selection).
- Select the SOAP operation corresponding to the Selected provider. (The list of all WSDL operations would be shown but only that operations will be available for selection which are not currently used in any other template. Already used operations will be greyed out.)The Security settings substep will be removed as the Security policy is now part of WS Provider activity.
- While creating new WS Provider the existing AIS provider interface will be presented.
- The provider interface now contain the radio selection to define the Provider type as 'Standalone Provider' or 'Webhook Provider'.
- This radio button will be hidden while creating WS Provider from template and by default Webhook will be selected.
- This radio button will be visible on Provider GUI when provider is created from Manage Objects page.
- The provider interface now also contain the radio selection to mark the provider execution as Sync or Async
- When Provider is of Webhook type then configuration to select the Process flow for the WSDL operations will be hidden as the process flow is already determined to be underlying process flow into which webhook is used.
Key Decisions
- The template is limited to single operation. Multiple templates can be created corresponding to each operation.
- The combination of Provider and its specific operation is unique across all the templates. That means a provider can be used in multiple templates, but the Provider and selected WSDL operation combination can't be repeated for any template.
- Sync or Async attribute will be defined at provider level instead of request level. However for existing Simple webhooks the sync attribute will continue to be supported at request level for backward compatibility.
- Sync or Async attribute is only applicable for Wehhook type Providers not for standalone providers.
- Provider would hold the template Ids. For each operation there would be a separate template. Every time the specific operation is used in template the Provider activity is updated with Template Id of that template. The provider activity can hold multiple Template Ids corresponding to each operation.
- For advance webhooks the security policy is the part of WS Provider but for simple webhooks the security policy is separately configured. For simple webhooks only the Basic Authentication is supported. For Advance webhook all the security configuration supported by WS provider would be supported.