Support Matrix

ILINX Platform

The ILINX Enterprise Content Management Platform (ECM) provides complete, agile document automation, streamlining the process of acquiring, storing, accessing and routing documents securely and confidently; while maintaining a lean, agile and highly adoptable design.

This document provides an administrator guide outlining the minimum hardware and software requirements for the installation of a core ILINX ECM platform. Actual requirements can vary significantly for each individual implementation, and impacted by infrastructure, process, integration and volume/load requirements.

The best method for sizing a suitable production implementation architecture is to run a “proof of concept” or “pilot” project prior to full implementation. Doing so allows the implementation team to further assess the known requirements, perform load testing and adjust the specifications accordingly.

For information on administering the system, please see the ILINX Capture and ILINX Content Store Administrator Guides.


Introduction

The line of ILINX products have minimum machine and server system requirements for each product. This document covers the system, server, and client requirements of the ILINX product suite. Below is a diagram of ILINX products and servers in relation to hosting/supporting Microsoft products.


Supported System Requirements

Important:  ImageSource only tests and supports integration with third party vendor products that are covered under their own “mainstream support” programs.  For information regarding Product Lifecycle support for ILINX products, please refer to the ILINX EULA file.

Note: SSL (Secure Sockets Layer), TLS (Transport Layer Security), & HTTPS (Hyper Text Transfer Protocol Secure) are all supported within ILINX. Refer to the Installation Guide for configuration information.

Virtualization Solutions

Citrix and other virtualization solutions are used in conjunction with ILINX products every day by customers around the world. ImageSource works to ensure that all ILINX applications operate correctly within these environments and strives to support our customers using these solutions. While ImageSource does not explicitly support the various virtualization products, our technical support group will endeavor to work with customers to troubleshoot and determine the root cause of any ILINX technical issue. ImageSource reserves the right to request our customers to diagnose certain issues on a Supported Operating System in a native environment. ImageSource will only make this request when there is reason to believe that the virtual environment is a contributing factor to the issue. If the issue cannot be reproduced in the native environment, ImageSource may conclude that the issue is specific to the virtualization environment, and unrelated to our software. The customer shall then refer their issue to Citrix or appropriate virtualization vendor.

ILINX Web Clients

The ILINX web clients entail ILINX Capture, ILINX Content Store, ILINX eForms and Flex.

Minimum Support Configurations
Quad processor (or more)
6 GB RAM (or higher)
10 GB (or more) disk space
1920 x 1080 desktop display (32 bit color) 19-24” wide monitor , 1600×900 laptop display,*Note: Other resolutions may not scale correctly
Certificate Delivery:

OPTION 1: Individual* Connect to URL
OPTION 2: Group Policy* Connect to URL

*Note:  See the Choice of client deployment | Push client certificate through active directory group policy section of the ILINX Installation Guide document for additional details.

Applications Supported Versions
Client Operating System Microsoft Windows 8.1, Windows 10
Microsoft Office 2016 & Office 365 (32 bit) (viewing)
ILINX Capture & Content Store browser Internet Explorer 11 (32-bit)
ILINX Flex browser Internet Explorer 11 (32-bit), Google Chrome 68.0, Mozilla Firefox 61.0, Microsoft Edge
.NET Framework Built and executes using version 4.7.2
Tested using version 4.8
Supports 4.7.2, & 4.8
For further information see: Determine Which .NET Framework Versions Are Installed

Important Note:  As of version 6.0, if you are using Windows XP and or any version earlier than Internet Explorer 9.0 as the OS / Web browser for the ILINX Content Store or ILINX Capture client, they will continue to function; however, they are no longer supported.

 

ILINX Capture Mobile & Mobile SDK

Mobile OS Supported Versions Device Camera
iOS (iPhone & iPad) 13.x & 14.x 8 MP (or higher)
Android 9.x, & 10.x 8 MP (or higher)

 

Mobile Updates Note:

Testing of major mobile version updates after an ILINX release

Apple and Android release operating system version updates on a frequent basis. ImageSource is dedicated to developing and testing against the latest versions of iOS and Android. After the initial ILINX release, the ILINX Capture Mobile application and mobile SDK will continue to be supported on the latest “dot” release of the two latest major versions of iOS and Android. A major version is defined by the first digit of the release number, for example, iOS 12 or iOS 13 or for Android version 9 or 10. A “dot” release refers to the second digit in the version number, for example, iOS 13.3 or iOS 13.4. Critical security updates are often delivered via “dot” releases therefore, ImageSource supports only the latest “dot” release for the two newest operating system versions and strongly encourages customers to keep their mobile device systems up to date.

When a new major version of iOS or Android is officially released after the ILINX release, the ILINX Capture Mobile application will be tested for compatibility with the new major version. Once testing has completed, ILINX Capture Mobile will continue to be supported on the new operating system version and the one major version prior.

Based on the above support information, if a device’s operating system cannot be upgraded to a version supported by ILINX Capture Mobile, that device will not be supported.

 

ILINX Capture Email Import Client

Mail Clients Minimum Supported Versions
Microsoft Outlook Desktop32-bit only Microsoft Office 2016
Microsoft 365 Desktop

Requirements Links
Visual Studio 2010 Tools for Office Runtime Download
Client Hardware specifications see ILINX Web Client

Note: Outlook Web App is NOT supported.

 

ILINX eForms & Flex

The browsers listed and their respective versions are fully compatible with ILINX eForms & Flex.

Note: Flex does not support file formats .exe or .msi to import nor download. Use ILINX Content Store or ILINX Capture if you need to capture these file formats.

Windows Browser Client for Flex (latest versions)
Internet Explorer v11
Google Chrome
Mozilla Firefox
Chromium-based Edge

Apple Browser Client for Flex (latest versions)
Desktop Safari
Mozilla Firefox

Other Client for Flex (latest versions)
PC Web Scanning is supported on Windows 10 only
iOS mobile: Safari (*)
Android mobile: Chrome (**)

Requirements Links
Visual C++ Redistributable 64-bit See Installation Guide for Downloads
PHP 7.4.x (x64), and PHP Manager for IIS See Installation Guide for Downloads
MS ODBC Driver 11 for SQL server 64-bit See Installation Guide for Downloads
SQL Server drivers for PHP 7.4 (SQLSVR40.exe) See Installation Guide for Downloads

 

ILINX Release

Minimum Support Configurations Notes
100 MB (or more – installation disk space)
6 GB RAM (or more)
Microsoft .NET Framework 4.61 Built and executes using version 4.7.2
Tested using version 4.8
Supports 4.7.2 & higher
Microsoft SQL Server
(refer to ILINX Database Server)
This software is required if you choose to export index values to a database or will be configuring the Audit database option.

 

ILINX Capture Format Converter

Minimum Support Configurations Notes
600 MB (or more – installation disk space)
6 GB (or more)
Microsoft .NET Framework 4.61 Built and executes using version 4.7.2
Tested using version 4.8
Supports 4.7.2 & higher
Microsoft Office 2016 & Office 365
(32 bit) (conversion)
Microsoft SQL Server
(refer to ILINX Database Server)
This software is required if you choose to export index values to a database or will be configuring the Audit database option.

 

ILINX Import

Minimum Support Configurations Notes
100 MB (or more – installation disk space)
6 GB RAM (or more)
Microsoft .NET Framework 4.61 Built and executes using version 4.7.2
Tested using version 4.8
Supports 4.7.2 & higher
Microsoft Office 2016 & Office 365 File system and email conversion during import
Microsoft SQL Server
(refer to ILINX Database Server)
This software is required if you choose to import index values to a database or will be configuring the Audit database option.

 

ILINX Export

Minimum Support Configurations Notes
100 MB (or more – installation disk space)
6 GB RAM (or more)
Microsoft .NET Framework 4.61 Built and executes using version 4.7.2
Tested using version 4.8
Supports 4.7.2 & higher
Microsoft SQL Server
(refer to ILINX Database Server)
This software is required if you choose to export index values to a database or will be configuring the Audit database option.

 

ILINX Servers

The ILINX Servers act as the supporting system for ILINX Capture and ILINX Content Store, as well as ILINX eForms, ILINX Flex, and ILINX Advanced Capture. The support specifications apply to all of these products.

Important:  The system specifications referenced the minimum supported configurations.  ImageSource strongly advises that the finalized system specifications for your environment be reviewed in detail with the Project Management and Technical Teams that will be performing the installation prior to purchasing your hardware and operating systems in order to make sure the system is sized correctly to meet the specific requirements and needs of your business unit(s) or Enterprise environment.

The ILINX database can be run on the same computer as the ILINX Web Server, but in a production environment, it is highly recommended that the SQL database be on its own dedicated server.

Minimum Support Configurations Notes
80 GB Hard disk space System drive
8 GB RAM (or more)
64-bit, 4 core Processor

Application Supported Versions
Windows Windows Server 2019 (LTSC) build 1903
Microsoft SQL Server refer to ILINX Database Server
Microsoft .NET Framework Built and executes using version 4.7.2
Tested using version 4.8
Supports 4.7.2 & higher
For further information see: Determine Which .NET Framework Versions Are Installed

AD FS Details

Important Note:  ImageSource highly recommends Active Directory Federation Services (AD FS) as the authentication model.  If there is an existing AD FS environment, we recommend you configure ILINX to use this.  If AD FS is not available, we recommend the AD FS service to be enabled on the ILINX server.  ILINX also has basic supports for WIS, which can be used if you have a simple Active Directory structure or setup.  If you find WIS is not sufficient for your needs, please use AD FS as described in the Enabling AD FS section.

> Provides federated authentication and authorization services for the ILINX products

> Minimum AD FS version 3.0 is required. Additional details:

– AD FS 3.0 ships with Windows Server 2012 R2

– AD FS 4.0 ships with Windows Server 2016

Note: AD FS configurations are only required for ILINX Content Store and ILINX Capture.

 

ILINX Database Server

Important:  The system specifications referenced the minimum support configurations.  ImageSource strongly advises that the finalized system specifications for your environment be reviewed in detail with the Project Management and Technical Teams that will be performing the installation prior to purchasing your hardware and operating systems in order to make sure the system is sized correctly to meet the specific requirements and needs of your business unit(s) or Enterprise environment.  SQL Server is a core component of the ILINX system and has a direct impact on total solution performance.  System resources for the SQL Server should be considered in relation to the expected ILINX solution complexity and transactions.  Minimum specifications described here are based off the SQL Server 2017 minimum recommended specifications – it is expected that systems will require additional resources to support ILINX.

Minimum Support Configurations Notes
Microsoft SQL Server
(Standard or Enterprise)
2016, 2017
– During installation of the SQL Engine, be sure to install the FullText feature as well.
– It is recommended that SQL server be installed and configured in accordance with best practices and individual organization requirements.
– Depending on SQL Database requirements (such as transparent data encryption, replication, high availability, or reporting) SQL Enterprise version may be required.
32 GB RAM It is important to configure disk space size with respect to the future. Consider your current document storage needs and future growth level to determine an appropriate size. Actual size requirements will vary greatly between implementations; if you are not sure of your database storage requirements contact the Support Department.
Memory 8 GB – SQL Server minimum required memory is 1GB
– ImageSource recommends at least 8GB for any SQL Server installation for ILINX. SQL Server can consume a large amount of memory to maintain performance depending on the ILINX solution transactional load. The minimum memory specified here likely needs to be monitored and increased.
Disk – Installation
15 GB Available
– SQL Server minimum required available space is 6GB
– ImageSource recommends at least 15GB of available space on the SQL installation drive.
Disk – Database Drives
10 GB Available
– Disk performance and space requirements are different for every system. It is recommended for production systems that disks be high performance, dedicated and separate physical drives partitioned for data, log and TempDB storage. When installing on-premise it recommended for production systems, if using Tiered Storage, to allocate tier 1 storage (fastest available). If deploying to Azure, use Premium or Ultra disk. Proper configuration of I/O subsystems is very important to the optimal performance and operation of SQL Server systems. For more information, see Monitoring Disk Usage.
It is important when specifying the drive size to remember that all content will be stored in the database. Data drive size should be planned accordingly to accommodate all current content as well as future. Logs drive size should be planned according to the ILINX solution transactional load and SQL Server backup strategy. It is recommended that TempDB be configured according to SQL Server best practices.
– In addition, you should proactively monitor your databases and tweak some settings when required. It is advisable to pre-size content database files, if possible, to the expected size. This way you can avoid the overhead of auto-growth which can take some resources and have negative performance impacts. There is no universal recipe for the values you can use for the initial size and auto-growth settings as this will heavily depend on your environment and usage.
CPU 2.0Ghz x64
Intel/AMD processor
– CPU core and speed requirements are different for every system. It is recommended that the cores and/or speed of the processor for SQL Server be increased from the minimum specifications to support the ILINX Solution.
Example sizing of a typical production system – As an example, a typical or average ILINX production system SQL specification is included below. Actual sizes for a system depend on the specifics of the intended ILINX Solution. It is highly recommended that the ImageSource Project or Support teams be consulted regarding the sizing for your system.
Memory: 32 GB
Disk: 60 GB – OS
320 GB – SQL Data
160 GB – SQL Log
10 GB – TempDB
CPU: 2x 4 Core Intex Xeon 2.6Ghz (8 cores total)

This recommendation is designed to serve as an indication of a suitable implementation architecture. Implementation may be possible with an architecture that differs from the one recommended, and with less or more hardware. SQL Server hardware resourcing is directly affected by the number of ILINX modules being used, the workflow complexity, the number of batches being processed and imaging demographics. The most reliable method for sizing a suitable implementation architecture is to run a proof of concept or pilot prior to full implementation. This will allow the implementation team to assess the likely success of the suggested implementation architecture and adjust the specifications accordingly if the need to do so is demonstrated by the results.

Estimates are based on available documentation, experience, testing, feedback, POCs, and best-practices. Solution implementations differ significantly, which means that an individual solution can differ quite significantly in its performance numbers. Due to the complexity of the solution space, we cannot guarantee any of the estimates displayed. They serve as a guideline in a pre-implementation phase to roughly estimate required hardware. Many factors can influence the final hardware requirement.