BSP versus J2EE development

[kimmo_sirpoma]

I read the topic 'Future of BSP'.

Actually SAP will have several development options on building WEB-applications: BSP, Webdynpro, plain J2EE development (with Jco). Could somebody clarify what is the best approach? I mean, there is not necessarily one best option but BSP could be fine for something and pure J2EE development on something. It varies according to requirements I think.

I am wrong if I say:

• BSP is good for todays WEB programming as WAS6.40 is not publically available or at least customers does not have it.

• BSP is good for small scale development ( not for large portals or shops ). You easily get results.

• BSP is good if customer does not have existing J2EE architechture

• BSP has some limited capabilities. I mean you could write as complex applications as HTMLB and clientside JavaScript allows you to do.

• J2EE development is good if customer has previous J2EE applications and therefore intrastructure exists already

• J2EE development is good for large scale development like portals and shops

• J2EE development allows you to build as complex applications you like to

By the way, SAP promotes webdynpros from now on. But they are still making new development with J2EE world like their applications Internel Sales and Customer e-services for Utilities ( which both use J2EE and struts framework and Jco ).

[Former Member]

Hi there,

I can only speak from experience...I've been developing Java iViews for just over a year now, and just recently I've gone head first into ABAP and BSP development for our Portal - (wanting to become Java / ABAP bi-lingual)

Both have there pros and cons:

1) You have MORE flexiblity with Java...I mean one of the big things for us is Excel upload and download functionality (Suppliers really seem to enjoy that sort of functionality)...now with Java you get some AWESOME libraries like "jxl.jar" for handling Excel files (great for formatting etc), but with ABAP you basically just say "put this internal table into an Excel file" - formatting is very limited and things like LOCKING certain rows / cols is not possible (I think). Also when you think about uploading an Excel file via a BSP into SAP, typically something like the following would have to happen....get the binary of the file being uploaded and write it to the server (whereas in Java you just deal with objects in memory...no writing out of files!!), then it'll probably be easier to read in the internal table from a CSV file so now you need to call (as an example) the "jxl.jar" library from the command line and pass it the Excel file on the server and get back a CSV file, then you can only VALIDATE the file and once done can pump the internal table into SAP...

2) Debugging a BSP is FAR easier than debugging a remote Java application in Eclipse...a BIG bonus for a developer!!!

3)Obviously the company needs to see what their skill set is...obviously if they have ABAP developers then BSP's are a better choice for now BUT I personally feel that LONG TERM Java will be the language of choice in the integrated SAP environment.

4)You can whip up a simple BSP application in no time at all...even though I'm a Java developer I can still develop BASIC iViews quicker in BSP than in Java.

That's all I can think of for now....I'm very keen to see the ABAP Webdynpros...I'm made one or two Java Webdynpros and it looks really cool...finally get a bit of drag and drop functionality!!!

Regards

Lynton