835 Outbound Sample Profile Workflow

This sample profile batches 835 transactions by the Line of Business (LOB) based on the Scheduler Batching Strategy.

Step 1. The profile picks up a data file with 835 transactions, validates the data, and splits the file into individual transactions. In this step, the profile extracts the value of the LOB for each valid transaction.

Step 2. The profile converts all the valid transactions to the XData format and stores them in the Batcher Outbound storage. The Batcher service uses the LOBs extracted on the previous step as the Batch Group Correlation IDs.

Step 3. When the Batcher Completion condition is met, the Batcher Inbound component activates and streams the items out from the storage.

Step 4. The profile extracts the items from the Batcher Inbound in the form of zip archives for easier transmission and handling. Unzips the received items and aggregates the results by LOB into a multimessage exchange.

Step 5. By using the batch mode, the XData Processing component converts data into the native format, combining similar (with the same LOB) XData transactions into a single native result.

Step 6. Stores the conversion results in the File System component Results. Each folder in Results represents a separate LOB – particularly, the Payee Name.

The Batcher Completion condition uses a Scheduler Batching Strategy named 835Processing. This strategy defines the rule (to batch every minute) and the system identifies the moment when the data storage is ready for the batching session.

This profile has the following routes:

This route picks up a batch file with 835 transactions, validates the data, and splits the file into individual transactions. Then, the route extracts the value of Line of Business (LOB) for each valid transaction by using the data node macro {DN[dns.fnm.Transaction.prp.PayeeName]}. The route converts all valid transactions to the XData format and stores them in the Batcher Outbound storage. The LOBs are used as Batch Group Correlation IDs.

Route Structure

1 Split and Batch Mode

Route Components Description

Component Name Component Type Description
FS Inbound FS Inbound Picks up a batch of 835 transactions from the file system.
Split & Validate Original XE Native Validates and splits the inbound data file by transactions using the split rules file DataSplitRules_Transaction.xml that is available in the directory ${XESProfileConfig}/artifacts/splitrules. The component extracts the LOBs by using the data node macro {DN[dns.fnm.Transaction.prp.PayeeName]} and generates an LDNS report.
Bad Transactions FS Outbound Stores bad transactions on the file system.
Convert to XData XE Native Converts all valid transactions from the native format to the XData format.
Checkpoint Checkpoint Saves the interim data state. If an error occurs during the task processing, the task restarts from this point as many times as defined by the parameter Retry limit in the settings of the component.
Batcher Outbound Batcher Outbound Stores all the XData files with LOBs used as Batch Group Correlation IDs.

When the Batcher meets the Completion condition, the Batcher Inbound component activates and streams the items out from the storage. The route extracts the items from Batcher Inbound in the form of zip archives for easier transmission and handling. Then, the route unzips the received items and aggregates the results by LOB into a multimessage exchange. By using the batch mode, the XData Processing component converts data into the native format, combining similar (having the same LOB) XData transactions into a single native result. Finally, the route stores the conversion results on the file system (route component Results). Each folder in Results represents the separate LOB – particularly, the Payee Name.

Route Structure

2 Batch Out Route

Route Components Description

Component Name Component Type Description
Batcher Inbound FS Inbound Streams the accumulated items out from the storage when the completion condition is met. The component extracts the items in the form of the zip archives. The Batch expiration occurs if a Batch Group remains in the open state for longer than specified in the expiration timeout settings.
Checkpoint Checkpoint Saves the interim data state. If an error occurs during the task processing, the task restarts from this point as many times as defined by the parameter Retry limit in the settings of the component.
UnZip Batches Unzip Unzip the transactions.
Aggr by LOB Aggregation Aggregates files by LOB into an XEServer multi-message exchange.
Batching by LOB XData Processing Converts data to the native format in the batch mode combining XData transactions with the same LOB into one file.
Results FS Outbound Stores the results in folders that represent the unique LOBs, in this scenario - the Payee Name.
Reports FS Outbound Stores reports on the file system.