Micro Focus Enterprise Developer 2.3 Update 2 for Eclipse > Deployment > Configuration and Administration > Enterprise Server configuration and administration > User Exits for Request Handlers > User Exit Points Provided

User Exit Points Provided

The following diagram shows the interaction between request handlers, the application container and the run-time interface mapper.

Figure 1. Request Handler Exit Points

The user exit points are indicated by squares numbered from 1 through 9. The table below gives the name and purpose of the exit points.

Number	Name	Description
1	External data value modification – input parameter	Enables you to modify the external data value specified in a client request before the request handler’s default mapping for the parameter occurs. This exit point is invoked for each external-to-internal input parameter mapping that is specified in the IDT.
2	Internal data value modification – input parameter	Enables you to override the internal data value created by the request handler’s default mapping for a parameter. This exit point is invoked for each external-to-internal input parameter mapping that is specified in the IDT.
3	Unmapped named external input parameter	Enables you to provide processing of any input parameters that do not have associated input parameter mappings defined in the IDT. This exit point is invoked for each unmapped named input parameter.
4	End of input request processing	Enables you to set up parameter values other than the external parameters specified in the client request. It also provides the opportunity for any resources allocated in exit points 1 through 3 to be released.
5	Start of response processing	Enables you to bypass completely the default mapping used to build a client response. The exit program is responsible for the creation of the response that will be sent back to the client by the application container.
6	Internal data value modification – output parameter	Enables you to modify the internal data value as created by the user application before the request handler’s default mapping for the parameter occurs. This exit point is invoked for each internal-to-external output parameter mapping that is specified in the IDT.
7	External data value modification – output parameter	Enables you to override the external data value created by the request handler’s default mapping for a parameter. This exit point is invoked for each internal-to-external output parameter mapping that is specified in the IDT.
8	End of response processing	Enables you to modify the response generated by the default mapping.
9	End of request processing	Enables you to release any resources that were allocated in exit points 1 through 8.