instal the new PasswordGenerator 23.6.13

HTTP – through Web Dynpro and NWBC – is the future anyhow -). To keep things simple, I will only look at HTTP rather than the DIAG protocol used by SAP GUI. I’m not going to worry about client-side CPU impact, as there are many more clients than servers, and they’re all multi-core systems running idle most of the time anyhow :-). Let’s try to get a handle on this by looking at the impact of switching to SSL to both network performance and server-side CPU load.

To me this has always seemed strange because SAP applications contain a lot of information I thought companies would be interested in keeping safe and secure: customer data, accounting information, salary information, etc.Įvery time I asked the question of a Basis consultant though, I received an answer along the lines of “SSL introduces too much overhead”, or it “slows things down”.īut hang on, it’s 2013! Google searches are now all done over HTTPS by default, for 38,000 search queries per second! So how hard can it be? I’ve often wondered why I see so many SAP systems which don’t offer SSL connections for their client applications, be they traditional SAP GUI clients, browsers running BSP or Web Dynpro applications or the IE runtime embedded into Netweaver Business Client.

Instal the new PasswordGenerator 23.6.13