Deployment differences between Maximo Asset Management and Maximo Manage

Maximo® Asset Management deployment is different from Maximo Manage deployment due to the change to Red Hat® OpenShift® Container Platform.

Figure 1. Maximo Asset Management 7.6 deployment architecture

Maximo Asset Management deployment

Maximo Asset Management 7.6 has an administrative workstation where the deployment software is downloaded. Deployment files are generated on the administrative workstation and deployed on an application server. The Maximo database and other external systems are run on separate servers.

In Maximo Asset Management deployment, the software is downloaded on the administrative workstation. The ear and war files are generated on the administrative workstation and deployed on an application server. In this deployment example, the cluster is running multiple servers for Classic UI, Work Centers, Cron, and BIRT reporting to distribute the load in a WebSphere® Application Server Network Deployment. The Maximo Asset Management database and other external systems for integration are running on separate servers.

Maximo Manage deployment in Red Hat OpenShift Container Platform

When you deploy Maximo Manage in Red Hat OpenShift Container Platform, the Maximo Manage operator pulls the images from the IBM Entitled Registry and, if any customization exists, pulls the customization archive from the customer repository. The operator builds an Maximo Manage administrative image and configures images or workloads, such as UI, Cron, BIRT reporting.

The configured images and workloads are deployed to the Maximo Application Suite containers.

The built images are stored in the Red Hat OpenShift internal image registry repository.

The following diagram shows an example of a Maximo Manage application deployment in Red Hat OpenShift Container Platform:

A diagram of an example Maximo Manage application deployment in Red Hat OpenShift Container Platform. The diagram is described in the surrounding text.

Red Hat OpenShift: Red Hat OpenShift contains the infrastructure layer, and an internal image registry to store Maximo Manage configured images and services. Maximo Manage dashboards are provided in Red Hat OpenShift. You can use the dashboards to review logs and monitor Red Hat OpenShift and other applications that are deployed in Maximo Application Suite.
Images: The images for the Maximo Manage operator, Maximo Manage base, industry solutions, and add-ons are provided by the Entitled Registry. These images contain software application classes, deployment descriptors, XML, and scripts.
Maximo Manage operator: The Maximo Manage operator is similar to an installer. The operator pulls the images from the Entitled Registry. This process is similar to downloading software from Passport Advantage® and Fix Central.
Maximo Manage workloads or server bundles: Maximo Manage supports All, UI, Cron, Report, and Maximo Enterprise Adapter workloads. You can configure the workloads during the application deployment. In the diagram, the UI, Cron, Report, and Maximo Enterprise Adapter workloads are deployed.
Customization archive: The customization archive is stored in the customer repository and can be accessed from Maximo Application Suite by using HTTPS.
Admin command processor: The admin command processor pod runs Maximo Manage tools, such as the integrity checker.
Other Maximo Application Suite applications: You can deploy other Maximo Application Suite applications, such as Maximo Collaborate, Maximo Health, Maximo Predict, and Maximo Monitor.
Maximo Manage database: You can deploy the Maximo Manage database, such as IBM® Db2® Warehouse, in a cluster.
Maximo Manage object storage: You can configure IBM Cloud Object Storage for document storage. For example, you can configure doc-links to use IBM Cloud Object Storage for storing documents.
Maximo Manage IBM MQ or Kafka: You can configure a messaging provider, such as JMS, IBM MQ, or Kafka, in a cluster.

Deployment from operator

The following steps describe how Maximo Manage is deployed by using the operator:

Create a custom resource (CR).
An administrator selects, configures, and deploys the Maximo Manage application. The deployment creates a CR. A CR contains a user-entered configuration for the application, for example, the name, version, number of pods, database type and connection, type of workloads, and location of customization archive.
Create the image.
The Maximo Manage operator pulls the images from the Entitled Registry and, if any customization exists, pulls the customization archive from the customer repository. The operator deploys the industry solutions or add-on images and the customization archive over the Maximo Manage base image to create the final images. The operator also validates for the dependency matrix. The operator creates an Maximo Manage administrative image and the Maximo Manage configured images or workloads. The final images are stored in the image registry repository.
Update the configuration.
If the Maximo Manage database does not exist, the operator installs the Maximo Manage administrator image. If the database does exist, the operator upgrades the Maximo Manage database for a new configuration and restarts the Maximo Manage deployment. Maximo Manage configured images or workloads are deployed to containers in Maximo Application Suite.

The following diagram shows how the operator is used to deploy Maximo Manage.

A diagram of how the operator is used to deploy Maximo Manage. The surrounding text describes the diagram.