4.11 Liquid UI Scripts Deployment Techniques

Purpose

Liquid UI offers very flexible means of deploying the scripts. Liquid UI supports 4 script directories. You can specify these directories in Liquid UI configuration file("guixt.sjs") or in User Catalog.

You can place Liquid UI scripts in various locations as per your requirement as explained below:

1. Scripts on the Local drive
2. Scripts on Network file server or a file share
3. Scripts on FTP and/or Web server
4. Scripts on SAP web repository

Scripts on the Local drive:

Generally, Liquid UI script developers and small testing teams create a path in the local drive to place their script files.

Pros:

1. Easy setup and use.
2. Developers get complete control of scripts for modifications.

Cons:

1. Not meant for large group of users.
2. High maintenance option. User has control of scripts and users can modify or delete the scripts.

Example: directory1="C:\\LiquidUI\\Scripts";

Scripts on Network file server or a file share:

Generally, Liquid UI script developers, testing teams and end users create a path in the Network file server to place their script files.

Pros:

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

Cons:

1. Additional dependency for using Liquid UI
2. Additional replication, etc must be setup if different servers are used across WAN
3. Additional users privileges must be setup for users to access these scripts

Example: directory1="\\\\DemoServer\\LiquidUI\\Scripts";

Scripts on FTP and/or Web server:

Generally, developers, testing teams and end users create a path on the Web Server to place their script files.

Pros:

1. Can be used across company’s internal network.
2. Centralized management of scripts.
3. Network traffic can be reduced by using File Replication option in Liquid UI settings

Cons:

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

directory1="http:\/\/www.demoserver.com\/LiquidUI\/Scripts";
[OR]
directory1="ftp:\/ftp.demoserver.com\/LiquidUI\/Scripts";

Scripts on SAP web repository:

Generally, testing teams and end users place the Liquid UI script files in the SAP Web Repository. 

Pros:

1. Centralized script administration with SAP's transport and correction mechanism.
2. Automatic caching for reducing script downloads.
3. No external dependencies.
4. Change access can be controlled using SAP’s authorization mechanism.

Cons:

1. Additional RFC overhead as scripts are retrieved from SAP using Remote Function Calls (RFC).
2. Difficult setup for developers as it is not very easy to change uploaded scripts.

directory1="SAPWR:ZLUI.DEMO";