Please verify that a supported version of Apache Tomcat is installed and that the “CATALINA_HOME” environment variable references the Tomcat installation folder. Also make sure that you have write access to the subfolder
webapps of the Tomcat installation folder, as the LUY installer will use this folder later on.
Before installing the application with the LUY installer utility, you must first install a compatible Java runtime environment (JRE). The JRE is also a prerequisite for running the Tomcat servlet engine. In addition, the environment variable JRE_HOME (alternatively: JAVA_HOME) must be set to the installation folder of the Java runtime or development environment.
The distribution package comes with the installation utility luyInstaller.jar. You can use it to create application packages (.WAR file) for both LUY and iTURM. Both files are configured according to the values you set in the installer and can be used for operation in a servlet engine. If necessary, the installer also creates the data required for running the application in the relevant databases – such as an initial user account for administration. Launch the LUY installer with the following command in a command line window:
java -jar luyInstaller.jar
In Windows, you can also launch the tool by double-clicking the file name in Windows Explorer.
First, you can select the authentication mechanism of LUY. The different authentication methods are described in the linked section.
In our example we chose the installation with LDAP/LDAPS. The next step is the configuration of the LDAP/LDAPS connection.
If the checkbox for "Encrypt password" is checked, the entered password is encrypted. If the checkbox is not set, the password is saved in plain text.
Optionally, you can adapt the user search filter, if it does not reflect your directory schema. You can also adapt the role membership filter, if your directory uses an attribute other than 'member' to store role members.
If any LDAP/S authentication is used, there is no need for installing iTURM. If you choose iTURM authentication, you can install both applications, LUY and iTURM.
The next step is configuring the name of the application. With the name of the application, you can specify the URI path from which the application can be addressed in the servlet container. With the default settings and default name "LUY", the application will be accessible under http://<servername>:<port>/luy. You will also be prompted to name your iTURM installation, if you are installing iTURM as well.
On the next window, choose the DBMS.
In our example, we chose the option “Mysql or MariaDB”. The next step is the configuration of the chosen database.
If the checkbox for "Encrypt DB password" is checked, the entered password is encrypted. If the checkbox is not set, the password is saved in plain text.
When connecting to an Oracle database, "User name for the DB" represents the "schema" (as this is the same in Oracle DB). One can either use the Oracle Service Name or the Oracle SID for the database connection. The choice between "ServiceName" and "SID" is only available, if Oracle has been selected as database.
If you install iTURM, you must specify the database connection for iTURM in a separate screen.
Next, you specify the folder in which the LUY technical log file should be stored. If you leave this field blank, the files are stored in the temp folder of the Tomcat installation. Make sure the servlet engine has read & write access to these paths. If you are also installing iTURM, you will be prompted for its log file path as well.
In the next step, you can adjust the path where LUY will store its search index. The Hibernate Search index contains a full-text index of all data entered into LUY. Make sure that the servlet engine has read and write access to the directory you specify here.
In the following form, you can enable last modification logging. With this option enabled, all building blocks in the database are tagged with the login name of the user who last modified the record and the corresponding modification time. This information will be visible to all LUY users in the GUI.
If you install iTURM, you will be asked whether you wish to initialize its database or not. Please initialize its database if it's a new installation.
If you chose to initialize the database, you are then asked to enter the location of the appropriate JDBC driver.
The next step is to specify a destination folder where the LUY installer will copy the generated luy.war file. We recommend choosing the webapps folder of Tomcat.
On the next dialog page, you have to select the required access protocol for LUY users. If you choose HTTPS, all connection attempts to LUY will be redirected to a secured HTTPS/SSL connection. This requires that your Tomcat servlet engine accepts HTTPS connections and has an appropriate SSL certificate installed. Please refer to configuration options and notes and to the Tomcat documentation for configuration instructions http://tomcat.apache.org/tomcat-9.0-doc/ssl-howto.html.
By choosing HTTP, LUY will accept both unsecured and secured connections. If your Tomcat has an HTTPS connector configured, LUY will accept HTTP and HTTPS connections.
On the last page, use the Execute button to create the .war file and – depending on your settings in the form – initialize the database.
Show details -> output shows the log output of this process;
Show details -> errors shows any errors that occurred.
Once generated, the .war file is copied in the folder you previously specified. When Tomcat is launched, the file is automatically unpacked and the application can be accessed in the browser.
With the default setting, the application can be accessed at http://*servername*:8080/luy/.
If you use iTURM for user management, the initial administrator user has the login name system and the password password. For security reasons we strongly recommend to change the default password after installation.
Configuring Chrome or Chromium (server side)
Chrome or Chromium must be installed on the LUY server to enable the Shared Visualization feature.
Additionally, a system property
chrome_binary must be set in the Tomcat startup configuration.