In my first two months at Talend I was mainly involved in building the first release of Talend Integration Factory (TIF). It is an Apache Licensed distribution of Camel with three interesting additions: A pre packaged OSGi container, an integration component for Talend Open Studio and some advanced examples. Let´s take a closer look at these addtions.
So why should you use Talend Integration Factory instead of Camel?
- Synchronized Release Cycles: As the version number already suggests we are following the Apache Camel releases. So for each Camel release there will be a Integration Factory release shortly after. So unlike with other products you do not have to wait half a year for the new features to appear
- No vendor lock in: The distribution is Apache Licensed so you can use it in almost any environment. We try to stay as near to the original Camel as possible. Bugfixes and Enhancements are directly committed back to Apache Camel and all other involved Open Source projects. In fact the current distribution did not need to patch Camel 2.6.0 as we got all our enhancements into the Camel Release.
- Pre packaged OSGi container based on Karaf, Camel and CXF: OSGi is very interesting for central integration servers as integrations can be deployed without restarting the server. The integration artifacts are also much smaller then for typical .war deployments. To give a rough number a .war with Camel and CXf easily reaches a size of 20MB. A typical integration project in the OSGi container is only about 100KB in size. So while the benefits are clear many fear the complexity of setting up an OSGi environment so that Camel and CXF work as expected. As TIF Container prepackages all these things it is really easy to use. Still we were very careful to keep the container open. So you can easily upgrade all dependencies even without waiting for a new TIF release. The container also leverages all the features of Apache Karaf. So deployments are very easy and nicely integrated with your maven builds
- Talend Open Studio integration: This component allows Talend Open Studio integrastions to participate in Camel routes. The component is the first step to a seamless integration with other Talend products
- Advanced Examples: We have put together some examples that show use cases that are quite common in enterprise environments. More abbout these below
The examples show
- jaxws_jms : Calling and publishing CXF JAXWS endpoints using Camel routes and JMS
- jaxrs_jms_http : Calling and publishing JAXRS endpoints using JMS and HTTP over Camel routes
- spring_security: Securing your integrations with Spring Security. Shows how to use Basic Authentication and @RolesAllowed annotations on the method level to secure CXF and Bean endpoints
- claimcheck: This example shows some advanced DSL usages. The following EAI patterns are shown: Splitter, Claimcheck, Resequencer, Delayer
All examples are built with Maven. They and work standalone, in web containers and in OSGi. Each example is self contained so it can be easily copied and used as a temlate for your own projects.
With this post I am beginning a series of posts about Apache Karaf. So what is Karaf and why should you be interested in it? Karaf is an OSGi container based on Equinox or Felix. The main difference to these fine containers is that it brings excellent management features with it.
Outstanding features of Karaf:
- Extensible Console with Bash like completion features
- ssh console
- deployment of bundles and features from maven repositories
- easy creation of new instances from command line
All together these features make developing server based OSGi applications almost as easy as regular java applications. Deployment and management is on a level that is much better than all applications servers I have seen till now. All this is combined with a small footprint as well of karaf as the resulting applications. In my opinion this allows a light weight development style like JEE 6 together with the flexibility of spring applications.
Installation and first startup
- Download Karaf 2.1.3 from the Karaf web site.
- Extract and start with karaf.bat
You should see the welcome screen:
Some handy commands
Shows the installed bundles. By default you will see nothing a there is a start level threshold that hides the karaf base bundles.
Shows the active OSGi services. This list is quite long. Here it is quite handy that you can use unix pipes like "ls | grep admin"
Also very handy is exports which shows the bundle id for each exported package. This helps to find out where a package may come from.
Shows which features are installed and can be installed.
This allows to install features (a list of bundles and other features). Using the above command we install the Karaf webconsole.
Now open the webconsole on http://localhost:8181/system/console . Log in with karaf/karaf and take some time to see what it has to offer.
Tasklist - A small osgi application
Without any useful application Karaf is a nice but useless container. So let´s create our first application. The good news is that creating an OSGi application is quite easy and
maven can help a lot. The difference to a normal maven project is quite small. To write the application I recommend to use Eclipse 4 with the m2eclipse plugin.
- Start Eclipse
- Install m2eclipse using the default eclipse update site
- download the sample project from https://github.com/cschneider/Karaf-Tutorial/zipball/master
- Extract to a directory
- In Eclipse : Import -> Existing maven project -> Browse to the extracted directory
Eclipse will now import the projects and wire all dependencies using m2eclipse.
The tasklist example consists of three projects
- tasklist-persistence : model and persistence implementation
- tasklist-ui : servlet that displays the tasklist
- tasklist-features : Features descriptor for the application that makes installing in Karaf very easy
This project contains the domain model and the service implementation. The model is the Task class and a TaskService interface. The persistence implementation TaskServiceImpl manages tasks in a simple HashMap.
The TaskService is published as an OSGi service using a blueprint context. Blueprint is an OSGi standard for dependency injection and is very similar to a spring context.
The bean tag creates a single instance of the TaskServiceImpl. The service tag publishes this instance as an OSGi service with the TaskService interface.
The pom.xml is of packaging bundle and the maven-bundle-plugin creates the jar with an OSGi Manifest. By default the plugin imports all packages that are imported in java files or referenced in the blueprint context.
It also exports all packages that do not contain the string impl or internal. In our case we want the model package to be imported but not the persistence.impl package. As the naming convention is used
we need no additional configuration.
The ui project contains a small servlet TaskServlet to display the tasklist and individual tasks. To work with the tasks the servlet needs the TaskService.
To inject the TaskService and to publish the servlet the following blueprint context is used:
The reference tag makes blueprint search and eventually wait for a service that implements the TaskService interface and creates a bean "taskService".
The bean taskServlet instantiates the servlet class and injects the taskService. The service tag publishes the servlet as an OSGi service with the HttpServlet interface and sets a property alias.
This way of publishing a servlet is not yet standardized but is supported by the pax web whiteboard extender. This extender registers each service with interface HttpServlet with the OSGi http service. It uses the alias
property to set the path where the servlet is available.
The last project only installs a feature descriptor to the maven repository so we can install it easily in Karaf. The descriptor defines a feature named tasklist and the bundles to be installed from
the maven repository.
Installing the Application in Karaf
Add the features descriptor to Karaf so it is added to the available features
Install and start the tasklist feature. After this command the tasklist application should run
Check that all bundles of tasklist are active. If not try to start them and check the log
Now create a text file "org.ops4j.pax.web.cfg" with the content "org.osgi.service.http.port=8080". This will tell the http service to start and use the port 8080.
Now the tasklist application should be available at http://localhost:8080/tasklist
In this tutorial we have installed Karaf and learned some commands. Then we created a small OSGi application that shows servlets, OSGi services, blueprint and the whiteboard pattern.
In the next tutorial we take a look at using Apache Camel and Apache CXF on OSGi.
Back to Karaf Tutorials