on 12-03-2008 5:29 AM
Hi,
We are currently in ECC6.0. Is ABAP Webdynpro advantageous over BSP for any UI development ECC6.0 onwards in general?
Specific requirement for which BSP is needed - we need a single application for a Help Desk team to handle calls from customers. The application will have multiple screens with data flowing into this application from multiple sources.
Need inputs on the above....
TIA,
Regards
Deepthi
Hi Deepthi,
Both webdynpro and BSP call ABAP function modules from HTTP. The BSP interface does this via programming in SE80, the webdynpro does this via programming in the Java development workbench. The BSP enters the SAP systenm via the ICM and is 'routed' to ICF where call are then made to executre ABAP (a good example is we use SOAP BSP's). Webdynpro routes via the ICM to the Java engine which then executes the Java to call the functions via an RFC interface called a JCo connection.
Another difference to note is SAP is now dedicated to using webdynpro as its internet platform of the future. This indicates that it aims to eventually retire such things as ITS and BSP.
If you needed to have a specific user interface, where you needed to code your own HTML or javascript, then BSP would be better, because you can not use your own HTML or javascript in WDA. You can not modify the UI elements in anyway when dealing with WDA.
Below are a few advantages of BSP over Web Dynpro as how suggested by Parry in [here|;:
Advantages of BSP over WebDynpro, Bit diffcult job but yes there are .
1) With BSP it is easy to do UI design and developeements .As you have many options avilable like HTML , HTMLB . In many cases you need to use HTML for Web Developement for such scenarios BSP is better choice.
2) You need not to strictly follow MVC(Model View Controller ) which is not case in WebDynpro .
3) May you can develope application that will do client side validations of input boxes and all with JAVA SCRIPT which is not the case in WebDynpro . Many times validation with JavaScript is easy .
4) Similarly you can introduce any Javascript function , you can easily use DOM (Document object model) with BSP .
5) Now in industry many projects are there in BSP as client normally don't switch to new technology like WebDynpro from BSP .As you have tried and Tested it .and dont feel of taking risk. So BSP is there in Market.
6) In case BSP you don't have this fundas like Context , node so at times it find easier .
Regards,
Uday
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
>Both webdynpro and BSP call ABAP function modules from HTTP. The BSP interface does this via programming in SE80, the webdynpro does this via programming in the Java development workbench. The BSP enters the SAP systenm via the ICM and is 'routed' to ICF where call are then made to executre ABAP (a good example is we use SOAP BSP's). Webdynpro routes via the ICM to the Java engine which then executes the Java to call the functions via an RFC interface called a JCo connection.
There are many incorrect statements in your posting. You appear to be compairing BSP to Web Dynpro Java - not Web Dynpro ABAP. Why would you do this in a Web Dynpro ABAP forum posting? Of course everything you stated about Web Dynpro running on the Java engine and using JCo and being programmed in the Java development workbench is totally wrong if you are comparing to Web Dynpro ABAP.
Here is the explaination of the differences from the SAP Press Book: Next Generation ABAP development (page 303):
Web Dynpro ABAP is SAPu2019s new UI strategy, which was introduced in SAP
NetWeaver 7.0. It is based on the Model View Controller (MVC) paradigm
that separates business logic from the user interface logic. Developers, like
Russel, can use this tool to develop robust business applications quickly and
easily, without ever having to deal with the inner coding of the user interface
elements.
The Web Dynpro ABAP framework provides a WYSIWYG view editor (What
You See Is What You Get) where the developer simply drags and drops the UI
elements into the view. This means that there is no coding of the UI elements.
This is not the case when working with Business Server Pages (BSP),
where the developer must know some HTML or JavaScript in order to code
the user interface.
The Web Dynpro framework approach can be viewed in a number of ways.
If a developer is not proficient in HTML or JavaScript, the Web Dynpro
ABAP tool looks pretty good. He doesnu2019t have to worry about coding the UI
and he can focus more on the business application logic. On the other hand,
if the developer wants to add his own look and feel or some additional UI
functionality to the Web Dynpro ABAP UI, he canu2019t. The UI implementation
is hidden from the developer and cannot be manipulated, such as adding
your own HTML or JavaScript. The reason for this protection is that Web
Dynpro was developed to provide a standard business application user interface
across all applications that leverage this tool.
There is another advantage to the client abstraction approach that Web Dynpro
takes. When you design a user interface in Web Dynpro, what is saved is
just a metadata representation of the layout and elements. In other words,
Web Dynpro is not tied to just HTML and JavaScript as its output medium.
The Web Dynpro runtime analyzes the type of client that is making a request and responds with the appropriate rendering output. Today that means web browsers are making the request and receiving HTML and JavaScript. But, in the future, when the next great UI revolution occurs, you wonu2019t necessarily
have to recreate your applications to take advantage of it. Already you can see examples of a smart client and Adobe Flex based rendering engines for Web Dynpro. Switching to these alternative presentation tools requires no coding changes within the applications themselves.
User | Count |
---|---|
101 | |
13 | |
13 | |
11 | |
11 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.