What's changed in Maximo IT

Maximo Application Suite uses a different licensing model and uses AppPoints to track application usage, runtime, and user access. AppPoints are allocated in your organization as defined by your license entitlement. You can configure your environment to enforce the AppPoint entitlement. For more information, see Administering licenses and AppPoints usage.

Installation, configuration, deployment, and upgrade are done by the Red Hat® OpenShift® operator in Maximo Application Suite. The entire deployment is based on Red Hat OpenShift.

Containerization is the packaging of software code with just the operating system (OS) libraries and dependencies that are required to run the code to create a single lightweight executable package that is infrastructure-agnostic. System properties, integration, and customization process when you upgrade from IBM Control Desk to Maximo IT are different because of containerization.

An integration framework integrates data with other applications, within your enterprise or with external systems. The framework includes predefined content and a toolkit to extend the predefined content to new integration points. It also enables message providers and an abstraction of message queuing features making Maximo IT in Maximo Manage independent of messaging models like JMS or Kafka.

The IBM Control Desk Service Portal is now replaced by Self Serve application in Maximo IT. Self Serve will allow users to log service requests, raise tickets, browse for solutions and offerings, and chat with service agents to get a ticket resolved. Self Serve will only support the user persona, unlike Service Portal which had agent and administrator personas as well.

You use REST API instead of Remote Method Invocation (RMI) for interactions with the product from custom extensions or external applications. RMI is not supported in the product.

For more information, see REST API as replacement for RMI.

You do not need to install or migrate IBM WebSphere® Application Server. IBM WebSphere Application Server Liberty is embedded in the Maximo image and deployed automatically by Maximo Manage. You can configure other server configurations in the Maximo Application Suite user interface. For more information, see Configuring the application server.

In Maximo IT, user authentication is configured at the Maximo Application Suite level. The upgrade process migrates the existing users to the Users application in Maximo Application Suite where you can view and edit their details. The users are synchronized from Maximo Application Suite to Maximo Manage by using a cron task. Security groups are configured in Maximo Manage. For more information, see Administering users and user access.

Maximo Application Suite is deployed on Red Hat OpenShift Container Platform. For more information, see IBM Maximo Application Suite technical overview.

Maximo Application Suite installation and configuration process includes customer-managed or IBM managed installations. You can choose from multiple platforms and environments. For more information, see Installing Maximo Application Suite.

In Maximo Manage, the System Configuration module contains the Platform Configuration module and the Migration module. You use the applications in the Platform Configuration module to perform numerous tasks, such as managing systems properties and domains. You use the applications in the Migration module to migrate configuration content from one environment to another. For more information, see System configuration module.

The login process differs based on whether you have a customer-managed, IBM managed, or SaaS instance of Maximo Application Suite. For more information, see Getting started.

Maximo IT is built in graphite which brings about significant changes in the user interface as compared to IBM Control Desk. The look and feel of the application is new in the suite. The functionalities and usabilities remain unchanged.