Skip to end of metadata
Go to start of metadata
StageWindowsLinux
InstallationIn addition to installing lsFusion, these installers/scripts also install OpenJDK, PostgreSQL, and Tomcat. Tomcat is embedded into the lsFusion Client installation, and OpenJDK and PostgreSQL are installed separately (in particular, in separate folders).

Executable exe files:

lsFusion 4.1 Server & Client (+ OpenJDK 11.0.9, PostgreSQL 13.1(x64)/10.8(x32), Tomcat 9.0.21):

 Older versions
 lsFusion 4.0 Server & Client
 lsFusion 3.1 Server & Client
 lsFusion 2.4 Server & Client

Subsequently, $INSTALL_DIR$ refers to the folder selected during the installation of lsFusion (by default, Program Files/lsFusion <version>). It is also assumed that all parameters (ports, web context name) are left equal to default values.

Bash scripts using yum / apt (the latest stable releases are used as minor versions):

lsFusion 4 Server & Client (+ OpenJDK 1.8, PostgreSQL 13, Tomcat 9.0.21):

OSCommand / Script
RHEL 7 / CentOS 7 / Fedora 29
Ubuntu 18 / Debian 9

source <(curl -s https://download.lsfusion.org/apt/install-lsfusion4)

PostgreSQL installs version 10, since that is the only one in the central repository


After installation

Ports

After the installation is completed, the following will by default be locally installed on the computer and launched as services:

  • DB server (PostgreSQL) on port 5432
  • application server (Server) on port 7652
  • web server (Client) on port 8080

Installing / updating anapplication

In order to upload the developed logic to the installed application server (Server), you must:

Place modules developed in the lsFusion language as files with an lsf extension in a folder located in the server's classpath (default value for automatic installation, see below). In addition, the rest of the resource files if any must also be placed there (e.g. report files, compiled Java files, images, etc.). These files may be placed in subfolders of the classpath, as well as inside jar files (zip archives with the jar extension). After all the files have been copied, you need to restart the server.

It is often convenient to place all project files inside a single jar file. To generate such a file automatically, you can use Maven (with assemble and noserver profiles) or the build tools built into the IDE.

By default, the server's classpath is equal to $APP_DIR$;$APP_DIR$/*;server.jar, i.e. the $APP_DIR$ folder and all its subfolders, all jar files in the $APP_DIR$ folder (but not its subfolders), and also the jar file of the application server itself

$APP_DIR$ is equal to:

$INSTALL_DIR$/lib

/var/lib/lsfusion

The application server is installed and started under the automatically created non-privileged user lsfusion so files in the folder should be accessible for this user to read. 

Installing / updating clients

To give users access to the installed system, you must:

Send users a link to http://<web address of the web server (Client)>:8080. When users open this link, they will be redirected by default to the login page, where, if necessary, they can install the desktop client via Java Web Start (requires Java (JDK) installed, for example, by following this link with registration or this one without).

Web and desktop clients are updated automatically with updates to the web server (Client).

Under Windows, you can also use desktop client installers (lsfusion-desktop- * files with the correct OS version and bit width). However, unlike installing with Java Web Start, a desktop client installed in this way will not be automatically updated. Therefore, you will need to update it manually by downloading the file of the new version of the desktop client (lsfusion-client-4.<new version>.jar) from the central server and replacing the $INSTALL_DIR$/client.jar file with it


All paths and commands are given below for the major version 4 of the platform (for other versions just replace 4 with the required number, for example lsfusion4-server → lsfusion11-server)
All paths by defaultPaths changed (in particular with symlinks) in accordance with Linux ideology
Updating

Programs installed separately (OpenJDK, PostgreSQL) are also updated separately (for more details about this process, see the documentation for these programs)

Platform components are also updated separately from each other. To do this, you must:

Download the file of the new version of the component from the central server and replace the following file with it:

Run the command:
Application Server (Server)

File on the central server: lsfusion-server-4.<new version>.jar

File to replace: $INSTALL_DIR$/Server/server.jar

OSCommand
RHEL 7 / CentOS 7 / Fedora 29
yum update lsfusion4_server
Ubuntu 18 / Debian 9
apt install lsfusion4_server

Web server (Client)

File on the central server: lsfusion-server-4.<new version>.jar

File to replace: $INSTALL_DIR$/Client/webapps/ROOT.war

To update Tomcat, you need to download the archive with the new version of Tomcat and unzip it to the $INSTALL_DIR$/Client folder without the webapps directory and the startup parameters file

OSCommand
RHEL 7 / CentOS 7 / Fedora 29
yum update lsfusion4_client
Ubuntu 18 / Debian 9
apt install lsfusion4_client
Custom installation


If any of the programs listed in the installation (platform components) do not need to be installed / are already installed on your computer:
These programs can be excluded during installation using the corresponding graphical interface.

The following are scripts for installing specific platform components:

Database Server - PostgreSQL 11:

OSCommand / Script
RHEL 7 / CentOS 7 / Fedora 29

source <(curl -s https://download.lsfusion.org/yum/install-lsfusion4-db)

Ubuntu 18 / Debian 9

source <(curl -s https://download.lsfusion.org/apt/install-lsfusion4-db)

PostgreSQL 10

Application Server - lsFusion 4 Server (+ OpenJDK 1.8): 

OSCommand / Script
RHEL 7+ / CentOS 7+ / Fedora 29+source <(curl -s https://download.lsfusion.org/yum/install-lsfusion4-server)
Ubuntu 18 / Debian 9source <(curl -s https://download.lsfusion.org/apt/install-lsfusion4-server)

Web server - lsFusion 4 Client (+ Tomcat 9.0.20): 

OSCommand / Script
RHEL 7+ / CentOS 7+ / Fedora 29+source <(curl -s https://download.lsfusion.org/yum/install-lsfusion4-client)
Ubuntu 18 / Debian 9source <(curl -s https://download.lsfusion.org/apt/install-lsfusion4-client)

When installing platform components on different computers, it is also necessary to configure the parameters to connect them to each other:

Components on different computersConnection parametersConfigurable file
DB server and application server (Server)

Application server to DB server

File lsFusion application server startup parameters
Application server (Server) and web server (Client)

Web server to application server

File lsFusion web server startup parameters

When installing under Windows, the above parameters are requested during the installation process and the parameter files are configured automatically.

Manual setup 

(file paths, service names)

















Application server (Server):

Java 

Java tab in the graphical interface $INSTALL_DIR/Server/bin/lsfusion4_serverw.exe

  • classpath - the Classpath parameter in the same tab

the FUSION_OPTS parameter in the file /etc/lsfusion4-server/lsfusion.conf

  • classpath: the CLASSPATH parameter in the same file

the file $INSTALL_DIR/Server/conf/settings.properties

the file /etc/lsfusion4-server/settings.properties

Web server (Client): 

Java 

Java tab in the graphical interface $INSTALL_DIR/Client/bin/lsfusion4_serverw.exe

the CATALINA_OPTS parameter in the file /etc/lsfusion4-client/lsfusion.conf

lsFusion 

the file $INSTALL_DIR/Client/conf/catalina/localhost/ROOT.xml

the file /etc/lsfusion4-client/catalina/localhost/ROOT.xml

Desktop client: Java parameters are set inside the j2se tag in the jnlp file

Restart 

Any changes made to the startup parameters, as well as changes to lsFusion modules, require a server restart (when changing lsFusion modules only the application server (Server)). This can be done with:

Application server (Server)

GUI:

Control Panel → Admin → Services → lsFusion 4 Server

or

Command
# Stop server
$INSTALL_DIR/Server/bin/lsfusion4_server.exe //SS//lsfusion4_server

# Start server
$INSTALL_DIR/Server/bin/lsfusion4_server.exe //ES//lsfusion4_server
Command
# Stop server
systemctl stop lsfusion4-server

# Start server
systemctl start lsfusion4-server

Web server (Client)

GUI:

Control Panel → Admin → Services → lsFusion 4 Client

or

Command
# Stop server
$INSTALL_DIR/Client/bin/lsfusion4_client.exe //SS//lsfusion4_client

# Start server
$INSTALL_DIR/Client/bin/lsfusion4_client.exe //ES//lsfusion4_client
Command
# Stop client
systemctl stop lsfusion4-client

# Start client
systemctl start lsfusion4-client







Platform logs are written to the following folders:

Application server (Server):

$INSTALL_DIR$/Server/logs

/var/log/lsfusion4-server
Web server (Client):
$INSTALL_DIR$/Client/logs/var/log/lsfusion4-client

The main logs (including the process of stopping and starting the server) are located in:

  • Application server (Server) - stdout
  • Web server (Client) - catalina.out (since the web server runs on Tomcat).

Desktop client logs: $USER_DIR$/.fusion/logs, where $USER_DIR$ is the user folder:

Users/<username>/home/<username>
LocaleThe locale used by the platform is determined based on the locale installed in the operating system. If necessary, it can be changed with:

GUI:

Control Panel → Language and Regional Standards

Command
localectl set-locale LANG=ru_RU.utf8
  • No labels