eiConsole v.24R1
Tutorial & Working Directory

eiConsole Tutorial – Topology

Configuration Using Transaction Attributes

Note: The Quick Start and Foundation tutorials should be completed before proceeding with the Topology Tutorials.

Overview

This interface tutorial demonstrates how the eiConsole utilizes 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 requires a complex filename based on the data
• An HTTP Post transaction needs to write to different URLs depending on the incoming data
• An email 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 depending on the data

Before You Begin

Configuration Using
Transaction Attributes
Working Directory

Download the Configuration-Using-Transaction-Attributes-Working-Directory.zip file with the sample Working Directory and unzip it on your computer to a convenient place. In our case, it’s c:\Users\{USER _NAME}\PilotFish eiConsole Working Directories\Configuration Using Transaction Attributes where {USER_NAME} is the user’s name.

Open the eiConsole, browse to your Simple route directory, and open it. The fully configured route (Using Transactions Attributes for Structured Configuration Parameter) is included in the working directory. Your Route File Management screen will open, as shown below.

Next, follow the tutorial and walk through it step-by-step.

Double-click on the Using Transaction Attributes for Structured Configuration Parameter route.

The Main Route Grid will open. This interface has two functioning pieces; the Listener and the Transport.

Listener Configuration

The Listener polls a directory set by a configuration value stored in the environment properties file (included with this interface) every 5 seconds. The sample file (Sample.xml) intended to be used with this interface is provided in the c:\Users\{USER _NAME}\PilotFish eiConsole Working Directories\Configuration Using Transaction Attributes\data directory.

The polling directory is c:\Users\{USER _NAME}\PilotFish eiConsole Working Directories\Configuration Using Transaction Attributes\in. In our case, we use the relative path “..\..\in“.

Transport Configuration

The directory transport configuration doesn’t look too remarkable from this view; click on the eye icon to the right of the configured file name.

You will see what it is doing.

Looks a little more interesting here, right? If you did the previous tutorial, you’d recognize this as our OGNL Expression Constructor, our tool for building OGNL expressions. This configuration concatenates the file extension with the file name – “Sample.xml” which will be written as “Samplexml”. This was intentional. You can try to use this expression:

getAttribute('com.pilotfish.FileName') + getAttribute('com.pilotfish.FileExtension')

Any Java function may be used here, as well as string concatenation; this particular output configuration, for example, lacks a period between the file name and file extension. It’s relatively simple to add this; the configuration becomes:

getAttribute('com.pilotfish.FileName') + '.' + getAttribute('com.pilotfish.FileExtension')

And the example interface will generate “Sample2.xml”. Or you can get the same result by moving the second getAttribute to the file extension configuration – Target file extension.

The prepopulated transaction attributes are simply those attributes that the eiConsole expects to be available; if you’ve created your own attributes which don’t show up, it’s relatively easy to use them here. Write “getAttribute(‘[attribute name]’), as seen here.

Go into the Testing Mode.

Then put the Sample.txt file found in c:\Users\{USER _NAME}\PilotFish eiConsole Working Directories\Configuration Using Transaction Attributes\data into the polling directory c:\Users\{USER _NAME}\PilotFish eiConsole Working Directories\Configuration Using Transaction Attributes\in.

Then click Execute Test.

The files Sampletxt should be in directory c:\Users\{USER _NAME}\PilotFish eiConsole Working Directories\Configuration Using Transaction Attributes\out.

This concludes the demonstration of using attributes in complex configurations.