The <transport> pipeline configuration element
Specifies handlers that are to be invoked only when a particular transport is in use.
Used in:
- Service provider
- Service requester
Contained by:
<provider_pipeline>element<requester_pipeline>element
Contains:
In a service provider:
- An optional
<default_transport_handler_list>element - An optional
<default_http_transport_handler_list>element - An optional
<default_mq_transport_handler_list>element - Zero, one, or more
<named_transport_entry>elements
In a service requester:
- An optional
<default_target>element. The<default_target>contains a URI that CICS uses to locate the target web service when the service requester application does not provide a URI. In many cases, however, the URI of the target will be provided by the service requester application, and whatever you specify in the<default_target>will be ignored. For example, service provider applications that are deployed using the CICS web services assistant normally get the URI from the web service description. - An optional
<default_http_transport_handler_list>element - An optional
<default_mq_transport_handler_list>element - An optional
<default_transport_handler_list>element
If any of the configuration elements are used, they must be used in the sequential order that they are listed.
Example
<transport>
<default_transport_handler_list>
...
</default_transport_handler_list>
</transport>