Skip to Content

In this weblog I present how to run SAPGui for HTML in Google Chrome even if it is not supported.

I executed the transaction “FI02 – Change Bank” in  a NW 7.01 to check how much Chrome is faster than IE.

The first test is to open the Webgui in Chrome via the link http://<server_name>:<port>/sap/bc/gui/sap/its/webgui?~transaction=FI02 ; you should get the message “This browser is not supported“. SAP Web AS knows the browser type querying the user-agent HTTP header.

Hacking Google Chrome it’s possible to specify a different user. Now I explain how to change user-agent in Chrome:

create a shortcut to Chrome file .exe with this parameter: “C:Users<logonuser>AppDataLocalGoogleChromeApplicationchrome.exe -user-agent=”Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)” and after executing the instruction put the webgui link ( for example http://<server_name>:<port>/sap/bc/gui/sap/its/webgui?~transaction=FI02 ) in the address bar and appears the transaction FI02 in WebDynpro ABAP as in the following picture.

FI02

Insert a bank country, bank key and press enter.

Now open the same link with another browser ( IE8 for example ) and insert the same data.

My feeling is that Google Chrome is really faster than IE.

As I presented in the blog (Measure Web Dynpro for ABAP rendering via Google Chrome Inspect  (Using Google Chrome Inspect element to measure the new Unified Rendering Light Speed in Web Dynpro ABAP)) Chrome offers also the Inspect element to perform accurate measurement of the Webgui rendering.

It follows a screen shot where we can also observe that WebGui doesn’t use Ajax technology. In the colored bar XHR (_X_ML_H_ttp_R_equest ) is not present; we verified instead that it was used by the new rendering of WDA in NW 7.01.

!https://weblogs.sdn.sap.com/weblogs/images/251764518/Inspect.png|height=206|alt=Inspect|width=584|src=https://weblogs.sdn.sap.com/weblogs/images/251764518/Inspect.png|border=0!</body>

To report this post you need to login first.

4 Comments

You must be Logged on to comment or reply to a post.

  1. Thomas Jung
    Well I get to cheat because I get access to the latest version of the software still in development; but I can say that the fact that SAPGUI for HTML doesn’t use the AJAX channel does change in the next Enhancement Package.  In NetWeaver 7.0 Enhancement Package 2, the SAPGUI for HTML ITS rendering also uses the Lightspeed UR rendering that came to Web Dynpro ABAP in 7.01. As you can see from this screen shot, the XHR rendering is included in SAPGUI For HTML pages as well.

    http://www.flickr.com/photos/tjung/3635684539/

    (0) 
    1. Alejiandro Sensejl
      Hello Thomas,

      it’s great news that the ITS will use Lightspeed UR!

      Can you tell me if there is any way (rss, blogs like your enterprisegeeks, sap notes, etc) to subscribe to such hot “on the horizon”-updates of ABAP development beside from catching some small pieces of information in SCN every now and then? As an application developer I am very interested in staying up to date with everything that allows me to provide more efficient programs with greater usability!

      Best regards from Germany,

      Alej

      (0) 

Leave a Reply