Showing results for 
Search instead for 
Did you mean: 

improve performance loading WD4A app "in NWP"

Former Member
0 Kudos


In our Portal (EP6 SPS16) several iViews run, which call Web Dynpro for ABAP apps on a different WAS7-server.

When clicking on an iView it takes 'some' time before the apps show.

There are several options to tweak the performance (or influence the user-perception of performance):

- improve the WD4A app, so it loads faster

- show a message "loading app"

- use browser caching (iView)

Are there other ways to improve the performance? Is it possible to cache the WD4A on the WAS-server?

Best regards,


Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos


I have a similar challenge. I've traced the HTTP traffic using HTTPWatch and there are 1MB of data which are loaded into the browser client from the server. The absolutely biggest files are:

sapUrMapi_ie6.js with 458KB

popup_ie6.js with 120KB

ur_ie6.css with 214KB

That is 800KB (or 80%) of initial load come from 3 js and css files.


How can I reduce the load time for these files? and/or

How can I reduce the size of these files? and/or

How can I avoid that alle these files are loaded although I may not need them (e.g. popup_ie6.js).

Important: In my scenario we are working in the Internet!!

Thanx for any hints!



Former Member
0 Kudos

Hello Volker,

1. switch on caching in browser

2. switch on compressing on abap-server

Best regards

Oliver Prodinger

Former Member
0 Kudos

Hi Oliver!

Like already mentioned we are in the INTERnet and not in an intranet. I do not know the browser settings and of course cannot influence them.



Former Member
0 Kudos

1) Is there any additional help, to reduce the size of the mentioned big files yet?

2) How can I turn on server compression? If I run my WDA App over the portal, I'd use the portal server?

Thanks in advance.

Former Member
0 Kudos

Hi Mark,

It all depends on how efficient is your Web dynpro application.

What is being called on portal?

Which rfc Library is it using ?

It should be a recent RFC library. If so complex structures are supported.

When using complex import and exporting structures instead of table statements,

the TABLE compression and delta table content handling isnt used.

But it can still perform ok. It just may not be using optimal compression.

Complex structures are just sent of the network.

Performance issues depend on your network and how much data is sent.

How much data is to be sent ? ASk you netowrk admin team if it is likely to be an issue.

The rfc library should cope.

The 64 mb limitation was removed over 10 years ago. The call is now limited to the receivers ability to hold data in memory. 2 Gb for a table on 32 bit systems.

Hope this clears your doubt!