Before getting started


This section describes the installation of the FlowerDocs GUI and FlowerDocs Core applications and the configuration associated with the data repository used.

Prerequisites


Make sure to harmonize the date/time configuration on the various servers making up the target architecture by using the same time zone (FlowerDocs servers as well as all third-party components). Discrepancies can cause problems when FlowerDocs checks the validity of a token (SSO, Web Services, etc.).

Operating system

Linux

Linux servers are required to install a FlowerDocs platform. FlowerDocs is supported and qualified on Amazon Linux 2 4.14. Any other Linux system is considered functional if it allows installing the Java version required by FlowerDocs.

Any other Linux system is considered functional if it allows installing the required Java version.

Application components

Java Runtime 8 or 11 (Oracle or OpenJDK) must be installed before the platform can be installed.


This documentation does not cover the installation of the ARender rendition server (version 4.8.17). It must therefore be installed beforehand and be accessible via the HTTP protocol from FlowerDocs GUI and FlowerDocs Core

OpenSearch and Redis

You need to install OpenSearch and Redis, which are prerequisites for FlowerDocs to work properly. OpenSearch and Redis versions corresponding to FlowerDocs versions are indicated at the beginning of the release notes.

Sizing

The architecture depends on the estimated capacity, but it is recommended to have at least:

Component vCPU RAM Note
FlowerDocs 2 4 GB The FlowerDocs GUI and FlowerDocs Core applications can also be installed on separate servers.
ARender Rendition Server 4 8 GB The sizing of a rendition server is closely linked to the type and number of documents viewed.

The sizing of a FlowerDocs platform needs to be carefully considered in order to achieve the best possible performance. The sizing factors include the number of concurrent users and the number of documents viewed.

Applications

The FlowerDocs platform requires installation of the executable JARs:

  • flower-docs-gui-webapp-2.8.2.jar
  • flower-docs-core-webapp-2.8.2.jar

These applications can be configured by property files located in the configuration directory called ${FD_HOME}. For example, FlowerDocs GUI can be configured using the gui.properties file and FlowerDocs Core using the core.properties file.


By default, the configuration directory ${FD_HOME} is the application execution folder. To define a configuration directory other than the runtime directory, set the JVM spring.config.additional-location property with the absolute path of the directory.



To configure the applications, follow the procedure for the specific data repository.

Verification of deliverable integrity

After downloading the application, check the integrity of the executables before installing them. It is important to check that these have not been altered (corrupted or fraudulently modified .jar file).

To do this, you need to calculate the file’s fingerprint using the SHA-256 hash function, so that you can verify it.

  • Use the command: sha256sum {fileName}.
  • Then retrieve the result of the command, which corresponds to the file’s fingerprint.
  • Check that the fingerprint of each downloaded file is equal to the content of the corresponding .sha256 file.

Download

Notes de version
Version : 2.8.2
FlowerDocs GUI
Interface graphique (Version : 2.8.2)
FlowerDocs Core
Coeur de l'application exposant des web services (Version : 2.8.2)
FlowerDocs CLM
Outils d'import/export de FD (Version : 2.8.2)

FlowerDocs default template
Template par défaut de FlowerDocs (Version : 2.8.2)


Would you like to download another version? Access old releases.