Recommended System Specifications (Clustered Environment) Maximo 7.6

Recommended System Specifications (Clustered Environment) – Maximo 7.6

Deciding on the correct hardware for a clustered Maximo environment can be a challenging task. Not all servers in a clustered environment serve the same function, nor are they subject to the same hardware load. This often creates some confusion, as hardware choice is server-type specific. Additionally, finding these specifications can sometimes be a bit of a challenge.

In this post, I have outlined all of the hardware specifications described by IBM required to support a clustered Maximo environment.

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

APPLICATION SERVER
Platform/hypervisor  Virtualized or Physical Machine
Processor Intel Xeon Processor (Or Similar) 
Memory See below for memory calculation 
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

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

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  
(Cron,  MIF, UI)  
 JVM  
 (RMI)   
HTTP  
Server  
Node  
Agent  
 O/S
 and Misc. 
Memory    1GB     6GB     512MB     256MB     512MB     4GB    

For Example:
An application server is running an O/S, 2 UI JVMs and 1 Node Agent. The calculation based on the above chart breaks down as follows:

Maximo JVM x 2      6 GB x 2
O/S and Misc4 GB
Node Agent512 MB
    = 16.5 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.