- SAP Managed Tags
The Flex Client for Web Dynpro will be available later this year. It will work in such that your Web Dynpro ABAP application will render xBCML instead of HTML/JavaScript which in turn is interpreted by a Flex SWF provided by SAP that does the UI rendering. This will not require any changes to your Web Dynpro ABAP application - it is all runtime supported functionality.
Bluesky
- SAP Managed Tags
The Flex Client for Web Dynpro will be available later this year. It will work in such that your Web Dynpro ABAP application will render xBCML instead of HTML/JavaScript which in turn is interpreted by a Flex SWF provided by SAP that does the UI rendering. This will not require any changes to your Web Dynpro ABAP application - it is all runtime supported functionality.
- SAP Managed Tags
Yes it will - in fact it kind of already does. Visual Composer in NetWeaver CE already only generates Web Dynpro Java Components behind the scenes. If you want the Flex Look and Feel, it uses this same Flex Client on top of Web Dynpro Java to acomplish that. However this earliest version of the Flex Client only has enough UI elements to cover what is supported in VC. The newer version of the flex client is designed to support all Web Dynpro UI element.
However this newer version of the Flex Client is still in development. So right now we have only released the version that works with Visual Composer generated components. The newer general version that works with Web Dynpro Java and ABAP is still in development. That is why there isn't really any public documentation for it yet.
- SAP Managed Tags
>
> Good to know. That kinda sounds as if the webdynpro app itself will not have to be modified at all. Does this apply to CE webdynpro only or will be NW7.0 webdynpro apps supported the same way? How's the xBCML code generated? Will the CE be an requirement?
That is correct - the apps do not have to be modified in any way. Web Dynpro was designed years ago with this kind of future in mind. The application rendering is separated in layers. One of those layers is the UI rendering itself. It was strickly designed so that we could "plug-in" new rendering engines over time.
So what technically happens is nice bit of OO magic. There are multiple implementations of each UI elment rendering class, but they all have the same interface. That way the rendering engine can determine what kind of client it is building the UI for at runtime and substitute a different rendering engine by calling the correct subclass. The first rendering engine that SAP supplied for Web Dynpro is what is called the Unified Renderer. This is what produces the HTML and JavaScript UI that we run today in the browser. In NW 7.0 EnhP1 ABAP and NW 7.1 CE EnhP1 we have actually rewritten this Unified Renderer completely - improving performance and adding in more AJAX functionality. So this same plug-in rendering technology can be used to seemlessly overhaul the HTML renderer as well.
With this plug-in rendering technology we were able to build an XML based renderer. This XML formatted output is what we call xBCML (Extensible Business Client Markup Language). Actually if you compare the two rendering engines it is much easier to build an XML description of the UI then it is to build HTML/JavaScript. This nice, neutral XML description of the UI elements and their properties can then be sent to the client machine over HTTP/HTTPS and interpreted by different technologies. We use this same XML format within a Flex, Silverlight, and .Net Client Renderer. This is how SAP has built the Flex Client, Flash Islands, Silverlight Islands, and the NetWeaver Business Client Smart Client Renderer.
On the ABAP side of the house for Web Dynpro we are bringing all of this new rendering technology to the 7.0 release via Enhancement Packages. The dependency of the Business Suite to run on top of NetWeaver 7.0 is a pretty much a driving factor to make sure that new Web Dynpro technology for ABAP must make it into the 7.0 code line to be effective.
The Java side is less clear. We have really focused future enhancements to Java Web Dynpro within the 7.1 CE codeline. Our current plans are to deliver this functionality to WD Java via CE (some of it is already there in CE 7.1 and some will come later with CE 7.1 EnhP1). I would be a little suprised to see a backport effort to 7.0 Java given the focus on CE. I realize that this leaves ESS/MSS in a strange location - so if there was customer demand around that application it might be the only thing to lead to a selective backport - but I certainly can't confirm that this will happen.
- SAP Managed Tags
>
> Hi Thomas,
> what do you mean with "The dependency of the Business Suite..." ?
> Could you explain me better if NW70 Enhp1 fits into SAP ERP 6.0 ?
> The real question is: when Web Dynpro Flex Island (or Web Dynpro Flex Client) will be available in SAP ECC 6.0 ?
> Thanks a lot,
> Sergio
Really there is no dependency to the Business Suite for the NetWeaver Enhancement Packages. SAP Enhancement Package 1 for NetWeaver 7.0 can be applied to any business suite application that is already running on NetWeaver 7.0. There is no technical dependency that you be on a partciular ERP Enhancement Package. In fact you can choose to have none of the ERP EnhPs installed and still upgrade to the NetWeaver Enhancement Package. The only dependencies are that the SPAM tool be a particular level and that you either have a certain level of NetWeaver Support Packages (SP15) on your system or that you merge these support packages into the Enhancement Package application process.
Now the dependencies will go the other way. ERP Enhancement Package 4 will be dependent upon NetWeaver 7.0 Enhancement Package 1. The NetWeaver Enhancement Packages will become prerequisites for the Business Suite Enhancement Packages, but not the other way around.
Now what I meant in my original quite is something different entirely:
"The dependency of the Business Suite to run on top of NetWeaver 7.0"
What I was refering to there was the decision two years ago that there would not be a major upgrade for ERP until at least 2010. We extended the maintenance on ERP 6.0 and decided to introduce innovation via Enahancement Packages instead of full upgrades. This locked the Business Suite into the NetWeaver 7.0 ABAP AS since you can't do a full upgrade of ERP to get it to the newer full versions of NetWeaver 7.1. Therefore we have to follow a similar pattern and backport 7.1 ABAP functionality into the NetWeaver 7.0 code line to serve the needs of the Business Suite development - hence the introduction of the NetWeaver Enhancement Packages. I wasn't talking about any kind of technical dependencies - just the business reasons why we have to have the NetWeaver Enhancement Packages and reassurances why Web Dynpro ABAP will continue to get new features on the 7.0 codeline.
| User | Count |
|---|---|
| 3 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
