The jETI Technology


jETI's integration philosophy addresses the major obstacle for a wider adoption, as identified during seven years of experience with tool providers, tool users and students: the difficulty to provide the latest versions of the state-of-the-art tools. The tool integration process required on dedicated jETI servers was too complicated for both the tool providers and the jETI team, making it impossible to keep pace with the development of new versions and a wealth of new tools. jETI's new remote integration philosophy overcomes this problems, because it replaces the requirement of 'physical' tool integration by a very simple registration and publishing. This allows the provision of tool functionalities in a matter of minutes. Moreover, whenever the portion of a tool's API which is relevant for a new version of a functionality remains unchanged, version updating is fully automatic!

jETI ArchitectureArchitecture

The realization of this registration/publishing-based integration philosophy requires the implementation of four components:

  1. a HTML Tool Configurator, which allows tool providers to register a new tool functionality just by filling out a simple template form,
  2. the Component Server, which (a) automatically generates appropriate Java classes, from these specifications and (b) organizes all the registered tool functionalities, including the corresponding version control,
  3. the jETI client, which automatically loads the relevant Java classes from the Component Server and provides a flexible Java development environment for coordinating the so obtained tool functionalities. Many different types of clients are available, e.g. for jABC or now also for Ricoh's Aficio printer series.
  4. a Tool Executor, which guarantees the correct and efficient execution of the specified tools at the tool providers' site.

jETI WebservicesWeb Service Ready