IBM Maximo Application Suite migration and modernization with Azure Red Hat OpenShift
Published Apr 25 2024 03:39 PM 1,589 Views
Microsoft

IBM Maximo has been a leading enterprise asset management solution in the industry for four decades, helping customers streamline work processes with a centralized platform for managing tasks, inventory, regulatory compliance and reporting capabilities. IBM Maximo Application Suite (MAS), the next generation of IBM Maximo, delivers a better user experience, faster integration, robust AI analytics, and a broad range of cloud deployment options. MAS provides organizations with a robust and modern asset management solution.

 

Red Hat OpenShift, the industry’s leading hybrid cloud application platform powered by Kubernetes, brings together tested and trusted services to reduce the friction of developing, modernizing, deploying, running and managing applications. OpenShift delivers a consistent experience across public cloud, on premises, hybrid cloud or edge architecture.

 

Microsoft Azure Red Hat OpenShift (ARO) provides highly available, fully managed OpenShift clusters on demand, monitored and operated jointly by Microsoft and Red Hat. OpenShift brings added-value features to complement Kubernetes, making it a turnkey container PaaS with a significantly improved developer and operator experience.

 

Maximo customers will be required to move to MAS when Maximo 7.x reaches end of life. MAS has been containerized to run specifically on Red Hat OpenShift. To ease this transition for customers who are unfamiliar with running containers in production, IBM, Microsoft and Red Hat have teamed up to provide a validated architecture for running MAS on Azure Red Hat OpenShift.

 

This blog will walk through the recommended options for running MAS on Azure and describe how the IBM, Red Hat and Microsoft Azure components come together and provide a solid foundation for running MAS. We will also explore the architectural decisions to consider, so you can choose the one that best fits your organization’s needs.

 

For each option below, there are two components to keep in mind: the MAS application and the platform MAS runs on (Red Hat OpenShift or Microsoft Azure Red Hat OpenShift).

Option 1 provides a scripted install process for the MAS application and the underlying OpenShift Container Platform (OCP). This process makes the overall installation process simpler. However, the ability to customize the MAS installation is limited since it is script-based. Additionally, because the underlying platform is a self-managed OCP, the customer has complete control over the infrastructure in exchange for monitoring and maintaining that OCP cluster.

 

Option 2a requires the customer to install MAS themselves but allows for greater customization of MAS during the installation process. This option also provides complete control over the underlying OCP but requires the customer to install, monitor and maintain OCP.

 

Option 2b requires the customer to install MAS themselves but allows for greater customization of MAS during the installation process. In this option, the underlying platform is Microsoft ARO, a managed version of OCP offered by Microsoft. The installation of ARO is scripted, and Red Hat site reliability engineers (SREs) are responsible for monitoring and maintaining the OCP cluster. However, because Red Hat SREs manage the cluster, customers will have less control over the platform infrastructure than in options 1 and 2a.

 

Installation option MAS installation MAS installation customization Platform creation Platform control Platform (OCP) management
Option 1 Scripted Less customization Scripted Complete control Customer managed
Option 2a Manual by customer More customization Customer driven Complete control Customer managed
Option 2b Manual by customer More customization Scripted Less control Red Hat SRE managed

 

Option 1: MAS on self-managed Red Hat OpenShift through Marketplace

 

This deployment option involves setting up MAS on an OpenShift cluster, which runs on the Azure platform. Azure Marketplace serves as the conduit through which this deployment is made possible.

 

One of the primary advantages of choosing this deployment option is the ease of deployment. Azure Marketplace simplifies the process by providing pre-configured templates and scripts that are deployed on the customer’s behalf. One can use this pattern to set up MAS quickly and efficiently, reducing software deployment complexity.

 

You can deploy a new cluster, use an existing one or deploy a new one into an existing network. However, you must provide the expected database and email configurations before the deployment. This flexibility enables organizations to optimize their infrastructure and adapt to changing needs. The Azure Marketplace pattern simplifies the deployment process, allowing businesses to focus on using MAS to enhance their asset management practices quickly.

 

It’s essential to carefully consider resource allocation, data security, integration and support to enable a successful deployment and maximize the benefits of MAS. With the right planning and execution, organizations can unlock the full potential of MAS in their asset management journey through Azure Marketplace with minimal effort.

 

MAS Option1.png

 

Option 2a: MAS on self-managed Red Hat OpenShift through “do it yourself” option

 

Deploying MAS on a self-installed OpenShift cluster on Microsoft Azure through the “do it yourself” option means you have complete control over the installation process. Unlike other deployment methods, where the environment is pre-configured, this approach empowers you to customize your MAS deployment to align with your specific requirements.

 

One of the primary advantages of choosing the “do it yourself” option is its unparalleled level of control. You can tailor the deployment to your unique needs, ensuring every component is configured to optimize the asset management processes.

 

With this option, you can select your preferred installer from various options, including installer provisioned infrastructure, user provisioned infrastructure and even an airgap configuration. This flexibility allows you to use your existing expertise or choose the installer that aligns best with your infrastructure and security requirements.

 

However, it’s essential to recognize this option’s need for skilled resources, the potential complexity of the deployment process and the ongoing support and maintenance responsibilities. With the right expertise and a well-thought-out plan, the “do it yourself” option can be a powerful choice for organizations looking to maximize the potential of MAS in their asset management journey.

 

MAS Option2a.png

 

Option 2b: MAS deployment on Azure Red Hat OpenShift managed by Microsoft Azure

 

MAS is deployed on ARO in this option. This strategic combination offers a range of advantages for businesses looking to streamline their processes. This option provides a middle ground between the previous two options.

 

MAS on ARO is straightforward to set up and will require less effort than the “do it yourself” approach while giving you similar levels of control over OpenShift and MAS. It is mainly for those who prefer not to manage OpenShift themselves, but who still want control over the hosting platform. However, as you’ll be interfacing with OpenShift directly, you will still need team members skilled in OpenShift to make this option work. While this option requires less work from an ongoing management perspective, as OpenShift management is taken care of, it will take additional upfront work because you will be deploying MAS by yourself.

 

The advantages of MAS deployment on ARO are multifaceted. First, it lowers the entry barrier and requires a smaller OpenShift/Kubernetes resources skill set on day one to get started. Most importantly, you no longer need to spend time and effort setting up OpenShift and applying subsequent updates.

 

Second, it provides a managed experience through a PaaS offering supported by Microsoft and RedHat. It provides distinct benefits for those prioritizing rapid access to support services. It simplifies the overall experience of managing the health and updates of OpenShift, as Microsoft is responsible for that.

 

Each MAS on Azure deployment option has its advantages and limitations. You should review these factors to align their deployment with your business needs and requirements. You should assess their infrastructure, customization and cost considerations to make an informed decision that ensures a successful and efficient MAS deployment. By understanding the strengths and limitations of each option, customers can choose the deployment option that meets their business objectives.

 

MAS Option2b.png

Work with IBM Maximo on Azure

1 Comment
Co-Authors
Version history
Last update:
‎Apr 25 2024 03:39 PM
Updated by: