button link for contact page

Pre-Installation Requirements v5.4x

Pre-Installation Requirements v5.4x

Fitrix Pre-Install Requirements – Version 5.4x

Last Updated: March 2013

Server Minimums:

  • Processor: Pentium 4, Xeon or greater
  • 32 or 64 bit
  • Hard drive space:
    • Native Linux: 12GB available for Fitrix on single hard drive
    • VMware Virtual: 32GB available for Fitrix Virtual Environment on single hard drive
  • RAM: 2GB (more is helpful, 4-8GB RAM recommended)
  • Please note that additional licensing is required for servers with more than 2 dual core processors or 1 quad core processor (For virtual environments only the cores assigned to the virtual server are counted).  Additional licensing is also required if more than 4GB of RAM will be allocated to the IDS database (needed on high volume systems with 25 or more concurrent users).

Fitrix Installation Methods:

Fitrix may be installed using one of the following methods:

  • Linux Native (non-virtual)

    • Fitrix is installed on a Linux server that you supply and configure
    • Full installation and configuration of Fitrix is required
    • You have a choice of Linux distributions
    • You decide how to configure Linux
    • If you are using this method, please ignore section II below
  • Linux virtual

    • Fitrix is installed on a Virtual Linux server that you supply and configure
    • Full installation and configuration of Fitrix is required
    • You have a choice of Linux distributions
    • You decide how to configure Linux
    • (This is eactly the same as “Linux Native non-virtual” except that you have implimented Linux as a virtual.
    • If you are using this method, please ignore section II below
  • Virtual Pre-Install Image (Recommended for all systems wtih less than 25 users)

    • Fitrix is delivered as a VMware virtual image, almost fully installed and configured
    • This can be hosted on any server that has a compatible VMware product on it (VMware Server, VMware Player, VMware EXS(i), …)
    • Your Host can be Windows, Linux, or EXS(i)
    • Inside the Fitrix virtual is a Linux O/S that we have configured, with the Fitrix server software already installed and configured
    • A few minor re-configurations steps are needed (point it to your network, your email, set up your initial users)
    • This greatly reduces the server installation and configuration effort
    • Your I.T. staff will not require any Linux skills beyond the most basic ones.
    • Backups and disaster recovey can be greatly simplified
    • This is the preferred method for systems with less than 25 users
    • If you are using this method, please ignore section I below

Section I: Linux (Native or Virtual) Server Requirements:

Linux Distribution

Only the following Linux Distributions are supported:

  • Red Hat Fedora

All other Linux Distributions must be approved by Fourth Generation Software to be supported

Linux (native or virtual) Installation and Configuration Requirements

  • Fitrix is only supported on Linux operating systems which are installed and configured according to the manufacturer’s instructions. (Note: upgrading the kernel or glibc version on an existing Linux installation can create complications, and is not recommended).
  • Fitrix is supported on a virtualized Linux operating system under VMWARE™, however Fitrix is not supported on Linux operating systems that are running through emulation or enhancement software or any other virtualization products.
  • A Linux ‘C’ development system must be installed (‘GCC’ compiler + utilities + libraries). The GNU GCC compiler is strongly preferred.
  • Install the package ‘libstdc++.so.5′ (if not installed) The file ‘/usr/lib/libstdc++.so.5’ must exist (on some Linux distributions this requires a link when the file is located elsewhere).
  • Install the package ‘rpm’ (if not installed), and create the directory: ‘/var/lib/rpm’ if it does not exist.
  • Install the package ‘gawk’ (if not installed).
  • The Linux firewall (ipchains service) must be turned off. (The Fitrix server cannot be a firewall server).
  • The ‘termcap’ package (the termcap runtime libraries) must be installed. (This is done by default with most Linux distributions) The file ‘/usr/lib/libtermcap.so’ must exist (on some Linux distributions this requires a link when the file is located elsewhere)
  • JAVA (jre) version 1.4.2 must be installed. (Fitrix Complete provides this, but if your server has an earlier version this will have to be upgraded).
  • If the Fitrix Windows Thin Client will be used, install and enable one of the following: ssh (recommended), telnet, or rlogin.
  • The Linux server must have a network card installed (even if not connected to a network).
  • The Linux server must have a static I.P. address assigned (even if not connected to a network).
  • The Linux server must be booted to level 3 (inetd must be running). If ‘X’ Clients will be used, the Linux server must be booted to level 5.
  • Note that Fitrix Complete is a 32-bit product but will run on 64-bit systems. A 64-bit version of Fitrix is available at an additional cost.
  • Server must have a CD/ROM drive

Partitioning your Linux drive space for Fitrix

There are many strategies for hard drives, RAID, and drive arrays and all are supported with Fitrix. Here are the minimum requirements and guidelines:

  • All of Fitrix (the software and the database) installs under a single folder structure.
  • For a typical installation, this is installed under /var/opt on the root (/) partition, however you are welcome to install it elsewhere.
  • While a small Fitrix implementation will only need 8GB, today’s hard drives are far larger and we recommend allocating much more space to the root partition (or the Fitrix partition if not root).
  • If you plan to use the Fitrix document clipboard feature (available soon) that allows importing documents and images into the Fitrix database, you will want to allocate much more space as 1GB will typically support 2000 to 8000 scanned document pages.

Linux partitions:

Swap - The standard recommendation is: 2X physical RAM for up to 2GB of physical RAM + 1X physical RAM for any amount above 2GB. i.e. for 2GB physical RAM, configure 4GB of Swap space, for 4GB of physical RAM, configure 6GB of Swap space.

/boot - this is not used by Fitrix and is typically set to a minimal size of around 128mb.

/tmp - this is optional but recommended as a separate partition rather than just a folder on the root partition. The /tmp partition should be mounted on /tmp. Fitrix uses /tmp for cache space for reports and temp database tables. This should be 5% to 10% of your total drive space, minimum 5GB.

/ (root) – For a typical installation with Fitrix installed under root, we recommending allocating your remaining space to the root partition.

There are other partitions that are commonly used all of which are optional and have no impact on Fitrix.

Section II: Virtual Pre-Install Image, Fitrix Server Environment Requirements:

The Fitrix server software can be supplied as a ready to use VMware virtual image. The Fitrix host software is fully installed on a virtualized Linux environment that can be easily installed on a server running VMware. This reduces the installation time and the need for a systems administrator with Linux experience. This has no impact on the Fitrix clients which are installed seperately.

  • Server Options: (any of the following that will support the VMware version listed below)
    • Windows (desktop o/s will work for very small user counts wtih a light load, server o/s recommended)
    • Linux
    • ESXi
  • Server chipset must be Intel
  • VMware version 2.02 or later (the free version works fine for most smaller systems)
  • A license for Red Hat Enterprise v 5 is required (which is used inside the virtual environment, no media or installation of this is required)
  • VMware Server Hard drive space requirement for the Fitrix environment: 30GB
  • VMware Server must be connected to your network

VMware virtual environment Systems Administrator Requirements:

(your systems administrator must be able to perform the following duties)

  • Install VMware and demonstrate that it can power up a virtual environment that can connect to your network.
  • Copy the Fitrix virtual image from a 16GB thumb drive formatted for NTFS to the VMware server (Fourth Generation Software can complete the installation from that point).
  • Provide an I.P. address to be used with the Fitrix Virtual Environment (Fourth Generation Software will install the I.P. address inside the virtual environment).
  • Provide VPN access to your network for Fourth Generation Software support access to the virtual Fitrix environment.
  • Power up and down the Fitrix virtual environment.
  • Backup the Fitrix Virtual environment (the entire environment can be powered down and backed up from the virtual server).
  • Confirm that all Windows (or other) Client PC’s to be used as Fitrix Clients are connected to the same network as the VMware server that is running the Fitrix virtual server environment.
  • Remote desktop access to the Virtual server (if Windows) is very helpful for Fourth Generation Support.
  • Confirm that all printers to be used with Fitrix are accessible from each User’s Client PC (if the user can print from their Windows PC to the printer, Fitrix will be able to access it). (Fitrix also supports Linux host based printers which require complex configuration not recommended if you do not have a senior level Linux systems administrator or do not have high volume printing requirements).
  • Connect the Fitrix fax modem to a serial port on the VMware server and map the port to the Fitrix virtual server environment if faxing of reports from Fitrix is desired.
  • Provide complete support for all hardware, software, networking and any other systems administration issues for everything except for the Fitrix virtual server environment.

Section III: Connectivity Requirements For Fourth Generation Support

In order for Fourth Generation Software to provide any support assistance that requires access to your Fitrix ERP server or client, you will need to provide access using one of the following methods:

Linux Server or VMware virtual server (listed in order of preference)

  1. VPN – A VPN connection offers the highest level of connectivity allowing Fourth Generation to provide support more quickly and economically. Allows 24×7 access without user intervention. Windows VPN is preferred, FGSS will charge a fee for setting up connections to other VPN products.
  2. Remote Desktop onto a Windows Server – Allows 24×7 access without user intervention
  3. Remote Desktop onto a users workstation – The user cannot work while Fourth Generation is providing support.
  4. Webex access to a users workstation (or windows server) – Requires a user to allow access, the user cannot work while Fourth Generation is providing support.
  5. Any other method must be approved by FGSS, and FGSS will charge a fee for setting up the connection. (Please note that dial-up access is not supported)

Windows Client

If you are using the Fitrix ERP Windows Thin Client, your Windows PC must be connected to the internet and have a working web browser. Fourth Generation Software will use Webex to gain access to your Windows Client for Support.

Client Requirements

  • Windows Client: (Minimum Requirements)
    • Intel processor (486 and up)
    • 10 MB available hard drive space
    • 32 MB RAM
    • TCP/IP and Telnet connection to Linux Host
    • Windows 95 or better (Win 98/2000/ME/XP/NT/Vista/7)
  • X11 (X-Windows) Client (Client must be Intel processor based and support WINE)

Other Requirements

  • All printers to be used for the optional graphical printing feature must be postscript compliant