Installation

Overview

The following sections discuss the requirements for a succesful installation of FMS. Further in depth detail on the requirements are discussed in the following chapters.

System Requirements

The FMS Server requires setup by a suitably qualified system administrator who has a good understanding of system security and networking. The server requires access to various system resources including the following

  • Access to TCP/IP ports 80, 443, 5432, 29360, 29450. Port 29360 is used for listening for management console connections typically coming from behind the company firewall. Port 80 and 443 access is required for receiving remote HTTP and HTTPS incoming connections. Port 5432 is typically used for connecting to the PostgreSQL database server if required.

    Any of the TCP/IP ports required by FMS may be configured to different values in the server interface configuration.

  • The FMS server must be installed on a machine appropriately configured for secure remote access with visibility from both the internal network and outside network for the responses. This may require configuration on the firewall.

  • FMS may be vulnerable to common TCP denial-of-service attacks including TCP SYN flooding. Server installations should include steps to minimize the impact of a denial-of-service attack using combinations of easily implemented solutions, such as deployment of firewall technology and border router filters to restrict inbound server access to known, trusted clients.

Supported Operating Systems

FMS runs on various UNIX, Linux and Windows operating systems but can also be installed on any operating system that supports the Java run time environment (JRE 1.8), including (but not limited to) the following:

  • CentOSTM 6, 7 and above

  • Mac OS XTM 10.8 and upwards

  • Microsoft WindowsTM Server 2003 and above

  • Microsoft WindowsTM 7 and above

  • RedHatTM Enterprise Linux 5, 6 and above

  • Sun SolarisTM

  • UbuntuTM 14.04 and above

Java Runtime Environment (JRE) Requirements

FMS requires JRE version 1.8 or later. This is included in the Windows distribution by default and is also available at https://java.com/en/download/.

Before proceeding verify that Java is in the executable path as follows

\
\java -version
\
\        

Should the version of Java not be at 1.8 or greater then either contact the system administrator to load the correct version or ensure that the PATH environment variable is updated to point to the correct version.

Certain modern encryption algorithms are only supported by Java 1.8 and later. These include the following

  • http://www.w3.org/2009/xmlenc11#rsa-oaep

  • http://www.w3.org/2009/xmlenc11#aes128-gcm

  • http://www.w3.org/2009/xmlenc11#aes256-gcm

Licence Requirements

The FMS licence file (fms.lcn) must be obtained from the provider and placed in the FMS installation directory prior to operation as per the Section called Licence Configuration in the post installation section.

Certificate Requirements

Secure Certificates may either be self generated or obtained from a commercial certificate authority (CA) such as Verisign or Thawte. See the Section called Creating a Keystore using the Key Generator in the Windows installation section and the Section called Keystore Configuration in the post installation section for further details.

Database Server

FMS uses a JDBC compliant database server for, amongst others, non-repudiation storage, message reporting, monitoring and logging, and for caching Collaboration Protocol Agreement (CPA) details.

Use of the database is recommended for all professional and enterprise installations.

Should FMS be configured with no database then AS4 pull requests is not supported. Message reporting and realtime display of message statistics will also not be available and the CPA details will only be cached in the running instance and will be lost on server re-start.

The database may be either installed on the same machine or on a dedicated server on the local area network. Version 9.5 of PostgreSQL or later is recommended. and may be obtained either as a standard install package with Linux operating systems or from http://www.postgresql.org.

Other JDBC compliant databases are currently not supported. Please contact the suppliers should this be a requirement.