PilotFish Interface Exchange (PIE)

This interface and related tutorials demonstrate the use of Transformers in Route configurations. In this particular exercise, an existing Route (from "Training - Creating a Simple Route") is modified to transform a Microsoft Excel worksheet to XML and then back to a Microsoft Excel format. More...

This interface and related tutorials demonstrate the use of Processors in Route configurations. In this particular exercise, an existing Route (from "Training - Creating a Simple Route") is modified to Base64 encode files. More...

This interface and related tutorials demonstrates the basics of creating and configuring a simple Route. In this exercise, the Route is configured to pick up a file from one directory and deliver it to another. More...

Synopsis: This interface demonstrates how to utilitize Transaction Attributes when transforming documents in the eiConsole, in this example using the filename of the incoming file. Transaction attribute based transformation may be used when: Data has been stored to a transaction attribute that needs to be utilized in the transformation Data needs to be written from a transformation into a transaction attribute More...

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 More...

Synopsis: This interface demonstrates how to use the eiConsole to separate a single data stream into multiple data streams each based on a subset of the original stream's contents for independent handling and processing. Transaction splitting may be used when: An incoming transaction contains multiple data payloads An incoming transaction needs to have different components processed separately More...

Synopsis: This interface demonstrates how the eiConsole and eiPlatform can be used to interact with an HTTP Webservice which provides a synchronous response. HTTP Request Response Pairs may be used when: A webservice callout needs to be made to acquire additional data A webservice is the final target of a route and the response needs to be recorded More...

Synopsis: This sample interface demonstrates how the eiConsole can be used to perform content-based routing. Content based routing may be used when: Data needs to flow conditionally to one or more target systems. Data should proceed conditionally. Data should process differently according to its contents; for example, when different data versions or data formats originate from the same source. More...