Step 4 Expiration 277_E2 Processing Route

The route makes a query to the Data Storage after the specified delay. If there are data items available in the Data Storage, the route extracts the data and sends it to the next processing step (Step 5 Generate 277_E2 Timeout Response route) to generate the timeout response. If there are no data items in the Data Storage, this indicates that the back end has already returned the result.

Route Structure

Route Components Description

Component Name	Component Type	Description
Expiration Processing	FS Inbound	Receives 277 data from the route Step 2 Validate 276.
Clear Body	Velocity	Clears the XEServer message body using the template ClearBody.vtmpl that is available in the directory ${XESProfileConfig}/artifacts.
Delay	Delay	Emulates a processing delay. The delay is specified in the XEServer system variable ${ProcessingTimeout}.
Get Request	Data Storage Inbound	Queries the XEServer Data Storage for 276 data items using the Correlation XEServer property. If the Data Storage returns a 266 data file, the component forwards it to the route Step 5 Generate 277 E2 Timeout Response. If no 266 requests are detected in the Data Storage, this means that the back end has already received the response (an acknowledgement). The component sets the XEServer property Exists276 that holds the number of data records returned from Data Storage.
Exists in DS	Router	Sends through only the messages with the property Exists276 more than 0.
Body for Exchange	Velocity	Clears Exchange body using the mock template ClearBodyExchange.vtmpl that is available in the directory ${XESProfileConfig}/artifacts
Timeout Response	FS Outbound	Stores the mock message on the file system, initiating the processing on the route Step 5 Generate 277 E2 Timeout Response.