IPF Runtime 2.0.0.m2

Added by Boris Stanojevic, last edited by Boris Stanojevic on Oct 14, 2009  (view change)

Downloads

Eclipse update site

You can install this release from the following Eclipse update site

http://repo.openehealth.org/sites/ipf-tools/runtime/updatesites/releases/2.0.0.m2/

Standalone Runtime

File Content
IPF-Runtime-2.0-m2.zip
  • System bundle and the configuration admin service from the Equinox 3.5.0 distribution
  • Fileinstall bundle from Apache Felix as interface to the configuration admin service
  • A subset of IPF bundles sufficient to run the OSGi tutorial on Equinox
  • All required external dependencies
  • Configuration .ini file
  • Startup scripts

Release notes

Feature Overview

Currently, the OSGi-based IPF runtime only support a subset of the IPF 2.x features. Extending the IPF runtime to support all IPF features in an OSGi environment is work in progress.

Feature Description
Apache Camel IPF is based on Apache Camel. For an overview of Camel's rich feature set (which can be fully used in IPF applications) refer to the project's integration patterns and integration components pages.
OSGi support Enables the deployment of IPF components (bundles) to OSGi platforms. IPF service bundles register platform services at the OSGi service registry for consumption by IPF applications. Extender bundles control the activation of DSL extensions inside an OSGi environment. A reference implementation of IPF on top of Eclipse Equinox is available as IPF runtime.
Groovy scripting layer With IPF you define integration routes with the Groovy programming language. It is more than a mere usage of Camel's domain-specific language (internal DSL or fluent API) inside Groovy: Camel's native DSL has been extended to support e.g. the usage of closures (for inline definitions of message processors, routing rules etc.) and also provides a DSL extension mechanism to define custom extensions to the Camel DSL.
DSL extension mechanism The DSL extension mechanism is a Groovy meta-programming-based mechanism for defining new DSL elements to be used in integration routes. This is especially useful if you want to provide custom language elements for re-occurring message processing patterns or if you want to design a project-specific message processing DSL (e.g. one that is related to the HL7 domain).
Core features These are domain-neutral message processors and DSL extensions usable for general-purpose message processing. The core features also enhance existing Camel DSL elements for usage with Groovy-specific language elements such as closures. For XML message processing there is special Groovy XML support.
HL7 message processing Basis for HL7 message processing is the HL7 DSL, the HAPI extensions and the HL7 validation DSL. These provides the basis for implementing HL7 message processing routes.
Flow management A platform service to monitor, query, audit, replay and cleanup message flows. The management interfaces are based on JMX.
Quality of service IPF provides extensions, guidance and solution blueprints (code examples) for implementing non-functional requirements. Covered topics are transactional messaging, flow management, load-balaning and high-availability.
Module adapters An infrastructure for including platform-independent message processing libraries into platform-specific message processing routes. An alternative is Camel's bean integration mechanism.

Documentation

Reference manual

Tutorials

Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.