SAP Portal vs ASP.NET Portal ... proof of concept?

We have an SAP portal, which is not user-friendly from the point of view of customers. As ASP.NET developers, we suggest using ASP.NET as the presentation layer for the SAP backend system instead of the SAP portal. We have already successfully integrated into the SAP database to insert and retrieve data.

So, we need to show the power of ASP.NET for the SAP team! As an ASP.NET portal, it will be much better than an SAP portal. We, however, AJAX functionality, the appearance of the user interface and portability of applications (cross-browser).

So, what are the advantages and disadvantages of the ASP.NET portal compared to the SAP portal? What are the problems that the SAP portal has, ASP.NET not? In short, how to convince ASP.NET decision makers over SAP in terms of UI / Performance?

+3
source share
3 answers

My five cents:

  • No one was fired for an SAP portal that really didn't work.
  • On the other hand, if you have a portal that you do yourself, the possibility of dismissal, if this is not a job, is much higher, because you cannot blame SAP for everything.
  • SAP software never works (consequence)
  • Consider point 3 at point 2 and the effect of your portal crashing on your carreer
  • Do you have TIME to do this? (=! = you have knowledge)
  • Windows Forms, , - ( JavaScript + )?
  • AJAX. Ajax , Google Chrome, IE 8 9 , IE 6
  • ? , Silverlight AJAX (. 7, 6)
  • SAP? , SAP ?
  • : SAP , , ( amp; , Unicode)?
  • SAP ? ? ? , ? SAP , , - .
+1

SCN ( SAP) , SAP Portal. , , .

0

Source: https://habr.com/ru/post/1786388/


All Articles