System Requirements

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.

Operating System:

  • 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.)

Runtime Memory:

  • 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

Disk Space:

  • 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)

Application Stack:

  • 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.

Adobe Content Server

  1. Adobe Content Server
  2. Release Notes
  3. System Requirements
  4. Upgrading ACS from 4.0 to 4.1 or 4.2, and to 5.0, 6.0, and 6.5
  5. Adobe Content Server: General
  6. ACS and eCommerce Stores
  7. Updating ACS to work with the MD5 algorithm after Oracle April 2017 patches 7u141 and 8u131
  8. Activations in Adobe RMSDK and Adobe Digital Editions
  9. Adobe Vendor ID specifications
  10. Vendor ID Workflow
  11. Changing the fulfillment URL in ACS
  12. Developing and Using Packaging Tools in ACS
  13. Adding Digital Rights Management (DRM) permission tags to eBooks when packaging them
  14. How does passhash work in Adobe Content Server and RMSDK reader applications?
  15. Join Account Workflow and Multiple Activations
  16. Opening NOOK books in Adobe Digital Editions
  17. PDF Compatibility, Adobe Digital Editions and Adobe Content Server
  18. Removing the Adobe Digital Edition authorization when it fails (erase authorization)
  19. Replacing an Existing Book in ACS
  20. Setting up ACS with Microsoft SQL Server Database
  21. Setting up Books for Loan in ACS
  22. Working with EPUBVER
  23. Working with Readium
  24. Adobe Content Server: Errors and Error Messages
  25. Admin Console Login Error
  26. Admin Console in ACS not handling large numbers of books
  27. Could not load database driver, ACS Status check 404/500 error
  28. E_ACT_SCHOOL_MODEL_INCOMPATIBLE_SOFT error, incorrect version of ADE
  29. E_ADEPT_CORE_LOAN_SIGNATURE error from Adobe Content Server
  32. E_ADEPT_DOCUMENT_TYPE_UNKNOWN error from ADE or other readers
  33. E_ADEPT_IO error from Adobe E-Book Reader Applications
  34. E_ADEPT_MISSING_ELEMENT from Adobe Content Server
  35. E_ADEPT_NO_TOKEN error Getting License: License Server Communication Problem:
  36. E_ADEPT_REQUEST_EXPIRED: Ebook download error from ADE or other e-readers
  38. E_ADEPT_UNKNOWN and Out of Memory error from ACS packaging
  40. E_LIC_CONNECTION_PROBLEM or Adobe Signing Server returns No Running error
  41. E_LIC_LICENSE_SIGN_ERROR from Adobe Content Server
  42. E_LIC_WRONG_OPERATOR_KEY Error from Adobe Content Server
  43. E_PACK_DATABASE Error from Adobe Content Server packaging
  44. E_PACK_DUPLICATE_SRC Packaging Error
  45. E_PACK_ERROR "MALFORMED" or "NullPointerException"
  46. E_PACK_ERROR null error from packaging books in ACS
  47. E_PACK_INCORRECT_FORMAT error from packaging
  48. E_URLLINK_AUTH error from ACS download link
  51. EPUB file failed to package - Error about incorrect language field
  52. Foreign Key Constraint Error when trying to delete resources in ACS
  53. Fulfillment status check 500 error - P12 BadPaddingException: Given final block not properly padded
  54. Fulfillment status check returns HTTP error code -500 or 404
  55. GBLINK_AUTH_SIGNATURE_NOMATCH error with ACS GBLink sent through email
  56. IO Error on Network Request? Error #2038
  57. Java Memory Error, Packaging Large Files
  58. Login Error: Change or Reset Admin Console Password
  59. MySQL error in your SQL syntax, check manual for “????”
  60. Packaging error, E_PACK_FILE_READ Permission Denied
  61. Print or copy permission shows zero pages in ADE on second device or computer
  62. Required Property Missing, ACS Status Check returns 404 error
  63. Unexpected end of ZLIB input stream
  65. XMLSigningSerializer.php generates incorrect <hmac> code in ACS
  66. E_ADEPT_UNKNOWN and JsafeJCE provider self-integrity check failed

Feedback and Knowledge Base