Recommended System Specifications (Non-Clustered Environment) Maximo 7.6

Recommended System Specifications (Non-Clustered Environment) – Maximo 7.6

Hardware is the backbone of any Maximo installation. That’s why understanding what the minimum standards for any system are is so important. Without this understanding you could undershoot them and have an incredibly poorly performing system or you could greatly overshoot them and waste resources.  In this post, I have outlined all of the hardware specifications described by IBM required to support a non-clustered Maximo environment. 

The physical memory recommendations in this post are based on the following heap size recommendation by IBM for Maximo 7.6: 

Initial: 6144m / Maximum: 6144m (Recommended)
Initial: 4096m / Maximum: 4096m (Minimum)

APPLICATION SERVER
Platform/hypervisor  Virtualized or Physical Machine
Processor Intel Xeon Processor (Or Similar) 
Memory 12 GB
CPU Count
4
DiskC:\ (Windows) 60GB
E:\ (Installations) 100 GB 
F:\ (Network Drive) – Attached documents will be stored on the file server 
O/S Windows Server 2012 
Windows Server 2012 R2 
Windows Server 2016 
AIX 
Red Hat

Note: Recommend Windows Server 2016
Note: See EXT_Platform_Matrix.xls for specific AIX and Red Hat versions. 

Ram Requirements breakdown:

    WebSphere  
Deployment Manager   
 JVM  
(MXServer) 
HTTP  
Server  
Node  
Agent  
 O/S
 and Misc. 
Memory    1GB     6GB       256MB     512MB     4GB    

For Example:
A non-clustered Maximo environment is running on a single server with the database running on its own server. The calculation based on the above chart is as follows:

Maximo JVM       6 GB heap
WebSphere
Deployment Manager    
 1 GB
HTTP Server    256 MB 
Node Agent   512 MB 
 O/S and Misc   4 GB 
    = 11.75 GB
Please follow and like us:
Posted in:
About the Author

Myles Vivian

Myles Vivian is an application consultant at Ontracks. He mostly spends his days performing large scale data migrations, configuring system infrastructure, writing automation scripts and writing Maximo blog posts. For the past year, he has also been involved with helping members of the IBM team develop their open source project called the maximodev-cli.