Assetize

Learning Lab

Level 6 · 15 levels · Practitioner · about 75 minutes

Level 6 — Versions: classic Maximo 7.6.1, MAS 8 and MAS 9

By the end: Explain how Maximo Application Suite differs from classic Maximo 7.6.1, how operators install, update and customise Manage, why the login changed from maxauth to API keys, what moved between 8.x, 9.0, 9.1 and 9.2, and which IBM support dates drive every upgrade.

The same Maximo work, run two ways. Left: classic 7.6.1, one big application copied onto WebSphere servers. Right: Maximo Application Suite, a core and applications running as containers on Red Hat OpenShift. Keep this picture in your head for the whole level.

On the left, Maximo 7.6.1 runs as one application on WebSphere servers. On the right, Maximo Application Suite runs in containers on Red Hat OpenShift: a core for users and licences, and applications such as Manage, Monitor, Health, Predict and Visual Inspection, each as pods.

Lesson 1

Classic Maximo 7.6.1: one application on WebSphere

For about twenty years Maximo was one Java application called Maximo Asset Management. You will hear it called "classic Maximo", "EAM" or just "7.6". Its last release line is 7.6.1. IBM shipped fix packs on that line (7.6.1.1, 7.6.1.2, 7.6.1.3) and smaller interim fixes on top of each fix pack. When a customer says "we are on 7.6.1.2 IFIX 14", they are telling you the release line, the fix pack and the interim fix, in that order.

How it runs. The whole of Maximo is packed into one big file called an EAR (enterprise archive: a zip of Java code, web pages and settings). The EAR is deployed onto IBM WebSphere Application Server, on servers the customer owns or rents. Behind it sits one database: IBM Db2, Oracle or Microsoft SQL Server. Bigger customers run the same EAR on several servers, often one group for users, one for integration, one for cron tasks and one for reports, but every server runs the same application.

How change goes in. The installation lives in a folder on an administration workstation, usually called SMP (C:\IBM\SMP\maximo on Windows). Custom Java classes are copied into that folder, the buildmaximoear command builds a new EAR, and an administrator deploys it to WebSphere during an outage. Database changes travel as DBC scripts, which the updatedb tool runs in order. You will use both ideas again in Level 7, and again when you see how MAS does the same job.

PartIn classic 7.6.1
The applicationOne EAR file, the same on every server
Application serverIBM WebSphere Application Server
Where it is builtThe SMP folder on an admin workstation, with buildmaximoear
Database changesDBC scripts run by updatedb
Who looks after itThe customer's own administrators and DBAs
LoginMaximo users, often through LDAP; many integrations send a maxauth header
Classic Maximo and MAS. Look at the left side only: one application, copied onto each WebSphere server. A change to it means a new EAR on every one of them.

On the left, Maximo 7.6.1 runs as one application on WebSphere servers. On the right, Maximo Application Suite runs in containers on Red Hat OpenShift: a core for users and licences, and applications such as Manage, Monitor, Health, Predict and Visual Inspection, each as pods.

The mistake: Treat "Maximo" as one product with one set of answers, and quote a forum post about 7.6.1.2 to a customer on MAS 9.2. Do this instead: Classic 7.6.1 and MAS run Maximo in different ways, with different login, install and customisation rules. Name the version first, then find evidence from that version.

Lesson 2

Maximo Application Suite: a core and applications on OpenShift

Maximo Application Suite (MAS) is how IBM ships Maximo today. Instead of one EAR on WebSphere, MAS is a set of containers. A container is a small sealed package that holds one program and everything it needs to run. Containers run inside pods (Kubernetes' name for "one running copy of something"), and the pods run on Red Hat OpenShift, a Kubernetes platform. A customer can run OpenShift in their own data centre or in a cloud account, or let IBM run the whole thing as MAS as a Service.

MAS has two layers. The core looks after what every application shares: users and login, licences counted in AppPoints, workspaces, and the navigator that moves you between applications. Applications sit on top. Manage is the application that does what classic Maximo did: assets, locations, work orders, inventory and purchasing. Others include Monitor (sensor data), Health and Predict (asset condition and failure risk), Visual Inspection (image models), Optimizer (scheduling) and, from 9.1, the facilities application that used to be IBM TRIRIGA.

Manage still has the business objects (MBOs) you met in Level 4, the same Database Configuration and the same automation scripts. What changed is the platform under it. Manage runs as server bundles: pods with one job each. IBM's bundle types are all, ui, cron, mea (integration), report and standalonejms (a JMS message server). The all bundle combines cron, mea, report and ui in one pod. Bigger systems split them so each part can scale on its own.

PieceWhat it does
Suite coreUsers, login, AppPoints licences, workspaces, the suite navigator
MongoDBStores the suite's own metadata; from 9.1 it runs as an external service (in 9.2, login users and groups move to the Manage database)
ManageAssets, work, inventory and purchasing: the classic Maximo work
Manage databaseDb2, Oracle or SQL Server, as before
Server bundlesall, ui, cron, mea, report and standalonejms pods
Other applicationsMonitor, Health, Predict, Visual Inspection, Optimizer and more
Classic Maximo and MAS. Now the right side: the core underneath and each application as its own pods. Manage is the one that carries your classic Maximo work across.

On the left, Maximo 7.6.1 runs as one application on WebSphere servers. On the right, Maximo Application Suite runs in containers on Red Hat OpenShift: a core for users and licences, and applications such as Manage, Monitor, Health, Predict and Visual Inspection, each as pods.

What stays the same in ManageWhat is new around it
  • The MBO business rules and data model from Level 4
  • Database Configuration, Domains and Application Designer
  • Automation scripts, workflow, escalations and cron tasks
  • The REST API under /maximo/api
  • Containers and pods on Red Hat OpenShift
  • Install and update by operators
  • Login through the suite core; API keys for programs
  • Custom Java through customisation archives
  • Licences counted in AppPoints

MAS architecture, drawn

Remember: When someone says "MAS", ask which application. Most of your work happens in Manage, but every user logs in through the core.

Lesson 3

Operators and custom resources: how MAS installs and updates itself

In classic Maximo a person ran the installer and deployed the EAR. In MAS that job belongs to operators. An operator is a program that runs inside OpenShift and looks after one product. It reads a custom resource, a short YAML document stored in the cluster that says what should exist, and keeps changing the cluster until what is running matches it. Kubernetes people call this the reconcile loop: read the wish, compare it with reality, fix the difference, repeat for ever.

MAS has an operator for the suite and one for each application. The Manage operator watches a custom resource called ManageWorkspace. It describes one Manage deployment: which add-ons and industry solutions are switched on, the database settings, the server bundles and how many copies of each, the languages, and the list of customisation archives. Change the ManageWorkspace and the operator does the rest: it builds new images, runs the database update and rolls the pods onto the new version.

A ManageWorkspace from a MAS 9.2 lab system, trimmed

apiVersion: apps.mas.ibm.com/v1
kind: ManageWorkspace
metadata:
  name: inst1-gtmdemo
  namespace: mas-inst1-manage
spec:
  components:
    base: { version: latest }
    health: { version: latest }
    spatial: { version: latest }
  settings:
    customizationList: []          # customisation archives, applied in this order
    db:
      dbSchema: maximo
      upgrade: { upgradeType: regularUpgrade }
    deployment:
      buildTag: latest
      serverBundles:
        - { name: all, bundleType: all, replica: 1 }
    languages: { baseLang: EN, secondaryLangs: [] }
status:
  conditions:
    - type: BuildReady         # "Build generated and tagged with 20260930T234607-9.2.197"
    - type: DeploymentReady    # "UpdateDB/Maxinst: Completed. Deployment all: 1 of 1 replicas ready"
    - type: Ready              # "Manage deployed in workspace gtmdemo"

Read the status block like a dashboard. BuildReady means the operator has built the Manage images. DeploymentReady covers the database update (updatedb, run by the maxinst pod) and the pods coming up. Ready means people can work. During an upgrade IBM also reports the stage and any failure in a DBReady condition. When a deploy seems stuck, these conditions are the first thing you read.

Updates arrive the same way. Each operator follows a channel in IBM's operator catalog. In IBM's words, the instance "is automatically kept up to date with the latest version that is available in the Maximo Application Suite operator's subscription channel", and you can set it so upgrades wait for a person to approve them. Moving to a new release line, say 9.1 to 9.2, means switching the channel, one line at a time.

How an operator keeps MAS running. Watch the loop: the ManageWorkspace says what should run, the operator compares it with what is running, and changes pods until the two match. Then it keeps watching.

A configuration file (the ManageWorkspace custom resource) says what should be running. The operator compares it with what is running and changes the pods until they match, then keeps watching.

The mistake: Open a terminal in a running Manage pod and edit a file or drop in a JAR to fix something fast. Do this instead: Pods are rebuilt from images, so a hand edit is gone at the next restart. Put the change where the operator reads it: the ManageWorkspace, or a customisation archive it points to.

Remember: Desired state lives in the custom resource. If it is not in the ManageWorkspace or an archive it names, it will not survive a restart.

Lesson 4

Customisation archives: how custom code reaches Manage

Custom Java, DBC scripts and changed deployment files still exist in MAS. They travel in a customisation archive: a zip file whose folders mirror the classic SMP/maximo folder. IBM's guidelines say each class file goes in the matching directory, for example applications/maximo/businessobjects/classes/..., so it lands on top of the product code in the right place. A product XML file names your DBC scripts and the classes you replaced.

Inside a customisation archive

my-archive-1.4.0.zip
├── applications/maximo/businessobjects/classes/custom/app/workorder/CustWO.class
├── applications/maximo/properties/product/a_customer.xml     # names your DBC scripts and custom classes
├── tools/maximo/en/cust/V7612_01.dbc                          # database changes, run by updatedb
├── deployment/was-liberty-default/config-deployment-descriptors/maximo-all/...   # web.xml and friends
└── additional-server-files/                                   # extra Liberty server files

You put the zip where the cluster can download it, over HTTP, HTTPS, FTP or FTP with SSL. IBM lists SFTP as not supported. Then you tell Manage about it: in the MAS administration screens, Manage's Customization section (clear System managed and paste the URL), or in the customizationList of the ManageWorkspace. With several archives, list them in the order they should be applied.

What happens next is the operator's job. It downloads the archives, builds a new admin image and new server bundle images with your files inside, runs the database update so your DBC scripts apply, and rolls the pods onto the new images. IBM's own support note says the build "could take up to 2 hours to complete, but can be faster than that". So a Java change on MAS is still a planned event. The difference is that the operator runs it the same way every time. Teams that build images outside the cluster set spec.settings.skipImageBuild to true, and the operator skips its own build.

  1. Zip the archive with a version in its name
  2. Host it at a URL the cluster can reach
  3. Add it to Manage: Customization section or customizationList
  4. Operator builds admin and bundle images
  5. updatedb runs your DBC scripts
  6. Pods roll onto the new images
How each kind of change moves. Find the lit lane: Java and DBC files ride in a customisation archive, and the operator rebuilds Manage. Configuration and data move in other lanes, which Level 7 covers.

Four lanes: configuration moves in Migration Manager packages, database structure moves in DBC scripts run by updatedb, Java moves in a customisation archive and a rebuild, and data moves in data loads.

Remember: Put a version in every archive name (my-archive-1.4.0.zip). IBM calls it good practice, and it is how you know which code each environment is running.

Lesson 5

The login change: from maxauth to API keys

Every call to Maximo has to say who is calling. Classic 7.6.1 supports native authentication through an HTTP header called maxauth: the user name and password joined with a colon and encoded in base64. Many 7.6.1 integrations were built that way years ago and still send it today.

Base64 is an encoding, not encryption. "wilson:wilson" becomes d2lsc29uOndpbHNvbg==, and anyone who sees the header can turn it straight back. A password in every request is also a password in every log and every proxy on the way.

In MAS, people log in through the suite core: local users, LDAP, or single sign-on with SAML or OpenID Connect. Programs send an API key instead: a long random string created for one Maximo user in the API Keys application. Each call runs as that user, with that user's security groups, and by default no server session is created. IBM documents the key as an apikey request header or query parameter. Use the header, because addresses end up in logs.

The same read, two ways to log in

# Classic 7.6.1: native login, user:password in base64
curl -H "maxauth: d2lsc29uOndpbHNvbg==" \
  "https://maximo.example.com/maximo/api/os/mxapiasset?oslc.pageSize=1"
# 200 on 7.6.1

# MAS 9.x: an API key for an integration user, read from the environment
curl -H "apikey: $MAXIMO_APIKEY" \
  "https://manage.example.com/maximo/api/os/mxapiasset?oslc.pageSize=1"
# 200 on MAS. The maxauth call above gets 401 here.
The login change. Two doors. The 7.6.1 door takes maxauth or an API key. The MAS door takes the API key only, and the maxauth caller bounces back with 401.

Two doors. The 7.6.1 door accepts a maxauth user and password and an API key. The MAS 9 door accepts only the API key; the maxauth caller bounces with 401.

Why this matters on an upgrade: screens and data move across, but integrations do not log themselves in. Each external system needs its own integration user in Manage, the right security groups, an API key kept in a secret store, and a test call before go-live. Mutual TLS (both sides showing certificates) can protect the connection as well, but it does not replace the API key.

MAS 9.2 changes users again. User and group data for login now lives in the Manage database, user synchronisation is removed (except for the facilities application), and the user management APIs deprecated in 9.1 are removed, so scripts that call them must move to the new APIs first. IBM also documents that after moving from 7.6 to MAS 9.x with Okta single sign-on, users create a separate password for electronic signatures.

Remember: Prove it in this level's missions: the same maxauth call answers 200 on the 761 lens and 401 on mas92.

Lesson 6

What changes between 8.x, 9.0, 9.1 and 9.2

MAS has its own release lines. IBM's release register gives the first release of each: 8.11.0 on 26 September 2023, 9.0.0 on 25 June 2024, 9.1.0 on 24 June 2025 and 9.2.0 on 25 June 2026. Each line then gets regular patch releases, and a monthly feature channel lets customers preview new features on non-production systems (and on MAS as a Service). Production runs the released versions.

Release lineFirst releaseWhat changed, at a high level
MAS 8.x8.11.0: 26 Sep 2023The suite on OpenShift with Manage as the classic Maximo. Installs and updates by operators. From 8.9, Maximo Anywhere and Work Centers are removed; Maximo Mobile replaces them.
MAS 9.025 Jun 2024The upgrade step from 8.11. MongoDB 5.0 and 6.0. Data Reporter Operator replaces User Data Services. SCIM 2.0 user and group sync. IPv6.
MAS 9.124 Jun 2025Manage on Java 17, so customisation archives are recompiled. A foundation service. MongoDB as an external service only. New user management APIs. Health becomes an add-on in Manage. Assist is renamed Collaborate. The facilities application (formerly TRIRIGA) joins the suite.
MAS 9.225 Jun 2026User and group data in the Manage database, user sync removed, the old user APIs removed. Db2 12 supported, by opt-in. Three admin permission modes: cluster, namespaced and minimal. Manage supports Java 25 and BIRT 4.21.

Two rules shape every move. First, IBM supports upgrading one release line at a time, called n-1: from 8.11 you go to 9.0, then 9.1, then 9.2. Second, classic to MAS is not an in-place upgrade. IBM's words: "You must install Maximo Application Suite when you upgrade from Maximo Asset Management." You install MAS, deploy Manage against your database, carry customisations in archives, run IBM's Integrity Checker first, and test everything. IBM also says every migration is different, so there is no single runbook to copy.

This is why every fact belongs to a version. Between 9.1 and 9.2 alone, IBM's data dictionary shows hundreds of attribute lengths changing, objects such as METERMETRICTYPE removed, and user APIs gone. A login rule changes between 7.6.1 and MAS. "Does Maximo do X?" has no answer until you say which Maximo. Assetize is built on that rule: every record carries the versions it applies to, the compare tool takes a from-version and a to-version, and the sim on this level has a lens per release line: 761, mas811, mas90, mas91 and mas92.

Your upgrade is a diff. Your upgrade is a diff. One circle is what IBM changed between the two releases; the other is the customer's own customisations. The overlap is where the real work is.

Two overlapping sets: what IBM changed between the two releases, and the customer's own customisations. Only the overlap is highlighted: the changes that touch the customer's own lines.

The mistake: Plan to jump from MAS 8.11 straight to 9.2 in one weekend. Do this instead: Follow IBM's n-1 policy: 8.11 to 9.0, 9.0 to 9.1, 9.1 to 9.2. Check each step's prerequisites (OpenShift, database, add-ons) before you book the window.

Remember: Before you trust any answer, ask two things: which version, and where is the evidence?

Lesson 7

The support clock that drives upgrades

IBM publishes a support lifecycle for every release. While a release is in standard support, IBM fixes defects and takes cases as normal. After that a customer can usually buy Extended Support, a paid add-on, for a while longer. The dates come from IBM support pages, and they decide when customers must move. They are the reason so much of your work will be upgrades.

DateWhat happensWhat IBM says to do
30 Sep 2025End of regular support for Maximo Asset Management 7.6.1.xBuy Extended and Sustained Support, or trade up to MAS and migrate to Manage
30 Apr 2026Standard support ends for MAS 8.10 and 8.11, which move to Extended Support from 1 May 2026. MAS 8.7, 8.8 and 8.9 reach end of support, with no Extended Support offeredMove to a current release or buy Extended Support
30 Apr 2027Dual Support ends: running 7.6.1.x alongside a MAS licenceSubscription Upgrade customers lose 7.6.1.x support; for Perpetual Trade-Up customers, 7.6.1 usage rights expire
1 Jul 2027MAS 9.0.x moves to Extended Support. IBM announced the date on 23 June 2026; its 9.0 lifecycle page shows the transition on 30 June 2027Plan the step to 9.1 or 9.2, or buy Extended Support

How the cycle works for MAS 9. IBM's lifecycle pages for 9.0 and 9.1 list "Support Cycle-3": 3 years of support, a critical fix extension of 1 year, then usage and existing fixes for 3 more years (3+1+3). For 9.0, IBM shows Extended, Sustained and Extension availability running to 30 June 2031.

What it means for the customers you will meet. A customer still on 7.6.1 is already past regular support, and if they traded up to a MAS licence they can run 7.6.1 under Dual Support only until 30 April 2027. A customer on MAS 8.11 is on Extended Support and has three steps to climb. A customer on 9.0 has a clock running to mid-2027. Each one is a project, and each project starts with the same question: which version are you on today?

The support clock. Read the clock from left to right. The marker is today. Every date to its left has already passed, so the customers on those releases are moving now.

A timeline: 30 September 2025 end of regular support for Maximo 7.6.1.x, 1 May 2026 MAS 8.x on Extended Support only, 30 April 2027 Dual Support ends, 1 July 2027 MAS 9.0 moves to Extended Support. A marker shows today.

Upgrading to MAS, drawn

Remember: Quote every support date with its IBM page. The Assetize upgrade deadlines page lists each date with its source and the days left.

Level 6 missions in the Maximo sim

  1. Turn the box into Maximo 7.6.1. Switch the sim to the 7.6.1 release line, then read the system info to prove it changed.
  2. Old-style login on 7.6.1. On the 7.6.1 lens, read assets with a maxauth header (user and password, base64) instead of an API key.
  3. The same login on MAS 9.2. Switch back to MAS 9.2 and send the same maxauth request. See why "we upgraded and the interface broke".

Real practice on the Maximo SIM

Tasks you do by hand on the training Maximo, with the evidence your trainer checks.

  1. Read the version from the box (DEV). Every answer belongs to a version. Prove which one you are talking to before you trust anything.
  2. Try the old login on a MAS-style API (DEV). The login change breaks more upgraded integrations than anything else. See it with your own eyes.

Check yourself: the Level 6 quiz

18 questions. Pass mark 70%.

  1. What platform does Maximo Application Suite run on?
    • Red Hat OpenShift, as containers in pods
    • Windows Server with IIS
    • IBM WebSphere Application Server only
    • A mainframe only
  2. Look at the picture. How is this Maximo deployed? (picture: Classic Maximo and MAS)
    • As pods looked after by operators
    • As a phone app
    • As one EAR file copied onto WebSphere servers
    • As a database stored procedure
  3. Which MAS application does the classic Maximo work: assets, work orders, inventory and purchasing?
    • Monitor
    • Predict
    • Visual Inspection
    • Manage
  4. Which picture shows Maximo Application Suite?
    • Picture A
    • Picture B
  5. Look at the picture. What does the operator compare? (picture: How an operator keeps MAS running)
    • Two database backups
    • The ManageWorkspace custom resource (what should run) with what is running
    • A user's password with LDAP
    • Two Excel files
  6. A colleague fixes a Manage problem by editing a file inside a running pod. What happens at the next restart?
    • The fix stays for ever
    • OpenShift emails the change to IBM
    • The pod starts again from its image, so the edit is gone
    • The ManageWorkspace copies the edit
  7. How does custom Java reach Manage in MAS?
    • In a customisation archive the operator builds into new images, before updatedb runs
    • By pasting it into Application Designer
    • With an SQL insert
    • By copying it onto a user's laptop
  8. The lit lane carries custom Java and DBC files into Manage. What does it travel in? (picture: How each kind of change moves)
    • A Migration Manager package
    • A data load spreadsheet
    • An email attachment
    • A customisation archive
  9. Which kind of address can the operator use to download a customisation archive?
    • SFTP
    • HTTPS
    • A Windows share path
    • A USB stick
  10. An old integration sends a maxauth header to the system in the picture. What comes back? (picture: The login change)
    • 401: the MAS API wants an API key
    • 200 OK and the records
    • 404: the object structure is missing
    • 500: the server crashed
  11. Why is a maxauth header risky even on 7.6.1?
    • It is slow
    • It only works at weekends
    • Base64 is an encoding, so anyone who sees the header can read the password
    • It deletes records
  12. Which picture shows a caller that will get its records back from MAS?
    • Caller A
    • Caller B
  13. A customer is on MAS 8.11 and wants 9.2. What route does IBM support?
    • Straight to 9.2 in one step
    • Back to 7.6.1 first
    • Any order they like
    • 8.11 to 9.0, then 9.1, then 9.2
  14. Which release moved Manage to Java 17, so customisation archives must be recompiled?
    • MAS 8.11
    • MAS 9.1
    • MAS 9.0
    • Maximo 7.6.1.3
  15. Look at the clock. A customer runs 7.6.1 alongside a MAS licence under Dual Support. Which date is their next deadline? (picture: The support clock)
    • 30 September 2025
    • 1 July 2027
    • 30 April 2027
    • There is no deadline
  16. In MAS 9.2, where does user and group data for login live?
    • In the Manage relational database
    • In a spreadsheet on the admin's laptop
    • Only in MongoDB
    • In each pod's file system
  17. Look at the picture. Which changes deserve your attention first on an upgrade? (picture: Your upgrade is a diff)
    • Everything IBM changed
    • Only the customer's customisations
    • None, upgrades are automatic
    • The overlap: IBM changes that touch the customer's own customisations
  18. Someone asks "Does Maximo support X?" What is your first question?
    • Which colour?
    • Which version?
    • Who is asking?
    • Is it urgent?

Remember it as a picture

  • Classic Maximo 7.6.1: One EAR on WebSphere, built in the SMP folder. Regular support ended 30 September 2025.
  • Maximo Application Suite: A core (users, login, AppPoints) and applications such as Manage, running as pods on Red Hat OpenShift.
  • Manage: The MAS application that does the classic Maximo work, with the same MBO business rules underneath.
  • Operator and ManageWorkspace: The Manage operator reads the ManageWorkspace custom resource and changes pods until reality matches it.
  • Customisation archive: A zip that mirrors SMP/maximo. The operator builds it into new images and updatedb runs its DBC scripts.
  • maxauth: The 7.6.1 native login header: user:password in base64. Easy to read back, and refused by the MAS API.
  • API key: How programs call MAS: an apikey header tied to one Maximo user and that user's security groups.
  • 401 after go-live: The classic sign of an integration still sending maxauth to MAS. Test every caller's login in rehearsal.
  • Every fact has a version: An upgrade is the overlap of what IBM changed and what you customised. Name both versions before you answer.
  • The support clock: 7.6.1 regular support ended 30 Sep 2025. Dual Support ends 30 Apr 2027. MAS 9.0 moves to Extended Support from 1 Jul 2027.
  • Know the route: n-1: Step one of every upgrade. IBM moves one release line at a time: 8.11 to 9.0, 9.0 to 9.1, 9.1 to 9.2.
  • Where the API key lives: In a secret store or environment variable only the running integration reads. Never in code, never in a URL.

Where these facts come from

Try it on the real tools

How did Level 6 go?

Rate the level and say what worked, what did not, what you liked and what you did not. Send it now, or with your full report.