The SOAP handler interfaces

The SOAP handler has two interfaces with user-written programs: the header processing program interface, which passes information between the SOAP handler and a header processing program; and the application interface, which passes information between the SOAP handler and the target application.

The application interface

Start of changeThe application interface is a channel that is passed between a SOAP handler and the target application program when it is invoked with a channel interface. When the target is invoked with a COMMAREA interface, the channel is not available to the target application program..End of change

The channel (named DFHAHC-V1) used by the application interface passes the following containers:
DFHWS-XMLNS
Contains a list of name-value pairs that map namespace prefixes to namespaces.
  • On input, the list contains the namespaces that are in scope from the SOAP envelope.
  • On output, the list contains the namespace data that is assumed to be in the envelope tag.
DFHWS-BODY
Contains the body section of the SOAP envelope. Typically, the application will modify the contents.
DFHNORESPONSE
In the request phase of a service requester pipeline, indicates that the service provider is not expected to return a response. The contents of container DFHNORESPONSE are undefined; message handlers that need to know if the service provider is expected to return a response need only determine if the container is present or not:
  • If container DFHNORESPONSE is present, then no response is expected.
  • If container DFHNORESPONSE is absent, then a response is expected.
The channel also passes all the context containers that were passed to the calling message handler. A header processing program may add containers to the channel; the added containers are passed as user containers to the next handler in the pipeline.