Used to create, update, delete and browse through plain SOAP channels.
Unlike plain HTTP channels that can accept data in any format, SOAP ones expect it always to be a SOAP XML.
|URL path||A path to mount this channel on. Must be unique in a cluster. URL path and SOAP action must be unique in a cluster.|
|Method||(Optional) An HTTP method that must be used by clients to invoke this particular channel. It can be any string and Zato won’t check if it’s a valid HTTP 1.1 method. Leave empty to allow any method be used.|
(Optional) The expected data format Zato should parse incoming messages as. This will also populate a service’s data_format attribute.
For SOAP channels, this almost always should be set to XML unless your channels are actually using SOAP for conveying non-XML messages.
|SOAP action||SOAP action this channel should be available as. URL path and SOAP action must be unique in a cluster.|
|SOAP version||Currently only version 1.1 SOAP channels are supported. Use a plain HTTP channel with a service which parses SOAP 1.2 itself if you need to expose services through the latter version.|
|Service||Name of an already existing service to invoke for each HTTP request received|
Pick ‘No security’ explicitly to indicate that no such definition should be used. This can be used to expose certain services without any usernames or to indicate that a service will implement a custom security scheme itself.
Deletes the channel from ODB and servers. The channel won’t exist anymore and invoking a URL it was mounted on will return HTTP 404 error.
If a channel is made inactive, an attempt to invoke it will result in an HTTP 404 error.