Assetize

Integration Flow Explorer · Documentation

How to design, test and fix a Maximo integration

Each stage of an enterprise service and a publish channel, what Manage 9.2 answers on each path, and how to clear every error the tool shows.

Start here

  1. Design: record, source system, format, delivery, mappings.
  2. Validate without sending.
  3. Run on sample, or send to your Maximo and read the record back.
  4. Fix: apply the correction, retry or reprocess, export the evidence.

API behaviour on Manage 9.2.197

  • POST /meaweb/es: HTTP 200 text/plain with an empty Sync…Response carrying a messageID; refusals are HTTP 400 text/html "Error 400: BMXAA…".
  • POST /meaweb/esqueue: accepted once it parses; needs a JMS provider with the inbound queues in JNDI (BMXAA1581E otherwise).
  • MXEXTSYSTEM (200): External systems with their enterprise services (maxextifacein) and publish channels (maxextifaceout).
  • MXAPIINTOBJECT (200): Object structures, their objects and authorising application.
  • MXAPIENDPOINT (200): End points and handlers (77 on the lab).
  • MXAPIAUTOSCRIPT (200): Automation scripts and launch points (23 on the lab).
  • MXAPIEXTSYSTEM (404): BMXAA4216E: use MXEXTSYSTEM.
  • MXAPIIFACEIN (404): BMXAA4216E: enterprise services come through MXEXTSYSTEM.maxextifacein.
  • MXAPIIFACEOUT (404): BMXAA4216E: publish channels come through MXEXTSYSTEM.maxextifaceout.
  • MXAPIINTMSGTRK (404): BMXAA4216E: Message Tracking needs its own read-only object structure over MAXINTMSGTRK.
  • MXAPIINTERROR (404): BMXAA4216E: Message Reprocessing needs its own read-only object structure over MAXINTERROR.

Troubleshooting

  • BMXAA4211E: 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. Expects: A work order number that does not exist at the site. The enterprise service inserts; it does not update an existing key. Fix: Send a new WONUM, or leave WONUM out so Maximo numbers the record.
  • BMXAA7094E: BMXAA7094E - The entered value {value} is not valid. Enter a valid integer value. Expects: An integer (WOPRIORITY is INTEGER). Fix: Map the sender’s label to the number, for example P1 → 1.
  • BMXAA4575E: BMXAA4575E - Work Type {value} is not a valid work type. Expects: A work type defined for the organization (Work Type values in Organizations). Fix: Send a defined work type, for example CM, or add the value in Organizations → Work Order Options → Work Type.
  • BMXAA4153E: BMXAA4153E - {value} is not a valid site. Enter a valid Site value as defined in the Organization Application. Expects: A site defined in Organizations, for example BEDFORD. Fix: Send a valid SITEID, or default it in an inbound processing script (OSIN beforeProcess).
  • BMXAA1562E: BMXAA1562E - The {extsys} external system is disabled. Expects: An enabled external system. Fix: External Systems → select the system → Enabled, then save. Check the enterprise service row is enabled too.
  • BMXAA1645E: BMXAA1645E - The {extsys} sender is not recognized. Expects: A sender that exists in External Systems; the name in /meaweb/es/{extsys}/… is that sender. Fix: Correct the external system name in the URL, or create the external system and add the enterprise service to it.
  • BMXAA9301E: 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. Expects: An object structure with an authorising application the integration user has access to. 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: BMXAA1581E - No object with the name {0} is set up in the JNDI tree. Check the JMS/JNDI setup in the server administration console. Expects: A JMS provider with the inbound queue bound in JNDI (jms/maximo/int/queues/sqin or cqin). 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: BMXAA4216E - Unknown Object named {os} has been encountered. Gather the logs from the <HOME> directory and determine the cause and source of the error. Expects: An object structure that exists on the target Manage. 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.

Integration scripts

OSIN.{object structure} beforeProcess, OSOUT.{object structure} overrideValues and PUBLISH.{channel}.EVENTFILTER, each with setup, a test message, a negative test and cleanup.

Command line and CI

node scripts/lab-runner/integration-flow.mjs manifest | sync | queued | outbound | recipes | cleanup

Open the tool