Integration Solution Development

Overview

For the Lifecycle Management of an IPP-based Solution, a combination of different Software Assets may define a Release of this Solution, e.g.

For the lifecycle management of an IPP-based Solution, a combination of different Software Assets may define a Release of this Solution, e.g.

  1. Camel Configurations in XML or Java
  2. IPP Process Models
  3. Rules Definitions (planned)
  4. Additional Java Bytecode (if needed)
  5. etc.

1. and 2. are the core Software Assets for IPP. They may be created in combination or just one of the two:

For convenience Camel Configurations can also be embedded into Camel Triggers and Camel Applications in an IPP Process Model. In any event, Camel Endpoints can invoke Processes and Processes can call into Camel Endpoints:

Java Camel Configurations

You can provided Java-based Camel Configurations like

from("seda:header").setHeader("visited", constant(true)).aggregate(header("cheese")).to("mock:result");

via Utility JAR files. However, we discourage to do so as this requires Java expertise for maintaining these artifacts.

Standalone XML Camel Configurations

Standalone XML Camel Configurations like

<camelContext id="camel" xmlns="http://camel.apache.org/schema/spring">
	<route>
   		<from uri="direct:start"/>
   		<aggregate>
   		<correlationExpression>
   			<simple>header.cheese</simple>
   		</correlationExpression>
   		<to uri="mock:result"/>
   		</aggregate>
   </route>
</camelContext> 

can be created either directly with the IPP Administration Portal or with an arbitrary text editor and uploading into the Administration Portal. These configurations may also contain references to enhancements in Java via Spring Bean definitions, e.g.

<camelContext id="camel" xmlns="http://camel.apache.org/schema/spring">
	<route>
   		<from uri="direct:start"/>
   		<aggregate strategyRef="aggregatorStrategy">
   			<correlationExpression>
   				<simple>header.cheese</simple>
   			</correlationExpression>
   		<to uri="mock:result"/>
   		</aggregate>
   </route>
</camelContext>

<bean id="aggregatorStrategy" class="org.apache.camel.spring.processor.MyAggregator"/>

Camel Configurations embedded in Process Models

Camel Triggers

Details on Camel Configuration can be found here.

Came Application Type

Details on the Camel Application Type can be found here.