First kindly notice that variables listed below are valid only for WINDOWS operational system. Some of them are very useful (e.g. to set path to ini file). On other hand some of them are not very known (e.g. RFC related ones). The list is not complete for sure; anyways here it is:
SAPLOGON_INI_FILE – location of initialization file (saplogon.ini) with all the entries with connection strings to SAP systems
RFC_TRACE_DIR – location where trace files (rfc*.trc) are stored
SAP_CODEPAGE – to set code page for communication between GUI and SAP system (e.g. UNICODE systems). Used in cased when client has different code page (by default) then server.
RFC_TRACE_TIME – runtime analysis on the external RFC communication
DPTRACE – activating trace can be be activated using this variable
ABTR_TRACE – trace between GUI and RFC; trace is written when this variable is set
TDW_TIMEOUT – specifies timeout of connection to message server by default it is 10 seconds.
SNC_LIB - variable specifies the path to the gssntlm.dll file.
P.S: in order to set operation system environment variable in WINDOWS use set command. E.g.: SET SAPLOGON_INI_FILE=%APPDATA%\SAP\SAPLOGON.INI
Have you ever wonder about SAP BW report that was accessible from your location but was not accessible for user located on other half of globe? In such cases we need to consider possible network or infrastructure issues which may pop up. How to make sure that reports are available from all users’ location? You cannot sit everywhere to check out it. Having local IT to check it is in case of small offices also an issue. There must be some way how to automate it. There is a tool for that. It is called SAP End-User Experience Monitoring (EEM) and it basically does the evaluation of IT systems from end user perspective. By this your IT department can be informed about issues up front before users even recognize it.
In my experience we just used in case of BW for checking either critical BW reports are up and running before users get into the offices. We set up several robots for report checking. Their results were collected in Solution Manager. IT is then notified by SOLMAN about any report outage.
Agree or not but as with every complex software system it is quite high effort to keep it running. SAP is not exception thought. To make it at least survivable SAP is offering as a part of their methodologies so called End-to-End Solution Operations. It is available on SAP Service Marketplace/OSS; under shortcut: service.sap.com/e2e. It is separated to 2 main parts:
·Business Process Integration & Automation Management