command you can reduce web traffic to a single access-to-server operation
per SAP logon when using scripts from the SAP web repository, SAP Mime
Repository or from ftp/http
By means of VersionNumber xxx you insert into the session script esession.txt (e= language key, fsession.txt for French) a freely assignable version number. The logon script and the session script will be newly loaded each time from the web repository or from the chosen ftp/http server, never from the local cache. GuiXT will now seek out all further scripts directly from the local cache, the index names of which have been gleaned from the GuiXT profile, and to which the chosen version number has been added. As a rule there will be no further cause for access to the scriptserver so long as the user calls up no further SAP screens. Without VersionNumber, on the other hand, each and every script would have to be newly cached for each SAP session.
Please note: Use the VersionNumber only in the "session" script, not in other scripts. Otherwise a different VersionNumber in one of the other scripts can invalidate the cache.
With 400 users, 30 different SAP screens per user and 500 dialog steps per user, the following numbers of access-to-server operations may be calculated for an integrated system:
Later on, should you wish to carry out changes to the GuiXT scripts and make them effective for all users, you simply increase the version number. The next time SAP is called up, GuiXT reads the new version number, effaces the previous cache index and proceeds to fill a new cache under the new version number.
With VersionNumber following data from the SAP Repository will be stored in GuiXT cache and will be only refreshed if the version number increased:
Please note that string is to contain only those symbols that are permitted for index names in Windows, preferably just letters and numbers.