Skip to Content
Author's profile photo Vijay Kumar Kalluri

New Features in Webdynpro JAVA CE 7.1& 7.2

Hello Friends,

Web Dynpro Java and Ajax in SAP NetWeaver CE 7.1 enhancement package 1

SAP NetWeaver CE 7.1 (CE) enhancement package 1 is currently available for download as beta software on SDN. The new SAP NetWeaver Business Process Management and Business Rules Management are certainly the most prominent and biggest changes in enhancement package 1. They has received their fair chair of well deserved coverage on SDN. With the spotlight on the new BPM functionality it’s easy to forget and overlook the other enhancements that are being made to CE. One of those, and the focus of this blog, will be the new Ajax capabilities in Web Dynpro Java.

But wait, you may say. Isn’t Web Dynpro already using Ajax? No, although I always refer to WD features such as flicker free refreshes and table paging and on demand loading as ‘Ajax like’, it was all SAP developed technology under the covers to accomplish these things. With CE 7.1 enhancement package 1 we are adding Ajax to the mix – namely using the XMLHttpRequest Object as the communication mechanism between the client and the server.

The SAP NetWeaver CE 7.2 Trial Version can be downloaded from the SDN download area. It can be used for instance to try the examples from TechEd 2009.

Highlights of the new features are

a) SAP NetWeaver BPM (Business Process Management):

  • Business user oriented process modeling
  • Support of Visual Composer UIs and offline SAP Interactive Forms by Adobe
  • Process reporting for composite business processes via rapid dashboard development (Visual Composer)  and SAP NetWeaver BW integration
  • Embedded Sub-Processes
  • Intermediate Message Events (allows process execution in asynchronous scenarios)

b) SAP NetWeaver BRM (Business Rules Management):

  • Business user oriented Web-interface
  • Graphical modeling of complex rules
  • Support for flow rules
  • Integration with Microsoft Excel
  • New rule testing and verification capabilities

c) Composite Developer Productivity

  • Composite Designer
  • Service Simplification and Mocking
  • Web Dynpro support for UI snippets for faster UI development
  • Visual Composer: Integration with SAP NetWeaver BPM, new model debugging capabilities, Context-sensitive help …
  • Enhanced Java EE Development Tools (i.e. Composite Designer Integration, JPA modeler, WTP 3.0, …)

Java Web Dynpro (Enhanced) :

Some new functions and features were added to Web Dynpro for Java. The following sections list the improvements made to Web Dynpro technology in the Web Dynpro runtime of the NetWeaver Application Server and in the design time in form of the Web Dynpro tools of the Developer Studio.

Portal Integration

Screen Print in Browser

Using a print button in the application, or via the print entry in the iView menu, the assigned iView is rendered in a new browser window in a print preview mode. This screen then can be printed without scroll bars and without IFrames. Currently, there are a few restrictions when using the new print option:

●      Internal scroll containers are not dissolved in browser print

●      When printing tables only those lines are printed that are part of the displayed application screen

●      Printing background graphics needs to be triggered manually

●      Page breaks are not always considered correctly

Partial Screen Updates in Page Builder

The Page Builder API which supports controlling the page size, refreshing the page and paging personalization now also provides the new feature of displaying partial screen updates.

iView Splitting Application Property

A content administrator can create individual iViews from each view in an application, in order to rearrange the layout of the application and to incorporate non-Web Dynpro iViews among the Web Dynpro iViews. To do this, the application must be developed to be split up into different iViews. Enabling a Web Dynpro application for iView splitting is done within the application properties wizard in Web Dynpro tools.


Support of setApplicationDirty() in wdDoPostProcessing()

Application developers can set the application mode to “dirty” by using the setApplicationDirty() method via wdDoPostProcessing().

destroy() method Returns IResponseResult

The destroy() method of the IApplicationProxy returns an instance of IResponseResult to enable the application to unsubcribe for an portal event in the wdDoExit() hook method.

Resource Service

The Resource service allows you to create context attributes of type Resource to bring files to context.

WDDeployableObject, WDConfiguration and WDURLGenerator API News

Methods which take the deployableObject as input parameter to access a deployed application resource have been deprecated. The deprecated methods have been replaced by corresponding methods which take an IWDWebModule as input. The deploy SAL service has been extended by IWDWebModule and methods to access an IWDWebModule.

Web Dynpro Source Migration

A Web Dynpro source migration tool removes legacy usage of internal classes.

Design Time Tools – News

Window API

The new interface with method void setTitle(String title) supports setting a title for the application unit Window.

Exception Definition

Defining exceptions for single controller methods can be done with wizard support now. The wizard is available for all controller/context types and started via the Methods tab.

User Interface Elements – New Attributes


There is a new design attribute which offers the possibility to render a ToggleLink without underline.


ToolBarButton spacing is computed automatically depending on item type. UI designers only need to place separators between item groups.

Administration and Configuration

Admin P13N

As of now, the Admin P13n standard is supported when the application is started via object-based navigation (OBN).

Invalidation of Metadata Caches

From the adminstrative tool Web Dynpro Console, invalidation of metadata caches is supported. This is useful if the application is using data from an SAP backend system where several caches are involved to keep the backend data values. This feature encreases adaptability of backend data.

Domain Relaxation

Domain relaxation code is required for cross-frame JavaScript; this is particularly important for Portal integration. Developers assign the application property domainRelaxation from the Web Dynpro tools environment.

User Support

In addition to the error page, also a Help Center is started and displayed to support users in case of dumps and fatal errors. Furthermore, embedded support data from the application is shown.

Referred links :

What’s new in SAP CE Version:

CE 7.2

CE Version Overview:


Vijay Kalluri

Assigned Tags

      Be the first to leave a comment
      You must be Logged on to comment or reply to a post.