Give the enterprise service the JSON processing class, add it to an external system, name the map after both, and post JSON to the service’s URL. It worked in our lab, with three surprises.
Versions: On Maximo Application Suite 9.1 we confirmed, read-only, that the JSON Mapping, Enterprise Services and External Systems applications, the MXASSET object structure and the messages are present (17 November 2026). We could not confirm the processing class or the URL there, because that needs a test call. The behaviour described here was tested in our lab on Maximo 7.6.1.0 (3 November 2026); we have not re-run it on Maximo Application Suite 9.1, where sign-in for integration calls is different (see below).
IBM’s page: IBM’s current Maximo Manage documentation has the JSON Mapping application; that page does not describe this wiring and points to IBM’s separate document “JSON Mapping application information”.
Last checked: 17 November 2026
| Item | What worked in the lab |
|---|---|
| Enterprise service | Object structure MXASSET, operation Sync, Processing Class com.ibm.tivoli.maximo.fdmbo.JSONMapperExit. |
| External system | Enabled, with the enterprise service row enabled. No end point and no queues were needed for the direct URL. |
| Map name | <EXTERNAL SYSTEM>.<ENTERPRISE SERVICE>.IN (an inbound map on MXASSET). |
| URL | POST /meaweb/es/<EXTERNAL SYSTEM>/<ENTERPRISE SERVICE>. A GET replies “Servlet is running. Please use HTTP POST to post data”. |
| Result | HTTP 200. The asset was created with the mapped values and long description. A second post updated it. |
| Content type | IBM’s JSON Mapping document says application/json is required. In our lab, text/plain also worked. |
What we observed in our lab: the reply was XML, not JSON, because there was no response map. For a JSON reply, IBM says to add a map named <EXTERNAL SYSTEM>.<ENTERPRISE SERVICE>.RESPONSE that uses the same processing class. And when we deleted the test asset afterwards, Maximo returned BMXAA4160E (a NullPointerException) — but the asset was deleted.
com.ibm.tivoli.maximo.fdmbo.JSONMapperExit. Save.<EXTERNAL SYSTEM>.<ENTERPRISE SERVICE>.IN./meaweb/es/<EXTERNAL SYSTEM>/<ENTERPRISE SERVICE> as an authenticated user. This is the direct (synchronous) route; errors come back in the HTTP response. IBM’s JSON Mapping document says a JSON map also works through the inbound queue; we did not test that. On Maximo Application Suite 9.1 the sign-in is different: IBM’s support page How to authenticate in Manage to use the Integration Framework says that until Manage 9.0 the only supported method was an API key in the request header, and that from Manage 9.1 other methods exist but still rely on API keys. We have not posted to this URL on Maximo Application Suite 9.1.To undo: clear Enabled on the service row and the external system, delete the external system, then the enterprise service, then the map, then the test records. Maximo keeps history rows (asset transactions) for deleted test assets.
On a Maximo 7.6.1.0 lab system we created a test map, a test enterprise service and a test external system, posted JSON to the service twice (create, then update) and read the asset and its long description back with SQL. Then we disabled and deleted everything in the order above. Only the history rows that Maximo keeps for a deleted asset remained.
Not tested: the queued route, a response map, message tracking and reprocessing, the screen steps. On Maximo Application Suite 9.1 we only read the configuration; we did not create a map or post anything there.
This page is part of our Maximo knowledge pages: answers we have checked on a real Maximo system in our lab. For questions about your own Maximo data, see Interpretos for Maximo.