Maximo Open Forum

 View Only

 What are the risks of running Maximo on Windows and DB2 on RHEL

  • Maximo Application Suite
Rockesh Rock's profile image
Rockesh Rock posted 08-30-2024 01:42

Hi Team,

We are working on Maximo migration project. We have below mentioned combinations to choose, please let us know what is the best combination to go for this migration?

Client is requesting for Combination#2, please let us know if this combination works? We are worried if running application and database across different Operating Systems (OS) could cause unknow issues. We are finding it difficult to decide on this.

Please let us know what is the best combination to go with... and what are the pros and cons of it... thanks!!

Combination#1:

Maximo (on Linux)      ----> DB2 (on Linux)

Combination#2:

Maximo (on Windows)      ----> DB2 (on Linux)

Combination#3:

Maximo (on Windows)      ----> DB2 (on Windows)

Thanks,

Rockesh

Jason VenHuizen's profile image
Jason VenHuizen posted 09-03-2024 11:05

Hi Rockesh,

If you are running Maximo 7.6.1.x then there really isn't any risks for any of the scenarios you have laid out.  If you are running MAS then there is no option to run Maximo on Windows since it deploys to OpenShift and OpenShift is either deployed to RHEL or more commonly with RCOS where OpenShift owns and manages the underlying RCOS image.

There is then a Pack available to run DB2 on OpenShift as well, although there is no issue with running your database outside the OpenShift instance if that is what you want to do.

Regards,

Jason

Viet Tran's profile image
Viet Tran posted 09-04-2024 19:19

I agree with Jason's comment above. There is no risk with running Maximo cross platform. I would recommend option 3 if there are no other factors involved. However, say if the IT department already has many applications and databases running on Linux, it makes more sense to keep everything in one OS platform. It keeps IT operations more standardized and simpler to manage.

However, I question the choice of DB2 database. Over the years, I have seen many projects that involve migrating Maximo from DB2 to SQL or Oracle. I haven't seen any project that goes in the other direction. 

While you can save some licensing cost with DB2, you should also consider the hidden cost of not being able to find people with adequate DB2 skill and the lack of skill causes lower quality/productivity of on-going support work.

Related Content