![[Note]](../images/admons/note.png)
|
Note |
|---|---|
|
The export / import functionality described below will be available from version 0.2 on. |
|
The application uses the openadaptor™ Framework (http://www.openadaptor.org) as the provider for their Import / Export functionality. There are internal Sinks (see Section 6.1, “ openadapter Framework”) defined for the file system and for an JMS server.
At the moment following functionality is provided by this subsystem:
-
Import of travel items from an PDA (Palm)
-
... others are pending
|
|
Note |
|---|---|
|
All the description and example pictures in this section are used from the Open Adapter documentation. They are just used to give a rough overview of this framework. All rights are reserved byopenadapter™. |
|
Theopenadapter™ framework is a message-based system integration toolkit. System integration work can be as simple as processing a file or as complicated as building real-time feeds between systems.
The framework abstracts the process of sending messages between systems (or transports). It provides a framework of "ready built" components that can be quickly assembled to integrate systems (by using simple configuration files rather than by writing actual program code).
The framework currently allows for the construction of adaptors (this framework will also be extended to allow for the construction of message-based services and gateways).
An adaptor is a one way link between one or more origins and one or more destinations. The origins and destinations could be many different things, e.g., flat files, TCP/IP sockets, databases, specific system APIs, middleware, RMI services, JMS queues, etc.
The different stages of the work required to send a message is illustrated below:
An adaptor is a single process - each Source component is run as a separate thread of execution. Below are examples of very simple adaptors:
