Welcome to OpenEngSB!

The Open Engineering Service Bus (OpenEngSB) project provides an easy-to-use and easy-to-adapt platform for tool integration. It offers graphical workflow design between software tools and avoids repetitive setup tasks. In contrast to typical Enterprise Service Bus approaches existing workflows can easily be adapted to software changes due to the domain-based integration model. Thus, OpenEngSB enables transparency in dynamic development processes too and frees the engineers' time for productive work.

About OpenEngSB

In engineering environments a lot of different tools are used. Most of these operate on the same domain, but often interoperability is the limiting factor. For each new project and team member tool integration has to be repeated again. In general, this ends up with numerous point-to-point connectors between tools which are neither stable solutions nor flexible ones.

This is the point where the Open (Software) Engineering Service Bus (OpenEngSB) comes into play. It simplifies design and implementation of workflows in an engineering team. The engineering team itself (or a process administrator) is able to design workflows between different tools. The entire description process happens on the layer of generic domains instead of specific tool properties. This provides an out of the box solution which allows typical engineering teams to optimize their processes and make their workflows very flexible and easy to change. Also, OpenEngSB simplifies the replacement of individual tools and allows interdepartmental tool integration.

Project management is set to a new level since its possible to clearly guard all integrated tools and workflows. This offers new ways in notifying managers at the right moment and furthermore allows a very general, distanced and objective view on a project.

Although this concept is very powerful it cannot solve every problem. The OpenEngSB is not designed as a general graphical layer over an Enterprise Service Bus (ESB) which allows you to design ALL of your processes out of the box. As long as you work in the designed domains of the OpenEngSB you have a lot of graphical support and other tools available making your work extremely easy. But when leaving the common engineering domains you also leave the core scope of the service bus. OpenEngSB still allows you to connect your own integration projects, use services and react on events, but you have to keep in mind that you're working outside the OpenEngSB and "falling back" to classical Enterprise Application Integration (EAI) patterns and tools.

However, this project does not try to reinvent the wheel. OpenEngSB will not replace the tools already used for your development process, it will integrate them. Our service bus is used to connect the different tools and design a workflow between them, but not to replace them with yet another application. For example, software engineers like us love their tools and will fight desperately if you try to take them away. We like the wheels as they are, but we do not like the way they are put together at the moment.

Features

The OpenEngSB comes with the following features out of the box:

• Abstract tool integration for mail, scm, issue tracking, build, test, deploy, auditing, reporting and microblogging. In detail we support the following tools: Mail, Twitter, Facebook, JIRA, Git and Maven with more to come.
• Modular UI presenting the state of the OpenEngSB and its installed modules.
• Completely integrated workflow and rule management.
• Very modular, powerful and reusable system based on OSGi.
• Full control over the system using console and ssh to connect to it; thanks to Apache Karaf

See the documentation, participate in the mailing lists or directly dive into the source.

News

Andreas Pieber posted on Feb 21, 2012
OpenEngSB Root 31 released

The OpenEngSB team is pleased to announce the availability of the OpenEngSB Root 31.
This release contains various library maven plugin upgrades. In addition the no longer required maven.openengsb.org repository had been removed. Another noteable change was the addition of a prerequisites section for maven 3 which forces now to use maven 3 to build the OpenEngSB or related projects.
For more information, please see the release notes.

Christoph Gritschenberger posted on Jan 17, 2012
OpenEngSB 2.0.1 released

The OpenEngSB team is pleased to announce the availability of the OpenEngSB 2.0.1.
The final release 2.0.1 of the Open Engineering Service Bus comes with OpenEngSB Framework 2.4.1 including some bugfixes to the framework.
For more information, please see the release notes.

Christoph Gritschenberger posted on Jan 17, 2012
OpenEngSB Framework 2.4.1 released

The OpenEngSB team is pleased to announce the availability of the OpenEngSB Framework 2.4.1.
This release was manly required for the addition of the easy WSDL build configuration for domains. In addition a feature had been added making the OpenEngSB version available easily via an http service at e.g. localhost:8090/system/framework.version.info. The correlationId and replyQueue fields are now optionally supported if using JMS. In addition various minor enhancements to the documentation had been done and the build had been optimized further. Various bugs in runtime (jetty, archetypes, offline usagage) had been fixed.
For more information, please see the release notes.

Andreas Pieber posted on Jan 12, 2012
OpenEngSB 2.0.0 released

The OpenEngSB team is pleased to announce the availability of the OpenEngSB 2.0.0.
The final release 2.0.0 of the Open Engineering Service Bus comes with OpenEngSB Framework 2.4.0 including a variety of new features: A general possibility to handle OAuth, now allowing connectors to e.g. Facebook and Twitter; A set of Karaf command line support (info, service, connector, domain); Implementation of the Engineering Database for version and storing models; A prototypic implementation of the Engineering Knoledge Base allowing to work with the models of tools and query against them; Minor enhancements in the administration UI (coloring, bug-fixes, ...); Java 7 compatibility; Full filter chains for the implementation of the remoting part making it possible to configure encryption, authentication, authorisation, and method calls quite easily; JPA support within the OpenEngSB; Possibility to create and change connector instances in configuration files. In addition those releases bring the following new versions and all their new features and bug fixes of the base tools to the OpenEngSB: Apache Karaf (2.2.5); Apache CXF (2.5.1), Apache ActiveMQ (5.5.1), Drools (5.3.0.FINAL), Wicket (1.4.19). The OpenEngSB 2.0.0 comes with the following tools and connectors: Binary Transformation Provider Factory (Smooks Binary Transform Provider Factory), Auditing (MemoryAuditing), Example (Example), Notification (Email), Appointment (Gcalendar), Contact (Gcontacts), Scm (Git), Issue (Github, Trac), Build (Maven), Test (Maven), Deploy (Maven), Report (Plain Text Report, ProM Report); All of those connectors and domains had been adapted to the latest version of the framework.
For more information, please see the release notes.

Christoph Gritschenberger posted on Jan 12, 2012
OpenEngSB Trac Connector 2.0.0 released

The OpenEngSB team is pleased to announce the availability of the OpenEngSB Trac Connector 2.0.0.
In this release all all interfaces and implementations have been adapted to the latest domain/openengsb versions. In addition EDB/EKB access has been implemented.
For more information, please see the release notes.

Older News

See the archive for older news no longer shown here.