Liquid UI - WS Reference Library

4.2.1 Using Liquid UI Server as a SAP Router

Liquid UI Server aka GuiXT Server can also be used as a SAP Router. To designate the Liquid UI Server as a SAPRouter, you must enter a SAP Router string into the SAP System Properties when you create your connection on the client system. The connection parameters for SAP GUI on desktop and mobile looks as shown below:


This system properties dialog box contains the following information:

  1. Description
    The description can be literally anything. Typically, this is either the name of the SAP server or the Liquid UI Server that the user will connect to. In our example, the description is ‘GuiXT Server’.
  2. Application Server
    The application server is the name of the application server the user will connect to. In our example, the application server is named ‘TEST’.
  3. System Number
    The system number is the system number of the application server. In most real-world cases, this will be ‘00’ as in our example.
  4. System ID
    The System ID is the SAP box to which the Server will be connecting. The System ID can be different depending on the corporate environment. Some examples might be ‘DEV’ for development, ‘QAS’ for regression testing or ‘PRD’ for production. Each of these can have specific data and restrictions associated. For example, development might be prohibited in PRD so as not to risk damaging the production system or data.
  5. SAP Router String
    The SAP Router string contains the actual IP address of the application server. In our example, the address is ’’. Connection strings are explained in more detail above.

    Liquid UI Server supports configuring SAP Router String in 3 different formats:

    • /H/<Router-String>
    • /H/<Router-String>/S/<Router-Port>
    • /H/<ApplicationServer-IP>

Sapproxy.ini Entries

When Liquid UI Server is being used as a SAP Router, you must also create a corresponding entry in the sapproxy.ini file. Using the settings in our screenshot as an example, the entry in the sapproxy.ini file would look as follows.








Important: When you configure Liquid UI Server as a SAP Router, you must specify both the TargetServer and TargetServerPort settings in the sapproxy.ini as 'saprouter' or the connection will fail. You must also ensure that GuiXT is not active on any clients that you will be using in this deployment. When Liquid UI Server is deployed, all Liquid UI customization is handled centrally, so you do not need to have Liquid UI enabled on the individual client systems.