Exercise 3.1 - Forking Transactions - Online Resource Center

Purpose:

To practice using forking to split one transaction into several

References:

Create a Route

1. From the eiConsole File Management screen, select the Add Route button.
2. In the dialog that appears, enter the name Forking and select OK.
3. The Route should now appear in the table on the screen. Double-click it to open it.

Document Source System

1. Select the Source System stage in the Route Editing Grid. The configuration panel will appear at the bottom.
2. Change the System Name to Zip File.
3. Select the Choose Source Icon button, and scroll down to select one of the icons with a folder on it.

Configure the Listener

1. Select the Listener stage in the Route Editing Grid. The configuration panel will appear at the bottom.
2. Select Directory / File from the Listener Type selection box. Optionally, click the … button to open the Module Search Dialog, which provides a faster way to find the module you’re looking for.
3. Assign a polling directory, using the … button to open the file selector. The polling directory should NOT be the directory with all the sample files, since files will be moved/deleted by the listening process.
4. Go to the Post-Process tab and select Delete from Postprocess Operation:

Configure the Forking Module

1. Select the Source Transform stage in the Route Editing Grid. The configuration panel will appear at the bottom.
2. Select the Add Format button. In the dialog that appears, enter Zip Forking as the name of the Format, and click OK. The configuration panel will update to provide new options.
3. In the newly expanded configuration panel, there is a tab for Forking. Select it to open the forking panel.
4. For the Forking Module option, choose Unzip Forking from the selection box. No other configuration is required.

Configure the Transport

1. Select the Transport stage in the Route Editing Grid. The configuration panel will appear at the bottom.
2. Select Directory / File from the Transport Type selection box. Optionally, click the … button to open the Module Search Dialog, which provides a faster way to find the module you’re looking for.
3. Select the Target Directory, using the … button to open the file selector.
4. Set zip-output as the Target File Name.
5. Set dat as the Target File Extension.

Document the Target System

1. Select the Target System stage in the Route Editing Grid. The configuration panel will appear at the bottom.
2. Change the System Name to Output File.
3. Select the Choose Target Icon button, and scroll down to select one of the generic File icons.

Prepare to Test

1. In the menu bar at the top, select Mode -> Testing Mode. Make sure the changes to the Route are saved.
2. Copy the file called sample.zip from the Samples directory provided into the directory chosen as the polling directory.

Perform the Test

1. At the top of the Testing Mode screen, select the Execute Test button.
2. If the Route was configured successfully, all the Stages should light up with green checkmarks.
3. Select the Listener stage. In the Test Results table at the bottom of the screen, there should be only a single test transaction shown.
4. Select the Routing stage. In the Test Results table at the bottom of the screen, there should be more than one test transaction shown. This is because the zip file was unzipped and separate Transactions were started for each file within it.

Output Files

Exercise 3.1 – Forking Transactions