Hi Chris,

sorry for my late answer.

In your case, if you can deploy a WebService on your SAP platform, you can create a HTTP provider in SMX and contact this service. It's very simple and mainly configuration based (in the xbean.xml if you use the JBI packaging).

The main workload will be in the message transformation between the in message and the backend component endpoint.

It's not easy to provide a real days man amount :)

For example, if you use a servicemix-bean based endpoint behind your HTTP provider, you need to get the in message extract content as you expect and fire some actions.

Regards
JB

Chris Jölly wrote:
Hi JB,

thanks for your reply and clarification :-) The ESB world is rather
huge, that’s basically the reason why I'm asking of the efforts evaluating
these technologies...

So, if I use servicemix as our integration layer, and I have to export our business objects to foreign systems like SAP Purchasing, SAP CRM, SAP SRM, SAP BW and so on, or trigger external workflows like PO sign-off, I have to transform our business objects to a format servicemix is able to process. And I have to configure servicemix for the message routing to
the correct external business application using ServiceMix HTTP or CXF BC?

So, back to my first question: how much effort should I expect to get a usable integration layer for let's say one - very famous :) - use case, creating PO in SAP, up and running?
Regards
Chris

-----Original Message-----
From: Jean-Baptiste Onofré [mailto:[email protected]] Sent: Donnerstag, 02. Juli 2009 17:42
To: [email protected]
Subject: Re: Integrating / evaluating servicemix

Hi Chris,

first of all, basicly, I think that the purpose of ServiceMix is not to be integrate in one application. The ESBs like ServiceMix are mostly made to integrate several applications (using different media channel) via a kind of backbone: the ESB.

Nevertheless, ServiceMix can be a new module of your application, dedicated to the integration layer. In this case, you are responsible of exposing your business service into ServiceMix and the integration needs will be put into ServiceMix.

In your case, if the SAP XI system provides a SOAP URI to you, you can use the ServiceMix HTTP or CXF BC to post and get message to/from SAP.

I have made the same investigation as you. It was two years ago and I have benchmarked:
- SMX
- OpenESB
- Mule
Each have skills and issues. I have made the choice of ServiceMix and begin to contribute on it. So I think that you have my point of view on this topic :)

Regards
JB

Chris Jölly wrote:
Hello all,

I have some questions regarding the efforts needed to integrate servicemix

into an application and how much time is needed to get the first results
when e.g. connecting servicemix via web services to an SOAP adapter of

an SAP XI system.

What I want to do is to evaluate some of this integration platforms and
compare  each other. Sure, this efforts depends on the skills of the developers

and the concrete use cases, but someone who uses servicemix could possible

give a rough figure for this efforts which is sufficient for my needs by now. J

And, maybe someone has evaluated other tools like Swordfish or Mule and

has figures for these platforms too?

thanks, Chris



--
Jean-Baptiste Onofré
---------------------------------
 HomePage
http://www.nanthrax.net
---------------------------------
 Contacts
[email protected]
[email protected]
---------------------------------
 OpenSource
BuildProcess/AutoDeploy
http://buildprocess.sourceforge.net
Apache ServiceMix
http://servicemix.apache.org
-----------------------------------
PGP : 17D4F086

Reply via email to