Morten,Thorsten, Jørgen, Alessandro and Ricardo (and probably many others over time) have done a great job with Detroubulator; but I can’t help thinking that it could be even better and potentially become part of SAP standard if it was ported into ABAP. And since I was reviewing the implementation of Detroubulator at my current workplace, I thought I would spend some time to reverse engineer this and see what would be involved in developing this in ABAP. I figured with the functionality at hand within ABAP, this may actually may not be a significant port and would provide greater enhancement opportunities.
The problem for me is that if I tried to do this alone, I would not learn from those who have implemented Detroubulator already and I may seriously miss the mark in delivering a comparable solution. Hence, in an attempt to use the power of SDN and collaboration, I’ve created a wiki with a very draft candidate design. Unfortunately, I’m not sure how to share UML files within WIKI but hopefully enough is published to get an idea of the design and to provide direct feedback.
Note – The alternative to this is simply to look at what would be involved to port this into the JAVA WAS of PI/XI but with NWDI being a requirement for SAP JAVA WAS development (from my perspective at least), I wasn’t sure how an open source approach would work on a project like this, especially when considering multiple versions of XI/PI. Regardless, this is definitely an option to pursue, especially in 7.1 and beyond.
Anyway, if you have a vested interest in Detroubulator, follow the link above, try not to get into an ABAP vs JAVA conversation (no one ever wins) and let’s see where this takes us.
ps. At time of posting this document, I didn’t realise I couldn’t move the WIKi post from the Sandbox to Exchange Infrastructure, so the link may change in the near future to the following: https://wiki.sdn.sap.com/wiki/display/XI/A+very+draft+design+for+Detroubulator+in+ABAP