Professional Documents
Culture Documents
ARXivar Next - Minimum Requirements 2.3.30 - ING
ARXivar Next - Minimum Requirements 2.3.30 - ING
ARXivar Next
Pag. 1 of 13
General requirements Web Server and Application Server
The installation packages are available in our download area at the following link:
Area Download
The installation of the Service Bus requires Erlang (language) and RabbitMQ (message broker) to be
installed in sequence.
The machine on which these prerequisites are to be installed must necessarily be 64-bit.
▪
Figure 1 Figure 2
▪ For IIS version 7.5, it must be installed using the appropriate setup available at the
following link.
Please note: restart the machine after installation otherwise the component will not
be seen.
Pag. 2 of 13
Here is a screenshot of the flags for IIS to be activated in the area "Activation or deactivation of
Windows features".
Figure 3
• Microsoft Framework .NET 2.0
• Microsoft Framework .NET 3.5
• Microsoft Framework .NET 3.5 SP1
• Microsoft Framework .NET 4.0
• Microsoft Framework .NET 4.5.1
• Microsoft Framework .NET 4.5.2
• Microsoft Framework .NET Core 3.1.8
• Microsoft Visual C++ Package in the following versions:
o 2008 SP1 Redistributable x86
o 2010 Redistributable x86
o 2010 Redistributable x64
o 2013 Redistributable x86
o 2013 Redistributable x64
Pag. 3 of 13
o 2015 Redistributable Update 3 x86
• ARXivar MongoDB 3.2.22
• Erlang OTP 19.3 x64
• RabbitMQ 3.6.8
• Visual Studio 10 Tools for Office Runtime x64
• CPU: 4 Core
• RAM: 8 Gb
• HDD: 10 Gb (minimum)
o Consider also the space that will be used by the files in the FileSystem Repository in case
it is on the same machine.
Pag. 4 of 13
Compatible RDBMS
• MS SQL Server 2012 Service Pack 4 or higher
• Oracle 10g or higher:
o Oracle Provider 10g or higher (minimum requirement for proper functioning) including
the 64-bit module Oracle Services for Microsoft Transaction Server
o The following package must be active, and the user system must have the necessary
grants to authorise its execution: DBMS_JOB for ARXivar NEXT 2.1 or previous;
DBMS_SCHEDULER for ARXivar NEXT 2.2 or later
o Always install the 32-bit version as well
• MySQL 5.0 a 5.7.5
o Versions 5.7.6 or higher are not supported (due to the new keyword VIRTUAL)
o The lower_case_tables_names option is not supported and therefore should be set as
follows:
▪ Linux / Unix: lower_case_table_name=0
▪ Windows: lower_case_table_name=1
o Connector/ODBC 3.5.1 (version 3.51.25 or higehr); always install the 32-bit version of
the driver too.
(*) Also consider the minimum requirements and the space that the database will use if you decide
to run the DB on the same ARXivar server:
http://msdn.microsoft.com/en-us/library/ms143506%28v=sql.105%29.aspx
http://docs.oracle.com/cd/B28359_01/install.111/b32002/pre_install.htm#i1011296
Pag. 5 of 13
Web applications architecture (Web Authorization – Web API –
Web Portal)
Features of the 5 web applications that compose the ARXivar Next solution:
Web Authorization
o Dedicated to all authentication operations
o Requires low system requirements
Web API
o Dedicated to all application logics
o It demands high system requirements
Web Portal
o Application Front-End Interface
o It demands low system requirements
Web Queue
o Dedicated to background processing that requires a long time
o It demands high system requirements
Web Workflow Api
o WorkFlow 2.0
o Dedicated to background processing of WorkFlow processes
o Demands high system requirements
Pag. 6 of 13
Client device requirements
Desktop devices:
Operating system (Windows, Linux or MacOs) with one of the following browsers installed:
• Edge 20 or higher
• Internet Explorer 9 or higher
• Chrome (last version)
• Firefox (last version)
• Opera 15 or higher
• OS X Safari 6.2.6 or higher
Mobile devices:
Pag. 7 of 13
Scalability assumptions
The Windows user used by the Web API Application Pool must have full access to the ARXivar
FileSystem Repository.
Pag. 8 of 13
RECOMMENDED CONFIGURATIONS
General considerations
MINIMUM CONFIGURATION
Infrastructure assumptions
(Infrastructure for Test Environment; Small Business Production Environment)
Minimal (1 Server) --- <= 20 Users – 5 WorkFlow – 5.000 Documents per year
Server 1 CPU: 8 Core – RAM: 16Gb – HDD: 60Gb
Server 1
Web Auth; Web API; Web Portal; Web Queue
WCF Service
ARX Mailer
ARX OCR
ARX Thumbnails
ARX ArchService
ARX Index
ARX Link Service
ARX BarCode Service
ARX SwapOut
ARX Invoice Xchange
ARX Folders
ARX Push Notifications
ARX Spool Recognition
ARX PlugIn Manager
Repository FileSystem
MongoDB
RabbitMQ
Pag. 9 of 13
RECOMMENDED CONFIGURATION
Infrastructure assumptions
Entry (2 Server) --- 20 Users – 5 WorkFlow – 5.000 Documents per year
Server 1 CPU: 8 Core – RAM: 16Gb – HDD: 20Gb
Server 2 CPU: 4 Core – RAM: 8Gb – HDD: 20Gb
Server 1 Server 2
WCF Service Web Auth; Web API; Web Portal; Web Queue
ARX Mailer MongoDB
ARX OCR RabbitMQ
ARX Thumbnails
ARX ArchService
ARX Index
ARX Link Service
ARX BarCode Service
ARX SwapOut
ARX Invoice Xchange
ARX Folders
ARX Push Notifications
ARX Spool Recognition
ARX PlugIn Manager
Repository FileSystem
Pag. 10 of 13
Large (3 Server) --- 150 Users – 10 WorkFlow – 150.000 Documents per year
Server 1 CPU: 8 Core – RAM: 16Gb – HDD: 10Gb
Server 2 CPU: 8 Core – RAM: 16Gb – HDD: 20Gb
Server 3 CPU: 8 Core – RAM: 16Gb – HDD: 120Gb
Server 1 Server 2 Server 3
Web Queue Web Portal Web API; Web Auth
WCF Service MongoDB Repository FileSystem
ARX Mailer RabbitMQ
ARX OCR
ARX Thumbnails
ARX ArchService
ARX Index
ARX Link Service
ARX BarCode Service
ARX SwapOut
ARX Invoice Xchange
ARX Folders
ARX Push Notifications
ARX Spool Recognition
ARX PlugIn Manager
Extreme (4 Server) --- 250 Users – 15 WorkFlow – 350.000 Documents per year
Server 1 CPU: 8 Core – RAM: 16Gb – HDD: 350Gb
Server 2 CPU: 8 Core – RAM: 16Gb – HDD: 10Gb
Server 3 CPU: 8 Core – RAM: 16Gb – HDD: 10Gb
Server 4 CPU: 16 Core – RAM: 32Gb – HDD: 400Gb
Server 1 Server 2 Server 3 Server 4
Web Queue Web API Web API Web Portal; Web Auth
WCF Service Load Balancing MongoDB
ARX Mailer RabbitMQ
ARX OCR ARX Link Service
ARX Thumbnails ARX SwapOut
ARX ArchService ARX Folders
ARX Index ARX Push Notifications
ARX BarCode Service ARX PlugIn Manager
ARX Invoice Xchange
ARX Spool Recognition
Repository FileSystem
Pag. 11 of 13
Extreme Plus (5 Server) --- 250 Users – +20 WorkFlow – +1.000.000 Documents per year
Server 1 CPU: 8 Core – RAM: 16Gb – HDD: 10Gb
Server 2 CPU: 8 Core – RAM: 16Gb – HDD: 10Gb
Server 3 CPU: 8 Core – RAM: 16Gb – HDD: 10Gb
Server 4 CPU: 16 Core – RAM: 32Gb – HDD: 350Gb
Server 5 CPU: 16 Core – RAM: 32Gb – HDD: 40Gb
Server 1 Server 2 Server 3 Server 4 Server 5
WCF Service Web API Web API Web Queue Web Portal; Web Auth
ARX Mailer Load Balancing MongoDB ARX Link Service
ARX OCR RabbitMQ ARX SwapOut
ARX Index ARX ArchService ARX Folders
ARX BarCode Service ARX Thumbnails ARX Push Notifications
ARX Invoice Xchange Repository FileSystem ARX PlugIn Manager
ARX Spool Recognition
Pag. 12 of 13
General disk occupancy considerations for the Repository on
FileSystem
In relation to the calculation of the physical occupation of each individual file (profile document or
profile attachment), we suggest running this simple formula adapting the number of files you plan to
manage in a year, the average weight of the files you usually manage (by convention we consider 150Kb)
and considering at least 3 years of archive maintenance:
• (([Tot N Doc] * [Average file weight in Kb]) * [N Years])
• On a case of 50,000 docs/year you will have:
o ((50.000 * 150Kb) * 3) = 22.500.000Kb 21,45Gb 22Gb (nearest)
Workflows and its active instances will also affect the occupation of disk space.
It is therefore advisable to consider the average number of instances that can be managed and to carry out
the same calculation considering the average weight of a workflow of approximately 60Kb.
• (([Tot N Instances] * [Average file weight in Kb]) * [N Years])
• On a case of 3,000 WorkFlow instances, you will have:
o ((3.000 * 150Kb) * 3) = 1.350.000Kb 1,28Gb 1,5Gb (nearest)
A disk space dedicated to the ARXivar Document Repository of at least 22Gb + 1.5Gb = 23.5Gb should
therefore be provided.
Pag. 13 of 13