Development Trends

For quite some time now SAP and Adobe has presented different methods and initiatives you could use if you would like to integrate Adobe Flex and SAP Netweaver.  I will try to summarize four different scenarios you could consider.

Using SAP Flash Island scenario

If you are using Netweaver 7.0 EhP1 or 7.1 then you can use the SAP Flash Island framework to integrate Adobe Flex with SAP (read more about SAP Flash Island here). The framework will create a ‘bridge’ between a SAP WebDynpro application and Flex. In order to ‘connect to this bridge/framework’ – you need to use a library from SAP in your Flex project – I have created a template project you can use for this purpose click here. Flash Islands are best suited for smaller applications/components – especially for areas where you are missing UI functionality in the WebDynpro, e.g. could be advanced graphics, interactive maps, graphs and statistics. Authentication, User and session management will be handled by the WebDynpro application.

Using SAP BSP and an embedded Adobe Flex component

So what do you do if your application is SAP is not based on WebDynpro – then you will be missing the framework and bridge which will make it easy to communicate with an Adobe Flex application – or ? Well in SAP BSP you can use <object><embed> … </embed><object> to include an SWF application in the application – read more here.  But the data binding and event handling you will have to handle yourself in the BSP and in the Flex application. This kind of integration is also meant for smaller applications/components – especially for areas where you are missing UI functionality in SAP BSP, e.g. again could be advanced graphics, interactive maps, graphs and statistics. Authentication, User and session management will be handled by the SAP BSP application.

Using an HTTP REST backend application in SAP BSP – and an Adobe Flex RIA as Frontend

So… what do we do if we want to build a larger application in Adobe Flex (RIA) which should be integrated with SAP Netweaver? Well.. One possibility would be to build a set of backend services in SAP BSP using the HTTP REST approach/architecture (read more here). In SAP you will then be building normal BSP’s which will receive the input parameters in a HTTP request – and send the reply to the calling application as XML. These services can be called from Adobe Flex using the HTTP-request object. The work could be divided in two parts: the work regarding the design and implementation in SAP and the work with the design and implementation of the RIA using Adobe Flex. In between you need to describe and design the implementation of the interface. User and session management could be handled by the SAP BSP application if it’s running as a state full application. Regarding Authentication you need to consider how you would implement this in the application.

Using WebService enabled SAP BAPI’s as backend application – and an Adobe RIA as Frontend

In the last method you could consider using Webservice enabled BAPI’s instead of having to write BSP’s to communicate with the frontend. From Netweaver 6.40 and onwards all BAPI’s in SAP could be webservice enabled – and from 7.0 the functionality has been improved. And it’s possible to call these webservice enabled BAPI’s directly from Adobe Flex. You can use standard BAPI’s and/or make custom development for your own specific BAPI requests. User and session management should be handled by the Adobe Flex application. Regarding Authentication you need to consider how you would implement this in the application.

A couple of weeks ago I went to the SAP CRM course CR580 – SAP CRM User Interface in London – a course about the new UI in SAP CRM 2007 – and it was quite an interesting course.

One feature you will notice rigth away – is the improvements to the user interface. I guess you could say that SAP CRM has been ‘AJAX’ified’   and suddenly you start dreaming about more RIA in SAP. And all the screen flikering is gone – and the UI works quite well.  It’s actually quite impressing…

But during the course something happend which confused me a bit – because I thought SAP had a quite clear Web UI Strategy in generel. In connection with the introduction of the course, the instructor told us about SAP’s considerations regarding the underlying development framework to use when building SAP CRM 2007. The CRM team were looking at a Web UI technology which was: stable, with a good performance, and a framework which offered a flexible and extendable user interface…    so thinking about the SAP Web UI strategy – you might think you have already guessed the answer… it could only be SAP WebDynpro… No?

SAP CRM 2007 is built in SAP BSP !! – and let me just underline I have no specific preferences to either BSP and WebDynpro (I love both of them) and I have done a lot of development with both frameworks, but I cannot understand why SAP decides to use BSP when the chosen Web UI strategy is WebDynpro? When I read about WebDynpro, SAP uses a lot of time to explain why we should use Webdynpro – and so far I haven’t seen them claim that WebDynpro should be less stable than BSP, perform worse compared to BSP and that WebDynpro should be less flexiable and harder to extend compared to BSP. So why SAP – why was BSP a better choice for SAP CRM 2007?

And how well will this match some of the other initiatives targeted towards WebDynpro? E.g – we are all looking forward to start using SAP Flash Islands. In order to do this – the underlying framework should be WebDynpro. And I guess SAP CRM could be quite an interesting platform for SAP Flash Island? I know it’s possible to embed Adobe Flash in BSP directly, but you will be missing the smart integration from the ‘real’ Flash Islands.

Seen from a development point of view – there is a new tool available together with SAP CRM 2007: “The BSP Component Workbench”. With this new tool you can extend your CRM solution without making modification to SAP standard, and this tool is so cool that I am already missing it in SAP ERP.