Kestrel Energy: upgrade readiness, 7.6.1.3 → 9.2
Every item names the script, property, escalation or object it comes from, and says what to do, who owns it and how you know it is done.
2must fix before cutover
0rewire for containers
0retest after upgrade
0clean up before you move
1your data and fields
The short version
- 1 custom Java class needs rebuilding. A class outside IBM's product packages, in
com.kestrel.maximo, were supplied as source or JARs. - Your code calls Maximo methods that 9.x removed. 1 file references classes whose methods are gone by 9.2:
PermitGate.
Plan on a page
| # | Action | Owner | When |
|---|---|---|---|
| 1 | 1 custom Java class needs rebuilding | Java developer | Before the first test upgrade |
| 2 | Your code calls Maximo methods that 9.x removed | Script / Java developer | Build |
1. Must fix before cutover
Must fix1 custom Java class needs rebuilding
- Found
- A class outside IBM's product packages, in
com.kestrel.maximo, were supplied as source or JARs. - Why it matters
- MAS does not take a businessobjects folder on a server. Custom classes ship in a customisation archive and must compile against the 9.2 classes they extend. Manage runs on Java 17 from 9.1 and on Java 25 at 9.2, and IBM asks for a recompile and a test pass for each move. A class that fails to load takes its object or screen down with it.
- Do this
- Get the source, or at least the deployed JAR. Rebuild each class with Java 25 against the 9.2 Manage libraries and check the parent classes and methods still exist. Package them as a customisation archive and reference it in the Manage workspace.
- Done when
- Every class loads in a 9.2 test environment, and each object and screen that uses one opens and saves.
- Owner · when
- Java developer · Before the first test upgrade
- Evidence
1 item
- com.kestrel.maximo.PermitGate — source PermitGate.java
- Sources
- IBM: Manage transition to Java 17 · IBM: Maximo Manage 9.2 and Java 25 · IBM: applying a customisation archive
Must fixYour code calls Maximo methods that 9.x removed
- Found
- 1 file references classes whose methods are gone by 9.2:
PermitGate. - Why it matters
- A call to a removed method fails at run time, the first time that line runs.
- Do this
- Read each call. Replace it with the supported API, or remove the code if it is no longer needed.
- Done when
- No supplied script or class calls a method the 9.2 API index does not carry.
- Owner · when
- Script / Java developer · Build
- Evidence
1 item
- PermitGate — Person.getAvailableHours, Person.getAvailableMbo, Person.getAvailableMboList
- Sources
- IBM: Manage transition to Java 17
2. Your data and fields
CheckYour own objects and fields carry across
- Found
- 0 custom objects and 8 custom fields on IBM tables.
- Why it matters
- These are yours and the upgrade keeps them.
- Do this
- After the test upgrade, confirm they exist and the scripts that use them run.
- Done when
- Every custom object and field exists in 9.2 and its scripts run.
- Owner · when
- DBA + script developer · After the first test upgrade
Standard upgrade steps
| Step | Why |
|---|---|
| Run Integrity Checker on a copy of production and clear every error | The Manage upgrade stops on dictionary inconsistencies. In MAS, run it through the Manage Tools API, not the GUI tool. |
| Take the capture from production | A capture from a development system may differ from production. |
| Do a full test upgrade on a production copy before design sign-off | It surfaces what no static check can: data volumes, long-running scripts, UPDATEDB failures. |
| Confirm the database version the 9.2 workspace supports | MAS supports a narrower database range than 7.6. |
| Clean duplicate or missing primary emails in MAXUSER, PERSON and EMAIL | Duplicate emails are a common cause of MAS user-sync failures. |
| Disable custom database triggers and commit pending database configuration | IBM upgrade checklist step. |
| Map every user to an AppPoints licence type | MAS licenses by AppPoints per user type. |
| If you use JMS queues, move them to the Liberty JMS bundle or Kafka with a persistent store | WebSphere SIBus is gone; the default Liberty store is lost on pod restart. |
| Train users on the new UI and start centres | 9.x changes the look of every classic screen. |
IBM upgrade checklist · IBM Community: Integrity Checker in MAS · IBM docs: JMS server in Manage · IBM Community: users not syncing after upgrade
What this is based on
Read from the input package: 1 automation script(s), 1 screen(s), dictionary, 1 Java class(es). Compared with IBM's 9.2 Manage metadata, IBM's configuration across every release mxh covers, IBM documentation and technotes, and issues other customers reported on the same move (sources on each item). Scripts are read, never run; a match in a comment is ignored. Not supplied: object-structures, launch-points, java-inventory.