Note

This document is intended for NIVOMAX license holders, such as ePub suppliers, and not for end-user organizations.

When setting up or maintaining the hosting infrastructure for NIVOMAX, follow these guidelines to ensure proper configuration, optimal performance, and security. This document provides IT professionals with best practices and requirements for hosting and managing the NIVOMAX server-side application. It is tailored for organizations with large data libraries and up to 1,000 concurrent users, ensuring operational scalability and compliance.

Hosting Requirements

Hosting Infrastructure Options

• On-Premise Hosting: Requires a dedicated physical or virtual server environment within the ePub supplier’s network.
• Cloud Hosting: Compatible with all major cloud providers (e.g., AWS, Azure, Google Cloud). Ensure compliance with hosting policies and security requirements.

Minimum System Requirements

Servers

• Primary Hosts: Quad-core processor or higher, 16 GB RAM (32 GB recommended for large deployments), SSD storage with a minimum capacity of 250 GB local storage.
• Backup Hosts: Similar to primary hosts with replication capabilities.
• Disaster Recovery Hosts: Geographically distant with equivalent specifications as primary hosts.

High-Performance Network Storage

• • Use SSD-based storage solutions (e.g., NAS or SAN) for fast access to data libraries and pre-production data for Builder.

Network Requirements

• • Stable broadband connection with at least 1 Gbps bandwidth for data transfer and user access.

Operating System

• Windows Server 2016 or later.
• Linux: CentOS 8, RHEL 8, or later (64-bit) recommended.

Database Options

• Oracle Database 19c or higher.
• Microsoft SQL Server 2019 or higher.
• PostgreSQL 13 or higher.

High Availability (HA) and Disaster Recovery (DR) Configuration

To ensure uninterrupted operation and data protection, implement the following architecture:

Primary Server Configuration

• 32 CPUs, 128 GB RAM, SSD storage (1 TB).
• Supports core applications with active database node and load balancing.

Backup Server Configuration

• Identical specifications as the primary server.
• Configured as a passive standby with database replication and automatic failover.

Disaster Recovery Site

• Geographically distant from the primary site.
• Includes replicated storage for critical datasets using snapshot-based backups.
• Recovery Time Objective (RTO): Less than 4 hours.
• Recovery Point Objective (RPO): Less than 15 minutes.

Load Balancer

• Distributes traffic between active and passive nodes.
• Ensures minimal downtime during failover or server maintenance.

Monitoring and Security

• Use monitoring tools to track resource utilization, application health, and replication status.
• Implement robust security protocols, including encryption (AES-256) and secure access controls.

Application Stack and Configuration Guidelines

Application Stack

The NIVOMAX platform requires a robust application stack to ensure optimal performance and scalability. Below are the recommended components:

Core Components

• Web Server: HTTPD Server.
• Application Server: Java-based application server Apache Tomcat (v10.1.34 or higher).
• Runtime Environment: Node.js (v20).
• Java Development Kit: JDK 17.0.12+.

Database Layer

• Oracle Database 19c or higher (recommended for high-transaction environments).
• Microsoft SQL Server 2019 or higher.
• PostgreSQL 13 or higher.

Deployment Tools

• Continuous Integration/Continuous Deployment (CI/CD): Jenkins or GitLab CI for automating build and deployment processes.
• Configuration Management: Ansible, Puppet, or Chef for consistent deployment and configuration management.

Monitoring and Logging

• Monitoring Tools: Prometheus, Grafana, or AWS CloudWatch for real-time system health checks.

Maintenance Best Practices

System Updates

• Regularly update the operating system to supported versions.
• Install the latest NIVOMAX application updates as released.
• Ensure database management systems are updated to the latest stable versions.

Performance Optimization

• Monitor server resource utilization (CPU, memory, and disk I/O).
• Scale resources dynamically based on concurrent user demand.
• Maintain a minimum of 20% free storage space on all systems.

Security

• Configure antivirus and firewall policies to allow NIVOMAX traffic.
• Regularly review user access permissions to ensure compliance.
• Enable logging and monitoring for suspicious activity.
• Implement role-based access controls (RBAC) for user and administrator permissions.

Support Channels

To receive support for on-premise NIVOMAX Platform installations, customers must hold a valid SLA and access credentials to the Synaxiom Support Ticket System and open a request there.

For questions or additional assistance, please contact your account representative or the NIVOMAX support team. Keeping systems compliant with these guidelines will ensure reliable operation and a seamless user experience.