niota

fascinating. logical.

User Tools

Site Tools


niota-docs:niota_install_clients

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
niota-docs:niota_install_clients [2025/04/24 16:31]
admin
niota-docs:niota_install_clients [2025/07/17 14:11] (current)
Line 1: Line 1:
-==== setting up a client ==== +==== Introduction ​==== 
- +A client is a group of configuration settings, grouped ​by a specified name. The name of the client is an identifier that has to be provided ​mandatory ​in the URL of the login page. 
-==== introduction ​==== +Each client has got it'​s ​own connection-,​ formatting-,​ system-default,​ ... file, image folder, script folder, etc. There can be multiple clients defined inside one niota installation. A client can be addressed by the ''?​client=''​ parameter in the URL of the login page. 
-A client is a group of configuration settings by a specified name. The name of the client is an identifier that has to be provided ​mandatary ​in the URL of the login page. +
-Each client has got its own connection-,​ formatting-,​ system-default,​ ... file, image folder, script folder, etc. There can be multiple clients defined inside one niota installation. A client can be addressed by the ''?​client=''​ parameter in the URL of the login page. +
  
 <code html url.html>​ <code html url.html>​
Line 9: Line 7:
 </​code>​ </​code>​
  
-All client specific data are located in folder ''​conf''​ below your niota root folder. At the very beginning you may download a sample ''​conf''​ folder from niota download page and adapt given samples to your needs. ​+==== setting up a client ==== 
 + 
 + 
 + 
 +All client specific data are located in folder ''​conf''​ below your niota root folder. At the very beginning you may download a sample ''​conf''​ folder from [[niota_links|niota download page]] and adapt given samples to your needs. ​
  
 ** Please take care not to update your ''​conf''​ folder with sample data after go live! An update package or a product fix should not update your ''​conf''​ folder ** ** Please take care not to update your ''​conf''​ folder with sample data after go live! An update package or a product fix should not update your ''​conf''​ folder **
Line 24: Line 26:
  
  
-You can address your configured clients by explicitly adding the ''?​client=<​myclientdi>''​ parameter at the end of the login URL.+You can address your configured clients by explicitly adding the ''?​client=<​myclientid>''​ parameter at the end of the login URL.
  
 <code html url.html>​ <code html url.html>​
 http://​localhost/​niota/​app/​login.php?​client=ABC http://​localhost/​niota/​app/​login.php?​client=ABC
 </​code>​ </​code>​
- 
  
  
 === folder structure === === folder structure ===
 Client-folders are placed inside ''​niota/​conf''​ folder. Each client has a home or root folder and must have a specified set of config files in a given structure below the root folder. Client-folders are placed inside ''​niota/​conf''​ folder. Each client has a home or root folder and must have a specified set of config files in a given structure below the root folder.
-One client is bound to exactly one configuration folder in file '**client.ini**' ​+One client is bound to exactly one configuration folder in file **''​client.ini''​** 
  
 {{:​niota-docs:​client_folder_structure.png?​nolink&​600|}} ​ {{:​niota-docs:​client_folder_structure.png?​nolink&​600|}} ​
Line 51: Line 52:
  
 ==== create a client ==== ==== create a client ====
-Make a copy of folder '​client_sample'​ and rename it to your desired name. In case there is no ''​client.ini''​ file in your ''​conf''​ folder, make a copy of file '​client.sample.ini'​ and rename it exactly ​'**client.ini**'. In file client.ini copy the the following section and adapt it to your needs+Make a copy of folder ​''​client_sample'' and rename it to your desired name. In case there is no ''​client.ini''​ file in your ''​conf''​ folder, make a copy of file ''​client.sample.ini'' and rename it exactly **''​client.ini''​**. In file client.ini copy the the following section and adapt it to your needs
 <​code>​ <​code>​
 [SAMPLE] [SAMPLE]
Line 71: Line 72:
 </​code>​ </​code>​
  
-{{:​niota-docs:​niota_doc_EDU01A_client.jpeg?​nolink&​600|}}+{{:​niota-docs:​niota_doc_edu01a_client.jpeg?​nolink&​600|}} 
  
 Folder structure on the web sever should look like this Folder structure on the web sever should look like this
  
-{{ :​niota-docs:​multi_client_04.png?400 |}} +{{:​niota-docs:​client_folder_structure_edu01a.png?nolink&​600|}} 
-((Figure 4 - client ​folder ​and client.ini file content ))+ 
 +==== shared ​folder ​==== 
 +If system settings are not changed, different clients share the content ​of some folders. This can be useful when you have multiple clients configured but you want to use the same set of image files or the same set of scripts or webservices amongst these clients. 
 + 
 +** These folders (and all subfoldersare shared amongst all clients that use system default configuration for images and script folders ** 
 +  images 
 +  scripts
  
 Client set up continues with system, connection and formatting configuration:​\\ ​ Client set up continues with system, connection and formatting configuration:​\\ ​
niota-docs/niota_install_clients.1745505118.txt.gz · Last modified: 2025/07/17 14:11 (external edit)