The <apphandler> element
Specifies the name of the application handler that the terminal handler of the pipeline links to by default.
The
<apphandler> element is used when
the terminal handler is one of the supplied SOAP message handlers.
This situation occurs when the <terminal_handler> element
contains a <cics_soap_1.1_handler>, <cics_soap_1.2_handler>, <cics_soap_1.1_handler_java>,
or <cics_soap_1.2_handler_java> element. However,
if your <terminal_handler> element contains a <cics_soap_1.1_handler_java> or <cics_soap_1.2_handler_java> element,
you can use the supplied Axis2 application handler by specifying the <apphandler_class> element
instead of the <apphandler> element. For more
information see the <apphandler_class> element.
However, you must not specify <apphandler_class> and <apphandler> elements
in the same pipeline configuration file. If you deploy your web service applications using the CICS web services assistant, you must
specify one of the following application handlers in the
<apphandler> element.- The supplied application handler DFHPITP if you do not want to process your application handler using Java.
- Your own application handler that uses DFHPITP.
- The name of the PROGRAM resource that you create.
Note: If you are defining a pipeline configuration file to set up a non-Java JSON
service provider, the configuration file should not contain an
For more information about
application handlers, see Application handlers.<apphandler>
element. If an application handler is specified, it is not invoked.Used in:
- Service provider
Contained by:
<provider_pipeline>element
Example
<apphandler>DFHPITP</apphandler>