Requirements:Managing software installation and scripts for user's across multiple locations
Pre-Requisites:Liquid UI Desktop (Local user software deployment), or Liquid UI Server (Central Software Deployment)
Scenario 1: The scripts are common across all locations from where user is required to access the solution.
[One set of scripts for all locations]
Preferred Solution:- Deploy software centrally using Liquid UI Server
- One Configuration file for all users across location
- Depending on the number of users, install single Liquid UI Server or multiple Liquid UI Servers and load balance them using a 3rd party hardware load balancer.
Refer to Server Sizing Requirements:
https://www.guixt.com/knowledge_base/content/18/310/en/32-server-sizing-requirements.html- Deploy the scripts either locally on the Liquid UI Server or SAP Web Repository
Refer to Script Deployment Options:
http://www.guixt.com/forum/index.php/topic,317.msg321.html#msg321- Set up SAPGUI Connection to Liquid UI Server for all users. ** No Need to Activate GuiXT" on end user's machine
Scenario 2: The scripts are different for individual locations from where user is required to access the solution.
[Multiple et of scripts for all locations]
Preferred Solution:- Deploy software centrally using Liquid UI Server for each location
- Separate Liquid UI Configuration file or each location identifying the script location
- Depending on the number of users at each location, install single Liquid UI Server or multiple Liquid UI Servers and load balance them using a 3rd party hardware load balancer.
Refer to Server Sizing Requirements:
https://www.guixt.com/knowledge_base/content/18/310/en/32-server-sizing-requirements.html- Deploy the scripts either locally on the Liquid UI Server or SAP Web Repository
Refer to Script Deployment Options:
http://www.guixt.com/forum/index.php/topic,317.msg321.html#msg321- Set up separate SAPGUI Connection to Liquid UI Server for users specific to their location . ** No Need to Activate GuiXT" on end user's machine
This will require different SAPGUI connection details based on where the user is located.
Alternatively:- User's can be assigned different role based on their location, and a usercatalog can be setup which is role specific
- The usercatalog allows specification of groups and directories based on groups
- This way solution can be deployed using
Scenario 1.
- Refer to article for using usercatalog:
http://www.guixt.com/forum/index.php/topic,152.msg156.html#msg156 With Liquid UI Server deployment approach a. Both software and configuration can be maintained centrally, and no software files and associated configuration files needs to be
deployed to each individual users.
b. Scripts can stay either centrally on Liquid UI Server folder or in SAP Web Repository depending on customer's preference.
c. Mobile ready, to leverage the solution on iOS, Android and Windows CE based devices
With Liquid UI Desktop Deployment Approach a. Software needs to be installed on each individual user's machine.
b. Software configuration files needs to be installed on each individual user's machine.
c. Software upgrade will require each user's machine to be updated.
d. If scripts are stored using network share location, then their is additional dependency on the network share, if the share is not accessible, the Liquid UI Solution is not accessible
Note: With both Desktop and Server Deployment, there are multiple options to deploy the scripts.
Refer to article:
http://www.guixt.com/forum/index.php/topic,317.msg321.html#msg321
