{toc}
h1. Downloads
h2. Eclipse update site
You can install this release from the following Eclipse update site
{noformat}
http://repo.openehealth.org/sites/ipf-tools/runtime/updatesites/releases/2.0.0/
{noformat}
h2. Standalone Runtime
|| File || Content ||
| [IPF-Runtime-2.0.0.zip|http://gforge.openehealth.org/gf/download/frsrelease/119/784/ipf-runtime-2.0.0.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 |
h1. Release notes
h2. Changes since 2.0.0.m2
||Category||Changes||
|New features| |
|Other| |
h2. Feature Overview
Currently, the OSGi-based IPF runtime only support a subset of the [IPF 2.x features|ipf2:IPF Overview]. Extending the IPF runtime to support all IPF features in an OSGi environment is work in progress.
|| Feature || Description ||
| [Apache Camel|http://camel.apache.org] | 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|http://camel.apache.org/enterprise-integration-patterns.html] and [integration components|http://camel.apache.org/components.html] pages. |
| [OSGi support|ipftools:OSGi support] | Enables the deployment of IPF components (bundles) to OSGi platforms. IPF [service bundles|ipftools:OSGi support#Service bundles] register platform services at the OSGi service registry for consumption by IPF applications. [Extender bundles|ipftools:OSGi support#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|ipftools:OSGi support#Download and installation]. |
| [Groovy scripting layer|ipf2:IPF Scripting Layer] | With IPF you define [integration routes|http://camel.apache.org/routes.html] with the [Groovy|http://groovy.codehaus.org] 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|ipf2:IPF Scripting Layer#Predefined DSL extensions] to support e.g. the usage of closures (for inline definitions of message processors, routing rules etc.) and also provides a [DSL extension mechanism|ipf2:IPF Scripting Layer#DSL extension mechanism] to define custom extensions to the Camel DSL. |
| [DSL extension mechanism|ipf2:IPF Scripting Layer#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). |
| [ipf2: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|http://groovy.codehaus.org/Closures]. For [XML message processing|ipf2:Core features#DSL extensions for Groovy XML processing] there is special Groovy XML support. |
| [HL7 message processing|ipf2:HL7 processing] | Basis for HL7 message processing is the [HL7 DSL|ipf2:HAPI DSL], the [ipf2:HAPI extensions] and the [HL7 validation DSL|ipf2:HL7 validation]. These provides the basis for implementing [HL7 message processing routes|ipf2:HL7 processing#DSL extensions]. |
| [ipf2:Flow management] | A platform service to monitor, query, audit, replay and [cleanup|ipf2:Flow removal] message flows. The management interfaces are based on JMX. |
| [ipf2:Quality of service] | IPF provides extensions, guidance and solution blueprints (code examples) for implementing non-functional requirements. Covered topics are [transactional messaging|ipf2:Quality of Service#Transactional messaging], [flow management|ipf2:Flow management], load-balaning and high-availability. |
| [Module adapters|ipf2:Core features#Module adapters] | An infrastructure for including platform-independent message processing libraries into platform-specific message processing routes. An alternative is Camel's [bean integration|http://activemq.apache.org/camel/bean-integration.html] mechanism. |
h2. Documentation
* [OSGi support|http://repo.openehealth.org/sites/ipf-tools/runtime/manuals/releases/2.0.0/OSGi%20support.html]
h3. Reference manual
* [Exported HTML|http://repo.openehealth.org/sites/ipf-tools/runtime/manuals/releases/2.0.0/IPF%20Runtime%20single.html] (single-page version)
* [Exported HTML|http://repo.openehealth.org/sites/ipf-tools/runtime/manuals/releases/2.0.0/IPF%20Runtime.html] (multi-page version)
* [Exported PDF|http://repo.openehealth.org/sites/ipf-tools/runtime/manuals/releases/ipf-runtime-2.0.0.pdf]
h3. Tutorials
* [OSGi tutorial|http://repo.openehealth.org/sites/ipf-tools/runtime/manuals/releases/2.0.0/OSGi%20tutorial.html]
h1. Downloads
h2. Eclipse update site
You can install this release from the following Eclipse update site
{noformat}
http://repo.openehealth.org/sites/ipf-tools/runtime/updatesites/releases/2.0.0/
{noformat}
h2. Standalone Runtime
|| File || Content ||
| [IPF-Runtime-2.0.0.zip|http://gforge.openehealth.org/gf/download/frsrelease/119/784/ipf-runtime-2.0.0.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 |
h1. Release notes
h2. Changes since 2.0.0.m2
||Category||Changes||
|New features| |
|Other| |
h2. Feature Overview
Currently, the OSGi-based IPF runtime only support a subset of the [IPF 2.x features|ipf2:IPF Overview]. Extending the IPF runtime to support all IPF features in an OSGi environment is work in progress.
|| Feature || Description ||
| [Apache Camel|http://camel.apache.org] | 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|http://camel.apache.org/enterprise-integration-patterns.html] and [integration components|http://camel.apache.org/components.html] pages. |
| [OSGi support|ipftools:OSGi support] | Enables the deployment of IPF components (bundles) to OSGi platforms. IPF [service bundles|ipftools:OSGi support#Service bundles] register platform services at the OSGi service registry for consumption by IPF applications. [Extender bundles|ipftools:OSGi support#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|ipftools:OSGi support#Download and installation]. |
| [Groovy scripting layer|ipf2:IPF Scripting Layer] | With IPF you define [integration routes|http://camel.apache.org/routes.html] with the [Groovy|http://groovy.codehaus.org] 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|ipf2:IPF Scripting Layer#Predefined DSL extensions] to support e.g. the usage of closures (for inline definitions of message processors, routing rules etc.) and also provides a [DSL extension mechanism|ipf2:IPF Scripting Layer#DSL extension mechanism] to define custom extensions to the Camel DSL. |
| [DSL extension mechanism|ipf2:IPF Scripting Layer#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). |
| [ipf2: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|http://groovy.codehaus.org/Closures]. For [XML message processing|ipf2:Core features#DSL extensions for Groovy XML processing] there is special Groovy XML support. |
| [HL7 message processing|ipf2:HL7 processing] | Basis for HL7 message processing is the [HL7 DSL|ipf2:HAPI DSL], the [ipf2:HAPI extensions] and the [HL7 validation DSL|ipf2:HL7 validation]. These provides the basis for implementing [HL7 message processing routes|ipf2:HL7 processing#DSL extensions]. |
| [ipf2:Flow management] | A platform service to monitor, query, audit, replay and [cleanup|ipf2:Flow removal] message flows. The management interfaces are based on JMX. |
| [ipf2:Quality of service] | IPF provides extensions, guidance and solution blueprints (code examples) for implementing non-functional requirements. Covered topics are [transactional messaging|ipf2:Quality of Service#Transactional messaging], [flow management|ipf2:Flow management], load-balaning and high-availability. |
| [Module adapters|ipf2:Core features#Module adapters] | An infrastructure for including platform-independent message processing libraries into platform-specific message processing routes. An alternative is Camel's [bean integration|http://activemq.apache.org/camel/bean-integration.html] mechanism. |
h2. Documentation
* [OSGi support|http://repo.openehealth.org/sites/ipf-tools/runtime/manuals/releases/2.0.0/OSGi%20support.html]
h3. Reference manual
* [Exported HTML|http://repo.openehealth.org/sites/ipf-tools/runtime/manuals/releases/2.0.0/IPF%20Runtime%20single.html] (single-page version)
* [Exported HTML|http://repo.openehealth.org/sites/ipf-tools/runtime/manuals/releases/2.0.0/IPF%20Runtime.html] (multi-page version)
* [Exported PDF|http://repo.openehealth.org/sites/ipf-tools/runtime/manuals/releases/ipf-runtime-2.0.0.pdf]
h3. Tutorials
* [OSGi tutorial|http://repo.openehealth.org/sites/ipf-tools/runtime/manuals/releases/2.0.0/OSGi%20tutorial.html]