Back End Emulation Route

The route emulates a back-end system. The route receives a 270 transaction, splits the transaction into dependent and subscriber parts and translates the transaction to a 271 transaction with the help of a Velocity component.

Route Structure

Route Components Description

Component Name	Component Type	Description
JMS Inbound	JMS Inbound	Scans the queue 270_To_Back_End for new 270 transactions.
Delay	Delay	Emulates a delay. The delay is specified as an XEServer environment variable ${BackEndEmulationResponseDelay}.
Native Processing	XE Native	Validates and splits the 270 transactions based on whether the inquiry is for a Subscriber or a Dependent. For each transaction, the component sets a number of XEServer properties (see component's Outputs tab). Later, on the route, these properties are used to generate a 271 response by the route component Velocity.
271 Subscriber, 271 Dependent	Velocity	The components generate 271 response transactions using the templates from the folder ${XESProfileConfig}/templates and the XEServer properties set by the route component Native Processing.
271 From Back End	JMS Outbound	Pushes the 271 responses to the 271_From_Back_End queue.