<service>

...

</service>

every AppServer instance definition is enclosed in  these tags

<name>...</name>

sets the name for the instance - can include Latin letters, arabic numbers (0-9), dashes (-), and underscores (_)

<port>...</port>

is used for the purpose of legacy compatibility (set the same value as <name>...</name>)

<applicationdir>...</applicationdir>

specifies the application server working directory (i.e., where programs will be deployed and executed)

By default,

C:\ProgramData\Querix\Lycia\progs

/opt/Querix/Lycia/progs

<logdir>...</logdir>

specifies the folder to which log files will be saved

By default,

C:\ProgramData\Querix\Lycia\logs

/opt/Querix/Lycia/logs

<envfile>...</envfile>

specifies where inet.env is situated

By default,

C:\ProgramData\Querix\Lycia\etc\inet.env

/opt/Querix/Lycia/etc/inet.env

<authmode>...</authmode>

specifies the authentication mode - can be none or full

<auth_module>...</auth_module>

specifies the authentication library:

modauthnt.dll

modauthcrypt.so, modauthshadow.so, modauthshadow.so

<logging>...</logging>

enables or disables logging - can be true or false

<description>...</description>

holds a short description of the instance

<accessfilter>...</accessfilter>

is used for the purpose of legacy compatibility (leave unchanged when adding new instances or modifying the already existing ones

<enabled>...</enabled>

allows disabling the instance without removing it

<sso>...</sso>

switches on the Kerberos protocol for SSO authentication - can be not set, false, or true:

if not set in listener.xml or set to false, standard authentication procedure will be used;

if set to true, LyciaWeb will try to go through the SSO authentication (and will ask for standard authentication procedure with entering user name/password only in case SSO authentication fails)

<toolset>...</toolset>

is used only in listener.xml to determine what Studio version is associated with this instance - can be hydra, lycia1, and lycia2 (for both Lycia II and Lycia III)