Enterprise Platform Database Server Requirements and Recommendations for On-Premise Deployments¶
Enterprise Platform is made up of these modules which are are available as local web services for aPriori On-Premise installations.
- aP Analytics
- aP Admin:
- Scenario Export (Required for aP Analytics)
- System Data Export (Required for aP Analytics)
- Scenario Synchronization
- LDAP Synchronization
- VPE Synchronization (for Digital Factory Synchronization)
.You can use the aP Admin modules to transfer data from aP Pro to aP Analytics or to synchronize data across servers that are located in disparate geographical regions.
You can use aP Analytics to create out-of-the-box and ad hoc reports based on the data that aP Admin transfers.
Database Requirements¶
For On-Premise deployments, the Enterprise Platform modules, have different database (also known as database schema) requirements. This table shows which databases are required for On-Premise deployments that use one or more modules. For more information, see the aP Admin and aP Analytics Installation Guide.
| Application | Module (Web Service) |
Required Database (Database Schema) |
|---|---|---|
| aP Admin | Scenario Synchronization | sync |
| aP Admin | VPE Synchronization (for Digital Factory synchronization) |
sync |
| aP Admin | LDAP Synchronization | ldap_sync |
| aP Admin | Quartz scheduler | quartz |
| aP Analytics | Quartz scheduler | quartz |
| aP Analytics | aP Analytics | reporting |
| aP Analytics | JasperReports® Server | jasperserver |
Operating System Requirements¶
The type of operating system that is required for the database server for On-Premise deployments of Enterprise Platform depends on the type of database management system (DBMS) that the deployment uses. This table includes the operating system requirements for the supported.
| DBMS | Operating System Requirement | Notes |
|---|---|---|
| Oracle® | Any server-class OS supported by the database vendor. | aPriori is tested against databases on Windows Server 2012 R2 x64 and 2016 x64, and ships with MySQL 8.0. Server-class OS is required for production environments, and any environment where production-like performance is needed (for example, performance/load testing environments, which should mimic production environments as much as is practicable). Server-class OS is recommended but not required for small deployments and other environments such as development, training, and demo systems. Windows Server tests are performed with Standard Edition, which also validates Datacenter Edition. These Server Editions are not validated: - Standard-Core - Nano When using MySQL on Linux, the MySQL installation must be case insensitive. For information on the supported versions of MySQL, Oracle, and SQL Server, see Enterprise Platform Client and Server Requirements for On-Premise Deployments. |
| Microsoft SQL Server® | Any server-class OS supported by the database vendor. | aPriori is tested against databases on Windows Server 2012 R2 x64 and 2016 x64, and ships with MySQL 8.0. Server-class OS is required for production environments, and any environment where production-like performance is needed (for example, performance/load testing environments, which should mimic production environments as much as is practicable). Server-class OS is recommended but not required for small deployments and other environments such as development, training, and demo systems. Windows Server tests are performed with Standard Edition, which also validates Datacenter Edition. These Server Editions are not validated: - Standard-Core - Nano When using MySQL on Linux, the MySQL installation must be case insensitive. For information on the supported versions of MySQL, Oracle, and SQL Server, see Enterprise Platform Client and Server Requirements for On-Premise Deployments. |
| MySQL | Server-class Windows® or Linux® | aPriori is tested against databases on Windows Server 2012 R2 x64 and 2016 x64, and ships with MySQL 8.0. Server-class OS is required for production environments, and any environment where production-like performance is needed (for example, performance/load testing environments, which should mimic production environments as much as is practicable). Server-class OS is recommended but not required for small deployments and other environments such as development, training, and demo systems. Windows Server tests are performed with Standard Edition, which also validates Datacenter Edition. These Server Editions are not validated: - Standard-Core - Nano When using MySQL on Linux, the MySQL installation must be case insensitive. For information on the supported versions of MySQL, Oracle, and SQL Server, see Enterprise Platform Client and Server Requirements for On-Premise Deployments. |
For information on the supported versions of MySQL, Oracle, and SQL Server, see Enterprise Platform Client and Server Requirements for On-Premise Deployments
RAM and Disk Space Recommendations¶
The amount of RAM that is required for the database server for On-Premise deployments of Enterprise Platform depends primarily on the size of the database and the computational cost of concurrent processes.
The required disk space depends primarily on the number of scenarios. Other factors include:
- The number of users
- The number and size of export sets
- The amount of retained data
aP Admin is required for aP Analytics, but aP Analytics is not required for aP Admin. Therefore, On-Premise deployments that require the data synchronization capabilities of aP Admin, but do not require the reporting capabilities of aP Analytics do not have disk space requirements for the jasperserver and reporting databases (schemas).
For aP Admin Scenario Synchronization, the initial disk space needed to handle a realm, the shared space that scenarios are exported to and then analyzed and synced with their databases in, for the first synchronization is equal to the size of the aPriori operational database. However, the disk space required for subsequent synchronization operations is much less.
For aP Admin Digital Factory (VPE) Synchronization, which does not use of realms, the disk space requirements are even less.
This table includes the RAM, and disk space requirements for the database server for On-Premise deployments of Enterprise Platform for a variety of situations.
| Type | Situation | Situation | Situation | Recommendation | Notes |
|---|---|---|---|---|---|
| RAM | Typical deployments | 8 - 16 GB | Small database may require as few as 6 GB. Large databases may require more memory. For example, 16-32 GB of RAM is recommended for a database that contains more than 200,000 scenarios. These RAM and disk space requirements include only aPriori usage. They do not consider DBA overhead or external factors such as back-up files. Larger RAM and disk space sizes are required when the database is serving multiple applications. The disk space requirements for reporting database sizes assume that all exports are purged on a monthly basis. |
||
| Disk Space | Demo Installation | 5 GB | Small database may require as few as 6 GB. Large databases may require more memory. For example, 16-32 GB of RAM is recommended for a database that contains more than 200,000 scenarios. These RAM and disk space requirements include only aPriori usage. They do not consider DBA overhead or external factors such as back-up files. Larger RAM and disk space sizes are required when the database is serving multiple applications. The disk space requirements for reporting database sizes assume that all exports are purged on a monthly basis. |
||
| Disk Space | Production Installation | aP Admin Initial synchronization |
Small database may require as few as 6 GB. Large databases may require more memory. For example, 16-32 GB of RAM is recommended for a database that contains more than 200,000 scenarios. These RAM and disk space requirements include only aPriori usage. They do not consider DBA overhead or external factors such as back-up files. Larger RAM and disk space sizes are required when the database is serving multiple applications. The disk space requirements for reporting database sizes assume that all exports are purged on a monthly basis. |
100K scenarios | 20 GB |
| Disk Space | Production Installation | aP Admin Initial synchronization |
Small database may require as few as 6 GB. Large databases may require more memory. For example, 16-32 GB of RAM is recommended for a database that contains more than 200,000 scenarios. These RAM and disk space requirements include only aPriori usage. They do not consider DBA overhead or external factors such as back-up files. Larger RAM and disk space sizes are required when the database is serving multiple applications. The disk space requirements for reporting database sizes assume that all exports are purged on a monthly basis. |
300k scenarios | 60 GB |
| Disk Space | Production Installation | aP Admin Initial synchronization |
Small database may require as few as 6 GB. Large databases may require more memory. For example, 16-32 GB of RAM is recommended for a database that contains more than 200,000 scenarios. These RAM and disk space requirements include only aPriori usage. They do not consider DBA overhead or external factors such as back-up files. Larger RAM and disk space sizes are required when the database is serving multiple applications. The disk space requirements for reporting database sizes assume that all exports are purged on a monthly basis. |
500K scenarios | 100 GB |
| Disk Space | Production Installation | aP Admin Initial synchronization |
Small database may require as few as 6 GB. Large databases may require more memory. For example, 16-32 GB of RAM is recommended for a database that contains more than 200,000 scenarios. These RAM and disk space requirements include only aPriori usage. They do not consider DBA overhead or external factors such as back-up files. Larger RAM and disk space sizes are required when the database is serving multiple applications. The disk space requirements for reporting database sizes assume that all exports are purged on a monthly basis. |
1M scenarios | 200 GB |
| Disk Space | Production Installation | aP Admin Subsequent synchronizations |
Small database may require as few as 6 GB. Large databases may require more memory. For example, 16-32 GB of RAM is recommended for a database that contains more than 200,000 scenarios. These RAM and disk space requirements include only aPriori usage. They do not consider DBA overhead or external factors such as back-up files. Larger RAM and disk space sizes are required when the database is serving multiple applications. The disk space requirements for reporting database sizes assume that all exports are purged on a monthly basis. |
100K scenario | 5 GB |
| Disk Space | Production Installation | aP Admin Subsequent synchronizations |
Small database may require as few as 6 GB. Large databases may require more memory. For example, 16-32 GB of RAM is recommended for a database that contains more than 200,000 scenarios. These RAM and disk space requirements include only aPriori usage. They do not consider DBA overhead or external factors such as back-up files. Larger RAM and disk space sizes are required when the database is serving multiple applications. The disk space requirements for reporting database sizes assume that all exports are purged on a monthly basis. |
300k scenarios | 15 GB |
| Disk Space | Production Installation | aP Admin Subsequent synchronizations |
Small database may require as few as 6 GB. Large databases may require more memory. For example, 16-32 GB of RAM is recommended for a database that contains more than 200,000 scenarios. These RAM and disk space requirements include only aPriori usage. They do not consider DBA overhead or external factors such as back-up files. Larger RAM and disk space sizes are required when the database is serving multiple applications. The disk space requirements for reporting database sizes assume that all exports are purged on a monthly basis. |
500K scenarios | 25 GB |
| Disk Space | Production Installation | aP Admin Subsequent synchronizations |
Small database may require as few as 6 GB. Large databases may require more memory. For example, 16-32 GB of RAM is recommended for a database that contains more than 200,000 scenarios. These RAM and disk space requirements include only aPriori usage. They do not consider DBA overhead or external factors such as back-up files. Larger RAM and disk space sizes are required when the database is serving multiple applications. The disk space requirements for reporting database sizes assume that all exports are purged on a monthly basis. |
1M scenarios | 50 GB |
| Disk Space | Production Installation | aP Analytics | Small database may require as few as 6 GB. Large databases may require more memory. For example, 16-32 GB of RAM is recommended for a database that contains more than 200,000 scenarios. These RAM and disk space requirements include only aPriori usage. They do not consider DBA overhead or external factors such as back-up files. Larger RAM and disk space sizes are required when the database is serving multiple applications. The disk space requirements for reporting database sizes assume that all exports are purged on a monthly basis. |
100K scenarios | 40 GB |
| Disk Space | Production Installation | aP Analytics | Small database may require as few as 6 GB. Large databases may require more memory. For example, 16-32 GB of RAM is recommended for a database that contains more than 200,000 scenarios. These RAM and disk space requirements include only aPriori usage. They do not consider DBA overhead or external factors such as back-up files. Larger RAM and disk space sizes are required when the database is serving multiple applications. The disk space requirements for reporting database sizes assume that all exports are purged on a monthly basis. |
300k scenarios | 120 GB |
| Disk Space | Production Installation | aP Analytics | Small database may require as few as 6 GB. Large databases may require more memory. For example, 16-32 GB of RAM is recommended for a database that contains more than 200,000 scenarios. These RAM and disk space requirements include only aPriori usage. They do not consider DBA overhead or external factors such as back-up files. Larger RAM and disk space sizes are required when the database is serving multiple applications. The disk space requirements for reporting database sizes assume that all exports are purged on a monthly basis. |
500K scenarios | 200 GB |
| Disk Space | Production Installation | aP Analytics | Small database may require as few as 6 GB. Large databases may require more memory. For example, 16-32 GB of RAM is recommended for a database that contains more than 200,000 scenarios. These RAM and disk space requirements include only aPriori usage. They do not consider DBA overhead or external factors such as back-up files. Larger RAM and disk space sizes are required when the database is serving multiple applications. The disk space requirements for reporting database sizes assume that all exports are purged on a monthly basis. |
1M scenarios | 400 GB |