•CentOS 6 or newer
•RedHat 6 or newer
•Debian 8 or newer
•Ubuntu 14.04 or newer
The following libraries are required as a prerequisite to install and run the application. If the packages below are not already available on your Linux machine, run the command yum (or apt-get if applicable) to install them.
•Perform installation either as root user or as a user with sudo privileges.
•The previous version of FlowForce Server must be uninstalled before a new one is installed.
•If you are installing FlowForce Server with other Altova server products, it is recommended to install FlowForce Server first.
Installing FlowForce Server
1.Download the installation package from https://www.altova.com/download#server to a local directory.
2.Change to the directory where you downloaded the installation package, for example:
3.Install the FlowForce Server package.
[Debian, Ubuntu] sudo dpkg --install flowforceserver-2020-debian.deb
[CentOS, RedHat] sudo rpm -ivh flowforceserver-2020-1.x86_64.rpm
|Note:||You may need to adjust the name of the package above to match the current release or service pack version.|
4.Start the FlowForce Web Server service.
[CentOS 6]: sudo initctl start flowforcewebserver
[CentOS 7]: sudo systemctl start flowforcewebserver
[Debian 8]: sudo systemctl start flowforcewebserver
[RedHat]: sudo initctl start flowforcewebserver
[Ubuntu 14.04]: sudo initctl start flowforcewebserver
[Ubuntu 16.04]: sudo systemctl start flowforcewebserver
Licensing FlowForce Server
1.Ensure that the latest version of Altova LicenseServer (https://www.altova.com/licenseserver) is installed and running either on the local machine or network.
2.Register FlowForce Server with Altova LicenseServer. For this, you need to know either the host name or the IP address of the computer where LicenseServer runs. For example, if LicenseServer runs on 127.0.0.1, you can register it as follows:
sudo flowforceserver licenseserver 127.0.0.1
|Note:||The command above assumes you are calling the executable from the program installation directory. On CentOS and macOS, make sure to prepend "./" in front of the executable.|
3.Log on to LicenseServer administration interface and assign the license to the machine where FlowForce Server runs.
For more information about licensing, refer to Altova LicenseServer documentation (https://www.altova.com/documentation).
1.Find the URL of the FlowForce Server setup page.
After you start the FlowForce Web Server for the first time as shown above, it starts on a random port and creates a setup page. If your Linux machine has a Web browser, you can open the setup page in the Web browser, for example:
sudo firefox file:///var/opt/Altova/FlowForceServer2020/flowforceweb.html
Alternatively, you can extract the setup page URL from the system log:
CentOS 7, RedHat 7
sudo grep running /var/log/messages
Debian 8, Ubuntu 16
sudo grep running /var/log/syslog
On Ubuntu 14.04 and CentOS 6, you can extract the setup page URL from the FlowForce Web server log file, using the following command:
CentOS 6, Ubuntu 14
sudo grep running /var/opt/Altova/FlowForceServer2020/data/ffweb.log
The output is similar to:
FlowForceWeb running on http://127.0.0.1:34597/setup?key=52239315203
To access the setup page from another machine on the network, type this link into the address bar of your browser and replace "127.0.0.1" with the host name of your server machine.
Make sure that the random port address on which FlowForce Web Server was started is not blocked by your firewall.
2.Configure the network address and port of the Web administration interface (see Defining the Network Settings).
3.Log on to the Web administration interface (by default, http://localhost:8082, unless you changed the address and port in the previous step) and change the default FlowForce Server root password. The default login name and password is root and root, respectively.
4.If other Altova server products have been installed alongside FlowForce Server (for example, MapForce Server, StyleVision Server, RaptorXML Server), and if you would like to set environment variables for them, see Setting Environment Variables.