271 from BackEnd Route

This route retrieves a 271 transaction from the back-end system and processes the data. The route validates the data and generates an LDNS report that is later used by the Visualizer Server. The route attempts to remove the original 270 transaction that was saved in XEServer Data Storage (in 270 to BackEnd Route) and depending on the results, the route sends data to the corresponding outbound destination.

Route Structure

Route Components Description

Component Name	Component Type	Description
From Back End 271	JMS Inbound	Scans the queue 271_From_Back_End for new messages.
Validate 271 Response	XE Native	Validates data, generates LDNS reports, and sets the XEServer property ErrorCount271 on the original output.
Archive Reports	FS Outbound	Stores the LDNS reports on the file system.
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.
Validation Ok?	Router	Passes only the 271 response transactions that have passed the XEngine validation and have the property ErrorCount271=0.
Remove original 270	Data Storage Inbound	Attempts to remove the 270 transaction that was saved by the route 270 to BackEnd from the XEServer Data Storage. The component sets the XEServer property ItemsRemoved that holds the count of items removed from the data store.
Is removed?	Router	Passes transactions through the output data only if the 270 transaction has been successfully removed from Data Storage (have the property {Prp[ItemsRemoved]} != '0') in the previous step.
271 to Client	JMS Outbound	Pushes the transaction to the ResponceToClient JMS queue.
Save Expired 271	FS Outbound	Stores the expired 271 response transactions.