...
| Minimum | Recommended |
CPU | 2 core (4 Thread) 2,4 GHz | 6 core (12 Thread) 2,6+ GHz |
RAM | 8 GB | 12/16 GB |
Storage | 1 TB* * dependent on the storage needs of the Customer | 1 TB* * dependent on the storage needs of the Customer |
Operating System | CentOS 7 Linux | CentOS 7 Linux |
Network | Gigabit | Gigabit |
Software | Apache Tomcat 8.0.28 | Apache Tomcat 8.0.28 |
MariaDB 5.5.4.4 | MariaDB 5.5.4.4 | |
Java JDK 1.8.0 | Java JDK 1.8.0 | |
ImageMagick 6.7 | ImageMagick 6.7 | |
Ghostscript 9 | Ghostscript 9 |
As regards the client component, plugin Peppers for InDesign currently in production is The InDesign plugin of Peppers is fully compatible with Adobe InDesign CS 5.5 and higher.
The new plugin (1.7.4) is compatible to today exclusively with Adobe InDesign CC2015, it is planned to extend the compatibility with Adobe InDesign CC2014.
The plugin Peppers communicates with the server by opening a socket on TCP port 11898 (value configurable anyway).
In addition to this, of course, we must consider the TCP port 8080 for the direct exposure of Tomcat, or TCP port 80 if you want to configure a reverse proxy extension using Apache2.
CC2015.
The communication between the clients with the InDesign plugin and the server module, is based on a TCP socket connection on a pre-configured port. By default, the port is 11898.
In addition, connections to the port 8080 shall be allowed for the direct exposition of Tomcat. Otherwise, TCP port 80 can be used in case the Customer wants to configure an internal reverse proxy through Apache2.
One more requirement regarding the automatic images processing using the Peppers InDesign plugin, is that the client machines must have the Adobe Bridge CC2015 software installed.
...