This section provides information on the web application server requirements.
Table 22. CMIS — Web Application Server Requirements for Windows
Operating System/Processor
Web Application Server
Windows Server 2008 R2 SP1 x64 Edition/x64 [2]
Windows Server 2012 x64 Edition/x64 [2]
Windows Server 2012 R2 x64 Edition/x64 [2]
Apache Tomcat
Content Management Interoperability Services System Requirements
Operating System/Processor
Web Application Server
Windows Server 2008 R2 SP1 x64 Edition/x64 [2]
Windows Server 2012 x64 Edition/x64 [2]
Windows Server 2012 R2 x64 Edition/x64 [2]
Oracle WebLogic Server 12c (12.1.2, 12.1.3)
Y Y Y
[1] With vFabric tc Server 2.9.x, you must use Tomcat 7.0.x. Other Tomcat versions might not work correctly.
[2] Support 64-bit version of the operating system in native mode.
Back to TableNavigator
Table 23. CMIS — Web Application Server Requirements for Red Hat Enterprise Linux Operating System/Processor
Web Application Server
Red Hat Enterprise Linux 6.x x64 Edition/x64 [2]
Red Hat Enterprise Linux 7.x x64 Edition/x64 [2]
Apache Tomcat 7.0.56, 8.0.14 Y Y
Pivotal vFabric tcServer
3.1.x Y Y
VMware vFabric tc Server
2.9.x [1] Y Y
IBM WebSphere (8.5.5.x)
and (8.5.0.x) Y Y
Oracle WebLogic Server 12c
(12.1.2, 12.1.3) Y Y
[1] With vFabric tc Server 2.9.x, you must use Tomcat 7.0.x. Other Tomcat versions might not work correctly.
[2] Support 64-bit version of the operating system in native mode.
Back to TableNavigator
Table 24. CMIS — Web Application Server Requirements for SUSE Enterprise Linux
Operating System/Processor Web Application Server SUSE Enterprise Linux 12/x64 [2]
Apache Tomcat 7.0.56, 8.0.14 Y
Pivotal vFabric tcServer 3.1.x Y
VMware vFabric tc Server 2.9.x [1] Y
IBM WebSphere (8.5.5.x) and (8.5.0.x) [4] Y
Oracle WebLogic Server 12c (12.1.2, 12.1.3) Y
Content Management Interoperability Services System Requirements
Operating System/Processor Web Application Server SUSE Enterprise Linux 12/x64 [2]
Red Hat JBoss EAP 6.3.x [5] Y
[1] With vFabric tc Server 2.9.x, you must use Tomcat 7.0.x. Other Tomcat versions might not work correctly.
[2] Support 64-bit version of the operating system in native mode.
[3] Multi-domain Kerberos is not supported on IBM WebSphere Application Server due to known exception from IBM.
[4] Multi-domain Kerberos is not supported on Red Hat JBoss EAP 6.3.x.
Table 25. CMIS — Web Application Server Requirements for IBM AIX
Operating System/Processor Web Application Server AIX 7.1 TL3/Power
IBM WebSphere (8.5.5.x) and (8.5.0.x) Y
Back to TableNavigator
Table 26. CMIS — Web Application Server Requirements for Oracle Solaris
Operating System/Processor Web Application Server Oracle Solaris 11/SPARC
Apache Tomcat 7.0.56, 8.0.14 Y
Pivotal vFabric tcServer 3.1.x Y
VMware vFabric tcServer 2.9.x [1] Y
IBM WebSphere (8.5.5.x) and (8.5.0.x) Y
Oracle WebLogic Server 12c (12.1.2, 12.1.3) Y
[1] With vFabric tc Server 2.9.x, you must use Tomcat 7.0.x. Other Tomcat versions might not work correctly.
Back to TableNavigator
EMC Product Requirements
This section lists the Documentum products that are depended on in order to achieve a basic level of functionality and lists the related Documentum products that enhance the overall functionality.
One of each of the following product versions listed for each product is/are prerequisites.
Table 27. CMIS — EMC Product Requirements
Content Management Interoperability Services System Requirements
Product Compatible Releases
Documentum Foundation Classes 6.7 SP2, 7.0, 7.1, 7.2
Back to TableNavigator
Product Notes
This section lists all the product-specific notes that may apply to the requirements information for Content Management Interoperability Services. TheAppendix B, General Notessection lists notes that apply to all products.
The following are the product notes:
• x64 refer to the 64-bit architecture, which includes AMD64 and Intel 64.
• For CMIS running in a web application server environment, all Java 6.0.x and 7.0.x versions that are supported by each web application server configuration listed in theJava Version Support, page 109table are supported. No support for Java 1.5.x.
• Supports 64-bit version of web application server.
• Supports only 64-bit version of JDK.
• Web servers internal to the supported web application servers are supported.
• Only the following forward proxy configurations are supported
— Auto configuration script
— Explicitly specifying the proxy server (for example, the host and port)
— Auto detect settings, configured using ProxyCfg.exe (proxy configuration tool)
• Red Hat Enterprise Linux 6.5 and Red Hat Enterprise Linux 7.0 were tested for this release.
Content Management Interoperability Services System Requirements
Chapter 6 Content Server System Requirements
This chapter describes the environment and system requirements for the Content Server (CS) release.
The system requirements are categorized as follows:
• Hardware Requirements, page 43
• Database Requirements, page 44
• Additional Third-party Supported Applications, page 45
• Product Notes, page 46
Hardware Requirements
This section provides information on the hardware requirements.
Table 28. CS — Hardware Requirements
Item Requirement
Memory [1] [3] [4] • 8 GB RAM on Windows, Red Hat Enterprise Linux, and AIX systems
• 12 GB RAM on Solaris systems
Disk space [2] 40 GB
[1] The amount of RAM that is available after taking into consideration all other RAM utilization requirements. We recommend that you run the xPlore and Content Server on separate host machines.
[2] If you are installing Content Server on a UNIX or Red Hat Enterprise Linux system, 2 GB of space are required in the /var/tmp directory. If you use a temp directory that shares the same disk partition as the installation destination, you must add an additional 2 GB to the disk requirement for the installation destination.
[3] On a Red Hat Enterprise Linux host, 4 MB minimum shared memory allocated and semaphores must be enabled.
[4] The amount of memory required depends on a variety of factors such as the number of docbasic methods being run, the number of docbasic method server worker threads, the number of Java methods, JBoss, and so on. Insufficient memory in the system might generate errors such as
Content Server System Requirements
Item Requirement
java.lang.OutOfMemoryError. In such situations, calculate and fine-tune the memory parameters in the $DM_HOME/bin/java.ini and/or increase system’s physical memory.
Back to TableNavigator