Problem with IE after installtion of SAP NetWeaver 2004s ABAP Trial Version

[Former Member]

Hi Guys,

I installed SAP NetWeaver 2004s ABAP Trial Version from this website. And now my Internet Explorer can not show the right popup information. Instead, it will directly go to SDN web site. Another thing is the print functionality of Internet Explorer has been disableed automatically after the installation. Any help is highly appreciated!

Bao

[Former Member]

Hi Bao,

For Web Dynpro ABAP you need :

WAS 7.0

NetWeaver 2004's

ECC6.0 onwards.

Prerequisites:

For Web Dynpro ABAP there are configuration settings for the areas ICM and ICF, as well as for the View Designer.

· HTTP/HTTPS must be set in the ICM (see also Displaying and Changing Services).

· The following configuration prerequisites must be fulfilled:

¡ ICF services must be activated.

If a service is not activated by default, you can activate it from the SAP Implementation Guide (IMG). In transaction SPRO choose Display SAP Reference IMG. The path in the Implementation Guide for SAP NetWeaver is: Application Server ® Internet Communication Framework ® Activate HTTP Services or Activate Services in Installation.

For more information see SAP note 517484.

¡ Administration of (ICF) server functions (authorization assignment): Administration of Server Functions

¡ Administration of (ICF) client functions (creation of RFC destinations, and so on): Administration of Client Functions

· For the layout editor in the View Designer, in addition to the services for Web Dynpro ABAP listed in note 517484, the following services must be activated:

¡ /sap/bc/webdynpro/sap/public/bc/viewdesigner/

¡ /sap/bc/wdvd/

SSO must be set up on the respective application server (see also the security section in the table).

Check the following link:

http://help.sap.com/saphelp_nw2004s/helpdata/en/7b/fb57412df8091de10000000a155106/content.htm

In previous preliminary versions there were several other values in addition to delta (default value of server-side delta rendering) and doubleBuffer, e.g. raw (for test purposes) and embedded (for portal integration). Before server-side rendering was introduced as standard there was a client-side framework which was, however, dropped in favor of server-side rendering.

Hope this will help!

Cheers

Darshna.

Message was edited by:

Darshna Thole