Documaker Enterprise Edition Requirements


The following operating system and infrastructure software is needed to run Oracle Documaker Enterprise:

  Operating System/Software Comments


Presentation Tier
Any operating system that supports WebLogic 12c, version 12.2.1.2 This layer hosts the web-based applications. Note: A 64-bit OS and a 64-bit JVM are required. The Web Tier should be enabled to use SSL.
Application Server 1 (logical) Hosts the Document Factory Dashboard and Documaker Administrator web applications, hosts the collection of messaging queues used for Factory processing. Messaging middleware can be either JMS or MQ. Also hosts DWS** for the first Assembly Line deployed, called dmkr_server.
Note: For WLS, the JMS queue server is a dedicated logical Application Server.
Application Server 2 (logical) Hosts the Oracle Service-Oriented Architecture (SOA) Suite 12c (12.2.1.2.0) with BPEL, Oracle Business Rules, OPSS, and UMS enabled, called soa_server. Note: SOA 12.2.1.2.0 does not support non Oracle databases.
Application Server 3 (logical) Hosts Documaker Interactive for Correspondence Use Case, called idm_server.
Note: This server is only needed for deployments using Documaker Interactive. Interactive for Correspondence Use Case.
Application Server 4 (logical) Documaker Interactive for the Contracts Use Case, called con_server.
Note: This server is only needed for deployments using Documaker Interactive Contracts Use case.
An HTTP web server for static content Hosts the WipEdit plug-in and can be used to host Online Help content.
Note: This server is only needed for deployments using Documaker Interactive.
Application Tier Windows 2008 Server or higher (64-bit) Standard Edition, and Oracle Enterprise Linux 7 or higher JVM is required for Document Factory processing This layer runs Documaker Document Factory and Docupresentment services.
Note: Documaker is a 32-bit application and requires 32- bit drivers when running on a 64-bit machine.
Data Tier Any operating system (64-bit) that supports the target database type and client - these database types are supported: Oracle 12c, IBM DB2 LUW version 11.1, or SQL Server 2016 Service pack2. This layer houses the database tables used to store system configuration and processing records. Unicode must be enabled and case sensitivity must be enabled (This is the default).The necessary database connections must be set up.
Archive/Enclosure Content (Optional) Oracle WebCenter Content Core Capabilities 12c (12.2.1.1.0) or higher Oracle WebCenter can be used to store attachments or to archive output from Documaker.

12c no longer supports SQLServer.

Use this formula to determine the number of database connections you need: 500 + (5 x number of users).

Web Server JDBC connection pools should also be adjusted appropriately.

*Formerly known as Universal Content Management (UCM).

**DWS can alternatively be deployed to a web server outside of the other ODEE deployments. In that case, the supported web application servers for DWS expands to include JBOSS and TOMCAT. If you are using Tomcat version 6.0.20 or later, you must also have JAX-WS RI because Tomcat is not a J2EE container and therefore does not provide a JAX-WS RI. Extract the JAXWSRI jar files and place them inside the WEB-INF\lib directory of the Tomcat.

DWS.war file before deployment. You can download the JAX-WS RI from this site: http://jax-ws.java.net/.


The following table lists the certified environment combinations that have been tested by Oracle’s Product Development team for this release version.

OS OS Version Database Web App
Linux Oracle Linux 7 Oracle Database 12c Enterprise Edition (v 12.1.0.2.0) WebLogic Server 12c (v 12.2.1.2.0)
Linux Oracle Linux 7 SQL Server 2016 WebLogic Server 12c (v 12.2.1.2.0)
Windows 2012 Enterprise R2 Oracle Database 12c Enterprise Edition (v 12.1.0.2.0) WebLogic Server 12c (v 12.2.1.2.0)
Windows 2012 Standard R2 SQL Server 2016 WebLogic Server 12c (v 12.2.1.2.0)
Windows 2016 Server Standard Oracle Database 12c Enterprise Edition (v 12.1.0.2.0) WebLogic Server 12c (v 12.2.1.2.0)

Note: For all the above mentioned Operating Systems, Queue and Identity Management types are JMS and OIMLDAP respectively.

Client Requirements

Clients accessing the web-based applications will need:

  • Adobe Acrobat Reader
  • One of these web browsers:
    • Microsoft Internet Explorer version 11 or higher
    • Mozilla Firefox version 52.0 or higher
Note:

The browser running the WIP Edit plug-in must be a 32-bit version and the operating system can be a 32- or 64-bit version. Additionally, the client running the WIP Edit plug-in must also have Java 8 installed.

For more information about WIP Edit plug-in, See KB article 1962423.1

Minimum hardware configuration

The following table outlines the minimum hardware configured used to test the system:

  Windows Linux
Presentation Tier
OS Windows Server 2012 R2, 2016 (64-bit) Oracle Enterprise Linux release 7
CPU # Intel® 2 Cores 2.3GHz x64 Intel® 2 Cores 2.3GHz x64 64-bit machines
Memory # 4 GB RAM 16 GB RAM
Hard disk 150 GB
Application Tier
OS Windows Server 2012 R2, 2016 (64-bit) Oracle Enterprise Linux release 7
CPU Intel® 4 Cores 2.3GHz Intel® 4 Cores 2.3GHz 64-bit machines
Memory* 4 GB RAM 16 GB RAM
Hard disk 150 GB  
Printer HP-compatible printers supporting PCL version 5 or Postscript with 8 MB RAM ***
Data Tier
OS Windows Server 2012 R2 or higher (64-bit) Oracle Enterprise Linux release 7
CPU Intel® 4 Cores 2.3GHz Intel® 4 Cores 2.3GHz 64-bit machines
Memory * 4 GB RAM 16 GB RAM
Hard disk 500 GB ****

Minimum sandbox platform

Here is the minimum hardware you need for a sandbox on each platform:

  Windows Linux
OS Windows Server 2012 R2 x64 Oracle Enterprise Linux release 7
CPU Intel® 2 Cores 2.3GHz x64 Intel® 2 Cores 2.3GHz x64
Memory 16 GB RAM
Hard disk 150 GB
Printer HP-compatible printers supporting PCL version 5 or Postscript
Printer Memory 8 MB RAM