According to Adobe Content Server User Manual, the system requirements are quite generic. The following requirements were established when ACS 4 was first released. ACS 5 and above requires Java version 1.7 or above. It is noted in the Java section below. In parenthesis, we will note anything about the newer versions that we have either tested or know that some of our customers have used.
- Linux: Ubuntu 8.04 (Newer version should work; Redhat is widely used and other flavors of Linux are not formally supported but can work as well. Ubuntu 14.04 and 15.04 are confirmed to work with ACS 6 and 6.5.)
- Windows Server 2003 (Windows 2008 and 2012 are confirmed to work with ACS 4, 5, 6 and 6.5)
- Processor: 32- or 64-bit (Make sure that software components use the same version, especially, Java and Tomcat. All software packages should run either 32 or 64 bit. Don't mix and match versions.)
- Services typically need 1GB to run (recommend at least 4GB to accommodate packaging and larger volume of transactions)
- Java needs to be allocated a heap of at least 1GB - more if packaging larger documents
- Services and Assets: less than 50MB (more on this later)
- Transaction logging: approximately 2KB per fulfillment
- MySQL (version 5 and higher)
- Microsoft SQL Server 2005 (or higher)
- Oracle 10 (or higher)
- (all need appropriate JDBC connectors)
- Java 1.7 or above (ACS 4 works with Java 1.5 and above, however it is a good practice to use at least 1.6 version. ACS 5 and above minimally requires 1.7)
- Servlet engine (Tomcat 6 or higher, Tomcat 5.5 is not sufficient)
- Apache PHP server version 2.2 or higher (required to run sample bookstore, not needed for running the content server)
- PHP 5 (required to run sample bookstore, not needed for running the content server)
- ACS does not need to run with SSL certificate. User and licensing information are encrypted or signed with secure keys.
Additional notes on the system requirements:
Even though ACS can run on a minimal setup, we advise customers to configure with more memory and hard drive space.
The hard drive space for storing ebook media (files) varies based on the number of books and their sizes. Packaged books add some overhead but usually about 10% or less in our experience. Text based EPUB files (such as novels) are usually less than a few MB. Specialty EPUB books, such as children's illustration books with pictures or medical books with images, can reach upwards to 100-200 MB. PDF files with images and illustrations can vary a great deal, anywhere from 10MB to100MB;10MB is probably more common but textbooks with illustration done in vector graphics can reach 100MB. If you don't have any dataset to estimate the storage, you can use these data to estimate your storage need. The important thing to note is that this is easily scalable so you can start with a reasonable system and expand as your business expands.
A production system should maintain high availability with some kind of failover mechanism. Since ACS consists of a set of commonly deployed technologies, industry and application specific guidelines can be followed to handle the failure that may arise from hardware, application, database, and file servers.
A couple of commonly used failover mechanisms include setting up one primary production server and a separate standby server or setting up a load balanced system. Either way you go, database and file servers need to be backed up periodically (very frequent in the case of the database backup). In the case of using a primary and a standby system, you may need to make a DNS switch to route the traffic to the backup server should the primary server fails.
The following lists some of the requirements on the client application side:
For each book, the client side stores one object per book that includes the decryption key, license token, and the unique identifier. This runs about 1KB in size. The client stores the encrypted books as well. Storage for books will vary based on the encrypted book size.
The client application is responsible for communicating with Adobe signing server which requires SSL client. There is nothing to be done on the ACS server side. The client application is built with SSL client libraries. Each fulfillment requires around 3KB of traffic bandwidth to communicate with the Adobe signing server and the ACS server. The book download bandwidth itself is separate and varies based on the size.