User Tools

Site Tools


implementation:general:hardwarerequirementscomplete

General Hardware Requirements

Server sizing

When installing a SAP Business One system together with Produmex solutions, both the hardware recommendations of SAP and of Produmex should be taken into account.
This document describes the additional hardware recommendations that should be considered on top of the SAP hardware recommendations.
Any deviation from these recommendations can lead to heavy performance issues.

Please note: all the recommendations in this document are minimum recommendations.

General recommendations

The general recommendations are independent from the product or components. Specific product-related recommendations are additions to the general recommendations.

Database server (MSSQL)

Memory
The amount of memory allocated to the MSSQL process should be at least equal to the total size of the production databases on the server. Only the size of the MDF files should be taken into account, the size of the log (LDF) files should be ignored.

The maximum server memory allocated to the MSSQL process should be set in such a way that a sufficient amount of memory is left free for the operating system. The amount of memory to be left free depends on the operating system. This setting can be set efficiently in an iterative way, by monitoring the amount of free memory.

Note: it’s recommended to use archiving functionality whenever possible in order to decrease the size of the production databases, and thus also the amount of memory needed on the database server.

Note: the database growth should be taken into account when calculating the size of the databases.

Example:

  • 3 production databases of 65GB, 20GB and 5GB: total 90GB
  • The operating system requires 8GB to operate.
  • At least 98GB of memory should be present on the server, out of which 90GB should be allocated to the MSSQL process.

Database server (HANA)

Memory
A strict minimum of 128GB of memory should be present on the server.
The amount of memory should be at least equal to the total size of the production databases on the HANA server.

Note: the database growth should be taken into account when calculating the size of the databases.

Example:

  • 3 production databases of 65GB, 20GB and 5GB: total 90GB
  • 90GB < 128GB → A minimum of 128GB is required

Produmex WMS

For an installation of Produmex WMS, the recommendations below should be taken into account in addition to the general recommendations.

Summary

Database MSSQL HANA
Minimum 56GB memory
Minimum memory size = DB size
+30GB memory / 1000 delivery lines
CPU = 4 + users x 0.25
Minimum 128GB memory
Minimum memory size = DB size
+50GB memory / 1000 delivery lines
CPU = 8 + users x 0.5
License server 32MB memory
1 CPU
Fat client 1GB memory / user
CPU = 2 + users x 0.25
Scale service 128MB memory
1 CPU / 4 scales
Other services Requires specific analysis
Add-on Heavy user Regular user
4GB memory
2 high-end CPU
800MB memory

Scope

The recommendations below are valid for installations within the following boundaries:

  • Database size < = 120GB
  • Average delivery notes lines per day < = 2000
  • Concurrent terminal users < = 30
  • Concurrent add-on users < = 20

For installations that exceed one or more of these parameters, a more complete analysis is required to determine the hardware requirements. It’s recommended that you contact Produmex in that regards.

Server split-up

The server roles should be split up as described below.

MSSQL
  • Database server
  • Produmex fat client server
  • Produmex server (all other Produmex services: license server, notification server, scale server, etc.)
  • (if any) Presentation server (SAP Business One client through RDP/Citrix)

If the only Produmex server is the license server, then the Produmex server can be combined with either the Produmex fat client server or the Database server on one single machine.

HANA
  • Database server
  • Produmex fat client server
  • Produmex server (all other Produmex services: license server, notification server, scale server, etc.)
  • (if any) Presentation server (SAP Business One client through RDP/Citrix)

If the only Produmex server is the license server, then the Produmex server can be combined with the Produmex fat client server on one single machine.

Database server

MSSQL

Memory
The recommendations below should be applied in addition to the general recommendations.
A minimum of 56GB of memory should be allocated to the MSSQL process.
An extra 30GB of memory should be added per 1000 delivery lines per working day (on average).

Example 1:

  • Total size of production databases: 90GB
  • On average, 1500 delivery lines are created per working day
  • Recommended memory: 90GB + 30GB * 1.5 = 135GB

Example 2:

  • Total size of production databases: 20GB
  • On average, 800 delivery lines are created per working day
  • Recommended memory: 20GB + 30GB * 0.8 = 44GB → minimum of 56GB

CPU cores
The amount of CPU cores should be calculated based on the number of concurrent users (fat client and add-on combined).
The minimum amount of CPU cores is 4 + [concurrent users] x 0.25 (rounded up)

Example:
10 add-on users + 8 scanner users → 4 + (10 + 8) x 0.25 = 8.5 → minimum 9 CPU cores

HANA

Memory
The recommendations below should be applied in addition to the general recommendations.
An extra 50GB of memory should be added per 1000 delivery lines per working day (on average).

Example 1:

  • Total size of production databases: 90GB
  • On average, 1500 delivery lines are created per working day
  • Recommended memory: 90GB + 50GB * 1.5 = 165GB

Example 2:

  • Total size of production databases: 20GB
  • On average, 800 delivery lines are created per working day
  • Recommended memory: 20GB + 50GB * 0.8 = 60GB → minimum of 128GB

CPU cores
The amount of CPU cores should be calculated based on the number of concurrent users (fat client and add-on combined).
The minimum amount of CPU cores is 8 + [concurrent users] x 0.5 (rounded up)

Example:
10 add-on users + 8 scanner users → 8 + (10 + 8) x 0.5 = 17 → minimum 17 CPU cores

Fat client server

Memory
1GB of memory should be counted for each concurrent fat client running on the server.

CPU cores
The amount of CPU cores should be calculated based on the number of concurrent users (fat client and add-on combined).
The minimum amount of CPU cores is 2 + [concurrent users] x 0.25

Produmex license server

The Produmex license server requires 1 CPU core and 32MB of memory.

Produmex scale service

The Produmex scale service requires 1 CPU core per 4 connected scales, and 128MB of memory.

Other Produmex WMS services

The Produmex notification listener’s requirements highly depend on the configuration. A more complete analysis is required to determine its hardware requirements.

Add-on

Heavy users
Users who use heavy functionality (= functions that require heavy computing) are considered heavy users, and they have higher requirements.

The following functions are considered heavy:

  • Create pick list proposals
  • Print pick lists
  • Create sales deliveries
  • Close production orders
  • Process cycle count

For each heavy user, an extra 4GB of memory and 2 CPU cores should be counted. A high-end CPU is also highly recommended (e.g. core i7 instead of core i3).

Regular users
For users who don’t use heavy functionality, an extra 800MB of memory should be counted for the add-on.

Produmex Manufacturing

Summary

Database MSSQL HANA
Minimum memory size = DB size Minimum 128GB memory
Minimum memory size = DB size
Service Broker 16BB memory
4 CPU
Add-on Heavy user Regular user
4GB memory
2 high-end CPU
800MB memory

Server split-up

The server roles should be split up as described below (there’s no difference between MSSQL and HANA).

  • Database server
  • Produmex service broker server
  • (if any) Presentation server (SAP Business One client through RDP/Citrix)

Database server

The general recommendations are sufficient.

Produmex service broker server

Memory
16GB of memory should be counted for the service broker, independently from the amount of concurrent connections and the number of modules.

CPU cores
4 CPU cores should be counted for the service broker, independently from the amount of concurrent connections and the number of modules.

Add-on

Heavy users
Users who use heavy functionality (= functions that require heavy computing) are considered heavy users, and they have higher requirements. The following functions are considered heavy:

  • MRP
  • Cost calculation
  • Job scheduling control panel
  • Production management cockpit

For each heavy user, an extra 4GB of memory and 2 CPU cores should be counted. A high-end CPU is also highly recommended (e.g. core i7 instead of core i3).

Regular users
For users who don’t use heavy functionality, an extra 800MB of memory should be counted for the add-on.

Produmex Scan, Operator

Summary

Database MSSQL HANA
Minimum memory size = DB size Minimum 128GB memory
Minimum memory size = DB size
Service Broker 16BB memory
4 CPU
Add-on 256MB memory

Server split-up

The server roles should be split up as described below (there’s no difference between MSSQL and HANA).

  • Database server
  • Produmex service broker server
  • (if any) Presentation server (SAP Business One client through RDP/Citrix)

Database server

The general recommendations are sufficient.

Produmex service broker server

Memory
16GB of memory should be counted for the service broker, independently from the amount of concurrent connections and the number of modules.

CPU cores
4 CPU cores should be counted for the service broker, independently from the amount of concurrent connections and the number of modules.

Add-on

An extra 256MB of memory should be counted on work stations that use the add-on.

Other recommendations

MSSQL server configuration

Compatibility level

The compatibility level of all databases should be set to the same level as the MSSQL server.

Hard drive separation

If the server has 2 separate physical drives, then the MDF and the LDF files should be stored on separate drives.
If the server has only one physical drive, then the MDF and the LDF files should be stored on the same drive.

Virtualization

If the servers are virtualized, extra memory and CPU cores should be counted for overhead.

Hard disks speed

Depending on the type of hard disks, and the usage of virtualization, the hard disks speed should be optimized.
SSD drives provide the best raw speed; for hard drives, using a proper RAID configuration is necessary.
Especially in the case of virtualized servers, make sure that the hard disk settings are tuned properly for the best performance possible.

Server role separation

Critical services should run alone on their server, so they do not compete for hardware resources with other processes.
The database server, Produmex fat client server and Produmex service broker servers are all critical services that should be separated.
All other applications and services (including file server, print server, exchange server, SharePoint, web servers, etc.) should run on other servers than the ones hosting the critical services.

Presentation server

If there is a presentation server (RDP/Citrix), where the SAP Business One client runs, then the “heavy users” of the add-on should be separated from the “regular users”. Heavy users typically execute complex computational functions that require a lot of hardware resources, and separating them will reduce the impact of these complex computational functions on regular users.

Network

The recommended connection between each server and the database server should be a link aggregation of 4 gigabit ethernet connections.

Device requirements

Produmex WMS

  • Wi-Fi
  • Barcode reader
  • Windows CE 5+ (PREFERRED), Windows Mobile 6+, Android 4.4.4, Android 6.0
  • Screen resolution: 240×320 or 320×320

Produmex Scan

  • Wi-Fi
  • Barcode reader (The suffix must be tab character, no new line needed.)
  • Windows CE 5+, Windows Mobile 6+ or Windows Mobile 7 (OS 7.2.2851.0 or higher)
  • Screen resolution: 320×320, 240×320 or 640×480
  • Minimum memory: 256 MB RAM
  • Minimum CPU: 800 MHz
  • Microsoft .NET Compact 3.5 framework

Produmex Operator

  • Wi-Fi
  • Android 6.0 or higher

Produmex PDC

  • Wi-Fi
  • Operating system: Windows 7/8/8.1/10 Professional or Windows Server 2012/2016
  • Screen resolution: 1024×768 or higher
  • CPU: Core i3 or better
  • RAM: 1GB per concurrent user
  • Device type: PC or tablet

Note: Bar code scanning for Produmex PDC on these devices can be achieved by using USB bar code scanners. These are not the same devices as the handheld devices used for Produmex WMS or Produmex Scan.

Produmex Weigh

  • USB or TCP/IP connection
  • Capable to reply the actual weight on command

Devices that partners have used

Mobile devices

Windows devices

Devices which are supported by Produmex Scan and Produmex WMS are listed below.

Honeywell Dolphin 60

Windows Embedded Handheld 6.5 Classic
WLAN IEEE 802.11 b/g/n
2.8“ QVGA 240×320 pixels
Memory: 256MB RAM
CPU:800MHz

M3 OX-10 (WM)-WSB-BGN-1D-AN1

Windows Embedded Handheld 6.5
WLAN IEEE 802.11 b/g/n
3.5” QVGA (WinCE) 240×320 pixels
Battery Li-Ion 3300mAh3.5“
Memory:256MB/1GB
CPU:833MHz

M3Mobile M3 SKY+

Microsoft Windows Mobile 6.5 Professional
WLAN IEEE 802.11 b/g
3.5” 240×320 screen
1D/2D Scanner

M3Mobile M3 T

Windows CE 5.0
WLAN IEEE 802.11 a/b/g
3.5“ 240×320 or optional 480×640

M3Mobile Compia Green

Windows CE 5.0
WLAN 802.11b/g
3.5” 240×320
3.7V Li-Ion 2200mAh battery / 3.7 Li-lon 4000mAh battery

Motorola MC9190

Microsoft Windows Mobile 6.5 Classic Edition
WLAN 802.11a/b/g
3.7“ VGA 480×640

Motorola MC3190

Microsoft® Windows Embedded Handheld 6.5.3
WLAN
3” QVGA 320×320 screen

Motorola MC9090-G

Windows CE 5.0
WLAN 802.11b/g
3.8“ 240×320

Datalogic Falcon X3

Microsoft Windows Mobile 6.5 or Windows CE 6.0 (preferred)
WLAN
3.5” 240×320 screen

Android devices
Supported by Produmex WMS

ZEBRA MC9200

Android 4.4.4 KitKat
WLAN 802.11 a/b/g/n
3.7“ Colour VGA 640×480 pixels
Memory: 1GB RAM
1D/2D Scanner

Supported by Produmex WMS and Produmex Operator

HONEYWELL DOLPHIN 75E

Android 6.0 Marshmallow with GMS
WLAN 802.11 a/b/g/n/ac
4.3” WVGA 480×800 pixels
Memory: 2GB RAM
1D/2D Scanner

Zebra MC3300

Android 7.0 Nougat
WLAN 802.11 a/b/g/n/ac/d/h/i/k/r/w
4.0“ WVGA
Memory: 2GB RAM
1D/2D Scanner

Touch screens

Devices which are supported by Produmex WMS are listed below.

D4POS MRP-120 Vision Series

MRP-127
17” TFT LCD with ELO touch (USB)
Slim housing and metal housing
Brightness (cd/m2): 300
Resolution: 1280 x 1024
Dimensions: 378 x 180 x 367 mm

MRP-127

MRP-129
19“ TFT LCD with ELO touch (USB)
Slim housing and metal housing
Brightness (cd/m2): 300
Resolution: 1280 x 1024
Dimensions: 422 x 180 x 401 mm

MRP-129

4POS MRP-255 Booster Series

MRP-255 Booster black
15” TFT LCD with ELO touch (USB)
Aluminum stand
Brightness (cd/m2): 350
Resolution: 1024 x 768
Dimensions: 377 x 231 x 344 mm

MRP-255 Booster black

3M™ MicroTouch™ Display M1700SS (17“)

3M™ MicroTouch™ Display M1700SS (17”)
17“ TFT LCD with 3M touch (USB/serial)
Brightness (cd/m2): 270
Resolution: 1280 x 1024
Dimensions: 405 x 413.3 x 247 mm

3M™ MicroTouch™ Display M1700SS (17")

3M™ MicroTouch™ Display M1500SS (15”)

3M™ MicroTouch™ Display M1500SS (15“)
15” TFT LCD with 3M touch (USB/serial)
Brightness (cd/m2): 225
Resolution: 1024 x 768
Dimensions: 408 x 398.3 x 258.7 mm

3M™ MicroTouch™ Display M1500SS (15")

Label printers

When using a label printer which is connected to or reachable from the server machine with Crystal Reports with a windows driver there is usually no compatibility problem.

Zebra printers with ZPL II language are also supported either as a network printer or a connected local printer on the server or a reachable shared printer.

Intermec PB32 Rugged Mobile Label Printer – WiFi

Mobile printer, can be attached to belt
203 dpi, thermal
WiFi - Network printer
Works with WH9 / Crystal Reports

Zebra S4M Direct Thermal Printer (USB, Ethernet or WiFi)

MResolution: 203 dpi
Print Width: 4: inch
Reports: ZPL or Crystal Reports
Flash Memory: 4 MB
Connectivity: USB, 10/100 Network adapter or WiFi is an extra option

implementation/general/hardwarerequirementscomplete.txt · Last modified: 2018/04/06 09:24 by csuhaa