Pre-Requisites

---

Assumptions

The engineer has a good working knowledge of Windows and Sage X3 administration, setup and installation.

The location of the following functions:

• PATCH
• GESAMK
• GESAUS

Knowledge of Windows Services, command line functionality and the registry

You have access to the Windows server (via remote desktop) where EDM for Sage X3 is to be installed

The Windows server were EDM for Sage X3 is to be installed is internet connected

You have received your licenses from the V1 Support team

You know the Sage X3 Endpoint(s) where EDD / EDM / PIA capability is to be applied

.NET 3.5 SP1 is installed on the installation server and client PC’s

You know the location of the solution.xml file in the Sage X3 directory structure

The Sage X3 SOAP Web-services are fully functional

If any of the above are not in place / you're unsure, STOP. Do not continue unless all the assumptions are satisfied or there is the potential for lengthy and costly delays to the project.

---

Sage X3 Compatibility

EDM for Sage X3 R14 has a reliance on Syracuse, therefore will only function against PU9 onwards and Minor Update Package 9.0.5 onwards.

You are of course advised to keep your version of Sage X3 as up to date as possible, given EDD, EDM and PIA are light touch, you are unlikely to experience compatiblity problems.

EDM for Sage X3 R14 was developed against and tested with V12 Patch 24.

NOTE: At the time of development and QA, this was the latest Sage release.

---

Firewall

The following binaries must be added to a whitelist / Firewall exceptions / Windows smart screen after the installation has been performed, for reference:

EDD

DbForm.exe
DbLoginServer.exe
DbFaxd.exe
DbFaxSend.exe
DbMailSend.exe

EDM (those in EDD, in addition)

httpPost.exe
DbCSArchiveServer.exe
DbLUQuery.exe
DbCSQuery.exe
DbCSBLOB.exe
DbRemoteBlob.exe

Ensure the firewall on the V1 Server opens the following ports:

5002
6181
80

PIA with DbCapture (those in EDD and EDM, in addition)

DbCapComms.exe
DbCapCommsUpdate.exe
V1SmartConnect.exe

Ensure the firewall on the V1 Server opens the following ports:

31450
31451
31452

NOTE: These ports are linked to the DbCapComms.exe which is a service allowing client connectivity to the DbCapture Server services. For load balancing purposes, more may be required for multiple users.

---

Anti-Virus / Malware

Given the number of files generated as part of the EDM for Sage X3 solution, you are advised to add the \V1 directory to a whitelist / exclusion area to prevent possible performance issues with real-time scanning can cause performance issues.

---

EDM

The core of EDM includes the authentication module (DbLogin) and a repository (DbArchive) to store the scanned / imported images. The minimum high level requirements for a server to run the core EDM components are:

Component	Specification
Operating Systems	Microsoft Windows Server 2012 (R2) Microsoft Windows Server 2016 Microsoft Windows Server 2019 Microsoft Windows Server 2022
RAM	8GB
Processor	Quad Core
Disk Space	10 gigabytes
LAN	Min 1GB LAN to clients

Component	Specification
Supported Databases	Microsoft SQL Server 2008 (R2) Microsoft SQL Server 2012 Microsoft SQL Server 2014 Microsoft SQL Server 2016 Microsoft SQL Server 2017 Microsoft SQL Server 2019 Microsoft SQL Server 2022 Oracle 11g

* Typical size is scanned documents 60KB – 100KB per page. For 20,000 pages per year allow at least 500MB of temporary storage on the scanstation PC, 2GB of storage on the V1 server and 2GB per year retained on the database server.

For example, the installation program could be run on a Windows 2016 server, but the database server can be either of the following:

• SQL, on the same server as the V1 server
• SQL, on a different server to the V1 server

The minimum requirements for a client PC to run the core EDM Settings components are:

Component	Specification
Operating Systems	Windows 7,8,10 and 11, 32 or 64 bit
RAM	4GB
Processor	Dual Core
Disk Space	5 gigabytes

---

PIA

The `core` PIA components include the authentication module (DbLogin), a file repository* (DbArchive) to store the scanned / imported images, an OCR module (ABBYY) and the services necessary to process images.

The OCR process is very processor and memory intensive so if the minimum specification (or better) is not adhered to, the installation will experience performance and reliability problems.

Ideally, the server components should always be installed on a dedicated server.
Under no circumstances should they be installed on, for instance, the same application server as Sage X3.

The minimum high level requirements for a server to run the core PIA components are:

Component	Specification
Operating Systems	Microsoft Windows Server 2012 (R2) Microsoft Windows Server 2016 Microsoft Windows Server 2019 Microsoft Windows Server 2022
RAM	16GB
Processor	8 Cores
Clockspeed	2.8GHz
Disk Space	10 gigabytes
Disk Plate	Solid State
LAN	Min 1GB LAN to clients

Component	Specification
Supported Databases	Microsoft SQL Server 2008 (R2) Microsoft SQL Server 2012 Microsoft SQL Server 2014 Microsoft SQL Server 2016 Microsoft SQL Server 2017 Microsoft SQL Server 2019 Microsoft SQL Server 2022

* Typical size is scanned documents 60KB – 100KB per page. For 20,000 pages per year allow at least 500MB of temporary storage on the scanstation PC, 2GB of storage on the V1 server and 2GB per year retained on the database server.

For example, the installation program could be run on a Windows 2016 server, but the database server can be either of the following:

• SQL, on the same server as the V1 server
• SQL, on a different server to the V1 server

The minimum requirements for a client PC to run the core PIA Settings components are:

Component	Specification
Operating Systems	Windows 7,8,10 and 11, 32 or 64 bit
RAM	4GB
Processor	Dual Core
Disk Space	5 gigabytes

---

Email

During the installation you will be prompted for the following details and they must be known before running the setup program to ensure setup is completed successfully.

• You have details of the customer’s mail server configuration
• Server address
• Server authentication
• Administrative email
• This email address is one who will be informed of activities on the server, so the I.T department for instance.

The minimum requirements for a server to allow mail relaying are:

Component	Specification
Mail Server	SMTP (on premise or hosted) or dedicated Microsoft 365 or Gmail mailboxes for both live and test.

---

Fax

During the installation you will be prompted for the following details and they must be known before running the setup program to ensure setup is completed successfully.

• You have a modem installed and attached either to the Sage Application Server or the V1 Server you intend to install against or another machine that has TCP-IP connectivity to either.
• You have details of the customer’s fax modem configuration
• COM port

The minimum requirements for a server to allow fax relaying for EDM are:

Component	Specification
Analogue Phone Line	Accessible via the modem present on the V1 server to be used or a server connected to it visible via TCP-IP

Fax modem

To send faxes requires a fax class 2 modem.

Note that there is a difference between the class 2 and the class 2.0 – the class 2.0 is not supported.

Additionally, the US Robotics class 2 fax modem is not supported.

V1 specifically recommend and support the following hardware:

MultiModem® ZDX desktop (model no. MT5656ZDX) – details are available at https://www.multitech.com/models/93571550LF

This is a simple plug and play device and is available generally in the US, Canada and UK. It is also available and supported globally through a network of local distributors.

---

Print

During the installation you will be prompted for the following details and they must be known before running the setup program to ensure setup is completed successfully.

You are advised to have at least one physical printer capable of printing A4/Letter documents from PDF's configured and available for testing.

When shared, ensure the share name doesn’t contain spaces.

These details include ensuring you have setup a user who has these printers shared against them. If this is not a requirement, this can be skipped during the install.

Ensure the transactional printers and barcode printer(s) to be used are accessible and visible to the server you intend to install EDD / EDM. They must be accessible by the Windows user.

For example, when logged in to the server where EDD / EDM is installed, logging in with the Windows user and opening Windows File Explorer, entering \\PRINTSERVER\ shows the printer(s).

---

Scanning and Hardware

The recommendations to allow image processing for EDM are:

Component	Specification
Scanner	TWAIN or ISIS / Kofax - Compatible workgroup scanner capable of scanning to TIFF or JPEG. Low volume - A4/Letter only – KodakAlaris S2000 series, eg S2070 Medium volume - KodakAlaris S3000 series, eg S3060 High volume - KodakAlaris i4000 or i5000 series, eg i4850 NOTE: Kofax VRS Elite / AIPE recommended when using barcode recognition.
Barcode Printing	Desktop Zebra Label Printer - preferably with Ethernet port - Zebra ZD421 Printer is connected to the network via a print server. Depending on the configuration, this must be accessible by a domain Windows user.
Barcode Labels	Type A 55mm x 32mm if your transaction numbers are typically less than 13 characters Type C 89mm x 39mm if your transaction numbers are typically greater than 13 characters
Transactional Printers	Printers must be ‘PDF enabled’, so assuming printing from the command line on the V1 Server: copy mypdf.pdf \\myprintserver\mysharedprinter Produces the result: 1 file copied. The PDF prints to the printer specified.