Integration Flow Explorer
Design, test and fix a Maximo integration
Pick the record and the sender, map the fields, send a test message and read the record back. Every response and error matches what Manage 9.2.197 returned.
Run on a live Manage 9.2.197
On 26 October 2026 the same tests ran against a live Manage 9.2.197 with JMS configured: 15 synchronous inbound tests, 9 queued and Message Reprocessing tests (held message, retry count, HOLD, corrected and reprocessed, sequential order) and 8 outbound tests (HTTP end point and event publish through the outbound queue) passed, each record read back. The four integration script recipes ran in Manage: default a site and accept one site inbound, map an outbound status and publish only a status.
Design inbound and outbound integrations
Inbound: external system → enterprise service → processing rules → object structure → Maximo record → response, synchronous on /meaweb/es or queued on /meaweb/esqueue. Outbound: business event → event filter → publish channel → queue → end point → external system. Each stage is labelled as read back on Manage 9.2, configuration, or how MIF runs it.
Test the message
Validate without sending, run on sample data with Manage 9.2.197 behaviour, or connect your Maximo with an API key and send it for real. The record is read back after a 200; a failure names its BMXAA code, cause, field, the correction and the recovery, then Retry or Reprocess.
Run the same test from the command line
node scripts/lab-runner/integration-flow.mjs all sends the same messages, reads every record back and writes a redacted journal with message IDs.
What each error means and how to clear it
- BMXAA4211E (Payload): BMXAA4211E - Database error number -803 has occurred when operating on WORKORDER : Site={site} Work Order={wonum}. Report the error to the owner of the deployment. Fix: Send a new WONUM, or leave WONUM out so Maximo numbers the record.
- BMXAA7094E (Payload): BMXAA7094E - The entered value {value} is not valid. Enter a valid integer value. Fix: Map the sender’s label to the number, for example P1 → 1.
- BMXAA4575E (Payload): BMXAA4575E - Work Type {value} is not a valid work type. Fix: Send a defined work type, for example CM, or add the value in Organizations → Work Order Options → Work Type.
- BMXAA4153E (Payload): BMXAA4153E - {value} is not a valid site. Enter a valid Site value as defined in the Organization Application. Fix: Send a valid SITEID, or default it in an inbound processing script (OSIN beforeProcess).
- BMXAA1562E (Maximo configuration): BMXAA1562E - The {extsys} external system is disabled. Fix: External Systems → select the system → Enabled, then save. Check the enterprise service row is enabled too.
- BMXAA1645E (Maximo configuration): BMXAA1645E - The {extsys} sender is not recognized. Fix: Correct the external system name in the URL, or create the external system and add the enterprise service to it.
- BMXAA9301E (Security): BMXAA9301E - The user of the transaction is not authorized for Object Structure {os}. Configure authorization in the object structure application and grant necessary access to the user. Fix: Object Structures → select the structure → Configure Object Structure Security, set the authorising application (MXWO → WOTRACK on the lab), and grant the integration user’s group access.
- BMXAA1581E (Messaging infrastructure): BMXAA1581E - No object with the name {0} is set up in the JNDI tree. Check the JMS/JNDI setup in the server administration console. Fix: Configure the JMS provider for Manage (in MAS, the Manage workspace’s JMS server bundle and its queues), then restart the bundle that runs the queue consumers.
- BMXAA4216E (Maximo configuration): BMXAA4216E - Unknown Object named {os} has been encountered. Gather the logs from the <HOME> directory and determine the cause and source of the error. Fix: Use MXEXTSYSTEM for external systems, services and channels; create a read-only object structure over MAXINTMSGTRK or MAXINTERROR to read tracking and reprocessing rows.
Walk the flow by version
Step through a Publish Channel or Enterprise Service from 7.6.1.3 to 9.3 and compare two releases stage by stage, with burst and chaos modes for sequential and continuous queues.