Skip to Content

SAP Solution Manager – SAP GUI Shortcuts with SAP Router Strings

The SAP Solution Manager contains HTML applications which start transactions in the SAP GUI for Windows or Java. The transaction may fail to start for users who have special connection requirements. This may be the case for users who connect from outside the network where the Solution Manager system resides, and therefore require a specific SAP Router string in order to connect to the system.

We provide customizing for such situations. You can do one of the following for these users:

  • Specify a SAP Router string, or
  • Specify a system description in the SAP Logon application

In each case, you can do this for selected users or all users in your system. The Solution Manager will then always use the string or description you specify when it starts an SAP GUI transaction.

Note that even if the Solution Manager starts transactions in managed systems, you have to enter connection data for the Solution Manager system itself: the SAP GUI transaction always starts first in the Solution Manager system and then uses additional information to navigate to the required managed system.

Specify a SAP Router String

If you have users who need to access Solution Manager SAP GUI transactions using an SAP Router string, you can enter the SAP Router string in customizing table DSWPUSERPREFS. Make an entry in the following form:

  • USERID = ID of the relevant user, or “*” for all users.
  • PREFVALUE = The SAP Router string (e.g., /H/<ip-address>/S/<port>/H/)

If you have many users to maintain, consider creating a simple report to automate this task.

Specify a System Description

This may be an easier option to maintain, but you have to ensure that all relevant users maintain a uniform description for the Solution Manager system in their SAP Logon applications. Make an entry in DSWPUSERPREFS as follows:

  • USERID = ID of the relevant user, or “*” for all users.
  • PREFVALUE = The description in the user’s SAP Logon application (e.g. “My SolMan System”)

An example entry in DSWPUSERPREFS:

Adding a system with description “SAP Solution Manager with Router Information” in the SAP Logon:

The SAP Logon application with the new system entry:

Further Information

There are some (ancient) SAP Notes which contain this and related information:

  • 787481 – SAP GUI shortcut without SAProuter information
  • 2441973 – SSO2 logon for SAP Java GUI
  • 1447500 – Work Centers: Enable SAPGUI for Java with Mac OS X
  • 1609210 – SAP GUI and Internet Explorer browser settings
  • 965745 – Start SAP GUI for Windows instead of Web GUI
You must be Logged on to comment or reply to a post.
  • Hello Gordon,

    Thank you for this solution. It works well as a workaround.

    I'm just curious though, wouldn't it be better if the original code picked up the FQDN from the LMDB, instead of using the IP address? Then if there is not FQDN maintained in the LMDB, provide the IP address?

    I actually found an old OSS Note that mentions a very similar problem: Note 753724. It states that the problem is that shortcuts are created referencing the fully qualified domain name. At that time the solution was to change the code to just use the IP address. This solution does not work well in hosted environments. For the shortcut would work fully if it was created using the FQDN.

    You can see the problem in method SAPSHORTCUT_LAUNCH class CL_AGS_WORK_WEBSERV_APP_LN. Line 37. Here is where it gets the IP address, it should be getting the FQDN of the system in question from the LMDB, only if that is not supplied should it revert to direct IP address.



    • Hi Rocky,

      You can see that I created Note 753724 about 14 years ago, and this along with the other workaround described above have served us well through the years. That I why I would be reluctant to change this back to the FQDN - especially since we discovered that users access the SAP Solution Manager system potentially through several different FQDNs: even if we get the FQDN from the LMDB or the server itself, we can never know for sure which FQDN is appropriate for each user.

      Also note that we always need the IP address (or FQDN) of the SAP Solution Manager system itself: we do not need the address of the managed systems. The SAP Shortcut always starts a program in the Solution Manager system and then tunnels through an RFC connection to the respective managed system.



      • Hello Gordon,

        I know it's been a bit since we've corresponded on this topic. A couple of questions around this.

        1. I've noticed that The field DSWPUSERPREFS-PREFVALUE forces the character string to all uppercase, however, the Gui obviously allows Mixed case for the fields, any way to account for mixed case, or should you just always assumed all caps when creating the entry in the SAP Gui?
        2. Obviously several things in SolMan utilize this functionality: Launching executables from Process Management, Running a manual test in the test suite, Using System Recommendations to download a note to name a few. However, it seems to me that there is no way to leverage this functionality without having the SAP Gui available. Is there not a way to utilize the Web Gui? We'd prefer not to allow Gui access for end users, only allowing them to use the Fiori Launchpad. However, to leverage these functionalities, it seems you would have to allow Gui access to SolMan.



        • Hi Rocky,

          I believe most functions in the SAP GUI are case insensitive. That is why the DSWPUSERPREFS upper casing has never bothered anyone, I assume.

          In some cases you can set your preferences to use the Web GUI instead of the SAP GUI for Windows/Java. This is also possible with DSWPUSERPREFS (you can see we created Note 965745 to do the opposite). I don't have the exact parameter necessary handy though. However individual applications, such as those requiring office integration, may override the user preference for the Web GUI and launch the Windows GUI anyway: the application would not work correctly in the Web GUI.



  • I have followed the whole guide which tells us the shortcuts with all type of router strings. Please specify more system description as I have checked on the Canon Support Number where everything is available. Everyone can check the information on the website.

  • Thanks a lot for this blog, this has resolved our issue for mass download of documents in SOLDOC (Solman 7.2 SP08) . which was get wrongly directed in firewall and network  side and we lost almost couple of months for that.

  • Hi,

    I'm facing the issue nothing happens when I click on a navigation. I'm using MacOS with JAVA Gui 7.50 SP12 with ST 720 SP11 in the backend, so the mentioned OSS notes are already implemented. Adding a user specific entry in table DSWPUSERPREFS has no visible effect. Could you supply more usefull examples? And which configurations do I need in SAP Router?

    Are there any tools to test the navigation setup?

    Best regards, Toine