Planning

IBM® Maximo® Application Suite uses Red Hat® OpenShift® run anywhere model. You can deploy on premises by using the CLI, or on a supported hyperscaler.

Planning for on premises
Before you install Maximo Application Suite by using the CLI, configure installation requirements and consider installation preferences, such as whether you want to create a Red Hat OpenShift cluster or reuse an existing one.
Planning to install on Amazon Web Services
Before you can install IBM Maximo Application Suite on Amazon Web Services, you must consider your installation preferences, such as whether you want to create a Red Hat OpenShift cluster or reuse an existing cluster.
Planning to install on Microsoft Azure
Before you can install Maximo Application Suite, you must configure the installation requirements and consider your installation preferences, such as whether you want to create an Red Hat OpenShift cluster or reuse an existing one.
Planning for IBM Cloud
Before you can install Maximo Application Suite on IBM Cloud, you must configure the installation requirements. There are dependencies that you must to install before installing the Maximo Application Suite itself and additional dependencies that you can install depending of the Suite application you are planning to deploy. As an alternative, you can make use of automation to provision the Red Hat OpenShift cluster on IBM Cloud and other dependencies by using the Ansible collection.
Operational mode for installation
From Maximo Application Suite 8.9 or later, you can consider installing and deploying IBM Maximo Application Suite in Production or Non-production mode based on your development and testing requirements and to optimize your AppPoint usage.
IBM Suite License Service
The IBM Suite License Service stores and manages the license of your IBM solution. After you install Suite License Service as part of your IBM solution, you upload the license file to the Suite License Service server.
High availability
High availability implies redundancy that supports failover. Prolonged application or system outages can have significant business consequences. You can increase the resiliency of the systems to environmental, hardware, or software faults or failure. Techniques and architectural patterns can minimize the impact on the overall system if a planned or unplanned system outage occurs. High availability techniques cannot be implemented at the detriment of other architectural considerations, such as capital cost, ongoing total cost of ownership, or manageability.