For the list of all supported Decision Insight downloads and releases, see the Downloads page.

Introduction to Data Integration

Data integration in a nutshell

Data integration is used to:

  • Access data from various sources: web services, files, databases... The deployment can pull information from your own data or from other Axway products.
  • Transform this data using splits, filters, transformations, etc.
  • Forward this data to the proper destinations: files, web services or the embedded database.

All these are defined in one or several routes of an Apache Camel context.

URIs

For the sources and destinations it uses a URI-base mechanism using the following schema: component:endpoint?foo=foo&bar=bar

Here are some URI samples:

URI Explanation
timer:foo?period=5000 A timer that triggers every 5 seconds
tnd-absorption:import The calcium mapping named import
log:camel The log4j stream named camel
direct:other The route name other from the same camel context

List of all the components

Expressions

In order to be dynamic, Camel uses expressions which can be:

Expression Description
<constant>Process</constant>

The constant string "Process"

<simple>body[name]</simple>

The value of the name key of the body 

<groovy>com.systar.tau.util.time.TimeUtil.createInstantAtNow()</groovy>
The ReadableInstant that represents now

Route sample

A clock in the logs

<routes xmlns="http://camel.apache.org/schema/spring" xmlns:u="http://www.systar.com/aluminium/camel-util">
    <route>
        <from uri="timer:foo?period=5000" />
        <setBody>
            <simple>Il est exactement ${date:now:HH':'mm':'ss}</simple>
        </setBody>
        <to uri="log:test" />
    </route>
</routes>

Organize your data integration elements

In each data integration screen:

  • A drop-down lists available spaces for the application, except dashboard spaces.
  • When you select a new option from the drop-down, the drop-down list is updated as well as the list of components associated to the selected space is displayed. 
  • When you save a component, it is automatically associated to the space you selected from the drop-down.

Each data integration element can be stored in its own specific space, depending on its purpose.

If the same component is needed for multiple purposes and you don't want to copy it in multiple spaces, then you should store all the elements and their common dependencies in the same space, and prefix elements to ease their management.



Related Links