Why Build on SAP NetWeaver?
Hi everyone, and welcome to the new forum.
For some time in Asia we have encouraged customers and SAP implementation partners to use parts of SAP NetWeaver for true custom development projects - that is, building and running Java applications, or porting existing Java applications onto SAP NetWeaver to consolidate and simplify technology landscapes and skills requirements.
We now have many organisations around the region who have successfully deployed new Java applications, and ported existing ones to run alongside SAP ERP on the same technology foundation. They have discovered many benefits in reducing costs and improving development productivity, leveraging even more from their strategic investment in SAP's SOA strategy and solutions.
However, we found that the majority of discussions on SDN relating to development focus on composition of Enterprise Services or ABAP programming, with little discussion on the true standalone Java development topic and how it relates to the broader SAP SOA strategy of delivering Enterprise Services and composing new applications.
We created this forum to bring a distinct focus to the topic, and encourage you to discuss and debate the aspects of it so that a greater understanding can be reached of when best to use SAP NetWeaver in such a scenario, whether or not combined with an implementation of SAP ERP.
We are no longer in a "Build or Buy" world - SAP's SOA allows organisations to "Buy and Build" and get the benefits of global best practice combined with their own unique requirements on a single business process platform.
Whether you Buy, Build or both, we look forward to your contributions!