The purpose of the Liquid UI Server is to deploy software from a central location. It requires no software footprint on the user's machine. The developers can develop and access scripts from their desktops by installing SAP GUI and local software.
The Liquid UI Console window allows troubleshooting in a multi-developer environment. The developed scripts are then deployed centrally using a web repository, or network share. When deploying the software centrally using Liquid UI Server, make sure that the production and non-production environment is executed on different machines to prevent any disruptions in production environment usage.
Liquid UI Server for development can also be run in console mode as needed, thus providing users access to the console window for further server-level debugging. Moreover, Liquid UI allows you to deploy scripts in a variety of ways. The following section details the locations where Liquid UI and WS scripts reside.
Liquid UI supports four script directories, which are specified in the Liquid UI profile or the User Catalog.
Scripts on the Local drive
It is the most common method used by Liquid UI script developers and small testing teams.
Pros:
- Relatively easy to launch and use.
- Developers get complete control to access and modify scripts.
Cons:
- It requires high maintenance and is not intended for larger user groups.
- The user has complete control to modify or delete the scripts.
Example:
Directory1=C:\GuiXT;
Scripts on Network file server or a file share
This option can be used for developers, testing teams and end-users.
Developers, testing teams, and end-users can use this option.
Pros:
- Easy to launch and use.
- Centralized script management.
- Access to scripts can be easily administered through network policies.
- Network traffic can be reduced using the File Replication option available in Liquid UI settings.
Cons:
- Liquid UI requires additional requirements for script deployment.
- If different servers are used across a WAN, it requires launching additional replication and other features.
- For users to access these scripts, requires additional user privileges.
Example:
Directory1=\\DemoServer\LiquidUI\Scripts;
Scripts on FTP and/or Web server
This option can be used for developers, testing teams and end-users.
Pros:
- Can be used across company’s internal network.
- Centralized management of scripts.
- Network traffic can be reduced by using the File Replication option in Liquid UI settings.
Cons:
- Additional dependency on web/FTP server.
- The script download time can vary based on server response time.
- All users must have access to the web/ftp server.
Example:
Directory1=https://www.demoserver.com/LiquidUI/Scripts;; Directory1=ftp://ftp.demoserver.com/LiquidUI/Scripts;
Scripts on SAP web repository
Developers, testing teams, and end-users can benefit from this option. This deployment approach is not recommended for developers.
Pros:
- Centralized script administration with SAP's transport and correction mechanism.
- Automatic caching for reducing script downloads.
- No external dependencies.
- Change access can be controlled using SAP’s authorization mechanism.
Cons:
- Additional RFC overhead as scripts are retrieved from SAP using Remote Function Calls (RFC).
- Difficult setup for developers as it is not very easy to change uploaded scripts.
Example:
Directory1=SAPWR:Z.LIQUIDUI.DEMO;
Additional notes:
- RFC is executed in Client 000 unless explicitly specified in Liquid UI Profile.
- RFC User name and password must be present for Liquid UI (Default RFC User SAPCIPC, Password admin).
- RFC user must have proper authorization for Liquid UI to use (functional group SHD0 and SURL).
