PilotFish Interface Exchange (PIE)

A marketplace for eiConsole (IDE) interface templates, components and industry bundles
eiConsole IDE 90-Day Free Trial!
Prerequisites
The eiConsole IDE is highly recommended to support graphical development of interfaces for deployment to the eiPlatform runtime The eiPlatform is required to run in production interfaces configured using the eiConsole
Version
1.1
Release Date
June 10, 2016
Resource Type
Interface

Product details

AIE: Underwriting Requirements - Carrier

This interface contains 4 routes:

  1. AIE - Send TX 121 Using AIE Transport
  2. AIE - Send TX 121 Using AIE Sender Processor
  3. AIE - Handle 121 Response
  4. AIE - Error Route

AIE - Send TX 121 Using AIE Transport:

This route picks up a file from a directory and sends it through the AIE using an eiPlatform transport. The transport then passes the response to the Response Handler route.

AIE - Send TX 121 Using AIE Sender Processor:

This route picks up a file from a directory and sends it through the AIE using an eiPlatform mid-route processor. The route then passes the response to the Response Handler route.

AIE - Handle 121 Response:

This route is triggered by either the AIE Transport or AIE Sender Processor route. It takes the response data and simply writes it to the local file system.

AIE - Error Route:

This route is triggered if any error occurs during a routes progress. Errors are written to the local file system.

Instructions:

  1. In the eiConsole, navigate to the working directory which contains the AIE_Underwriting_Requirements_Carrier interface.
  2. In the edit menu, select the Local eiPlatform Emulator.
  3. In the emulator, hit the Configure Emulator button and make sure only the routes inside the example interface have 'run' checked. Make sure to only have either the Using AIE Transport or Using AIE Sender Processor selected (not both) so that it can be determined which route is sending to the AIE.
  4. In a system file explorer, navigate to the ../working directory/AIE_Underwriting_Requirements_Carrier/data directory. Here you can see the results of the routes. If successful, there will be a file called 'response.xml' under the ../data/responses directory. If there was an issue, details of said issue will be in the ../data/errors directory.
  5. If you wish to send a different file than the one provided in the ../data/out directory: replace the test.xml with your version of the 121 gold standard.

Release Details

First Release