System Requirements
Operating System
Our software requires a Windows Server environment. The following versions are supported:
Windows Server 2019 (or newer)
Ensure that the server is up-to-date with the latest security patches and updates provided by Microsoft to maintain stability and security.
Database Management Systems
Our software is compatible with the following database management systems. Please ensure that your environment meets the requirements for the database of your choice:
Microsoft SQL Server:
MSSQL Server 2019 (or newer)
Oracle Database:
Oracle 19c (or newer)
Hardware Recommendations
Application Server
For the application server, the following minimum and recommended specifications are required for Production environment based on the expected system load:
Minimum requirements:
Processor: 8 cores, 2.4 GHz CPU
Memory: 16 GB RAM
Storage: 80 GB SSD
Recommended for higher loads (1000+ production items/day):
Processor: 8+ cores, 3.2 GHz CPU
Memory: 32 GB RAM
Storage: 80 GB SSD or larger, depending on data volume and log storage.
Database Server
The database server must meet the following requirements for Production environment to ensure smooth data processing:
Minimum requirements:
Processor: 8 cores, 2.4 GHz CPU
Memory: 16 GB RAM
Storage: 50 GB SSD
Recommended for higher loads (1000+ production items/day):
Processor: 8+ cores, 3.2 GHz CPU
Memory: 32 GB RAM
Storage: 50 GB SSD or larger, depending on database growth.
Additionally, the connection between the application and the database server must be properly configured to ensure smooth communication.
Environment Recommendations
It is recommended to maintain at least three distinct environments. Each environment serves a specific purpose in the software lifecycle, ensuring smooth operations, testing, and troubleshooting.
1. Production Environment (PROD)
The production environment is the live system where all real-time operations and business-critical processes occur. This environment must have the highest level of security, stability, and performance, as it is the main platform used by end users.
2. Test Environment (TEST)
The test environment should be a 1:1 clone of the production environment. It is crucial to maintain identical configurations between PROD and TEST to accurately reproduce and simulate any bugs or issues that occur in the live system. This allows for precise diagnostics and validation of bug fixes before deploying them to production. For this reason, it is also recommended to have the capability for a quick database dump from the production environment into the test environment to ensure data consistency when addressing live system issues.
The TEST environment generally does not require the same hardware capacity as PROD but should be configured similarly enough to accurately reflect production conditions, especially when performing stress or performance tests.
3. Development Environment (DEV)
The development environment (DEV) is used for feature development, configuration changes, and early-stage testing. Unlike TEST, the DEV environment can be less resource-intensive and does not need to mirror the production setup in detail.
The DEV environment can even be hosted on the same server as the TEST environment, as its operations typically do not create a significant load on the server.
Backup and Maintenance Responsibilities for On-Premise Installations
For on-premise installations, the following responsibilities fall on the customer's internal IT team:
Database Backup Strategy: It is the customer’s responsibility to implement and maintain a robust database backup plan to prevent data loss.
Server Maintenance: The local IT team must manage the regular maintenance of servers, including applying software updates, managing security patches, and ensuring system health.
Productoo does not assume any responsibility for the state, maintenance, or performance of local infrastructure in an on-premise environment. Our support is limited to ensuring the functionality of the installed application and the SID database used by the software.
Remote Support and Access Requirements
For any support requests or troubleshooting that requires direct intervention from Productoo, the customer must provide:
Remote Access to the relevant servers via a secure VPN connection.
RDP (Remote Desktop Protocol) access to the servers where the application is hosted.
A user account with administrator privileges to ensure we have the necessary permissions to investigate, diagnose, and resolve issues effectively.
Without this access, we may not be able to provide full technical support or resolve critical issues in a timely manner.
Cloud vs. On-Premise Installations
On-Premise Installations
For customers choosing an on-premise installation, the following responsibilities remain fully managed by the customer's IT department:
Server Infrastructure Management: This includes ensuring server availability, hardware maintenance, and monitoring for any potential hardware failures.
Database Management: The customer’s IT team is responsible for performing regular database checks, backups, and maintaining data integrity.
Security Management: All firewall settings, security protocols, and access controls for both the server and the database are handled internally by the customer’s IT.
Cloud Installations
If the customer chooses to deploy via the Productoo Cloud Solution, the following services are handled by Productoo:
Infrastructure Management: Productoo manages all aspects of server maintenance, uptime, and performance monitoring.
Database Maintenance: This includes performing backups, ensuring data integrity, and applying necessary updates.
Security and Access: Productoo implements security protocols, controls access, and ensures the system is secure.
By choosing the cloud option, customers can focus on using the software and managing their data without the burden of maintaining the infrastructure or dealing with hardware issues.