Difference between revisions of "Additional Registry Entries and Environment Variables"
From Lianjapedia
Yvonne.milne (Talk | contribs) (Created page with "''Under Construction'' ==Overview== There are additional Lianja Server settings that can be defined as Registry entries (Windows) or environment variables (Linux and Mac). A...") |
Yvonne.milne (Talk | contribs) (→Settings) |
||
| (11 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | |||
| − | |||
==Overview== | ==Overview== | ||
| − | There are additional Lianja Server settings that can be defined as Registry entries (Windows) or environment variables (Linux and Mac). | + | There are additional Lianja Server settings that can be defined as Registry entries (Windows) or environment variables (Linux and Mac). These can help developers to debug and optimize their Web Apps. |
After modifying the Registry entries or environment variables, restart the Lianja Server. | After modifying the Registry entries or environment variables, restart the Lianja Server. | ||
| Line 11: | Line 9: | ||
==Windows== | ==Windows== | ||
| − | Incorrectly modifying the Registry can cause serious problems on your system, so do not proceed if you are not completely sure how to do | + | Incorrectly modifying the Registry can cause serious problems on your system, so do not proceed if you are not completely sure how to do this. You should consider backing up your registry and using .reg files. Consult the Microsoft support site for full recommendations, e.g. [https://support.microsoft.com/en-gb/help/310516/how-to-add-modify-or-delete-registry-subkeys-and-values-by-using-a-reg] |
| − | ===64 bit Location=== | + | ===64 bit Registry Location=== |
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Lianja\Lianja Server\Netserver | Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Lianja\Lianja Server\Netserver | ||
| − | ===32 bit Location=== | + | ===32 bit Registry Location=== |
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Lianja\Lianja Server\Netserver | Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Lianja\Lianja Server\Netserver | ||
| Line 32: | Line 30: | ||
|- | |- | ||
|valign="top"|DB_CACHE_ENABLED | |valign="top"|DB_CACHE_ENABLED | ||
| − | |valign="top"|During Web App development you can set DB_CACHE_ENABLED to false to disable caching and set it to true for production systems. | + | |valign="top"|During Web App development you can set DB_CACHE_ENABLED to false to disable caching and set it to true for production systems.<br>Note that some browsers (Chrome, for example) already disable caching when the developer tools are open. You can uncheck this in the "Network" tab then refresh your app several times to see the caching in operation. |
| + | |- | ||
| + | |valign="top"|DB_ODATATRACE | ||
| + | |valign="top"|During Web App development you can set DB_ODATATRACE to true. Run the Web App then check the debug directory for odata_tracexxx.log files. These are text files that contain full OData performance metrics tracing information. From v5.3.<br>This setting can also be toggled on Windows in the [[Lianja_Server_Manager_on_Windows#HTTP_Settings|Lianja Server Manager]]. | ||
|- | |- | ||
|valign="top"|DB_SQLDEBUG | |valign="top"|DB_SQLDEBUG | ||
| − | |valign="top"|During Web App development you can set DB_SQLDEBUG to | + | |valign="top"|During Web App development you can set DB_SQLDEBUG to true. Run the Web App then check the debug directory for sql_debugxxx.log files. These are text files that contain SQL tracing information and show you all the OData calls being made and how the queries were optimized. |
| + | |- | ||
| + | |valign="top"|DB_WWWAUTOUPDATE | ||
| + | |valign="top"|When DB_WWWAUTOUPDATE is set to true, auto updating of packages is enabled. See [[Lianja Package Manager]] for more information on package updating.<br>This setting can also be toggled on Windows in the [[Lianja_Server_Manager_on_Windows#Security|Lianja Server Manager]]. | ||
| + | |- | ||
| + | |valign="top"|DB_WWWDEBUG | ||
| + | |valign="top"|During Web App development you can set DB_WWWDEBUG to true. Run the Web App then check the debug directory for firecat_debugxxx.log files. These are text files that contain server activity information. | ||
|- | |- | ||
|} | |} | ||
[[Category:Lianja Server]] | [[Category:Lianja Server]] | ||
| + | [[Category:Lianja v4.2]] | ||
| + | [[Category:Lianja v5.3]] | ||
Latest revision as of 05:30, 22 April 2020
Contents
Overview
There are additional Lianja Server settings that can be defined as Registry entries (Windows) or environment variables (Linux and Mac). These can help developers to debug and optimize their Web Apps.
After modifying the Registry entries or environment variables, restart the Lianja Server.
Windows
Incorrectly modifying the Registry can cause serious problems on your system, so do not proceed if you are not completely sure how to do this. You should consider backing up your registry and using .reg files. Consult the Microsoft support site for full recommendations, e.g. [1]
64 bit Registry Location
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Lianja\Lianja Server\Netserver
32 bit Registry Location
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Lianja\Lianja Server\Netserver
Linux
Environment variables are defined in the text file /etc/lianja.d/lianja.conf.
Mac
Environment variables are defined in the text file /usr/local/lianja/server/conf/lianja.conf.
Settings
| Setting | Description |
|---|---|
| DB_CACHE_ENABLED | During Web App development you can set DB_CACHE_ENABLED to false to disable caching and set it to true for production systems. Note that some browsers (Chrome, for example) already disable caching when the developer tools are open. You can uncheck this in the "Network" tab then refresh your app several times to see the caching in operation. |
| DB_ODATATRACE | During Web App development you can set DB_ODATATRACE to true. Run the Web App then check the debug directory for odata_tracexxx.log files. These are text files that contain full OData performance metrics tracing information. From v5.3. This setting can also be toggled on Windows in the Lianja Server Manager. |
| DB_SQLDEBUG | During Web App development you can set DB_SQLDEBUG to true. Run the Web App then check the debug directory for sql_debugxxx.log files. These are text files that contain SQL tracing information and show you all the OData calls being made and how the queries were optimized. |
| DB_WWWAUTOUPDATE | When DB_WWWAUTOUPDATE is set to true, auto updating of packages is enabled. See Lianja Package Manager for more information on package updating. This setting can also be toggled on Windows in the Lianja Server Manager. |
| DB_WWWDEBUG | During Web App development you can set DB_WWWDEBUG to true. Run the Web App then check the debug directory for firecat_debugxxx.log files. These are text files that contain server activity information. |
