10 Steps to Building an Interface

10 Easy Steps to Building an Interface

Point, Click, Drag N’ Drop Your Way to Systems Integration with the Enterprise Integration Console (eiConsole)

The rapid creation of end-to-end interfaces is supported in the eiConsole following an “Assembly Line” approach using a combination of configuration screens, an intuitive Data Mapper and File-to-XML Editor.

Step One: Select the Interface
The eiConsole Route File Management Screen (Example 1 below) provides a single place from which to manage all of a company’s interfaces. When an existing interface is selected, or you click “New,” a graphical representation (Example 2 below) of that end-to-end interface is presented with all of its configurable components. Components of the interface include the Source System, Listener, Source Transform, Route, Target Transform, Transport, and Target System.

Route File Management Screen

Example 1. Route File Management Screen

Route File Management Screen in PilotFish eiConsole

Example 2. Main Route (Interface) Configuration Screen

Step Two: Identify the Source System
Click the “Source System” icon and fill in descriptive information about the system outputting the interface data. This information is user-defined and might include the system name, system owner, format type, etc. Later, this information can be used to search for interfaces maintained in the eiConsole.

Step Three: Configure B2B Connectivity (Listener)
Click the “Listener” icon (Example 3), select a Listener from the drop-down list, and fill in the configuration information for the type of Listener selected. All of the popular Listeners are supported, including Database Table, Directory, Email (POP3), Encrypted FTP, FTP, HTTP Post, JMS, Programmable Java, and SOAP Web Service. You can also configure Processors at the same time; for example, you may want to add a decryption processor from the list of those available.

Configure the Listener or Source System of the Route

 

Example 3. Configuring B2B Connectivity

Step Four: Map the source data to the common XML standard
The eiConsole supports data transformation using a point, click, drag, and drop visual interface. Clicking the “Source Transform” icon presents you with two powerful eiConsole components to enable the transformation of the data format output from the Source System into the common XML standard format. These are the File-to-XML Editor (File Specification Editor) and the Data Mapper.

The File-to-XML Editor lets you import sample data formats and data from the Source System into the File Spec Editor, where it can be visually edited. By clicking “Save,” the incoming interface format is converted to a generic XML format – the first stage in the transformation process.

Map Source Data to Common XML Format

Example 4. File-to-XML Editing

The Data Mapper is then used to generate the XSLT necessary to transform the generic XML format into the industry-standard XML format. This is accomplished by dragging corresponding fields from the Source schema (left column with blue nodes) and the industry standard schema (right column with green nodes) to a visual map in the middle. Constant values, expressions, tabular mappings, and Java extensions are also supported through the drag-and-drop interface.

Data Mapper is Used to Generate XSLT

Example 5. Data Mapper Screen

Specific time-saving features of the Data Mapper Include:

  • An import feature that lets you read in the Industry schema and its associated Metadata when available (for Example ACORD Schema) directly into the Data Mapper thereby eliminating the need to search external sources for documentation necessary for the data mapping process.
  • An import feature that lets you directly import Excel spreadsheets and flat file definitions including associated documentation. No time consuming and tedious custom programming is required.
  • Templates for a wide variety of transactions (see Products & Pricing for full list) are included saving thousands of hours that would be spent reviewing implementation guides and custom defining transactions.
  • The “import XML format as template” feature lets you automatically load a sample of the Source or Target XML into the Data Mapper making transformations to the desired XML format a simple “drag & drop” exercise.
  • Support for mapping recursive elements (for example, multiple Parties differentiated by Role) eliminates the confusing and error-prone process of drawing connecting lines with ambiguous annotations.
  • All of the potentially thousands of codelists can be automatically imported and mapped with an intuitive Tabular Mapper saving thousands of hours.

An integrated schema maintenance component allows users to easily manage internal canonical models, derivations of industry standards, and upgrades to new releases of Standards. There are dozens of other features that simplify the entire mapping process. XPath functions are available in the XPath functions tab (Example 6). A set of macros make it very easy to do common mapping tasks. The Notes tab under the Source or Target tree can be used to annotate any field or structure within the Source or Target formats. This can be useful for tracking questions or documentation provided by a Trading Partner, Business Analyst, etc.

XSLT and XPath Options

Example 6. XSLT Structures and XPath Tab Options

The Data Mapper can also be used to document the Source and Target formats, as well as to extend those formats.

Under the covers, these mappings are represented as W3C – compliant XSLT. The XSLT can be viewed by clicking on the XSLT view tab. The XSLT is fully editable. The editing view includes code completion, and any changes made here will be immediately reflected back on the graphical mapping tab.

Step Five: Name the Route (Interface)
Click the “Route” icon and give your route (or interface) a name, and as much other user-defined information about the Route as you like. You can also specify that Transaction Logging should occur for the production interface by clicking a checkbox.

Step Six: Map the common XML standard format to the format of the Target System
Clicking the “Target Transform” icon will again present you with the File Specification Editor and the Data Mapper. This time, however, the purpose is to transform the industry-standard XML format to the format of the Target System. If the Target System is capable of accepting the industry-standard XML, simply click the “Use Direct Relay” checkbox.

Step Seven: Configure the Transport
Click the “Transport” icon, select a Transport method from the drop-down list, and fill in the configuration information for the type of Transport selected. Transport types include delivery to a Database Table, Directory, Email (SMTP), Encrypted FTP, HTTP Post, JMS, SOAP Web Service, and programmable Java.

Configure Transport in the Route Configuration

Example 7. Transport Configuration Screen

Step Eight: Identify the Target System
Click the “Target System” (Example 8) icon and fill in descriptive information about the system receiving the interface data. This information is user-defined and can be used later to search for interfaces maintained in the eiConsole.

Identify the Target in the Route

Example 8. Target System Screen

Step Nine: Test the interface
Feed sample data to your local copy of the newly created interface and step through all of the components you have configured for the receipt, transformation, and delivery process to test the interface. Test (Example 9) any stage in the process and review test results.

Test the Interface

Example 9. Testing Screen

Step Ten: Deploy the interface to the eiPlatform server
Click “Commit Route, ” and your interface will be uploaded to the eiPlatform server using a secure web service.

That’s all there is to it! Your interface has been built and deployed into production in less than 1/20th the time previously possible!

BACK TO >> IDE INTEGRATION

This is a unique website which will require a more modern browser to work! Please upgrade today!