Child pages
  • WebCenter 16 Server System Requirements
Skip to end of metadata
Go to start of metadata

The following are the minimum system requirements for WebCenter 16. Exceeding these requirements will in most cases lead to a performance increase. Running WebCenter on a system that does not meet these requirements is not supported.

About the WebCenter Server System Requirements

WebCenter employs three distinct servers, a Web Server, an Application Server and a Database Server. It also has a FileStore and an On-Board Graphics Engine (OBGE), which is used to generate view data.

Entry Level (two servers)

WebCenter Entry Level requirements are based on activity with 10 concurrent users active at any time and less than 100 users in the system, but works well up to 30 concurrent users for most installations (results may vary depending on application usage and could result in requiring the Advanced Level Setup). In the Entry Level setup, the installation of the Application Server and Database Server is combined onto a single machine. The OBGE and the FileStore are on the Application Server. For security reasons, the Web Server is always on its own dedicated server and placed in a demilitarized zone (DMZ). We recommend the use of hardware firewalls for creating the DMZ.

Advanced Level (three or more servers)

When the WebCenter Entry Level cannot meet the load requirements of the system, it is possible to scale the system. For security reasons, the Web Server will always be a separate server in a DMZ. Each of the other WebCenter components (Application Server, Database Server, FileStore and OBGE) can be offloaded onto separate machines in different combinations. For Advanced Level installations, it is recommended to choose the Advanced Installer option to allow more custom configuration, and to choose Extra Large for the Deployment Size.

Minimum System Requirements for WebCenter 16

CategoryServer

Entry Level (Standard: < 100 users)

Advanced Level (Extra Large: 100+ users)

Advanced Scaling Options

DisplayAll1024 x 768 pixels, 16-bit color 
Media DrivesAllDVD-ROM or connection to networked DVD-ROM drive 
NetworkAll10/100/1000 Base-T Ethernet, TCP/IP v4 protocol. 
Processor TypeAll

x86-64 compatible processor (Intel® or AMD®)

 

CPU (Number of Cores)

Only SMP multicore is supported. Running on NUMA systems can lead to unpredictable performance.

Application Server with OBGE8126 + 6 per 100 users
Separate Database Server482 + 6 per 100 users
Web Server462 + 4 per 100 users
All other servers

4

6

2 + 4 per 100 users

RAM Memory


Application Server12 GB18 GB18 GB
Application Server with OBGE12 GB24 GB24 GB
Application Server with DB and OBGE12 GB32 GBNot Supported
Separate Database Server12 GB

12 GB or size of the DB (whichever is larger)

add  8 GB per 100 users
Web Server6 GB12 GB12 GB
Hard Disk Space (Free Space, so excl. OS,...)


All

An NTFS volume is required. A backup solution is strongly advised.

 
Application Server20 GB60 GB 
Web Server20 GB60 GB 
Database Server40 GB80 GB 
FileStore100 GB, should be expandable as data storage grows with usage 
Database SoftwareDatabase Server
  • MS SQL Server 2008: Workgroup, Standard and Enterprise Edition
  • MS SQL Server 2008 R2/2012: Express, Workgroup, Standard and Enterprise Edition
  • Oracle® 10g or 11g Enterprise Edition
  • MS SQL Server 2008/2008 R2/2012: Workgroup, Standard and Enterprise Edition
  • Oracle® 10g or 11g Enterprise Edition
 

For more information about memory limitations in Windows operating systems, please consult this table.

Supported Operating Systems

Recommended operating systems are highlighted in green in the tables below.

If an operating system is not listed here, it is not supported. Do not try to install WebCenter Server on a computer running an unsupported operating system.

Windows Server 2012 R2

Edition64-bit
Windows Server 2012 R2 Standard(tick)
Windows Server 2012 R2 Datacenter(tick)
Windows Server 2012 R2 Essentials(tick)
Windows Server 2012 R2 Foundation(error)

Windows Server 2012

Edition64-bit
Windows Server 2012 Standard(tick)
Windows Server 2012 Datacenter(tick)
Windows Server 2012 Essentials(tick)
Windows Server 2012 Foundation(error)

Windows Server 2008 R2

Edition64-bit 
  SP1
Windows Server 2008 R2 Standard(tick)(tick)
Windows Server 2008 R2 Enterprise(tick)(tick)
Windows Server 2008 R2 Datacenter(tick)(tick)
Windows Server 2008 R2 Foundation(error)(error)
Windows Web Server 2008 R2(tick)(tick)
Windows Server 2008 R2 HPC Edition(error)(error)

Unsupported Operating Systems

  • Window Server 2008 (all editions)
  • Windows Server 2003 (all editions)
  • Windows 2000 (all editions)
  • Windows Vista (all editions)
  • Windows XP (all editions)
  • Windows 7 (all editions)
  • Windows 8 (all editions)

Virtualization Platforms

VMware® is supported. We have had bad experiences with HyperV in the past, hence it is not recommended. Xen is still to be tested.

Scaling Recommended System Requirements

WebCenter can be scaled up to 300 concurrent users in single installation. These limits are set based on our flied experience and internal lab test. This limit will be changed to higher numbers as in when we learn more.

In general, high speed hard drives (both throughput and seek time; e.g.: SSD) will work beneficial, but are not a requirement. Write speed should not be traded off for read performance as both are of importance to the application. Try to avoid large seek times (e.g.: due to NAS/SAN), also for the FileStore, as this will make performance degrade quickly.

For the Database Server, in general, the higher read and write speed are and the lower seek time is, the better everything will work. For very large installations, having the transaction log, temporary DB and actual DB each siting on an individual SSD can be considered.

For the OBGE, It is possible to run multiple preview generation process in parallel if that is enabled in your configuration.

Port Configurations

Below you can find the ports which need to be open/available for proper functioning of WebCenter:

  • Port 80 (HTTP) from the internet to the WebCenter Web Server (DMZ).
  • Port 443 (HTTPS) from the internet to the WebCenter Web Server (DMZ).
  • Port 80 (HTTP) from the LAN to the WebCenter Web Server (DMZ).
  • Port 443 (HTTPS) from the LAN to the WebCenter Web Server (DMZ).
  • Port 1099 (JBOSS Naming Service) from the WebCenter Web Server (DMZ) to the WebCenter Application Server (LAN).
  • Port 2500 (JBOSS Naming Service RMI) from the WebCenter Web Server (DMZ) to the WebCenter Application Server (LAN).
  • Port 4444 (RMI/JRMP invoker object) from the WebCenter Web Server (DMZ) to the WebCenter Application Server (LAN).
  • Port 3873 (EJB3) from the WebCenter Web Server (DMZ) to the WebCenter Application Server (LAN).
  • Port 25 (SMTP) from the WebCenter Application Server (LAN) to the Mail Server.

Optional:

  • Port 11099, 12500 and 14444 between the Application and Web Server in case of External View Service.

Finally, JBoss needs the following ports on the Application Server. These ports are only accessed from the Application Server (so calling itself) and do not need to be configured on the firewalls. However, if any of these ports are taken by another application, JBoss will fail using them which can expose problems from failing to start or failing to execute certain functions. Ports: 8083, 8086, 4446, 3528, 1161, 1162, 1090, 1091.

Automation Engine calls on port 5445 of the Application Server to get approval feedback in case both are in the same LAN.

Server Name Resolution

Configuring WebCenter with IP addresses no longer works (since WebCenter 12.x). In case the WebCenter web server is not able to find the application server via DNS, Active Directory or other name resolution systems, configuring WebCenter during the installation with the IP addresses of the servers won’t solve the issue anymore as this only rewrites the jndi.properties file on the web server.

The application server communicates with the web server on how to find the application server, sends back its own host name over JNDI as connection information. The web server will fail if it is not able to resolve the application server hostname.

In the cases where the web server is not able to find the application server via name resolution, we need to resolve the hostname of the application server by adding a mapping between the IP address of the application server and the hostname of the application server in the hosts file located under C:\Windows\System32\drivers\etc\hosts. Example: 10.31.140.69 myappserver

System Requirements
Applies to

WebCenter Server

Version16
Last revised 06-Jun-2016

Useful Links

Software downloads: mysoftware.esko.com

Software installation and user doc: https://www.esko.com/en/support

Contents