IBM Maximo 7.1 Birt Reports and Chrome
Updated: Feb 25
Its tricky situation when a client with an older version of Maximo is trying to upgrade their browsers and yet maintain backwards compatibility. This situation is particularly interesting when a client is, for relatively valid reasons, is trying to use a newer version of Chrome or any WebKit-based browser (including Edge) and is facing issues when using an older version of Maximo running Birt reports.
In this particular case, the major complaint was regarding BRIT reports! BIRT reports just won’t run and the following not-so-useful message is shown.
Error Message thrown when trying to run Birt reports using Chrome with an older version of Maximo, in this case 7.1
Further investigating the issue reveals the exact exception being thrown.
Lets go to prototype.js:683 and start looking around.
Bug tickets were filed for Chromium and Eclipse and it’s caused by certain application servers (WebSphere and WebLogic included) failing to deal with Content-Type sent by WebKit based browsers.
Debugging Maximo Birt prototype.js using chrome developer tools
A possible work around is to allow WebKit based browsers to send the correct content type without explicitly defining the Content-Type header.
Hot-replacing Maximo Birt prototype.js code lines using chrome developer tools
Users will also need to clear their browser cache to make sure that no residual old JS file is being used when accessing the report.