270 to BackEnd Route

This route handles the 270 transaction processing flow. The route validates the inbound transaction and if a validation error occurs, the route generates acknowledgements (XEngine Selector option). If the 270 transaction is valid, the transaction is sent to the back-end system for further processing. The JMS message that has the arrival time of the 270 transaction is sent to the expiration queue.

Route Structure

Route Components Description

Component Name	Component Type	Description
Inbound 270	JMS Inbound	Picks up 270 transactions from the JMS queue 270.
Validate 270	XE Native	Validates 270 transactions, generates LDNS reports and acknowledgements.
Archive Reports	FS Outbound	Stores the LDNS reports on the file system.
Response to Client	FS Outbound	Stores the processing results (271 responses) from the JMS queue 271.
Visualizer Enabled?	Router	Directs the LDNS reports to Visualizer Server if the profile-level environment property VisualizerEnabled has been set to true.
To Visualizer	FS Outbound	Stores the LDNS reports for further visualization.
Ack to Client	JMS Outbound	Pushes the acknowledgements to the queue ResponseToClient.
Archive Ack	FS Outbound	Stores the acknowledgements on the file system and sets the property DataType=Ack. This property is used on the Visualizer Route to filter data for visualization and tracking.
Accepted 270 filter	Router	Passes 270 transactions that have the property ErrorCount=0.
Save 270	Data Storage Outbound	Stores 270 transactions in the XEServer Data Storage and sets the XEServer property TimeStamp marking the time of the arrival of the transaction.
To Back End	JMS Outbound	Pushes the transaction to the queue 270_To_Back_End.
Expiration template	Velocity	Creates an expiration marker using the template ReplaceMessageBody.tm available in the directory ${XESProfileConfig}/templates.
To expiration flow	JMS Outbound	Pushes the expired transactions to the queue 270_Expiration.