XI with ABAP stack only ?
Looking at some very annoying problems with the XI Java Stack and applications (stability, memory consumption), following question comes to mind:
is it technically possible to run an XI system without the Java stack ? How much functionality do we have in there, can we do customers projects with that ?
In ABAP stack, we have the following functions:
- Business Process Engine
- Integration Engine
- HTTP Adapter
- IDoc Adapter
- ABAP-Mapping (XSL or handmade)
also, we have of course the functionality of using File/FTP,Mail in ABAP. This means the most important adapter types are available in ABAP (without needing the Java adapter engine).
Of course the Integration Builder is not available then. But do we really need it ?? Same applies for the SLD.
Are the pipeline objects (receiver determination, interface determination and so on) stored in the ABAP stack ? I assume that is the case. Does ABAP stack contain the XI message type objects ? Or is that stored in Java ?
Anyone tried that path ? Is it already failing in the installation because some core XI ABAP components require Java parts ? Or would it work ?
Of course the answer depends on "what do we define to be XI". For me it is the core integration engine with the pipeline architecture plus mapping and proxy extension points. Everything else (e.g. tools) needed can be built around it.
Customer benefits would be: focus on ABAP only (Java knowhow not needed), easier administration and more stability.