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.
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.