I have been writing a series of (very occasional) KBA’s & Wiki’s on the NW Client subject and I feel it is now time to share my experience with you in a more.. say informal way .. I want to use that first blog page to share my experience on the topic so hopefully I can help SAP administrator pointing to the right lecture and material and also with the requirements prior to rolling-out the front-end software.
Before you might even want to start off with the SAP_Front_End_Installation guide there are some background lecture that might be useful to look at.
For example, the SAP GUI family presentation is very useful to start with. That document discusses the different kind of GUI solution available (SAP GUI for Windows, SAP GUI for Java, SAP GUI for HTML- aka WebGUI), why several GUI’s are available to access SAP back end systems and shall hopefully give you a clear picture to determine which one is the right GUI technology for your organization needs.
Talking local installation, your choice will then be restricted to either WinGUI or JavaGUI.. and due to the limitations of the JavaGUI (listed in page 19) in comparison for Win GUI, and (again) because the percentage majority of market share of the operating systems used in computers remains in favor of Microsoft Widows OS..you will probably decide to deploy SAP GUI for Windows on a Windows operating system environment.(WTS/Citrix included)
Note that Java GUI can be installed on Windows also…
In addition, the SAP GUI Technical Infrastructure pdf file provides at a lower level of abstraction information about the client architecture and should help understanding how they communicate with the SAP system. It also explains the performance requirements of the infrastructure and describes troubleshooting options.