Talk:SAP NetWeaver

}}

Ranting, but no action
Guys, I see a lot of ranting here on the form of this page, but no action to change it -How about come to action and do something about it?

Regards, Benny--155.56.68.220 (talk) 13:45, 17 December 2008 (UTC)

This whole page looks as an advertisement.
There is no content. You can't actually figure out what SAP NetWeaver is (assuming it is something besides a marketing buzzword) from what is written here. As someone pointed out below, it doesn't even make sense to claim that it can "be extended with, and interoperate with, technologies such as Microsoft .Net, Sun Java EE, and IBM Websphere.".

Nonsense
"From a technical point of view, one can say that NetWeaver achieves its functionality by formatting in XML."

Clearly it is not the case that NetWeaver achieves it's functionality by formatting in XML, yes the ability to converse with XML is important and a key component, but it is not a tool or set of tools to format XML.

This article reads like sales speak, specifically the numbered points in the second paragraph. Thanks.

.NET/Java & WebSphere
"SAP NetWeaver is built using open standards and industry de facto standards and can be extended with, and interoperate with, technologies such as Microsoft .NET, Sun Java EE, and IBM WebSphere."

Above statement suggests that .NET, J2EE and WebSphere at are technologies at same level. IMHO, one can not treat WebSphere at the same level as that of .NET/J2EE. In broad terms, WebSphere, among other things, is one of the vendor offering J2EE based products.

Clarification
This wikipedia article is pretty poor, i think. It is possible it's due to the fact that there is no hype about it in the common public - NW is a large, complex, enterprise-oriented platform and it is unlikely that the common surfer will be able to utilise knowledge about it. Still, I'd like to give a few guidelines: First of all, NW is an integration platform. Its neither java ee/web services/rdbms/r3/portal/source control/central build system/knowledge management/etc, but rather, all of the above. Its purpose is to enable creation and integration of components to serve various enterprise needs and also, support the whole SDLC of those components, all done at a high level, and, say, in a RAD manner. I know it sounds silly that NW is supposed to do almost everything, but theoretically that's its idea, and it is realised to a certain extent, imho. NW interoperates with Oracle, IBM, .NET, etc, and this is not marketing buzzword but fact. This is done through xml, web services, and the SOA paradigm. As long as a system is capable to communicate through WSDL/SOAP/UDDI (the last being not mandatory), netweaver is capable to interoperate with it. Thats the beauty of Web Services, anyways. NW is not BACKWARD compatible with sap R/3. SAP R3 is part of nw stack. Interoperability with sap r3 is achieved through Remote Function Calls. As far as JEE integration of Netweaver is concerned, SAP is the first vendor to have made a Sun certified JEE5 Java AS. I think this speaks of itself.

Good place to start if you are interested in the NW platform is,.

SAP Central Process Scheduling
Any objections to my merging SAP Central Process Scheduling here? It seems pretty non-notable except as a component of NetWeaver itself. Dai Pritchard (talk) 18:37, 13 October 2014 (UTC)