Advantages of BSP

Hello All,
Can you pen down the advantages of BSP over ASP and what
are the side effects of using BSP considering the load
on the server where it is running.
Would be glad to have your views......
TQ,
- Sravan

What's the biggest single advantage to using BSP? 
That fact that you write your web pages in ABAP of course!
That is assuming that you know and like ABAP as a programming language.  All joking aside this is a huge benefit if you have a development team like ours (people with many years of experience programming ABAP in the R/3 environment).  The transition to a Web Based development platform is made that much easier by not having to learn the syntax and (more importantly) the ins and outs of a new programming language. 
As far as performance and other technical details, the weblogs mentioned above should give you plenty of reading.  I can add to those by telling you about the experiment that we did before we choose to use BSP.  We built a purchase requisition application in both BSP and ASP.Net.  The ASP.Net application used the .Net Connector to access all of its data while the BSP used native RFC naturally. 
We ran both applications on indentical hardware and did some tests.  Our tests weren't the most scientific in nature, but let's just say that BSP visibly won hands down in the performance department.  That's not a dig at ASP by any means.  I like it just fine and feel that it is a good tool as well.  We just found that in our SAP environment we got much better performance from the BSP tools.

Similar Messages

  • Advantages of BSP over Webdynpro ABAP

    Hi,,
    Can anyone please explain what are the advantages of BSP over WebDynpro ABAP, In what cases do we need to stick with BSP?
    Thanks,

    Hi,
    There is a SAP web GUI map and it contains different technologies as follows:
    If you have the SAP screen already available , then the best solution would be to go for the ITS solution(Web Gui).
    But if you were to compare the man days required to code a dynpro and a web dynpro screen from scratch then they would approximately be the same.
    Yes if you want to leverage on Web Dynpro you will have to currently code all screen from scratch , and encapsulate your backend logic as function modules.
    Apart from BSP you have the option to use Portal Development Kit (if you have SAP EP in your landscape) . JSPHTMLB(tag libraries)JCO running on WAS 6.2 or 6.4 or other Java server.
    If you have just one screen and currently dont have the WAS 6.4 in your landscape and it would involve delays interms of procurement , setup and training, then its better you go with either of the above solutions depending on the skillsets in your team.
    If you can make an FM of your trx, the BSP solution might be the easiest step. No additionial knowledge (except from some HTML(B)) is needed.
    Advantages of web dynpro:
    Additionally,
    I would say if you would want a quantum leap in advantages by preferring a UI solution , then it has to be webdynpro be it ABAP or Java.
    Some of the features that I have heard about and noticed as well is
    -> Metadata based which means tomorrow SAP could easily support a new client without you not requiring even to change a line of code.
    -> Support for Java gui and Win gui for web dynpro coming up(over http)
    -> More professional UI and flicker free
    -> Faster development time when compared to BSP or JSP
    -> Future proof
    Disadvantages:
    On the down side
    -> You loose control on so many things that you took for granted in web programming such as javascript support, DHTML
    Hope this will help you.
    Cheers,
    Darshna.

  • Advantages of ABAP Webdynpros over BSP??

    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

    >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.

  • What are the advantages..

    Hi friends,
          can you please tell me <b>what are the advantages of using MVC?</b> because <b>i can use ABAP Objects without using MVC.</b>
    Thanks in advance,
    Regards,
    Kannan.

    Hi Kanna,
            For Dynamically componentised you need to use controller.In the main page you partition for what you want to present dynamically and then call controller as a response to the user.What the action you have take in case of Page flow logic(Event Handler) need to be placed in controller.
    Using the MVC design pattern has the following advantages:
    ·        Structuring BSP applications is simplified, since the view is cleanly separated from the controller and the model.  This not only facilitates changing BSP applications, but also considerably improves their maintenance.
    ·        You have the option of generating program-driven layout. The HTML/XML output is therefore created by program code instead of a page with scripting.
    ·        Navigation using the <bsp:goto> element and call using the <bsp:call> element. The advantage of using <bsp:goto> navigation over redirect is that there is no additional network traffic. Furthermore, you remain in the same work process, which can have advantages for creating objects and memory space. The call using <bsp:call> element is more variable than adding them using INCLUDEdirective, since it is triggered at runtime.
    With the call option using <bsp:call>, you can also distribute the user interface into components.
    ·        Optimized performance due to fewer redirects.
    ·        Intuitive and east-to-use interface for application development.
    Main advantage of MVC is that you can keep these(Model View ,Controller) separately.If you need to change in logic you do not have to worry about presentation(View).
    Regards,
    Albert

  • Disadvantages of BSP

    hello friends,
    To the date we talked a lot about advantages of using BSP over JSP or so far, do we have some dis-advantages of BSP... are there any curcumstances where JSP is ahead to BSP or etc.
    Looking farward to your replies

    Hi,
    This has been covered in threads like
    JSP vs BSP in Real World
    Why of webdynpro and not BSP or JSP?
    Benchmarks: BSP / JSP
    Eddy

  • What is BSP extension?

    Could anyone please let me know what is BSP extension?
    Thanks in Advance.
    Best Regards,
    Vijaya

    Creation our own BSP Extensions
    Advantages of BSP Extensions –
    1.     Reduces the complexity of the BSP pages.
    2.     Reuse.
    3.     Clear-cut role distribution.
    4.     Tool support within the workbench by the BSP extension editor.
    Firstly while creating an element under the extension there is a provision for entering the attributes and then tin the element handler class Generally these are the methods that are to be redefined while creating our own BSP Extensions-
    1.     COMPILE_TIME_IS_VALID
    2.     RUNTIME_IS_VALID
    3.     DO_AT_BEGINNING
    4.     DO_AT_END
    COMPILE_TIME_IS_VALID –
         Determines at compile time whether correct values have been assigned to element attributes. The validation result is written to the return parameter valid.  The possible values for valid are ‘X’ or ‘’ (blank).
    RUNTIME_IS_VALID –
         Determines at runtime whether correct values have been assigned to the element attributes.
    DO_AT_BEGINNING –
         This method is always accessed at the beginning of the element call when the BSP page is processed.
    Using the return parameter RC you can control whether the content of the current BSP element is to be evaluated or not. The possible values of the return parameter RC are therefore: CO_ELEMENT_CONTINUE and CO_ELEMENT_DONE
    DO_AT_END –
         This method is accessed, whatever the case, at the end of the element call. Since the entire element content is available at this point, this method can be used for Manipulation of the Element Content.
    Using the return parameter RC, you can control whether the entire BSP page is to be evaluated further or not. The possible values are therefore: CO_PAGE_CONTINUE and CO_PAGE_DONE.

  • Show Dynpro from external application

    I was wondering which possibilities exist to show a Dynpro page of an SAP application within another 3rd party application (written in Smalltalk).
    As far as I know it is not possible to call an RFC which returns a Dynpro page, so which alternatives exist.
    What came into my mind is the following:
    - Using ITS and calling the respective URL from the external application to show the Dynpro in SAP GUI for HTML
    - Re-Write Dynpro application in WebDynpro
    - Re-Write Dynpro application in BSP
    - Call BAPI/RFC to get application data on backend side and create an new UI to show the data in the 3rd party application
    - Separate Logon to SAP systems
    Do you see any other alternatives?
    In my opinion the ITS solution is the only feasible way on a short term basis.
    Any comments are welcome.
    Thanks,
    Michael

    Looks like you've arrived at a pretty comprehensive list - depending on which version of SAP you are using, there's also the Web Service option to get data from SAP... or if you are very brave and the data is stored in a simple format (e.g. not BSEG!) then you could visit the database directly.  You've got the usual dilemma regarding which of the 2 front tiers need to be implemented where - the SAPGui for HTML means you can leave everything to SAP which has its advantages e.g. consistent business logic...( you could also use ITS over custom dynpros built in ABAP - but that's probably heading away from the market trend )... the next two options require a re-rendering of the presentation layer - the advantage of BSP would be the richness of the result, the advantage of the WebDynpro would be the potential for having the output rendered in other SAP-supported GUIs in the future e.g. Flex.  There may also be options around Citrix too - SAP training course here are presented this way via a browser-based solution.
    Jonathan

  • Why ITS and not WebDynpro

    Hello,
    I understand ITS was the first in the series to Web enable SAP Applications. Later BSP and now in 640 WebDynpro can be used to Web enable the SAP Applications.
    But why still ITS is retained? Does it have any advantages over BSP/Web Dynpro?
    In SRM-EBP,ITS is used & almost all transactions are Web Transactions.Why BSP/WebDynpro is not used to develop these transactions in SRM. Is there a specific reason to retain ITS-Web Transactions in SRM.
    Will it be retained in future SRM Releases or will ITS be replaced by BSP/WebDynpro is future releases.
    Thanks & Regards,
    Prasanna

    >
    Maria Graziano wrote:
    > Hey Thomas,
    >  
    >
    > I think we are experiencing a similar issue.
    >
    > We are using SAP GUI 7.10 and are trying to print cheques with smartforms using locl
    >
    > We need LOCL working as it is the preferred method for SmartForm printouts like the pay statement.  For groups like Payroll, they will want this to work.  Not using LOCL will make printing out of manual pay statements look bad.
    >
    > How should this be configured? and is it as simple as assigning LOCL to the users' default printer option?
    >
    > OR do they need to direct the pay statements to a particular printer... Just a bit confused
    >
    > Please advise
    > Maria
    Are you talking about printing from Web Dynpro ABAP?  If so, LOCL will not work.  There is no direct connect to the SAPGUI/Client in Web Dynpro.  You have to follow the same rules as when running in Batch - which means no LOCL printing.

  • SLCM Audit WebDynPro

    Hi,
    I noticed in Appendix B to the Audit Handbook that an audit viewer WebDynPro, available in EhP3, was showcased. Is this something that is going to remain available as a display-only application, or are there plans to develop this into a fully functional audit application? Can anyone (Michael) speak to whether there are plans to phase out development on the PIQ_AUDIT BSP application in favor of a WebDynPro in the future?
    Thank you,
    Eric

    Eric,
    Certainly we hope to turn the WD application PIQ_AUDIT_EXECUTE into a full-featured audit execution user interface (with subsitutitions, etc.), but I have no specific timeline for that yet.  As you know, WD offers many advantages over BSP.
    Michael

  • Advantages of SP13  for PI 7.0

    Hi,
       can any body give me  the documenation  about Support Pack13 for PI 7.0 ...  because  i need to give a demo on this  SP13 .. what are  the advantages of SP13 ..  and what are the new features.. these all thing i  want to know... so, can any body provide me  a brief idea abt that..
       i gone through  this link but i was unable to find the documenation .. so, plz provide me the helpful  information..
    https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sps/index.do?pvnr=01200615320900001250
    any help ... plz...
    Thanks
    Babu

    Hi Babu,
    Apart from the links provided these are also additions for sp13
    3.1     SP 13
    Some mapping programs require additional data from an application system to map messages to each other. Furthermore, you may want to reuse existing mapping routines from an application system.
    It was previously only possible to read values for/while executing message, Java, or XSLT mapping programs from a global value-mapping table. Also, If you wanted to execute calls to an application system during a mapping, you could use the Java Connector (JCo), for example. Calls of this kind are known as lookups, and were previously only visible in the program code of the mapping program. This Support Package Stack contains a new API for the mapping runtime that enables you to execute lookups for message mappings, Java mappings, and XSLT mappings (J2EE Engine).
    •        The lookup API contains methods for generically accessing application systems by using the RFC, JDBC, and SOAP adapters. Also included is a special API for the JDBC adapter, which simplifies the procedure for accessing application systems.
    •        You configure the access procedure by using a communication channel in the Integration Directory.
    •        When configuration is complete and the runtime is active, you can test lookups that are part of a mapping program by using the test environment of an interface mapping.
    See also:  Mapping Lookups
    Reward points if found useful.

  • Your opinion on:  BSP or Java Webdynpro or ABAP Webdynpro?

    Could you please give me your opinion on the business scenario we have here:
    We are implementing SRM 4.0 with backend R/3 4.6C, WAS 6.4 and Portal 6.0. SRM has its typical shopping cart applications mainly for procurement and the workflow trail displaying the approval. The client wants us to build a few custom forms on the web frontend of SRM (or may be in Portal). The idea is to store these forms and display when needed with the status info just like a shopping cart.
    <b>Now the requirements for these forms are as follows:</b>
    1. These forms will have multiple fields which need to have the F4 kind of help. (the F4 options will reside in SRM or R/3)
    2. The form should have some kind of a ALV grid  (autoexpanding feature) which will allow the user to put in multiple line items so that they could submit more items on one form.
    3. Users need to be able to attach a spreadsheet to the form which should not be editable once the form is submitted. The attached spreadsheet should be stored. (We are planning on using Archivelink Filenet for this)
    4. Upon submission, a workflow will be kicked off as per the defined Org structure for approval of the form.
    5. After submission, the user should be able to go and view the approval status of the form and also print the summary of the values that he entered in the form. (may be a smartform could be provided for this)
    We looked at different options to accomplish this task:
    <b>BSP:</b>
    Creating BSP pages and giving access as links to the user on the webfrontend of SRM. Now, if we go the BSP route, we need to develop in SRM as the R/3 4.6 c does not have BSP development capabilities. If we take this approach, I am not sure if all the above requirements (specially like attaching spreadhseets) will be met with BSP pages.
    SAP Webdynpro Java: 
    It seems that the Webdynpro is easier to use because of the graphical tools available. But the only problem if we go this route is that we will have to find a java guy.
    SAP Webdynpro ABAP:
    We currently have WAS 6.4. As per the documentation, the ABAP Webdynpro development tool is available from NW04s onwards. So, we are still not sure if we could use it. But, we want to push towards upgrading if necessary. Being an old time ABAPer, developing ABAP Webdynpro seems do-able. (i know it may not be that easy).
    Last but not the least, DIALOG Program:
    Creating a dialog program in R/3 or SRM seems fairly simple. Then, an iview could be created on the portal for this transaction, though at this point I am not sure how a spreadsheet could be attached and stored within a dialog program.
    The creation of the workflow may not be that bad after the original form is designed. The graphical display of the approval trail might be difficult, but we might get away with a report for that. For printing the details of the form, I guess I could develop a smartform and put out a button on the screen to print it out in the display view.
    Could you please give me your opinion /  best approach for accomplishing this task, keeping in mind the complexities of these new dimension products?
    Thanks
    Sri

    I would say that all four solutions to solving your tasks are technically feasible.  Here are some thoughts that I had however:
    First ABAP Webdynpro: it is true that ABAP webdynpro is only available with Netweaver04s.  04S is still in ramp-up which means that only a subset of the customer base is allow to implement it.  It will not become generally available until later this year (check the service marketplace for current release estimates).  That being said, it probably elimintes WDA as a possiblity for your project unless you are will to wait and to upgrade.
    However having worked with WDA for a while it is probably the best tool to custom develop what you describe.  It has excellent built-in F4 value help.  It also has a damn fine ALV grid implementation.  The spreadsheet could be just as simple as file upload in binary or your could try your hand at office integration.  Finally for the form you could use Adobe Interactive Forms which also has very nice integration into WDA. 
    Now to Dialog Programming: You could of course use dialog programming.  It seems a little bit of a waste to custom build something so large if WDA is in your near future.  There are obvious disadvantages (little OO structure, no MVC, etc).  You would have ALV grid, office integration and of course F4 help.  You could still use Adobe forms if you implement this on the 640 system.  However there are integration points with dialog and Adobe Interactive Forms.  You could still use printed forms however. If you did the dialog program on the 640 system, you could use the integrated ITS to expose it to the web.  The integrated ITS in my experience has quite nice performance although the look and feel remains just like the SAPGui.
    The Java Webdynpro route:  Well you hit the nail on the head - if you don't have a Java programmer already and you don't have the bandwidth to invest in learning Java, this can be a problem.  The Java Webdynpro environment is quite nice.  There are some things I like better than ABAP and some things that ABAP is defintely still better at.  However when it comes to heavy integration with an ABAP backend - ABAP Webdynpro is still the way to go.  Java Webdynpro does have a help feature (OVS), but it isn't "for free" or nearly as nice as the ABAP Webdynpro (perhaps it will get there some day).  That is one of the major advantages of WDA - its closeness to the business data brings several framework advantages like F4 and field help.  WebDynpro Java in 640 also doesn't have an ALV grid implementation.  I am sure that this is something both environments will eventually have, but right now ABAP has the advantage.  On the other hand, Webdynpro Java has equal support when it comes to office integration, file upload, and Adobe Forms support.  You would have a more difficult time integration SmartForms however.
    Finally we come to BSP.  Honestly if I were in your position I would probably choose BSP (unless you could wait for the ABAP Webdynpro upgrade).  You could build a nice MVC OO application using BSP (stateful or stateless).  The BSP product is mature and quite well documented thanks to SDN.  You have the BSP Extensions which when used in Design2003 use the Unified Renderer.  That means that your output will look nearly identical to the same UI elements in Webdynpro.  Also BSP supports portal integration (session management, eventing, and themes). 
    The downside to BSP is that it isn't a full framework (also one of its advantages).  You can insert all your own html and javascript (unlike webdynpro). But this also means that SAP doesn't delivery as many framework services.  For instance there is no ALV or Value Help.  There is no Office Integration or Adobe Forms integration.  There is some farily good Smart Forms integration.  Now the upside- many people have already hit these limitations and overcame them.  In the weblogs on SDN and in a certain SAP Press book (cough, cough) you will find out of the box solutions for many of these problems.  You can find ready to use solutions for Adobe Integration, Office Integration (using Microsoft Office Web Controls), and F4 help.  It will mean investing a little more time up front to get this "home grown framework" up and running - but it is perfectly feasible. 
    There is a learning curve to all these new technologies however.  This sounds like an abmious project.  I wouldn't want to try and tackle this project in any of these technologies if I was new to them.  With Webdynpro or BSP - consider giving yourself time to learn the environment and cut your teeth on some demo apps before jumping into such a huge development.

  • Enhancing standard BSP application by using WebDynpro components

    Hi all,
    We have standard BSP application delivered by SAP; we need to enhance the functionality and some new views to meet our requirement. We have planned to develop new things in WebDynpro ABAP and attach those to BSP.
    Is it good practice to use WebDynpro component instead customizing BSP application?
    If any body has fair knowledge on BSP and WDA, please let me know.
    Regards,
    Rajesh

    hi
    good
    BSP->
    It is a set of pages that represent a user interface (layout and page flow definition). The layout part of a page normally contains ABAP or JavaScript code which is inserted into the HTML structure. They can contain server-side scripting code in either JavaScript or ABAP. BSP applications use all the conventional ABAP technologies, such as Open SQL and internal tables, allowing developers to create Web pages quickly. This enables existing SAP logic, data structures, and interfaces to be directly used in Web applications.
    http://www.thespot4sap.com/Articles/SAP_WAS_BSP_Apps.asp
    WDA->
    Web Dynpro for ABAP or Web Dynpro for ABAP (WD4A, WDA) is the SAP standard UI technology for developing Web applications in the ABAP environment. It consists of a runtime environment and a graphical development environment with special Web Dynpro tools that are integrated in the ABAP Workbench (SE80).
    Web Dynpro offers the following advantages for application developers:
    &#9679;      The use of declarative and graphical tools significantly reduces the implementation effort
    &#9679;      Web Dynpro supports a structured design process
    &#9679;      Strict separation between layout and business data
    &#9679;      Reuse and better maintainability by using components
    &#9679;      The layout and navigation is easily changed using the Web Dynpro tools
    &#9679;      Stateful applications are supported – that is, if the page is changed and the required data remains intact so that you can access it at any time throughout the entire application context.
    Note that stateless applications are not possible.
    &#9679;      Automatic data transport using data binding
    &#9679;      Automatic input check
    &#9679;      Automatic operation of the Web Dynpro application using the keyboard
    &#9679;      User interface accessibility is supported
    &#9679;      Full integration in the reliable ABAP development environment
    http://help.sap.com/saphelp_nw04s/helpdata/en/77/3545415ea6f523e10000000a155106/content.htm
    thanks
    mrutyun^

  • Why to use htmlb elements in bsp applications

    Hi All,
       I have a doubt that why to use htmlb elements for implementing user interface in bsp applications .Implementing bsp application using htmlb is difficult than html because we have handle event triggering in oninputprocessing but this is not required in html.Can anybody help me out in understanding the advantages of htmlb over html. 
    Thanks in Advance......

    Dear Srilalitha
    Re: Why htmlb is prefered to normal html code ?
    Please go thorught this. This will surely help.
    Regards
    Vijay.M

  • BSP vs Web Dynpro ABAP

    Hello,
    we are looking for a listing that states the functional and technical differences between Web Dynpro ABAP an BSP.
    Is there anybody who has come along such a list ?
    Tx a lot in advance!
    Best regards,
    Ana

    Annette,
    check this
    The SAP Web Application Server (WAS) provides a page-based programming model with server-side scripting as well as server page technology for developing, designing and implementing Web applications:
    Business Server Pages (BSP). Server-side scripting enables direct access to all elements in the application server (such as function modules, database tables, ABAP Objects, and so on.).
    We can create HTML pages or Business Server Pages (BSPs) with server-side scripting in ABAP or JavaScript.
    The HTMLB and XHTMLB HTML Business libraries are available as BSP Extensions for a uniform layout and its associated usability advantages.
    And In the Web Application Server, the presentation layer is separate from the business logic. This makes it possible to implement front-end technology.
    Why BSP NOT WebDynpro
                              BSP
                  ABAP WEBDYNPRO
    Currently PMUSA/JMC customers are using Fire fox (Mozilla), Internet Explorer and Netscape navigator web browsers to access WEBUYPM application.
    BSP supports these web browsers.
    Restricted (Some of the features will not be supported by WebDynpro)
    Existing WEBUYPM application is written in HTML, Business HTML and JavaScript language.
    BSP supports these languages. And it allows even to mix ABAP, HTML and JavaScript thus has more flexibility to convert WEBUYPM application into BSP.
    Web Dynpro does not support HTML/JavaScript.
    Existing WEBUYPM displays the trade communications (Information tab) based on JavaScript and custom configuration file
    BSP supports JavaScript, we can display the trade communications in BSP too.
    Web Dynpro does not support Java Script.
    Existing WEBUYPM application has different colors schemes, Logos and graphical elements for PMUSA/JMC companies.
    BSP support s multiple color schemes/logo. These color schemes can be set dynamically based on company code selection at runtime.
    Separate Themes has to be developed for each User Interface elements.
    Development effort needs to be involved to even display a logo.
    BSP supports client side (user) validations. As most of these validations can be done at client side, the no. of hits on the server can be reduced and thus giving better response for the user inputs.
    In this way, performance can be increased.
    Web dynpro does not support any client side validations, every time the request must be sent to server to validate the useru2019s input. This increases the traffic and reduces the performance
    WEBUYPM application has logos, images.
    BSP supports Client side caching, and thus loads these element from client side very quickly.
    Web dynpro supports very little use of caching on the client side, and hence quite a significant delay in starting on some customeru2019s browsers.
    BSP has no restriction on user interface possibilities, Ex. Grid, drop down boxes, Font colors, size etc.
    Significantly more restrictive in user interface possibilities.
    Ex. Only those fonts, which are provided by SAP, can be used.
    Appearance can be changed dynamically using same web pages, to support different colors for different companies.
    We can have same (or better) look and feel if we convert the application into BSP.
    As there is no HTML coding involved in web dynpro the same look and feel as we have it today can't be achieved by using web dynpro.
    BSP is built for developing any type of web application (including mobile applications. It can be accessed from desktop, laptop, and any kind of smart devices like PDA.
    Web dynpro applications can not be accessed from PDA s (Not possible)
    Why WebDynpro NOT BSP
                 ABAP WEBDYNPRO
                               BSP
    Personalization can be given to the end user if they do not want see any of the user-interface elements.
    We can not hide any of the user-interface elements (Ex buttons ex) during the runtime.
    Note - Current WEBUYPM application does not support any of these options.
    Currently we are setting/retrieving the runtime context values in a session.
    Web dynpro supports State full applications.
    No additional development would be required. 
    BSP also supports to set runtime values and to retrieve the runtime context values, but minor development would be required to achieve this functionality. 
    Currently users can see view source for WEBUYPM HTML pages.
    Using Web dynpro this can be restricted thus providing more security to the application.
    HTML view source can be available to the users, Users can see the HTML client side code (not server side coding) as it does today.
    By using Adobe Flash Island, powerful web pages (RIA) can be created.
    But, Flash Island comes with Net weaver.
    BSP does not support Flash Island. But, BSP supports Java Script.
    JavaScript is essential for the new trend of rich internet applications (RIA), it is used by all the new applications, Ajax, Widgets, Flash, and even Microsoft is supporting JavaScript for the new generation of RIA
    Web dynpro has wizard tools to generate the code to create/configure the User Interface elements.
    Development effort would be required to create UI elements.
    We dynpro has uniformity as we use standard colors provided by SAP
    Uniformity can be achieved by using style sheets (minor development would be required).
    Thanks
    Bala Duvvuri

  • Advantages of WD4A

    Hi all,
    I want to know the advantages of Web Dynpro ABAP over Web Dynpro Java and BSP.
    Can anyone eloborate the comparision of WD4A over WD Java and BSP?

    Hi
    Basically there are pros and cons of webDynpro for ABAP .
    I am giving you wonderful link that made my many concept clear about WD ABAP and Java .One of which was Support over Mobile Devices .Yet WD ABAP dont have that Provision ,One has to Go for WD JAVA for Developing Mobile SAP solutions .
    <a href="/people/oliver.mayer/blog/2006/06/14/web-dynpro-abap-or-java in WD JAVA and ABAP</a>
    In my view WebDynpro ABAP and Wd Java are not same.
    Basically WebDynpro ABAP and Java are two different webDynpro provided by NetWeaver Stack.
    Basic conceptual base of WD ABAP and WD Java is same.I mean to say concepts like Context binding , node , elements , Layout both support are same.
    But when you provide background functionality to your Web Screen then Java or ABAP come in to picture.Just take case , you want do some thing on click of some button then
    1) in case of java may you will call some ejb or you will may write some java code on click.
    2) but in case of WD ABAP you have to do same thing with ABAP classes . You will call some call or some method of some system defined class.
    Ulimately point I want make
    1) WD ABAP and WD java 's Base is same but you code in completely different way.
    2) Purpose for which SAP came with two different WDynpro is different. Java can be used for developing quite sophistcated Web services.
    Hope I have clear your Doubt.
    Give point if It has served purpose.

Maybe you are looking for