Documentos de Académico
Documentos de Profesional
Documentos de Cultura
700
Here is an example:
In this example, the environment has the following specifications:
User Count - 35 users (Office + MES users)
Application Load Profile typical manufacturing customer except they would prefer to run
MRP during busy times.
Number of Epicor 9.05 Application Servers and Database Server Choice - Epicor 9.05.700
using Microsoft SQL Server 2008 R2 database on a physical server configuration.
Important Comments
Be sure to tell your hardware vendor that you plan to use these machines as an ERP application
server and database server. The processing demands of a database server and application server
versus a file server are much different and your hardware vendor should adjust the recommended
configuration accordingly. Consider other factors such as manufacturer reliability, service, and
maintenance. These factors are extremely important if the machine runs into a hardware problem
and you are faced with downtime.
Expandability. You should consider expandability when choosing server(s). For example, if you
require multiple processors in the future, will the machine accept more processors? What if you find
out that your business practices requires extensive I/O can you add more disks to your system or
add an external disk array? Can you add more RAM?
Database server cannot be scaled out. The available CPU resources on the SQL database server will
determine the room for growth in an Epicor 9.05 environment.
It is possible to add additional Epicor 9.05 application servers over time (scale out) as the
application usage load grows. SQL Server on the other hand cannot be scaled out; it can only be
scaled up (by adding additional resources to the server). If you are planning on growing your
environment and introducing additional heavy load in the future, then consider purchasing a server
with a motherboard that has four CPU sockets and leave two of them available for future growth.
This is a good insurance against having to replace the whole server if additional CPU resources are
required.
Deploy the supported version of software at all times. It is strongly recommended that you run fully
supported versions of software at all times. As a practical matter, Epicor cannot support or certify
releases for third party vendor software, such as Microsoft, or any other vendor software, that no
longer carries mainstream support from that vendor. In other words, when the vendor phases out its
support of a particular package, Epicors support for that same software package or version
generally ends as well.
Virtual Deployment of Epicor Applications. Virtualization is an abstraction layer that decouples the
physical hardware from the operating system to deliver enhanced IT resource utilization and
flexibility. There are various non-Epicor software products available that can be used to build your
virtual deployment. Epicor does not itself support or warrant these virtual environments or the Epicor
Software as used in the virtual environment. However, Epicor does and will continue to support its
Performance Tuning. Relational databases are advanced systems that sometimes require tuning for
optimal performance. One major selling point of both platforms is that the database engines are
largely self-tuning. However, it can still be useful to perform some level of tuning on a database
particularly in the area of database input/output operations to the physical disk subsystem. If
performed by an experienced professional, this tuning can substantially improve performance on
your hardware. Note that there are many considerations, outside of the scope of this guide, that are
involved in maintaining the server at peak performance.
Dont run other Applications on Epicor Production application and database Server. Due to the
mission critical nature of any companys Enterprise Resource Planning (ERP) system, it is
recommended that you have a server dedicated to running Epicor 9.05 production instance.
Running other applications including Test / Training / Pilot / development implementation of Epicor
9.05 application on the database and / or separate application server can degrade performance.
While certain situations may be suitable for dual hosting, it is strongly recommended that Epicor run
on a dedicated machine. Microsoft Small Business Server (SBS) is not a recommended platform for
Epicor due to the multi-application design of this product.
Where do we Run Test / Pilot / Training / Development Environments? These installations dont require
a high end server like the one required for production environment and hence should be on a
separate and possibly less powerful server.
File Server Functions. The server machine for Epicor should not be used as a network file server
because file and print services require large amounts of resources. Using a single server for both file
and print services and your Epicor database will significantly reduce database performance.
SQL Server Licensing. When deciding on processors, note the SQL Server 2008 R2 licensing can be
processor dependent so factor that into the total performance vs. cost determination. We do not
recommend using CAL based licensing.
Spread I/O Load Across Multiple Disk Spindles. Once you have adequate RAM and CPU, focus on
the Disk Subsystem to improve performance. Generally, if you have the fastest disks then the more
disks in a RAID 10 the faster the READ / WRITE performance will be. Spreading the I/O load across
multiple physical RAID configurations also helps. Enterprise SSDs can greatly improve the I/O
subsystem performance.
Direct Network Connection Between the Application Server and Database Server. When you
separate the database server from the Epicor 9.05 Application Server, it has to be directly
connected with at least a 1 Gigabit network connection between the application and database
servers. If this condition is not met the application performance will suffer. We dont want any
latency between them.
Disaster Recovery and High Availability. Unfortunately it is beyond the scope of this guide to cover
the details of this topic. Epicor Technical Solutions group is a great resource for this discussion and
they will be happy to work with you to design a DR and HA solution that suits your business needs.
These application load profiles represent an approximation of what a Standard, Medium and High
application load entails. This helps determine that for the same number of user count does your application
usage pattern equate to standard or high usage. It is recommended that you contact Epicor Technical
Solutions for a detailed application load sizing activity.
(recommended)
Epicor 9.05 files (Epicor905)
Reports and temporary data (EpicorData)
Two SSDs are required.
Two SCSI / SAS HDDs are required.
Hard Disk Drive storage Operating system: 2 x 15k RPM HDDs in RAID 1
The following files are stored in 6 x 15k RPM HDDs in RAID 10:
Epicor 9.05 files (Epicor905)
Reports and temporary data (EpicorData)
Eight SCSI / SAS HDDs are required.
Network For good network performance, use 1 Gbit (or faster) network cards
To ensure that network latency is as low as possible between the Epicor
application server and the SQL database server, add at least two network cards:
One dedicated network card that is directly connected to the SQL
database
(Cable from network card to network card)
One dedicated network card that is connected to the LAN
(and is processing all network traffic except SQL database traffic)
Example server HP DL380, Dell R710
make/model
(recommended)
SQL database
SQL transaction log
SQL tempdb
Four SSDs are required (6 Gbit/s S-ATA or SAS is recommended)
Two SCSI / SAS HDDs are required.
SQL Server is very write intensive and the SSD has to be able to accommodate
heavy writes (both from a performance and durability perspective). SLC-based
SSDs are recommended.
Contact Epicor Technical Solutions or your storage vendor for additional details on
how to design a solution that can accommodate the performance and durability
requirements that SQL Server has on the storage subsystem.
Network For good network performance, use 1 Gbit (or faster) network cards.
To ensure that network latency is as low as possible between the SQL database
server and the Epicor application server(s); add one dedicated network card for
each Epicor application server.
The Epicor application server(s) should then be directly connected to the SQL
database server - cable from network card to network card.
An example:
If the environment has two Epicor application servers, then the SQL database
should have at least three network cards:
One dedicated network card per connected Epicor application server
One network card for general LAN connectivity.
Network For good network performance, use 1 Gbit (or faster) network cards.
To ensure that network latency is as low as possible between the SQL database
server and the Epicor application server(s); add one dedicated network card for
each Epicor application server.
The Epicor application server(s) should then be directly connected to the SQL
database server - cable from network card to network card.
An example:
If the environment has two Epicor application servers, then the SQL database
should have at least three network cards:
One dedicated network card per connected Epicor application server.
One network card for general LAN connectivity
Network For good network performance, use 1 Gbit (or faster) network cards.
To ensure that network latency is as low as possible between the SQL database
server and the Epicor application server(s); add one dedicated network card for
each Epicor application server.
The Epicor application server(s) should then be directly connected to the SQL
database server - cable from network card to network card.
An example:
If the environment has two Epicor application servers, then the SQL database
should have at least three network cards:
One dedicated network card per connected Epicor application server.
One network card for general LAN connectivity.
These recommendations represent an approximation of the required hardware to support an implementation based on
the application load profile.
For more detailed recommendations; contact Epicor Technical Solutions and they can help you design the best
hardware configuration to run your business.
Application Load
* LOAD01 Standard * LOAD02 Medium * LOAD03 High
Profile
Number of Epicor 1 x APP01 1 x APP01 1 x APP01 (Interactive)
9.05 application
servers 1 x APP01 (Reporting)
(See Table: APP01 for
hardware details)
Total: 2 x APP01
SQL database server SQLBOX01 (see table) SQLBOX01 (see table) SQLBOX02 (see table)
These recommendations represent an approximation of the required hardware to support an implementation based on
the application load profile.
For more detailed recommendations; contact Epicor Technical Solutions and they can help you design the best
hardware configuration to run your business.
Application Load
* LOAD01 Standard * LOAD02 Medium * LOAD03 High
Profile
Number of Epicor 1 x APP01 1 x APP01 (Interactive) 1 x APP01 (Interactive)
9.05 application
servers 1 x APP01 (Reporting) 1 x APP01 (Reporting)
(See Table: APP01 for
hardware details)
Total: 2 x APP01 1 x APP01 (SC / EDI)
Total: 3 x APP01
SQL database server SQLBOX01 (see table) SQLBOX01 (see table) SQLBOX02 (see table)
For more detailed recommendations contact Epicor Technical Solutions and they can help you design the best
hardware configuration to run your business.
Application Load
* LOAD01 Standard * LOAD02 Medium * LOAD03 High
Profile
Number of Epicor 1 x APP01 1 x APP01 (Interactive) 1 x APP01 (Interactive)
9.05 application
servers 2 x APP01 (Load 2 x APP01 (Reporting)
(See Table: APP01 for balanced - Reporting)
hardware details)
2 x APP01 (SC / EDI)
Total: 3 x APP01
Total: 5 x APP01
SQL database server SQLBOX02 (see table) SQLBOX02 (see table) SQLBOX03 (see table)
Contact Epicor Technical Solutions if your workload is at fits any of the LOAD02 Medium or LOAD03 High application
load profiles ( See table in Application Load Profile section).
For more detailed recommendations contact Epicor Technical Solutions and they can help you design the best
hardware configuration to run your business.
Microsoft SQL Server
1000 users, application usage profile: Standard
2008 R2
Number of Epicor 9.05 Epicor 9.05 is a stateless application so it is possible to add additional Epicor 9.05
application servers (See application servers as the load grows.
Table: APP01 for
hardware details) Note that the SQL database server cannot be scaled out it can only be scaled
up (by adding additional CPUs / RAM).
2 x APP01 (Interactive)
2 x APP01 (Reporting)
Total: 4 x APP01
Create two load balanced pools (Interactive and Reporting) of application
servers.
If needed, you can create an additional pool for Service Connect / EDI.
A hardware load balancer is recommended.
SQL database server SQLBOX3 is the recommended choice if the load profile is LOAD01 Standard.
CPU:
The available CPU resources on the SQL database server will determine the room
for growth in an Epicor environment.
It is possible to add additional Epicor 9.05 application servers over time (scale
out) as the load grows.
SQL Server cannot be scaled out; it can only be scaled up (by adding additional
hardware resources to the server).
If your current expected load is at the LOAD01 Standard level and you are
considering introducing additional heavy load (growing to LOAD02 Medium or
LOAD03 High) which could require additional CPU resources; then consider
purchasing an eight-socket server and leave four of the CPU sockets available for
future growth. This is a good insurance against having to replace the whole server
if additional CPU resources are required.
Intel Xeon Ten-Core recommendations (for eight-socket server motherboard):
2.4 GHz frequency (E7-8870 or faster)
30MB L3 cache or more, QPI Speed of 6.4 GT/s
It is recommended to leave Hyper-Threading enabled (check BIOS settings).
Storage:
PCI Express-based SSD storage is recommended (for example Fusion-io).
SLC-based SSDs are recommended.
For more detailed recommendations contact Epicor Technical Solutions and they can help you design the best
hardware configuration to run your business.
Small 5-40 Users
OpenEdge Database
(Office + Data Collection)
Operating System Windows Server 2008 R2 Standard Edition (2008 x64/32 will also work)
Linux ES 3.0 (32-bit)
Unix HP/UX 11 (32-bit or 64-bit)
Processors 2 x CPU sockets with at least Xeon Six-core.
Intel Xeon Six-Core recommendations:
3 GHz frequency (X5670 or faster)
12MB L3 cache or more, QPI Speed of 6.4 GT/s
It is recommended to leave Hyper-Threading enabled (check BIOS settings).
Disable Power Saving options and C-States in BIOS.
Memory (RAM) 16 GB DDR3-1066 (or faster) ECC
Solid State Drive (SAS / Operating system: 2 x 15k RPM HDDs in RAID 1
SATA based) storage
The following files are stored in 2 x SSD in RAID 1:
(recommended)
Epicor 9.05 files (Epicor905)
Reports and temporary data (EpicorData)
OpenEdge database files
OpenEdge database bi files
Two SSDs are required.
SLC-based SSDs are recommended.
Two SCSI / SAS HDDs are required.
Hard Disk Drive storage Operating system: 2 x 15k RPM HDDs in RAID 1.
The following files are stored in 4 x 15k RPM HDD in RAID 10:
Epicor 9.05 files (Epicor905)
Reports and temporary data (EpicorData)
OpenEdge database files
The following files are stored in 2 x 15k RPM HDD in RAID 10:
OpenEdge database bi files
Consider separate partition for Epicor 9.05 reports.
Eight SCSI / SAS HDDs are required.
Network 1 Gbit or faster
These recommendations represent an approximation of the required hardware to support an implementation based on
the LOAD01 Standard application load profile (See table in Application Load Profile section).
For more detailed recommendations contact Epicor Technical Solutions and they can help you design the best
hardware configuration to run your business.
Medium - 41-150 Users
OpenEdge Database
(Office + Data Collection)
Operating System Windows Server 2008 R2 Standard Edition (2008 x64/x32 will also work).
If you wish to utilize more than 32GB of RAM, Enterprise Edition must be used.
These recommendations represent an approximation of the required hardware to support an implementation based on
the LOAD01 Standard application load profile (See table in Application Load Profile section).
For more detailed recommendations; contact Epicor Technical Solutions and they can help you design the best
hardware configuration to run your business.
Large - 151 300 Users
OpenEdge Database
(Office + Data Collection)
Operating System Windows Server 2008 R2 Standard Edition (2008 x64/x32 will also work).
If you wish to utilize more than 32GB of RAM, Enterprise Edition must be used.
(recommended)
Epicor 9.05 files (Epicor905)
Reports and temporary data (EpicorData)
OpenEdge database files
OpenEdge database bi files
Six SSDs are required.
SLC-based SSDs are recommended.
Two SCSI / SAS HDDs are required.
These recommendations represent an approximation of the required hardware to support an implementation based on
the LOAD01 Standard application load profile (See table in Application Load Profile section).
For more detailed recommendations; contact Epicor Technical Solutions and they can help you design the
best hardware configuration to run your business.
These recommendations represent an approximation of the required resources to support an implementation based on
the application load profile.
For more detailed recommendations contact Epicor Technical Solutions and they can help you design the best
hardware configuration to run your business.
Application Load
* LOAD01 Standard * LOAD02 Medium * LOAD03 High
Profile
Number of Epicor 1 x VMWAREAPP01 1 x VMWAREAPP01 2 x VMWAREAPP01
9.05 application (Interactive) (Interactive) (Load balanced -
servers (See Table: Interactive)
VMWAREAPP01 for 1 x VMWAREAPP01 2 x VMWAREAPP01
configuration details) (Reporting) (Load balanced - 2 x VMWAREAPP01
Reporting) (Load balanced - Reporting
Total: 2 x
/ SC / EDI)
VMWAREAPP01 Total: 3 x VMWAREAPP01
Total: 4 x VMWAREAPP01
SQL database server SQLBOX01 (see table) SQLBOX01 (see table) SQLBOX01 (see table)
Hard Disk Drive Place the .vmdk files on Place the .vmdk files on Place the .vmdk files on a
storage a RAID 10 partition with a RAID 10 partition with RAID 10 partition with at least
at least four 15k RPM at least four 15k RPM four 15k RPM disks
disks disks
Solid State Drive (SAS Place the .vmdk files on Place the .vmdk files on Place the .vmdk files on a
/ SATA based) a RAID 1 partition with a RAID 1 partition with at RAID 1 partition with at least
storage at least two SSDs least two SSDs two SSDs
(recommended)
For more detailed recommendations contact Epicor Technical Solutions and they can help you design the best
hardware configuration to run your business.
Application Load
* LOAD01 Standard * LOAD02 Medium * LOAD03 High
Profile
Number of Epicor 2 x VMWAREAPP01 2 x VMWAREAPP01 3 x VMWAREAPP01
9.05 application (Load balanced - (Load balanced - (Load balanced -
servers (see Table: Interactive) Interactive) Interactive)
VMWAREAPP01 for
configuration details) 2 x VMWAREAPP01 3 x VMWAREAPP01 5 x VMWAREAPP01
(Load balanced - (Load balanced - (Load balanced Reporting
Reporting) Reporting) / SC / EDI)
Total: 4 x Total: 5 x VMWAREAPP01 Total: 8 x VMWAREAPP01
VMWAREAPP01
SQL database server SQLBOX01 (see table) SQLBOX01 (see table) SQLBOX02 (see table)
Hard Disk Drive Place the .vmdk files on Place the .vmdk files on Place the .vmdk files on a
storage a RAID 10 partition with a dedicated RAID 10 dedicated RAID 10 partition
at least four 15k RPM partition with at least four with at least six 15k RPM disks
disks 15k RPM disks
Solid State Drive (SAS Place the .vmdk files on Place the .vmdk files on Place the .vmdk files on a
/ SATA based) a RAID 1 partition with a RAID 1 partition with at RAID 1 partition with at least
storage at least two SSDs least two SSDs two SSDs
(recommended)
For more detailed recommendations; contact Epicor Technical Solutions and they can help you design the best
hardware configuration to run your business.
Application Load
* LOAD01 Standard * LOAD02 Medium * LOAD03 High
Profile
Number of Epicor 3 x VMWAREAPP01 4 x VMWAREAPP01 5 x VMWAREAPP01
9.05 application (Load balanced - (Load balanced - (Load balanced -
servers (see Table: Interactive) Interactive) Interactive)
VMWAREAPP01 for
configuration details) 3 x VMWAREAPP01 4 x VMWAREAPP01 5 x VMWAREAPP01
(Load balanced - (Load balanced - (Load balanced Reporting
Reporting) Reporting) / SC / EDI)
Total: 6 x Total: 8 x VMWAREAPP01 Total: 10 x VMWAREAPP01
VMWAREAPP01
SQL database server SQLBOX01 (see table) SQLBOX02 (see table) SQLBOX03 (see table)
Hard Disk Drive Place the .vmdk files on Place the .vmdk files on Place the .vmdk files on a
storage a dedicated RAID 10 a dedicated RAID 10 dedicated RAID 10 partition
partition with at least partition with at least six with at least eight 15k RPM
four 15k RPM disks 15k RPM disks disks
Solid State Drive (SAS Place the .vmdk files on Place the .vmdk files on Place the .vmdk files on a
/ SATA based) a RAID 1 partition with a RAID 1 partition with at RAID 1 partition with at least
storage at least two SSDs least two SSDs two SSDs
(recommended)
These recommendations represent an approximation of the required resources to support an implementation based on
the application load profile.
For more detailed recommendations contact Epicor Technical Solutions and they can help you design the best
hardware configuration to run your business.
Application Load
* LOAD01 Standard * LOAD02 Medium * LOAD03 High
Profile
Number of Epicor 1 x HYPERVAPP01 1 x HYPERVAPP01 2 x HYPERVAPP01
9.05 application (Interactive) (Interactive) (Load balanced -
servers (see Table: Interactive)
HYPERVAPP01 for 1 x HYPERVAPP01 2 x HYPERVAPP01
configuration details) (Reporting) (Load balanced - 2 x HYPERVAPP01
Reporting) (Load balanced - Reporting
Total: 2 x HYPERVAPP01
/ SC / EDI)
Total: 3 x HYPERVAPP01
Total: 4 x HYPERVAPP01
SQL database server SQLBOX01 (see table) SQLBOX01 (see table) SQLBOX01 (see table)
Hard Disk Drive Place the .vhd files on a Place the .vhd files on a Place the .vhd files on a RAID
storage RAID 10 partition with at RAID 10 partition with at 10 partition with at least four
least four 15k RPM disks least four 15k RPM disks 15k RPM disks
Solid State Drive (SAS Place the .vhd files on a Place the .vhd files on a Place the .vhd files on a RAID
/ SATA based) RAID 1 partition with at RAID 1 partition with at 1 partition with at least two
storage least two SSDs least two SSDs SSDs
(recommended)
For more detailed recommendations contact Epicor Technical Solutions and they can help you design the best
hardware configuration to run your business.
Application Load
* LOAD01 Standard * LOAD02 Medium * LOAD03 High
Profile
Number of Epicor 2 x HYPERVAPP01 (Load 2 x HYPERVAPP01 3 x HYPERVAPP01
9.05 application balanced - Interactive) (Load balanced - (Load balanced -
servers (see Table: Interactive) Interactive)
HYPERVAPP01 for 2 x HYPERVAPP01 (Load
configuration details) balanced - 3 x HYPERVAPP01 5 x HYPERVAPP01
Reporting) (Load balanced - (Load balanced Reporting
Reporting) / SC / EDI)
Total: 4 x HYPERVAPP01
Total: 5 x HYPERVAPP01 Total: 8 x HYPERVAPP01
SQL database server SQLBOX01 (see table) SQLBOX01 (see table) SQLBOX02 (see table)
Hard Disk Drive Place the .vhd files on a Place the .vhd files on a Place the .vhd files on a
storage RAID 10 partition with at dedicated RAID 10 dedicated RAID 10 partition
least four 15k RPM disks partition with at least four with at least six 15k RPM disks
15k RPM disks
Solid State Drive (SAS Place the .vhd files on a Place the .vhd files on a Place the .vhd files on a RAID
/ SATA based) RAID 1 partition with at RAID 1 partition with at 1 partition with at least two
storage least two SSDs least two SSDs SSDs
(recommended)
For more detailed recommendations contact Epicor Technical Solutions and they can help you design the best
hardware configuration to run your business.
Application Load
* LOAD01 Standard * LOAD02 Medium * LOAD03 High
Profile
No of Epicor 9.05 3 x HYPERVAPP01 (Load 4 x HYPERVAPP01 (Load 5 x HYPERVAPP01 (Load
application servers balanced - Interactive) balanced - balanced - Interactive)
(see Table: Interactive)
HYPERVAPP01 for 3 x HYPERVAPP01 (Load 5 x HYPERVAPP01 (Load
configuration details) balanced - 4 x HYPERVAPP01 (Load balanced Reporting / SC /
Reporting) balanced - Reporting) EDI)
Total: 6 x HYPERVAPP01 Total: 8 x HYPERVAPP01 Total: 10 x HYPERVAPP01
SQL database server SQLBOX01 (see table) SQLBOX02 (see table) SQLBOX03 (see table)
Hard Disk Drive Place the .vhd files on a Place the .vhd files on a Place the .vhd files on a
storage dedicated RAID 10 dedicated RAID 10 dedicated RAID 10 partition
partition with at least partition with at least six with at least eight 15k RPM
four 15k RPM disks 15k RPM disks disks
Solid State Drive (SAS Place the .vhd files on a Place the .vhd files on a Place the .vhd files on a RAID
/ SATA based) RAID 1 partition with at RAID 1 partition with at 1 partition with at least two
storage least two SSDs least two SSDs SSDs
(recommended)
Windows Vista / 7
Business Edition Recommended Configuration
Network Workstation
Operating System Windows 7 Professional
OR Windows Vista Business Edition
(32-bit or 64-bit*)
Processor 2.8 GHz or higher. Recommended dual core 32-bit or 64-bit processor and
SATA hard drives. SSD is especially beneficial if the workstation runs
multiple applications at the same time.
RAM 4 GB
Disk Space for Epicor 2 GB
Monitor SVGA or higher adapter
Color SVGA monitor with 1024 X 768 resolution
DVD-R DVD-R drive (if not on server)
Other Internet connection recommended for online support and downloading
latest updates. Fast network connection recommended between client
and Epicor 9.05 Application Server. Epicor 9.05 application will work on
slower networks but the performance will be better if you have a fast
connection with low latency.
(*) The Epicor 9.05 and Vista Service Pack will run Windows Vista Business Edition 64-bit version by
using the Microsoft Windows-32-bit-on-Windows-64 (WOW64) subsystems. WOW64 is an x86 emulator
that allows 32-bit-bit Windows-based applications to run on 64-bit Windows.
Microsoft Remote
Up to 25 Users
Desktop Services
Operating System Windows Server 2008 R2 Standard Edition (2008 x64 will also work)
If you wish to utilize more than 32GB of RAM, Enterprise Edition must be used.
Processor 2 x CPU sockets with at least Xeon Six-Core.
Intel Xeon Six-Core recommendations:
3 GHz frequency (X5670 or faster)
Intel Xeon Ten-Core recommendations (for two-socket server motherboard):
2 GHz frequency (E7-2850 or faster)
Intel Xeon Ten-Core recommendations (for four-socket server motherboard):
2 GHz frequency (E7-4850 or faster)
It is recommended to leave Hyper-Threading enabled (check BIOS settings).
Disable Power Saving options and C-States in BIOS. Enable Turbo Boost.
Memory (RAM) 32 GB or more
Solid State Drive (SAS / 2 x SSDs in RAID 1
SATA based) storage
(recommended)
Hard Disk Drive storage 6 x 15k RPM SCSI / SAS Drives in RAID 10
Free Disk Space 20GB Minimum
Network 1 Gbit or faster
(recommended)
Hard Disk Drive storage 6 x 15k RPM SCSI / SAS Drives in RAID 10
Free Disk Space 20GB Minimum
Network 1 Gbit or faster
Enable Static and/or Dynamic IIS Compression if your CPU utilization permits.
Epicor Service
Connect
Operating System Windows Server 2008 R2 Standard Edition (2008 x64 will also work)
Processor 1 x CPU socket with at least Xeon Quad-Core
It is recommended to leave Hyper-Threading enabled (check BIOS settings).
Disable Power Saving options and C-States in BIOS. Enable Turbo Boost.
Note: Epicor Service Connect generates additional load on Epicor 9.05
Application Server. If you have a high volume of transactions flowing through
Service Connect to the Epicor 9.05 application server, then consider using a
dedicated Epicor 9.05 application server for this purpose. High volume Service
Connect workflows that use multiple threads can generate a lot of load on the
receiving Epicor 9.05 application server and consequently on the database
server.
Memory (RAM) 8 GB
Hard Disk Drive storage 2 x 15k RPM SCSI / SAS Drives in RAID 1
Free Disk Space 20GB Minimum
Network 1 Gbit or faster
This table is meant to list other Epicor or 3rd party software that might need
additional server hardware. It is beyond the scope of this guide to spec
out in detail what those hardware requirements will be. We are listing
commonly used systems here so that you can plan for additional
hardware procurements.
Epicor Replication For hardware specs, please contact Epicor Technical Solutions group
EPM For hardware specs, please contact Epicor Technical Solutions group
AFR, Info worker, Enterprise For hardware specs, please contact Epicor Technical Solutions group
Search, Activity Stream, E9
Portal, Open4, Insite Manifest
PLM , IQS For hardware specs, please contact Epicor Technical Solutions group
Hardware for any other If you have purchased any other software license from Epicor, please work
Epicor or 3rd party software with the Epicor Technical Solutions group to see if you need extra servers
purchased through Epicor? to run them. Some applications can be installed on one shared server.
Access Points
IEEE 802.11 Radio Frequency standards support
Barcode Equipment
Support for Bar 39 Barcode
MES Workstation
PioneerPOS Stealth M5
Same configuration as Epicor workstation
Communications
An Internet connection is required to access the Epicor Online Support Center for interim and
commercial releases and remote support.
DSL or higher quality connection recommended.
Internet Explorer 7.0 or higher is needed for Epicor Help.
Printer
At least one laser printer required for standard reports and forms
Must have current Windows drivers
Backup Equipment
Epicor recommends your company invest in a reliable backup system. Your hardware vendor can
recommend and install one for you.
Network Bandwidth
The bandwidth of a network defines the amount of data that can be transferred across the network
at once. If the bandwidth of the network is insufficient for the amount of information being
transmitted (usually because too many users are on a single network segment), performance drops
noticeably. In these cases, the network will need re-configuring to lower the amount of traffic or
increase the bandwidth of the network. Traditional hubs are being replaced by high-speed data
switches, which further help alleviate network bottlenecks. Multiple server network cards and
automated load balancing may be considered too.
Network bandwidth is not the only factor that determines the "speed" of a network as perceived by
the end user. The other key element of network performance is latency. While it would often appear
that data is transmitted instantly between one point and another (that is, with no delay at all), this is
typically not the case. Network latency may be caused by:
The time it takes for a packet to travel from point to point
The transmission medium (optical fiber, wireless, etc.) may introduce some delay because larger
packets typically take longer to move from place to place
Routers and other processing points each take time to examine and possibly make changes to
packet header
Intermediate devices such as switches and bridges may cause delays
It is often difficult to diagnose a network bandwidth or latency issue and this is best handled by
professional network analysts.
As a general rule, the Epicor client has a bandwidth requirement of 10 Kbps (kilobits per second) to
500Kbps. This will vary depending on the volume of data transferred between the client and the
server. Additionally, file attachments require increased bandwidth.
A simplified rule of thumb for the number of clients to connect per network segment is to determine
the worst-case acceptable throughput for each network client, then divide that amount into the
selected network throughput. For example, if each client should have no less than 1.5 Mbps of
available bandwidth, and the network supports 100 Mbps, the segment could possibly support 66
The following tests are designed to test various aspects of an I/O disk subsystem i.e. bandwidth
(Mega Bytes/second i.e. MB/Sec), Latency (milliseconds), performance of your I/O system with
desired block size (64KB) and file size and type of I/O read or write and sequential v/s random
writes. The parameters described in previous statement have a great impact on IOPS and hence
they are specified exactly as needed here for testing using SQLIO. On the same machine you will
get different IOPS number if you change any one parameter. So testing with Epicor recommended
parameters is highly recommended.
Instructions: The default install path on a 64-bit OS for SQLIO is C:\Program Files (x86)\SQLIO\
In the SQLIO install path, the configuration file called param.txt determines which drive letter SQLIO
will test.
If you want to test the D-drive letter, then change the param.txt content to the following:
D:\testfile.dat 2 0x0 80000
Modify the param.txt file so that it points to the database drive letter and then run the following
command:
sqlio -kW -t8 s900 -o8 -frandom -b64 -BH -LS -Fparam.txt
Modify the param.txt file so that it points to the transaction log drive letter and then run the
following command:
sqlio -kW -t2 s900 -dM -o8 -fsequential -b64 -BH -LS Fparam.txt
Modify the param.txt file so that it points to the tempdb drive letter and then run the following
command:
sqlio -kW -t8 s900 -o8 -frandom -b64 -BH -LS -Fparam.txt
Growth Path Buy a system which allows you to put several disks internally. If your scenario dictates
external disk array / SAN then you should always buy an array which allows you to slide in more disk
spindles if needed. Remember, we add more disk spindles not to add capacity but to spread the
I/O load across multiple spindles.
Epicor recommends RAID 10 for database files and Epicor 9.05 application servers temporary
and report files.
RAID 5 (or any other combination similar to RAID 5). Not recommended and supported. It
does not mean that Epicor 9.05 application will not work. It means that performance will
suffer if you configure your disks in a RAID 5 or any other RAID 5* combination.
Implementation Types
The four common RAID implementations include:
In the operating system
In the disk controller
Via a dedicated RAID controller hardware
In a separate subsystem
Implementing RAID as part of the operating system is the least expensive option and also the least
desirable. Software implemented RAID solutions lack hardware level control and place additional
load on the server, reducing the amount of server resources available for your Epicor applications.
Backup Devices
It is extremely important that your business information is backed up on a regular basis. The
frequency and type of backup should be discussed with your implementation team, but one or
more tape / backup drives on the server can ensure a timely backup is made. It is also possible to
backup to the local disk, and then copy the file elsewhere for storage. Consider off-site storage for
backups as well. Test your backup scripts and restore procedures and backup files regularly.
For over 20 years, Epicor has been a recognized leader dedicated to providing leading edge
enterprise software solutions to midmarket companies around the world. With over 20,000
customers, Epicor delivers end-to-end, industry-specific solutions that enable companies to
immediately improve business operations and build competitive advantage in todays real-time
global economy. Epicors comprehensive suite of integrated software solutions for Customer
Relationship Management, Financials, Manufacturing, Supply Chain Management, and Services
Execution and Control provide the scalability and flexibility to support long-term growth. Epicors
solutions are complemented by a full range of services, providing a single point of accountability to
promote rapid return on investment and low total cost of ownership.
Disclaimer
This document and its contents, including the viewpoints, recommendations, dates and
functionality descriptions expressed herein are believed to be accurate as of its date of publication,
February 2012. However, Epicor Software Corporation does not make any guarantee,
representations or warranties with regard to the enclosed information and specifically disclaims the
implied warranties of fitness for a particular purpose and merchantability. All information contained
herein is subject to change without notice. The usage of any Epicor Software shall be pursuant to an
Epicor end user license agreement and the performance of any consulting services by Epicor
personnel shall be pursuant to Epicors standard services terms and conditions. Any hardware
purchased shall be subject to its own equipment purchase agreement. Epicor is a registered
trademark of Epicor Software Corporation. All other trademarks acknowledged. Copyright 2012
Epicor Software Corporation.
Trademark and Copyright Acknowledgement
Copyright Epicor Software Corporation 2012. Epicor, Vantage and Vista are trademarks and/or
registered trademarks of Epicor Software Corporation. All other trademarks acknowledged. Epicor
reserves the right to make modifications or changes to the functionality, and plans described herein
without further notice. This document is intended solely to inform the audience of Epicor's current
intentions. Epicor makes no warranties, express or implied in or by this document. The contents of this
document are believed to be current and accurate as of its date of publication. For a complete
description of the product features, please refer to the products user guides, reference manuals
and release notes.