The <terminal_handler> element
Contains the definition of the terminal message handler of the service provider pipeline.
Used in:
- Service provider
Contained by:
- <service> element
Contains:
One of the following elements:
- <handler>
- <cics_json_handler_java>
- <cics_soap_1.1_handler>
- <cics_soap_1.2_handler>
- <cics_soap_1.1_handler_java>
- <cics_soap_1.2_handler_java>
If you expect your pipeline to process both SOAP 1.1 and SOAP 1.2 messages, you must use either the <cics_soap_1.2_handler> or <cics_soap_1.2_handler_java> element.
Remember: In a service provider, you can specify the <cics_soap_1.1_handler> and <cics_soap_1.2_handler> in
the <service_handler_list> element, as well as
in the <terminal_handler> element. However, in
a service provider, you can only specify <cics_soap_1.1_handler_java> and <cics_soap_1.2_handler_java> in
the <terminal_handler> element.
Example
<terminal_handler>
<cics_soap_1.1_handler>
...
</cics_soap_1.1_handler>
<service_handler_list>

Example: Enabling non-Java processing of JSON messages
To enable non-Java processing of JSON messages, specify the terminal handler program as DFHPIJT:
<terminal_handler>
<handler>
<program>DFHPIJT</program><handler_parameter_list/>
</handler>
</terminal_handler>
Note: When you use DFHPIJT as the terminal handler,
do not define an application handler in the pipeline configuration file, that is, the pipeline
configuration file should not contain an <apphandler> element. If an application
handler is specified, it is not invoked.
