Liquid UI - WS Reference Library

3.1 Deploying Liquid UI Scripts


Liquid UI offers very flexible means of deploying scripts. Following section discusses various locations of GuiXT aka Liquid UI and WS scripts can reside.

Liquid UI supports four script directories. These directories are specified in Liquid UI profile or in User Catalog.

Scripts on the Local drive

GuiXT aka Liquid UI script developers and small testing team usually use this option.

Pros:

  • Relatively easy to setup and use.
  • Developers get complete control of scripts for modifications etc.

Cons:

  • Not meant for large group of users. High maintenance option.
  • User has control of scripts and users can 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.

Pros:

  • Easy to use and setup.
  • Centralized management of scripts.
  • Access to scripts can be easily administered with use of network policies etc.
  • Network traffic can be reduced by using File Replication option in Liquid UI settings

Cons:

  • Additional dependency for using GuiXT aka Liquid UI.
  • Additional replication etc. must be setup if different servers are used across WAN.
  • Additional user privileges must be setup for users to access these scripts.

Example:

Directory1=\\DemoServer\GuiXT\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 File Replication option in GuiXT settings.

Cons:

  • Additional dependency on web/ftp server.
  • Script download time can vary. The download time is dependent on server response time.
  • Web/Ftp server access must be setup for all the users.

Example:

Directory1=http://www.demoserver.com/GuiXT/Scripts;
Directory1=ftp://ftp.demoserver.com/GuiXT/Scripts;

Scripts on SAP web repository

This option can be used for developers, testing teams and end-users. However, it is recommended that this deployment mechanism should not be used 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:ZGuiXT.DEMO

Additional notes:

  • RFC is executed in Client 000 unless explicitly specified in GuiXT Profile.
  • RFC User name and password must be present for GuiXT (Default RFC User SAPCIPC, Password admin).
  • RFC user must have proper authorization for GuiXT to use (functional group SHD0 and SURL)

Was this information helpful? Send Feedback