Bill hits the nail on the head writing about the resignation of SAP's Shai Agassi...
And so it goes. The slow death of SOA.Netweaver was Agassi's baby and was expected to be more revolutionary for the company than it is turning out to be. Several SAP architects I'd spoken to did not even realize that Netweaver included an implementation of JMS, nor did they really understand what JMS is and when it might be used instead of their XI orchestration mechanism (which is built on R3's relatively cumbersome ABAP workflow engine, not on Java/Netweaver).
The most agile mechanism for working with SAP that I have seen remains an open source Perl API demo'd at OSCON several years ago.
I do hope Agassi is successful applying his abilities and resources to the energy industry though. That could be a better move than remaining with SAP.