I discounted this article as FUD, a type of sales and marketing strategy aimed at making yourself look good by planting Fear, Uncertainty and Doubt about the competition, you summed it up in the above comment
I am assuming the article which is published in the Australian InsideSAP Magazine was pitched at business and not technical people, it doesn't go into enough technical detail or suggest an alternative, why chose X because of Y.
wrt to the middle layer
How do you integrate with SAP®? SAP® .Net Connector [SOURCE Frequently asked questions]
RFC and SAP .Net Connector are 2 very old Proprietary frameworks, I don't see or hear much can about the SAP .Net connector and can only imagine with the focus on Gateway Productivity for Microsoft, this connector must be close to, if not at EOL, with no source code or community to support any issues which might arise from upgrade on any of the dependencies may be challenging.
Interestingly I have done a number of projects lately, where the goal of the project is to decommission old COTS (Commercial-off-the-shelf) connector based solutions, SAP DCOM, IDoc Connector, JCO etc, and replace with a similar solution using modern supportable techniques like SAPUI5 and Netweaver Gateway, customers choice.
My observation which makes for good FUD, there is always an old box in the corner of the server room running an XP VM stuck in time, nobody knows how it got there, no one knows how it works, no one wants to support it, no one to call to ask for help, by definition Legacy.
JSP
