This document describes the minimum configuration requirements when installing the Software package application and data servers on a Microsoft® Windows - SQL Server 2012 SP2 server.
| Category | Configuration requirements |
|---|
| Operating system | - Microsoft Windows Server 2008 R2 x64 Standard and Enterprise.
- Microsoft Windows Server 2012 R2 x64 Essentials, Standard, and Datacenter.
|
| Computer | - 100 percent compatible PC.
- Processor Intel Xeon Quad Core X5570 2.93GHz or above recommended to manage up to 50 users simultaneously in a single-tier architecture.
- 1 core per group of 40 sessions.
|
| RAM memory | - 2 GB for the OS + 2 to 6 GB per database instance (average) + 60 MB per connected user.
|
| Disk space | - SQL server 2012 SP2: 3 GB.
- For Sage X3 People (reference folder and software): 4 GB.
- For the demo folder: 4 GB.
- For the exploitation folder: Depends on the data managed. A sizing tool is available to calculate the size requirements.
|
| Database software | - Microsoft SQL Server 2012 R2 x64 Enterprise Edition, installed with the following options:
- A named instance is required. It will be used to create the product database.
- By default, the communication by TCP/IP or Namepipe is not activated. It must be enabled for these two modes.
- The SQL Server Browser service must be launched.
|
| Mail server | - The workflow engine used in Classic mode requires a SMTP/POP3 server accessible from the server.
|
| Publication server | - An Apache server version 2.2 (up to build 2.2.25, which is the recommended build) must be installed on the application server.
|
| User accounts | - For the actual software users, it is recommended to define a user group and assign the access to the different software folders after the software component installation.
|
| Others | - A SAFE X3 ADXADMIN administration runtime must be installed on the server.
- A JDK or java runtime environment (version 7 or later) must be installed.
|
When installing the Sage X3 People software, standard scripts are supplied and will run to create the database instances, users, tables with the right configuration parameters. Changing the values of these parameters without a formal approval by Sage technical teams is strongly discouraged and might bring to serious issues Sage will not be held responsible for.