Blog about Java EE / SOA / Cloud Computing

Talend has several connectors to integrate SAP systems. However, this guide is no introduction to Talend’s SAP components. Instead, this guide helps to

• understand different alternatives to integrate SAP systems with Talend
• set up a local SAP system
• configure Talend Studio for using SAP components
• use Talend’s SAP wizard
• run a first Talend Job which connects to SAP

All further required information and example use cases for Talend’s SAP components should be available in the Talend component guide at www.help.talend.com. If that’s not the case, please create a JIRA Documentation ticket (https://jira.talendforge.org/browse/DOCT)!
Now let’s take a look at different alternatives for integration of SAP systems with Talend.

I had a very interesting talk at OOP 2013 in Germany. OOP is a great conference for software architects and decision makers. The topic of my talk was “Spoilt for Choice: How to Choose the Right Enterprise Service Bus (ESB)”. Hereby, I want to share the slides with you…

I had a talk at Java User Group Frankfurt (JUGF): “Showdown: Integration Framework (Spring Integration, Apache Camel) vs. Enterprise Service Bus (ESB)”. The room was fully packed! Interest in integration frameworks, ESBs, and corresponding tooling increases every year… I uploaded the slides at Slideshare:

If you have any questions or other feedback, please write a comment or contact me via Email, Twitter or Social Network (LinkedIn, Xing).

Best regards,

Kai Wähner (Twitter: @KaiWaehner)

Disclaimer: I work for an “open source company”. The following is my personal opinion!

Great Article: “What is the TCO difference between WebSphere and JBoss?”

I have spotted a really great article about comparing prices of open source and proprietary products: “What is the TCO difference between WebSphere and JBoss?“. The interesting aspect is, that this article is written by an IBM-biased company (Prolifics). Usually, only open source vendors write such comparisons. I really like this article, seriously! It is good to see comparisons not only by open source vendors, but also by vendors such as IBM (in this case, Prolifics cannot be considered unbiased, it is an IBM consulting company – but that is fine). I just want to give my two cents to this article in the following…

Apache Camel is my favorite integration framework on the Java platform due to great DSLs, a huge community, and so many different components. Camel is used by many developers from different companies all over the world. However, most guys are not aware that some really cool and – more important – enterprise-ready tooling is available for Camel, too. Many people ask me about Camel tooling when I do talks at conferences. This is the reason for this short blog post about Camel tooling.

[FYI: I work for Talend (one of the vendors). Please also read the comments from my Red Hat friends at the bottom!]

These days, I am at JavaOne 2012 in San Francisco. That’s the largest and most important Java conference worldwide. In this blog post, I wanna share the slides of my two talks…

Lessons learned: Use of Modern JVM Languages besides Java

I explain my lessones learned while using other programming languages on the Java Platform besides Java, e.g. Groovy, Scala, Clojure, JRuby, Jypthon, Erjang, and others.

Today, I was at the SOA CLOUD Service Technology Symposium 2012 in London (http://www.servicetechsymposium.com). Believing the organisors, it is „the World’s Largest Conference Dedicated to SOA, Cloud Computing & Service Technology“.

I was at this conference for the second time. Two year ago, the conference took place in Berlin. Unfortunately, the venue was awful this time. It was uncomfortable, no seats / tables available, and the rooms for the sessions were tough to find. Nevertheless, it was an awesome international conference with plenty of good content regarding SOA and Cloud Computing.

Data exchanges between companies increase a lot. The number of applications, which must be integrated increases, too. The interfaces use different technologies, protocols and data formats. Nevertheless, the integration of these applications shall be modeled in a standardized way, realized efficiently and supported by automatic tests. Such a standard exists with the Enterprise Integration Patterns (EIP) [1], which have become the industry standard for describing, documenting and implementing integration problems. Apache Camel [2] implements the EIPs and offers a standardized, internal domain-specific language (DSL) [3] to integrate applications. This article gives an introduction to Apache Camel including several code examples.

Data exchanges between companies increase a lot. The number of applications which must be integrated increases, too. The interfaces use different technologies, protocols and data formats. Nevertheless, the integration of these applications shall be modeled in a standardized way, realized efficiently and supported by automatic tests.

Three integration frameworks are available in the JVM environment, which fulfil these requirements: Spring Integration, Mule ESB and Apache Camel. They implement the well-known Enteprise Integration Patterns (EIP, http://www.eaipatterns.com) and therefore offer a standardized, domain-specific language to integrate applications.

The integration framework Apache Camel already supports several important cloud services (see my overview article at http://www.kai-waehner.de/blog/2011/07/09/cloud-computing-heterogeneity-will-require-cloud-integration-apache-camel-is-already-prepared for more details). This article describes the combination of Apache Camel and the Amazon Web Services (AWS) interfaces of Simple Storage Service (S3), Simple Queue Service (SQS) and Simple Notification Service (SNS). Thus, The concept of Infrastructure as a Service (IaaS) is used to access messaging systems and data storage without any need for configuration.