
Better Error Messaging from Maximo Web Service Response
- May 30, 2019
- Bob
- One Response
- May 30, 2019
- Bob
- One Response
You are ready to test drive your perfect web service that you just spent the last few minutes constructing in Maximo. A final comparison is performed on your test message to ensure that the structure of the XML is aligned with your object structure. You are satisfied with the message and it is placed in SOAPUI or your favorite XML test engine. The message is sent and the response you receive is:
Internal Error
In this example I am trying to add my labor code using an organization identifier that does not exist in my Maximo system. The response in no way helps me understand the problem however.
Internal Error? How “internal” should I look? Could the message possibly be vaguer? With a sigh it’s off to the logs in order to find more information. All the while hoping that the message hasn’t rolled off into a backup log.
Thankfully there is a way to configure WebSphere 8.5.X and newer to display the Maximo error code in the response message.
Log in to the WebSphere Administration Console and navigate to WebSphere Application Servers. Click on your application server.
On the right side under Server Infrastructure expand Java and Process Management and select Process Definition.
Select Java Virtual Machine.
Select Custom Properties.
Click New and enter the following information.
Name: webservices.unify.faults
Value: false
Click Apply or Ok. Save and restart the WebSphere Application Server. Note that all you have to do is navigate to WebSphere application servers and restart the server from there. You do not have to restart all WebSphere services or the Cell or Node.
After the application server has restarted retry your message in SOAPUI. You should see a Maximo error code along with a more helpful message.





1 Comment
How would you achieve the same result in a different J2EE App Server like Weblogic?
There seems to be no equivalent to webservices.unify.faults
Thank you.