Submit Search

Step 2 Validate 276 Route

The route receives individual 276 transactions from the Step 1 Client Emulation Route. If the 276 data file fails to pass XEngine validation, the route generates an acknowledgement and sends it to the Step 1 Client Emulation Route and no other processing takes place. If there are no errors in the received 276 data file, then the route:

Puts the 276 data file in the XEServer Data Storage.
Sends the 276 data to the backend emulation (Step 7 Back End 277_Good Emulation route).

At the same time, XEServer activates the time expiration mechanism (Step 4).

If the 276 data file yields no errors, the route creates no acknowledgements.

Also the route stores 276 LDNS, 276 data, and 276 acknowledgement files in the Archive. Then, the route sends the generated acknowledgements (if any) and the 276 LDNS reports to Visualizer (Step 8).

Route Structure

Route Components Description

Component Name	Component Type	Description
RESTful Web Service Inbound	RESTful Web Service Inbound	Receives the 276 data from the route Step 1 Client Emulation.
Validate 276 Transaction	XE Native	Validates the 276 data, generates LDNS reports, and generates acknowledgements if there are errors.
276 LDNS Archive	FS Outbound	Stores the LDNS reports to be archived.
Router	Router	Sends through the XML-formatted LDNS reports.
XML Value Extractor	XML Value Extractor	Extracts the values ReceiverID and SenderID from the LDNS report.
Visualizer Enabled?	Router	Directs the LDNS reports and the acknowledgements to Visualizer Server if the profile-level environment property VisualizerEnabled has been set to true.
To Visualizer	FS Outbound	Stores the LDNS reports and the acknowledgements for further visualization.
Ack Restful	RESTful Web Service Inbound	Returns an acknowledgement to the route Step 1 Client Emulation.
276 Acks Archive	FS Outbound	Stores the acknowledgements to be archived.
Accepted 276	Router	Sends the original 276 data through if no errors occurred during XEngine validation.
Store Request	Data Storage Outbound	Stores the original 276 data in the XEServer Data Storage. Then, the component directs the transaction to the backend (the Step 7 Back End 277 Good Emulation route) and to the route Step 4 Expiration 277_E2 Processing.