Minimum / Recommended System Requirements

This Web Page is designed to provide you with some basic information related to the installation of our applications. It will also provide you with some basic information regarding minimum hardware requirements needed to run our application efficiently.

Please note: the details outlined on this Web Page are generic, and only take into consideration the operational requirement of our application. None of this information/specification provided takes into account other systems or network requirements related to the use of other third party application, including SQL Server®. Please refer to your IT/hardware provider for final requirements.

 

Server - Minimum System Requirements

Server - Recommended System Requirements

Processors: AMD or Intel Dual Core Processors: Intel Xeon Quad Core/AMD Opteron Quad Core
Memory: 4 GB of Ram Memory: 8-12 GB of Ram
Hard Drive: 120 Gigabyte HDD Hard drive: 500 gigabyte HDD (Raid Array recommended)
Second Drive: CD/DVD Drive Second Drive: CD/DVD Drive
OS: Windows Server 2003 R2 (64-Bit) *Note* If Connecting through Terminal Services Windows Server 2008 or Higher is required. OS: Microsoft Server 2008 standard edition (64-Bit)
Database: SQL Server 2005 Database: SQL Server 2008 (Standard)
Backup Device Plan: (Media or Cloud Based backup) Backup Device Plan: (Media or Cloud Based backup)
   

Web Server - Minimum System Requirements

Web Server - Recommended System Requirements

Processors: AMD or Intel Dual Core Processors: Intel Xeon Quad Core/AMD Opteron Quad Core
Memory: 4 GB of Ram Memory: 8-12 GB of Ram
Hard Drive: 120 Gigabyte HDD • Hard drive: 500 gigabyte HDD (Raid Array recommended)
Second Drive: CD/DVD Drive Second Drive: CD/DVD Drive
OS: Windows Server 2003 R2 (64-Bit) *Note* If Connecting through Terminal Services Windows Server 2008 or Higher is required OS: Microsoft Server 2008 standard edition (64-Bit)
Internet Information Services: Microsoft IIS 6.0 or above *Note* - Certain .Net modules have compatibility issues with Microsoft SharePoint Internet Information Services: Microsoft IIS 7.0 or above *Note* - Certain .Net modules have compatibility issues with Microsoft SharePoint
Backup Device Plan: (Media or Cloud Based backup) Backup Device Plan: (Media or Cloud Based backup)
   

Work Station - Minimum System Requirements

Work Station - Recommended System Requirements

Processors: AMD or Intel Single Core ( 1ghz or Higher) Processors: AMD or Intel Quad Core
Memory: 2 GB of Ram Memory: 4 gigabytes of Ram
Hard Drive: 120 Gigabyte HDD Hard Drive: 250 Gigabyte HDD
Second Drive: CD/DVD Drive Second Drive: CD/DVD Drive
OS: Windows Vista Business, 7 Pro, or 8 Pro (32-Bit) OS: Windows 7 or 8 Professional (64-Bit)
Monitor: To Avoid Display issues, Monitor size has to be a minimum of 1024x768 Monitor: 20 inch or larger, set to Native resolution (min. 1024 x 768)
Software: Outlook 2007 *Note* Outlook is utilized for the Emailing and Printing features of Enterprise Software: Outlook 2013 *Note* Outlook is utilized for the Emailing and Printing features of Enterprise
Backup Device Plan: (Media or Cloud Based backup) (Optional) Backup Device Plan: (Media or Cloud Based backup) (Optional)
   
*Please Note* - All requirements will vary depending on Infrastructure/environment setup  
   

Crystal Reports (Created/Modified by Clients)

 
Crystal Reports: Version 2008 or Higher Is Required in order to be compatible with Enterprise. *Note* Reports created in previous versions will not run unless verified with a newer version of crystal.  

 

Common Installation Sernerios

Enterprise 32 - Basic Installation - Network Diagram

The installation diagram shown below provides a graphical view of a common Enterprise 32 installation. In this diagram, the system installation is broken up into three separate sections, your office workstations (computers 1- 3), database server, and shop floor data collection workstations (computers 4 – 6).

The first group of computers depicted in this diagram are the office workstations, (computers 1- 3). Each of these workstations will have Enterprise 32 application installed, with each being connected to the database, once installed, through your network using a standard network connection configured in Enterprise 32, which includes the Server Name, User ID, and Password.

The second group depicted in this diagram is the database server, which may host other application and/or databases besides the Enterprise 32 database. However, in this example we will assume the primary role of this server is dedicated to the sole use of Enterprise 32 application. With the server in place and connected to your network, you will need to have Microsoft® SQL® Server application installed and running. With SQL® in place, you can then attach the blank Enterprise 32 database provided by EPMS to SQL®, allowing access to Enterprise 32. You’re not required to install the Enterprise 32 application on your server although some customers do. This allows for basic system maintenance, such as running the “Database Update” routine required after an upgrade of the application has been performed.

The third group of computers depicted in this diagram are the Shop Floor workstations (computers 4- 6), which are used as data collection terminals. These computers will have the Enterprise 32 application installed direct on each of them, with a connection to the database, once installed, through your network using a standard network connection, that includes the Server Name, User ID, and Password.

 

Enterprise 32 - Installation using Terminal Services® - Network Diagram

The installation diagram shown below provides a graphical view of a common Enterprise 32 installation using Terminal Services® to remotely launch Enterprise 32. In this diagram, the system installation is broken up into three separate sections, your office workstations (computers 1- 3), database/application server, and shop floor data collection workstations (computers 4 – 6).

The first group of computers depicted in this diagram are the office workstations, (computers 1- 3). Each of these work station will access the Enterprise 32 application through the network using the Remote Desktop Connection®, which is the client side of Terminal Services®, which is a Microsoft® product. The advantage to using Terminal Services® is substantial, because it will eliminate the need to have the Enterprise 32 installed individually on every workstation. Instead you will be viewing an image of the application generated at the application server via Terminal Services®. Another advantage is that it will simplify the ongoing maintenance and upgrade process substantially, since it only installs on the application server as opposed to each individual workstation. Also, with a download from Microsoft® you can run the Remote Desktop Connection® client for a Mac, allowing any Mac user in your company to access Enterprise 32.

The second group depicted in this diagram is the database server, and an application/Terminal Server, both of which may host other application and/or databases besides the Enterprise 32 database/application. However, in this example we will assume the primary role of these servers is dedicated to the sole use of the Enterprise 32 application, and Terminal Services®. With the database server hardware in place and connected to your network, you will need to have the Microsoft® SQL Server® application installed and running. With SQL® in place. You can then attach the blank Enterprise 32 database, provided by EPMS, to SQL®, allowing access to Enterprise 32 once installed on the Terminal Server.

The third group of computers depicted in this diagram are the Shop Floor workstations (computers 4- 6), which are used as data collection terminals on your production floor. Like your office work station, each of these workstations will access the Enterprise 32 application through the network using Terminal Services®.

 

Enterprise 32 - Basic Installation with Enteprise.NET Ecommerce - Network Diagram

The installation diagram shown below provides a graphical view of a common Enterprise 32 installation combined with the use of Enterprise.NET. In this diagram the system installation is broken up into four separate sections, your office workstations (computers 1- 3), application server and web server (Center Section), shop floor (Data Collection Stations)(computers 4 – 6), and three computers that are a representation of your customer accessing your Enterprise.NET site via the internet.

The first group of computers depicted in this diagram are the office workstations, (computers 1- 3). Each of these workstations will have Enterprise 32 application installed, with each being connected to the database, once installed, through your network using a standard network connection configured in Enterprise 32, which includes the Server Name, User ID, and Password.

The second group depicted in this diagram is the database server, and web server, which may host other application and/or databases besides the Enterprise 32 database. However, in this example we will assume the primary role of this server is dedicated to the sole use of Enterprise 32 application. With the server in place and connected to your network, you will need to have Microsoft® SQL Server® application installed and running. With SQL® in place, you can then attach the blank Enterprise 32 database provided by EPMS to SQL®, allowing access to Enterprise 32. You’re not required to install the Enterprise 32 application on your server although some customers do. This allows for basic system maintenance, such as running the “Database Update Routine" required after an upgrade of the application has been performed. The web server will need to be properly configured for use as a web server, and on your network. You will then install all required the Entperise.NET files, and complete the necessary configuration per EPMS instructions.

The third group of computers depicted in this diagram are the Shop Floor workstations (computers 4- 6), which are used as data collection terminals. These computers will have the Enterprise 32 application installed direct on each of them, with a connection to the database, once installed, through your network using a standard network connection, that includes the Server Name, User ID, and Password.

The last group depicted in this diagram, are representation of your customers internet connection to your implemented Entperise.NET sites.

 

 

EPMS on LinkedIn

 

Face Book