niota

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. 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.

url.html

https://localhost/niota/app/login.php?client=ABC

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.

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

There is always a system (default) client configured. The home folder of the system default client is located in app/conf folder. Avoid to change the system (default) client. Use an own client instead

You can address the system client by explicitly adding the ?client=system parameter at the end of the login URL.

url.html

http://localhost/niota/app/login.php?client=system

You can address your configured clients by explicitly adding the ?client=<myclientid> parameter at the end of the login URL.

url.html

http://localhost/niota/app/login.php?client=ABC

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

These files are mandatory for a client configuration and must be found in the client's home folder

connections.php
debug_defaults.php
formatting_defaults.php
hosts.php
system_defaults.php

These folders (and some subfolders) are part of a client configuration and should not be renamed or removed

formattings
log

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

[SAMPLE]
conffolder=client_sample
[/SAMPLE]

In case you want to configure e.g. a client for some trainings and you would like to address the client by ?client=EDU01A and the home folder should be name client_EDU_01A then it would look like this.

Client name has to be defined inside brackets […] and home folder must be referenced in parameter conffolder. The content of the client.ini file is the following according to the examples:

[EDU01A]
conffolder=client_EDU_01A
[/EDU01A]

url.html

http://localhost/niota/app/login.php?client=EDU01A

Folder structure on the web sever should look like this

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 subfolders) are 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:
default system configuration
configure connections
configure format / look and feel