2 Sample Route

This route receives data from the 1 Client Route and performs dummy processing using the Mock component that emulates a real-life processing phase. The route sends back the results of the processing to the client through the JMS queue if there are no errors (errors are simulated using XEServer environment properties).

If there is an error during the transition of the message through a queue, the Error Channel Inbound component catches this error and sends the data to 3 Validate Error Route. The route ValidateError decides what to do next with the message, and the options are the following:

  • store the message in Data Storage,
  • make another attempt to re-deliver the message to the client,
  • or store the message in the Data Storage as a Not Specified error.

Route Structure

This route includes two major flows.

2 Sample Route

Route Components Description: Flow 1

Component Name Component Type Description
Inbound FS Inbound Receives data from the 1 Client Route through the SampleRoute queue.
Sample Route Mock Performs dummy processing on the data received using the template 837.dat that is available in the directory ${XESProfileConfig}/artifacts.
JMS NO Error Router

Checks the XEServer environment property ${JMS_Primary--JMS_Good_Enabled_and_JMS_Bad_Disabled} and forks the data flow depending on whether a transport error should be emulated.
Primary Good, Primary Bad JMS Outbound Sends the processing results to 1 Client Route through the ResponseToClient queue. The combination of JMS Primary Good, JMS Primary Bad and the Router JMS NO Error emulates the work of a single JMS component in the Error or No Errors mode based on the value of the XEServer environment property ${JMS_Primary--JMS_Good_Enabled_and_JMS_Bad_Disabled}.

Route Components Description: Flow 2

Component Name Component Type Description
Error Channel Inbound Error Channel Inbound Catches all the messages that caused errors and sends these messages to the failed output. Also the component stores the error details as XEServer properties.
Stored in DS FS Inbound Picks up data from the 4 Error DS Check and the 5 DS Retry routes.
ValidateError Subroute

Submits data to 3 Validate Error Route.
To Store in DS FS Outbound Stores messages from 3 Validate Error Route that should be stored in the Data Storage on the 4 Error DS Check Route.
To Retry FS Outbound Stores messages from 3 Validate Error Route that should be submitted once again on 6 Response Retry Route.
Msg Stored DS Router Determines the location of the error data in Data Storage (either primary or secondary) by checking the XEServer message property Storage.
Primary, Secondary Data Storage Inbound The components extract data from the Data Storage using the XEServer property REPLAY_ID. This property is set on the Flow 1 after the route receives data from 1 Client Route.
Not Specified Error FS Outbound Stores data in the directory ${XESWorkspace}/test-data/outbound/Archive/NotSpecified_Error.