PilotFish Interface Exchange (PIE)

Prerequisite

A full or Trial License of the eiConsole (Download a 90-Day Trial Now!). Completion of Level I Training.

Synopsis

This interface demonstrates how the eiConsole can be used to utilize Transaction Attributes to dynamically set configuration values for modules.

Transaction Attribute based Configuration may be used when:

• A file being written needs to use the same filename as a file that was read (Example)
• A file being written needs to use a complex filename based on the data
• An HTTP Post transaction needs to write to different URLs depending on the incoming data
• An e-mail needs to be written to different targets depending on the incoming data
• A database transport needs to change username and password and/or target database dep. on data

Core Concepts:

• Transaction Attributes
• Advanced module configuration
• OGNL

How to Run This Example

You must run from the listener by configuring the attached environmental properties file; any input file will work. It must be run for the listener to avoid an error, as the transport depends upon transaction attributes created by the Directory Listener.

The incoming transaction will be written to disk, using the incoming filename and extension to determine the filename.

How it Works

The relevant configuration is found in the directory transport at the end of the route:

Select the following icon to the right of "Target file name"

to bring up the advanced configuration dialog:

The transaction attributes shown are automatically discovered by the eiConsole; this doesn't necessarily represent the full set of transaction attributes available to you, for example if you're coming from a programmable listener or have created custom transaction attributes using a processor or transformation, but represents those the eiConsole knows may be present.

You may notice that the filename is a simple concatenation of the incoming filename and extension; "Sample2.xml" will be written as "Sample2xml". This was intentional; if desired, an additional concatenation may be added using '.' [i/e, getAttribute('com.pilotfish.FileName') + '.' + getAttribute('com.pilotfish.FileExtension') ] in order to make the example interface generate "Sample2.xml", or the second getAttribute may be moved to the file extension configuration.

Java string functions may be utilized within the OGNL; substrings, regular expression replacements, concatenations - any Java string function may be called directly from the OGNL on the strings produced. Other Java static functions may also be utilized according to the OGNL specification, but that is outside the scope of this demonstration.

How to Use This Example

Download the interface using the Free Download button under the eiConsole Interface logo.

Note: if you are not logged in to the eiConsole, or have arrived at this page via a browser, you will be prompted to login before the interface downloads into your eiConsole "PIE" inbox.

Note: If you have not downloaded and installed a FREE Trial you will have the opportunity to register via a simple process after you click the Free Download button.. Once you are logged in the interface will automatically download into your "PIE" inbox.

Next, download one of the tutorials on this page (from the right column) and walk through it step-by-step. You may check your work against the provided Route (Sample Data).