|
1
|
- Quickly, the evolution, and
- a roadmap for you
|
|
2
|
- Internet Transaction Server
- ESS/MSS Web Studio – Limitations
- Flow Logic
- Workplace
- TopTier – Iviews, Drag and Relate
- Web Application Server – Business Server Pages
- Object Oriented ABAP
- SAP Java (J2EE) Server
- Netweaver – Netweaver Studio
- Portal Development Kit – Iview Studio
- Business Packages – xApps
- ABAP developer to SAP developer roadmap
|
|
3
|
- ITS “scrapes” the SAPGUI screen elements.
- The generated HTML screen has these elements.
- The button clicked on HTML eventually invokes the screen flow logic of
SAPGUI
|
|
4
|
- The templates could be modified using Web Studio or SAP Studio
- Supported client ‘Branding’
- Business HTML
- WEBGUI could be used for most Applications
|
|
5
|
- ITS Flow Logic Programming used RFCs
- The HTML template could use open technologies like CSS, DHMTL,
JavaScript
- The FLOW FILES controlled the RFC calls and the screen flow
|
|
6
|
- Screen elements not displayed well and sharp
- Limitations with Control elements like ALV and Table Controls
- Limitations with Front-end functionality like Excel download, etc.
- Performance
- Very limited Persistence memory
- Not an open technology
- IIS and Windows platform dependant
|
|
7
|
- Portal Solution
- Single Sign On
- Role based CUA
- MiniApps
- Metadata
|
|
8
|
- Iview Servlet
- Drag and Relate Servlet
|
|
9
|
- Business Server Pages
- ABAP Code within HTML
- Now MVC Architecture
- Web AS as a server that serves HTML – integrated authentication
- Optional Business HTML frontend design
- SE80 as IDE
- Integrated with SAP Transport Mechanism for code and mimes
- Via BSP, ABAP stack of SAP Web AS meets JSP on the J2EE side
|
|
10
|
- Object Oriented – Classes and Methods: Polymorphism, Encapsulation,
Inheritance
- BADI, Controls Framework, Classes for HTML interfacing, etc.
- Example: Employee as an Object
- Unicode
- XML Transformations
- Shared Objects, New Debugging Tools, Memory Monitor, etc.
|
|
11
|
- Limited ABAP community; flourishing J2EE Community
- Acquired InQMy – developed and refined
- J2EE 1.3 Certified by Sun Microsystems
- Base of SAP Portals, and forms J2EE stack of Web AS 6.3, and onwards
|
|
12
|
- WAS – ABAP Engine + J2EE Engine – preserves investments
- Exchange, BI and Portal Infrastructure
- Browser or Application Client/SAPGUI
- Java IDE – Open Source Eclipse based
- Java Dictionary, Open SQL for Java
- Web Dynpro – MVC
- xApps – Composite Application Framework
|
|
13
|
- Roles, Worksets and Iviews
- Now runs on J2EE Engine
- PDK or Business Packages PDK
- JBuilder or Netweaver Studio
- Business Packages – SAP & non-SAP
- RFCs. Also IAC, ISR, BSP
- JSP/Servlets -> Web Dynpro
|
|
14
|
- Web
- JSPs ~ BSPs
- Servlets ~ BSP Controllers
- Business Programming
- Enterprise JavaBeans ~
BAPIs/RFCs
- SAP Enhancements for Business Development
- Java Dictionary ~ ABAP Data
Dictionary
- Open SQL for Java ~ Open SQL for
ABAP
- Java Development Infrastructure
~ ABAP Development Infrastructure
|
|
15
|
- Learn ABAP Objects and Object Oriented Programming
- Learn BSP – the ABAP Objects based web programming
- Take basic Java courses
- Take J2EE Classes – including JSP/Servlets and SAP’s own J2EE Classes….
- Get familiar with the different IDEs
|